Public report of banq/jivejdon, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 22 October 2026, 19:57 UTC · Survey ID cd_87a8f89c55a24f47bded41b134358c48

banq/jivejdon

Measured 22 October 2026, 19:49 UTC, at code version d75100d

Code coverage: not measuredTest distribution: not measured

Code coverage is not measured: Suite not runnable in-image and no committed report.

Test distribution is not measured: No automated tests.

CAI score 29out of 100 At risk No change since the last survey

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

Domain Modelling 100 Exemplary Architecture 87 Adequate Security and Compliance 72 Adequate Maturity 70 Strong Performance 62 Adequate Accessibility 32 Weak Code Health 23 Critical Production Readiness 17 Critical

A medium codebase: 45,872 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 17

Findings by how serious they are

120 critical 657 serious 99 minor

11 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 19:49 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 Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸

79of 83 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
863of 876 findings point to an exact file and line, so you can open each one in the code. The other 13 concern the repository as a whole, such as missing documentation.
83dimensions across 8 lenses, read from 45,872 lines of product code in 1 project.
Chapters

Executive summary

banq/jivejdon scores 29 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 17 and is rated Critical. Its Test Distribution dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 1 No tests found finding(s) in Test Distribution and to add a CI workflow that builds and runs the test suite on every push/PR, and if Production Readiness rose to 70, the score would rise from 29 to about 39.

120 findings are critical: 40 in Forms & labels, 40 in Text alternatives, 15 in Keyboard semantics, eight in Page structure, seven in Dependency Vulnerabilities, seven in Secrets (history), two in Static Analysis (SAST) and one in IaC & Container Security.

Watchdog couldn't measure 10 dimensions in this code, among them Dependency Hygiene, License Compliance and Internal API Consistency, so they are left out of the score. The product code is 45,872 lines, which would take an estimated 0.4 person-years, around €53,000, to rebuild.

Code Health 23 ⚠ Critical, capped by Type Safety, Cyclomatic Complexity, Dead Code, Structured logging and Nullable reference types Architecture 87 Adequate, capped by Project Cohesion Maturity 70 Strong Production Readiness 17 ⚠ Critical, capped by Test Distribution, Test Coverage, CI/CD gates and Security & performance tooling Security and Compliance 72 Adequate, capped by Secrets (history), Static Analysis (SAST) and Dependency Vulnerabilities Domain Modelling 100 ★ Exemplary Accessibility 32 Weak, capped by Text alternatives, Page structure and Keyboard semantics Performance 62 Adequate

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

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

If Production Readiness rose from 17 to 70, the lowest score rated Strong, the score would rise from 29 to about 39.

Code composition: what the lines of code are
Product code 99%Tests 1%
New since the last survey: 58 findings

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

  • Cognitive Complexity · RefererCaptchaAction.verifyAndRedirect (cognitive 16) src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java
  • Code Duplication · Duplicated block (6 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java
  • Code Duplication · Duplicated block (6 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java
  • Static Analysis (SAST) · REDACTED
  • Large Files · REDACTED: 9688 lines of code REDACTED
  • Large Files · REDACTED: 1472 lines of code REDACTED
  • Large Files · application/common/js/window.js: 1151 lines of code application/common/js/window.js
  • Large Files · application/common/ckeditor/plugins/bbcode/plugin.js: 639 lines of code application/common/ckeditor/plugins/bbcode/plugin.js
  • Large Files · application/common/ckeditor/plugins/base64image/dialogs/base64image.js: 444 lines of code application/common/ckeditor/plugins/base64image/dialogs/base64image.js
  • Exception handling · Swallowed exception (empty catch) application/common/login2.js
  • Exception handling · Swallowed exception (empty catch) application/common/form.js
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) application/common/ckeditor/plugins/base64image/dialogs/base64image.js
  • Exception handling · Swallowed exception (empty catch) application/common/ckeditor/plugins/bbcode/plugin.js
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) application/forum/js/form.js
  • Exception handling · Swallowed exception (empty catch) application/message/js/messageEdit.js
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/js/jdon.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/js/styles/style.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie8.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie8.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie8.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_iequirks.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_iequirks.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_iequirks.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor_gecko.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor_gecko.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor_gecko.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor_gecko.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor_gecko.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor_gecko.css
  • Visual & motion safety · Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor_gecko.css

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

Fixed since the last survey: 312 findings

These 312 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one. The first 100 are listed here.

  • License Compliance · Banned license: com.ocpsoft:ocpsoft-pretty-time
  • License Compliance · Banned license: mysql:mysql-connector-java
  • Static Analysis (SAST) · Medium: REDACTED src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/en-ca.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/en-gb.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/en.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/eo.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/es.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/et.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/eu.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/fa.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/fi.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/fo.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/fr-ca.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/fr.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/gl.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/gu.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/he.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/hi.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/hr.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/hu.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/id.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/is.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/it.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ja.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ka.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/km.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ko.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ku.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/lt.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/lv.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/mk.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/mn.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ms.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/nb.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/nl.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/no.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/pl.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/pt-br.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/pt.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ro.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ru.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/si.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/sk.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/sl.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/sq.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/sr-latn.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/sr.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/sv.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/th.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/tr.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ug.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/uk.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/vi.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/zh-cn.js
  • Dead Code · Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/zh.js
  • Dead Code · Dead file (~7 LoC) application/common/ckeditor/plugins/autosave/lang/de.js
  • Dead Code · Dead file (~7 LoC) application/common/ckeditor/plugins/autosave/lang/en.js
  • Dead Code · Dead file (~7 LoC) application/common/ckeditor/plugins/autosave/lang/zh-cn.js
  • Dead Code · Dead file (~5 LoC) application/common/ckeditor/lang/vi.js
  • Dead Code · Dead file (~5 LoC) application/common/ckeditor/plugins/imagebase/lang/en.js
  • Dead Code · Dead file (~0 LoC) application/admin/js/admin.js
  • Dead Code · Dead file (~0 LoC) application/common/ckeditor/plugins/dialog/dialogDefinition.js
  • Documentation (README) · README may be stale
  • Text alternatives · <img> without a text alternative application/thread/messageListBody.jsp
  • Forms & labels · <input> without a programmatic label application/admin/search/hotkeys.jsp
  • Forms & labels · <input> without a programmatic label application/admin/sitemap/urlList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTag.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTag.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTag.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTag.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTag.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTagList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTagList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTagList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTagList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/tag/threadTagList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/editAccount.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/editAccount.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/editAccount.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/userBanIPList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/userBanIPList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/userBanIPList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/userBanIPList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/userList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/userMessageList.jsp
  • Forms & labels · <input> without a programmatic label application/admin/user/userMessageList.jsp
  • Forms & labels · Link with no accessible name application/blog/header.jsp
  • Forms & labels · <input> without a programmatic label application/blog/header.jsp
  • Forms & labels · Custom control with no accessible name on <img> application/blog/header.jsp
  • Forms & labels · <button> with no accessible text REDACTED
  • Forms & labels · <input> without a programmatic label REDACTED
  • Forms & labels · <select> without a programmatic label REDACTED
  • Forms & labels · <select> without a programmatic label REDACTED
  • Forms & labels · Link with no accessible name REDACTED
  • Forms & labels · <button> with no accessible text REDACTED
  • Forms & labels · Link with no accessible name REDACTED
  • Forms & labels · <input> without a programmatic label application/common/ckeditor/index.html
  • Forms & labels · <textarea> without a programmatic label application/common/ckeditor/index.html
  • Forms & labels · Custom control with no accessible name on <div> application/common/js/window.js
Rebuild cost: about €53,000 · Estimate
Cost to rebuild€18,000 to €88,000, for 294 to 931 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemHigh, 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 29. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 45,872 lines of product code

How the estimate is made: Watchdog prices 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 No tests found finding(s) in Test Distribution.
Raises the score by about 11 points · Low effort · Test Distribution
2
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 4 points · Medium effort · CI/CD gates
3
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Raises the score by about 4 points · Medium effort · Security & performance tooling

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €53,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 17 (Critical). 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 No tests found finding(s) in Test Distribution. Of all the actions in this report, it raises the score most for the work it takes: about 11 points for low effort, because it clears the 1 Test Distribution findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.1 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 2,322 lines over the last 90 days, which is about 9,417 lines a year. At that pace, the extra work comes to an estimated 0.5 to 3.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: 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.

124 modules, with 438 dependencies between them. 3 loops run through 39 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 domain.model.util2 domain.model.message3 domain.model.realtime4 domain.model.shortmessage5 domain.model.message.output.beanutil6 infrastructure.dto7 util8 domain.model.message.upload9 infrastructure.repository.acccount10 infrastructure.repository.property11 spi.component.query12 domain.model.query13 infrastructure.repository.dao14 domain.model.message.output15 infrastructure.repository16 spi.component.shortmessage17 spi.component.subscription18 domain.model.subscription19 domain.model.property20 domain.command21 domain.model22 api.query23 domain.model.attachment24 api.property25 domain.model.account26 api.impl.upload27 api.util28 infrastructure.repository.builder29 presentation.form30 spi.component.mapreduce31 api.impl.shortmessage32 auth33 infrastructure34 infrastructure.repository.dao.sql35 api.impl.account36 api.impl.message37 infrastructure.repository.subscription38 api.impl.subscription39 infrastructure.repository.dao.filter40 spi.pubsub.subscriber
1 domain.model.util
2 domain.model.message2
3 domain.model.realtime111
4 domain.model.shortmessage2
5 domain.model.message.output.beanutil1
6 infrastructure.dto112211
7 util1
8 domain.model.message.upload222
9 infrastructure.repository.acccount216
10 infrastructure.repository.property1452
11 spi.component.query11111121
12 domain.model.query11
13 infrastructure.repository.dao1111112412
14 domain.model.message.output211
15 infrastructure.repository1115
16 spi.component.shortmessage1121
17 spi.component.subscription211111
18 domain.model.subscription121
19 domain.model.property1
20 domain.command33332
21 domain.model1111411454
22 api.query12
23 domain.model.attachment12
24 api.property1312
25 domain.model.account3131222
26 api.impl.upload11211122
27 api.util111
28 infrastructure.repository.builder114316105151
29 presentation.form21212513
30 spi.component.mapreduce12114421
31 api.impl.shortmessage211111
32 auth1112
33 infrastructure1114111
34 infrastructure.repository.dao.sql11111931131241621
35 api.impl.account933641
36 api.impl.message1111112411111
37 infrastructure.repository.subscription12131141
38 api.impl.subscription111111
39 infrastructure.repository.dao.filter11741312101
40 spi.pubsub.subscriber111311111
Uses a module listed above itPart of a loopThe module itself
1 domain.model.util2 domain.model.message3 domain.model.realtime4 domain.model.shortmessage5 domain.model.message.output.beanutil6 infrastructure.dto7 util8 domain.model.message.upload9 infrastructure.repository.acccount10 infrastructure.repository.property11 spi.component.query12 domain.model.query13 infrastructure.repository.dao14 domain.model.message.output15 infrastructure.repository16 spi.component.shortmessage17 spi.component.subscription18 domain.model.subscription19 domain.model.property20 domain.command21 domain.model22 api.query23 domain.model.attachment24 api.property25 domain.model.account26 api.impl.upload27 api.util28 infrastructure.repository.builder29 presentation.form30 spi.component.mapreduce31 api.impl.shortmessage32 auth33 infrastructure34 infrastructure.repository.dao.sql35 api.impl.account36 api.impl.message37 infrastructure.repository.subscription38 api.impl.subscription39 infrastructure.repository.dao.filter40 spi.pubsub.subscriberdomain.model.util1domain.model.message2domain.model.realtime3domain.model.shortmessage4domain.model.message.output.beanutil5infrastructure.dto6util7domain.model.message.upload8infrastructure.repository.acccount9infrastructure.repository.property10spi.component.query11domain.model.query12infrastructure.repository.dao13domain.model.message.output14infrastructure.repository15spi.component.shortmessage16spi.component.subscription17domain.model.subscription18domain.model.property19domain.command20domain.model21api.query22domain.model.attachment23api.property24domain.model.account25api.impl.upload26api.util27infrastructure.repository.builder28presentation.form29spi.component.mapreduce30api.impl.shortmessage31auth32infrastructure33infrastructure.repository.dao.sql34api.impl.account35api.impl.message36infrastructure.repository.subscription37api.impl.subscription38infrastructure.repository.dao.filter39spi.pubsub.subscriber402111211122111222216145211111121111111112412211111511212111111211333321111411454121213123131222112111221111143161051512121251312114421211111111211141111111193113124162193364111111124111111213114111111111741312101111311111+84 more modules (most-connected shown)

At a glance — Code Health · 23% · Critical · gated by R1, R2, R7, X4, X5 ·

The Good
D3 · .NET / C# God Classes 8.6 D4 · .NET / C# Code Duplication 8.5 D17 · .NET / C# Explicit Debt 9.9 IC1 · Repo Incompleteness & stubs 10.0 R10 · React / TS Code Duplication 9.0 R3 · React / TS Large Files 8.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0
The Bad
D1 · .NET / C# Cyclomatic Complexity 5.8 X27 · Repo Collection changed while being enumerated 6.2 X3 · Repo Exception handling 6.2
The Ugly
D2 · .NET / C# Cognitive Complexity 4.2 R1 · React / TS Type Safety 0.0 R2 · React / TS Cyclomatic Complexity 1.0 R7 · React / TS Dead Code 0.0 X4 · Repo Structured logging 3.9 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 87% · Adequate · gated by D26 ·

The Good
D6 · .NET / C# Cohesion (LCOM4) 9.9 D27 · .NET / C# Navigability 8.7 D35 · .NET / C# Change Coupling 10.0 AX10 · Repo Code composition 8.3 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.7 R9 · React / TS Circular Imports 10.0
The Ugly
D26 · .NET / C# Project Cohesion 0.0

At a glance — Maturity · 70% · Strong ·

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D19 · .NET / C# Documentation Quality 9.0 D21 · .NET / C# Naming Consistency 10.0 D34 · .NET / C# Knowledge Freshness 10.0 M1 · Repo Documentation (README) 7.3 M3 · Repo Folder & project structure 8.0 M4 · Repo Documentation accuracy 10.0
The Bad
M2 · Repo Architecture documentation 5.0
The Ugly
D20 · .NET / C# ADR Quality 0.0

At a glance — Readiness · 17% · Critical · gated by D9, R4, P1, P3 ·

The Good
D13 · .NET / C# REDACTED Scanning 10.0 P2 · Repo Observability 7.0 P6 · Repo Release Hygiene 8.0
The Bad
P4 · Repo Deployment & Rollback 5.0
The Ugly
P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 R4 · React / TS Test Coverage 0.0

At a glance — Security · 72% · Adequate · gated by D28, D29, D30 ·

The Good
D31 · .NET / C# IaC & Container Security 9.4 D32 · .NET / C# Data Compliance (PII/GDPR) 8.1 D43 · .NET / C# Malicious Dependencies 10.0 D44 · .NET / C# Platform End-of-Life 10.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0
The Ugly
D28 · .NET / C# Secrets (history) 3.0 D29 · .NET / C# Static Analysis (SAST) 2.5 D30 · .NET / C# Dependency Vulnerabilities 3.4 X24 · Repo Document value interpolated into markup unescaped 4.8

At a glance — Domain Modelling · 100% · Exemplary ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM10 · Repo One transaction, one aggregate 10.0 DM12 · Repo Ambient inputs in the domain 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0

At a glance — Accessibility · 32% · Weak · gated by AC1, AC3, AC4 ·

The Good
AC5 · Repo ARIA correctness 10.0
The Ugly
AC1 · Repo Text alternatives 3.3 AC2 · Repo Forms & labels 4.3 AC3 · Repo Page structure 3.1 AC4 · Repo Keyboard semantics 1.0 AC6 · Repo Visual & motion safety 4.9 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 62% · Adequate ·

The Bad
PF2 · Repo Allocation hygiene 6.2

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection24High / Critical
A03:2025 — Software Supply Chain Failures12High / Critical
A02:2025 — Security Misconfiguration10High / Critical
A07:2025 — Authentication Failures8High / Critical
A01:2025 — Broken Access Control2Medium

Roadmap

First, resolve the missing test finding in Test Distribution and establish a CI workflow that builds and runs the test suite on every push or pull request. Integrate security scanning using spotbugs or semgrep into this new pipeline to ensure security regressions fail the build immediately. Next, expand test coverage by adding tests for the currently unreached production modules to ensure they are exercised. Finally, improve type safety by adopting TypeScript for the frontend, starting with a typecheck step and prioritizing the highest-traffic modules for conversion.

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

Do thisHelpsEffortDimension
Resolve the 1 No tests found finding(s) in Test Distribution.+10.5 ptsLowTest Distribution
Add a CI workflow that builds and runs the test suite on every push/PR.+3.7 ptsMediumCI/CD gates
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+3.7 ptsMediumSecurity & performance tooling
Add tests that import the unreached modules (directly or through their public entry).+3.7 ptsMediumTest Coverage
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.+2.2 ptsMediumType Safety
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.+2.2 ptsMediumDead Code
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.+1.7 ptsMediumCyclomatic Complexity
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+1.7 ptsMediumKeyboard semantics

File quality

Per-file score 0–10 — a quality signature. Of 116 files carrying findings, judged against the Production bar: 3% slop · 52% mixed · 45% near-clean.

FileScoreBandWorst signal
REDACTED0.4SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED3.5SlopSecrets (history): REDACTED: REDACTED
REDACTED3.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java6.0MixedExplicit Debt: HackComment
src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java6.0MixedExplicit Debt: XxxComment
src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java6.3MixedCode Duplication: Duplicated block (20 lines × 2)
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.4MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.7MixedStatic Analysis (SAST): Medium: REDACTED
src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java6.7MixedExplicit Debt: TodoComment
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java7.0MixedCyclomatic Complexity: JavaCodeViewer.javaCodeFilter (cyclomatic 122)
application/common/js/calendar.js7.0MixedCyclomatic Complexity: calendar.Calendar.parseDate (cyclomatic 36)
application/common/ckeditor/plugins/base64image/dialogs/base64image.js7.0MixedCyclomatic Complexity: base64image.CKEDITOR.dialog.add("base64imageDialog").onShow (cyclomatic 31)

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 — 120

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 — 657

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 — 99

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

Could not be resolved — 11

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

Watchdog 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. 79 of 83 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 83 dimensions across the health lenses
D1D2D3D4D6D9D13D15D17D19D20D21D26D27D28D29D30D31D32D34D35D43D44AC1AC2AC3AC4AC5AC6AC7AX10AX3AX4AX5AX6DM1DM10DM12DM6DM8DM9IC1M1M2M3M4P1P2P3P4P6PF2R1R10R2R3R4R7R9S1X1X12X13X14X15X16X17X18X19X20X21X22X23X24X25X26X27X28X29X3X30X4X5

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

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

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16529-2642-7144-9ef4-4770a3b26452.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The test suite couldn't be built/run in-image and no coverage report is committed, so line coverage was not measured — and it is EXCLUDED from the score rather than scored on a LoC-ratio proxy. No coverage collector was found in your CI either, so there is no existing report to hand us. You can widen what we reach: optional: add a coverage collector to your test run and commit (or publish) its Cobertura/OpenCover/lcov output anywhere in the repo, or make the suite runnable in-image, and real coverage will be measured.
  • D12 Dependency Hygiene — not measured this run — Watchdog 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 46 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 3305 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 1 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D22 Internal API Consistency — not measured this run — Watchdog 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: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • AC1 Text alternatives — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 1 JSP template file(s) carrying 70 markup element(s) (e.g. application/social/contentfollower.jsp) — and the accessibility cards on this run were measured over the 193 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC1 Text alternatives — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 1 further occurrence(s) are not listed individually; the score already reflects all 41.
  • AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 1 JSP template file(s) carrying 70 markup element(s) (e.g. application/social/contentfollower.jsp) — and the accessibility cards on this run were measured over the 193 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC2 Forms & labels — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 84 further occurrence(s) are not listed individually; the score already reflects all 124.
  • AC3 Page structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 1 JSP template file(s) carrying 70 markup element(s) (e.g. application/social/contentfollower.jsp) — and the accessibility cards on this run were measured over the 193 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC3 Page structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 154 further occurrence(s) are not listed individually; the score already reflects all 194.
  • AC4 Keyboard semantics — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 1 JSP template file(s) carrying 70 markup element(s) (e.g. application/social/contentfollower.jsp) — and the accessibility cards on this run were measured over the 193 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC4 Keyboard semantics — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 9 further occurrence(s) are not listed individually; the score already reflects all 49.
  • AC5 ARIA correctness — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 1 JSP template file(s) carrying 70 markup element(s) (e.g. application/social/contentfollower.jsp) — and the accessibility cards on this run were measured over the 193 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC6 Visual & motion safety — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository renders user interface from a TEMPLATE LANGUAGE — 1 JSP template file(s) carrying 70 markup element(s) (e.g. application/social/contentfollower.jsp) — and the accessibility cards on this run were measured over the 193 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
  • AC6 Visual & motion safety — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 36 further occurrence(s) are not listed individually; the score already reflects all 76.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via Dockerfile (REDACTED). docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped.
  • C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog 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 and Scala source only, and this repository's Java 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.
  • R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 60 further occurrence(s) are not listed individually; the score already reflects all 100.
  • X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 226 further occurrence(s) are not listed individually; the score already reflects all 266.

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

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
  • AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
  • AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
  • AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
  • AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
  • AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
  • AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
  • 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.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity5.8 / 10Adequate✓ Tool-verified

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

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

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

92 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was JavaCodeViewer.javaCodeFilter at 122.

initialize (cyclomatic 30) · ×2REDACTED:8
setSize (cyclomatic 17) · ×2REDACTED:419
maximize (cyclomatic 16) · ×2REDACTED:588
JavaCodeViewer.javaCodeFilter (cyclomatic 122)src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:303
(anonymous) (cyclomatic 100)REDACTED:3973

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

What to do

  1. Bring the 4 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with JavaCodeViewer.javaCodeFilter (cyclomatic 122), (anonymous) (cyclomatic 100), _generateHTML (cyclomatic 91). — 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 4 together lifts Cyclomatic Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity4.2 / 10Weak✓ Tool-verified

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

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

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

135 method(s) exceeded the cognitive complexity threshold of 15; the worst was JavaCodeViewer.javaCodeFilter at 300.

initialize (cognitive 39) · ×2REDACTED:8
maximize (cognitive 25) · ×2REDACTED:588
_saveCookie (cognitive 23) · ×2REDACTED:720
FiltersUtils.getPropertyHTML (cognitive 19) · ×2src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:18
getPageSize (cognitive 19) · ×2REDACTED:1018

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

What to do

  1. Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with JavaCodeViewer.javaCodeFilter (cognitive 300), _generateHTML (cognitive 210), Emoticon.convertEmoticons (cognitive 179). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 4.2 to about 5.4/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
  2. Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

14 god class(es) detected.

TooManyMethods: JavaCodeViewer · ×8src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:31
FileTooLong: REDACTED · ×3REDACTED
FunctionTooLong: base64image.CKEDITOR.dialog.add("base64imageDialog") · ×2application/common/ckeditor/plugins/base64image/dialogs/base64image.js:5
ClassTooLong: MessageQueryDaoSqlsrc/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:44

What to do

  1. Resolve the 8 TooManyMethods finding(s) in God Classes — start with JavaCodeViewer.java, JavaCodeHighlighter.java, Account.java. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 3 FileTooLong finding(s) in God Classes — start with REDACTED, REDACTED, JavaCodeViewer.java. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 2 FunctionTooLong finding(s) in God Classes — start with base64image.js, plugin.js. — One of this dimension's main actionable groups (2 warning-level).
  4. Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication8.5 / 10Strong✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

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

141 duplicated block group(s) detected. A further 6 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (9 lines × 2) · ×9src/main/java/com/jdon/jivejdon/api/impl/account/OAuthAccountServiceImp.java:99
Duplicated block (10 lines × 2) · ×8REDACTED:49
Duplicated block (6 lines × 2) · ×8src/main/java/com/jdon/jivejdon/domain/model/subscription/SubscribedState.java:62
Duplicated block (11 lines × 2) · ×7src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:186
Duplicated block (8 lines × 2) · ×7src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:120

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

What to do

  1. Resolve the 9 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with MessageQueryDaoSql.java (2), OAuthAccountServiceImp.java, Emoticon.java. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 8 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with REDACTED, MessageDaoSql.java, MessageSearchProxy.java. — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 8 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with MessageQueryDaoSql.java (2), RefererCaptchaAction.java (2), SubscribedState.java. — One of this dimension's main actionable groups (8 warning-level).
  4. Stand up a CI pipeline, then gate Code Duplication in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

1 of 173 classes have LCOM4 above 3.

Low cohesion: UploadHelper (LCOM4 4)src/main/java/com/jdon/jivejdon/domain/model/message/upload/UploadHelper.java:25

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with UploadHelper.java. — One of this dimension's main actionable groups (1 warning-level).
  2. Stand up a CI pipeline, then gate Cohesion (LCOM4) in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D9 · Test Distribution0.0 / 10Critical✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

No test suite found.

No tests found

What to do

  1. Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).

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

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

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

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

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

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

27 deducted task-comment markers across 45872 LoC (0.1/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.

TodoComment · ×5src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:131
XxxComment · ×3src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:234
HackCommentsrc/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:706
TodoComment repeated across 14 filessrc/main/java/com/jdon/jivejdon/domain/model/realtime/NotificationLocator.java:65

What to do

  1. Resolve the 5 TodoComment finding(s) in Explicit Debt — start with ShortMessageServiceImp.java, MPageTag.java, ShortMessageFactory.java. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 3 XxxComment finding(s) in Explicit Debt — start with TextStyle.java (3). — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 1 HackComment finding(s) in Explicit Debt — start with JavaCodeHighlighter.java. — One of this dimension's main actionable groups (1 warning-level).
  4. Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D19 · Documentation QualityExemplary◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README is a clear, well-structured overview of Jivejdon (a chain notebook/blog with DDD/Event Sourcing/CQRS and powered by jdonframework) that describes its features, a canonical deployment link, and two runnable demos. It also documents the domain-centric architecture, a use case diagram, an aggregate model, and install instructions for Docker and manual setup of Tomcat/JAAS plus database configuration (MySQL). The four READMEs under application/common/ckeditor/* and doc/performanceTest/* each document their own directories and do not conflict with the root's scope. Architecture/Docs markdown files are present but not shown in this summary.

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

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

1 of 1 build units (Maven) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D27 · Navigability8.7 / 10Strong✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

78 % of calls cross a namespace and 26 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

What to do

  1. Improve Navigability — currently 8.7/10. — 78 % of calls cross a namespace and 26 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)3.0 / 10Weak✓ Tool-verified

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

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

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

7 finding(s): 0 critical, 7 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 7 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

D29 · Static Analysis (SAST)2.5 / 10Weak✓ Tool-verified

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

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

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

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

26 finding(s): 0 critical, 2 high, 18 medium, 6 low. semgrep hit a parse error in 1 file(s) — `application/common/ckeditor/ckeditor.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D30 · Dependency Vulnerabilities3.4 / 10Weak✓ Tool-verified

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

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

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

12 finding(s): 2 critical, 5 high, 5 medium, 0 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
  3. Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).

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

D31 · IaC & Container Security9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

10 finding(s): 0 critical, 1 high, 1 medium, 8 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified

What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.

Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.

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

2 finding(s): 0 critical, 0 high, 2 medium, 0 low.

REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked. Counted over 229 of the 549 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

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

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

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

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

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

Strongest change-coupling: ForumMessageQueryServiceImp.java↔MessageQueryDaoSql.java 55%

Change coupling: ForumMessageQueryServiceImp.java ↔ MessageQueryDaoSql.javasrc/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:1

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 46 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives3.3 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×40) — application/account/profileView.jsp:41, application/account/profileView.jsp:44, application/account/profileView.jsp:49, …

What to do

  • Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels4.3 / 10Weak✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×32) — application/account/IncludeAccountFields.jsp:98, application/account/IncludeAccountFields.jsp:102, application/account/IncludeAccountFields.jsp:108, …
  • This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×6) — application/account/newAccount.jsp:67, application/account/newAccount.jsp:75, application/account/newAccount.jsp:82, …
  • This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — application/account/newAccount.jsp:69, application/account/newAccount.jsp:90

What to do

  • Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure3.1 / 10Weak✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×7) — application/503.jsp:6, application/account/login.jsp:0, application/account/login_error.jsp:0, …
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×7) — application/503.jsp:6, application/account/login.jsp:0, application/account/login_error.jsp:0, …
  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×25) — application/account/fwd.jsp:29, application/account/login.jsp:33, application/account/login.jsp:52, …
  • A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — application/account/protected/upload/result.jsp:0

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM). (×14) — application/account/login.jsp:60, application/account/login.jsp:74, application/account/login.jsp:77, …
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×7) — application/blog/header.jsp:149, application/common/js/window.js:375, application/common/js/window.js:376, …
  • An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. (×5) — application/blog/header.jsp:279, application/blog/header.jsp:304, application/common/bookmark.jsp:72, …
  • An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×6) — REDACTED:131, REDACTED:6251, REDACTED:8354, …
  • The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×8) — application/forum/forumList.jsp:67, application/forum/forumList.jsp:132, application/forum/maxPopThreadlist.jsp:170, …

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety4.9 / 10Weak✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `.btn-warning:hover,.btn-warning:focus,.btn-warning:active,.btn-warning.active,.open .dropdown-toggle.btn-warning` sets color: #fff on background-color: #ed9c28 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — application/js/jdon.css:2
  • `tr:hover, tr.odd:hover` sets color: #ffffff on background-color: #3d80df — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — application/common/style/template/classic.css:30, application/common/style/template/itunes.css:25
  • `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `.dropdown-menu>.active>a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `.open>a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `.btn-group>.btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `.navbar-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `.carousel-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — application/js/jdon.css:2
  • `footer .footer-1 input[type="text"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — application/js/jdon.css:2, application/common/js/styles/style.css:912
  • `.cke_hc .cke_dialog_footer` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — application/common/ckeditor/skins/moono-lisa/dialog.css:5, application/common/ckeditor/skins/moono-lisa/dialog_ie.css:5, application/common/ckeditor/skins/moono-lisa/dialog_ie8.css:5, …
  • `.cke_dialog a.cke_btn_over` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — application/common/ckeditor/skins/moono-lisa/dialog.css:5, application/common/ckeditor/skins/moono-lisa/dialog_ie.css:5, application/common/ckeditor/skins/moono-lisa/dialog_ie8.css:5, …
  • `.cke_dialog_contents_body .cke_tpl_list a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — application/common/ckeditor/skins/moono-lisa/dialog.css:5, application/common/ckeditor/skins/moono-lisa/dialog_ie.css:5, application/common/ckeditor/skins/moono-lisa/dialog_ie8.css:5, …
  • `.cke_wysiwyg_div` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — application/common/ckeditor/skins/moono-lisa/editor.css:5, application/common/ckeditor/skins/moono-lisa/editor_gecko.css:5
  • `.cke_panel_block:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — application/common/ckeditor/skins/moono-lisa/editor.css:5, application/common/ckeditor/skins/moono-lisa/editor_gecko.css:5
  • `a.cke_button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — application/common/ckeditor/skins/moono-lisa/editor.css:5, application/common/ckeditor/skins/moono-lisa/editor_gecko.css:5
  • `.cke_menubutton_disabled:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — application/common/ckeditor/skins/moono-lisa/editor.css:5, application/common/ckeditor/skins/moono-lisa/editor_gecko.css:5
  • `.cke_menubutton_disabled:hover .cke_menubutton_icon` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — application/common/ckeditor/skins/moono-lisa/editor.css:5, application/common/ckeditor/skins/moono-lisa/editor_gecko.css:5
  • `.cke_menuitem .cke_menubutton_on` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — application/common/ckeditor/skins/moono-lisa/editor.css:5, application/common/ckeditor/skins/moono-lisa/editor_gecko.css:5
  • `span.cke_path_empty` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — application/common/ckeditor/skins/moono-lisa/editor.css:5, application/common/ckeditor/skins/moono-lisa/editor_gecko.css:5

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

  • No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 193 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

  • Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX10 · Code composition8.3 / 10Strong✓ Tool-verified

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

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

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

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

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

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

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

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

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

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

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.

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

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

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

  • `AccountService` declares 21 abstract methods: `checkUser`, `createAccount`, `deleteAccount`, `deletePasswordassit`, `forgetPasswd`, `getAccount`, `getAccountByName`, `getAccountByNameLike`, `getAccounts`, `getLoginAccountByName`, `getPasswordassit`, `getUserpropertys`, `getloginAccount`, `initAccount`, `insertPasswordassit`, `saveUserpropertys`, `update`, `updateAccount`, `updateAccountAttachment`, `updateAccountEmailValidate`, `updatePasswordassit`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/jdon/jivejdon/api/account/AccountService.java:29
  • `ForumMessageQueryService` declares 17 abstract methods under just 14 distinct name(s): `getDigThreads`, `getHotThreads`, `getMesageListByUser`, `getMessage`, `getMessages`, `getMessages`, `getRecursiveMessages`, `getThread`, `getThreadListByUser`, `getThreadModifiedDate`, `getThreadName`, `getThreads`, `getThreads`, `getThreads`, `getThreadsPrevNext`, `searchMessages`, `searchThreads`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/main/java/com/jdon/jivejdon/api/query/ForumMessageQueryService.java:11
  • `ShortMessageService` declares 17 abstract methods: `checkReceiveShortMessages`, `deleInDraftMessage`, `deleteShortMessage`, `deleteUserAllShortMessage`, `deleteUserRecAllShortMessage`, `getFromShortMessage`, `getReceiveShortMessages`, `getSaveShortMessages`, `getSendShortMessages`, `getShortMessages`, `getToShortMessage`, `initShortMessage`, `saveInDraftMessage`, `saveShortMessage`, `sendInDraftMessage`, `sendShortMessage`, `updateShortMessage`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/jdon/jivejdon/api/shortmessage/ShortMessageService.java:38
  • `MessageDao` declares 18 abstract methods: `createMessage`, `createMessageReply`, `createThread`, `delReBlog`, `deleteMessage`, `deleteThread`, `getAnemicMessage`, `getMessageVOCore`, `getReBlogByFrom`, `getReBlogByTo`, `getThreadCore`, `getThreadRootMessageId`, `saveReBlog`, `updateForum`, `updateMessage`, `updateMovingForum`, `updateThread`, `updateThreadName`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/MessageDao.java:30
  • `MessageQueryDao` declares 23 abstract methods: `find`, `findThread`, `findThreadsAllCount`, `getDigThreadIDs`, `getForumLatestPostMessageId`, `getForumLatestThreadIds`, `getForumMessageCount`, `getHotThreadIDs`, `getLatestPostMessageId`, `getMesageListByUser`, `getMessageCount`, `getMessageCountOfUser`, `getMessages`, `getMessages`, `getThreadListByUser`, `getThreadModifiedDate`, `getThreadName`, `getThreads`, `getThreads`, `getThreads`, `getThreads`, `getThreadsPrevNext`, `getTreeModel`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/MessageQueryDao.java:33
  • `TagDao` declares 17 abstract methods under just 15 distinct name(s): `addThreadTag`, `checkThreadTagRelation`, `createTag`, `createThreadToken`, `delThreadTag`, `delThreadTag`, `delThreadToken`, `deleteTag`, `getTaggedThread`, `getTaggedThread`, `getThreadTag`, `getThreadTagByTitle`, `getThreadTagIDs`, `getThreadTags`, `getThreadToken`, `searchTitle`, `updateTag`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/TagDao.java:25

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
  • Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.

Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.

DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

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

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

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

M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

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.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

  • Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.

What to do

  • Group tests in the folder your build system expects (tests/, test/, spec/, or your module's test source set) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

P1 · CI/CD gates0.0 / 10Critical✓ 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.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.

What to do

  • Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

What to do

  • Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified

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

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

  • The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
PF2 · Allocation hygiene6.2 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.

Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.

What to do

  • Raise allocation-aware density on the hot paths — currently 18 use(s) across 54,395 production line(s) (~0.3/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
  • Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
R1 · Type Safety0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 0 typed · 101 plain JS — the untyped files are application/admin/js/admin.js, REDACTED, application/common/ckeditor/build-config.js, application/common/ckeditor/config.js, application/common/ckeditor/lang/vi.js, application/common/ckeditor/plugins/autogrow/plugin.js (+95 more).

What to do

  • Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication9.0 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • application/common/js/window.js:2 · REDACTED:3 — these 2 files are line-for-line copies of one another — 1081 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — application/common/js/window.js:2
  • REDACTED:1157 · application/common/js/window_effects.js:1 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — REDACTED:1157
  • REDACTED:1024 · REDACTED:3663 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1024
  • application/common/js/calendar-setup.js:1 · application/common/js/calendar.js:55 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — application/common/js/calendar-setup.js:1
  • application/common/js/calendar-zh.js:2 · application/common/js/calendar.js:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — application/common/js/calendar-zh.js:2
  • application/common/form.js:54 · application/forum/js/form.js:159 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — application/common/form.js:54
  • REDACTED:6410 · REDACTED:6437 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:6410
  • REDACTED:9496 · REDACTED:9521 — 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. — REDACTED:9496
  • REDACTED:865 · REDACTED:3039 — 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. — REDACTED:865
  • REDACTED:1133 · REDACTED:3766 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1133
  • application/common/form.js:11 · application/common/messageList12.js:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — application/common/form.js:11
  • REDACTED:4603 · REDACTED:4886 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:4603
  • REDACTED:7232 · REDACTED:7257 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:7232
  • application/common/js/pagination.js:55 · application/forum/js/threadList.js:3 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — application/common/js/pagination.js:55
  • REDACTED:1198 · REDACTED:3828 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1198
  • REDACTED:2739 · REDACTED:2843 — 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. — REDACTED:2739
  • REDACTED:4673 · REDACTED:5181 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:4673
  • REDACTED:4715 · REDACTED:4754 · REDACTED:4844 · REDACTED:4928 · +2 more site(s) not listed — all 6 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:4715
  • REDACTED:4481 · REDACTED:4492 · REDACTED:4504 — 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. — REDACTED:4481
  • REDACTED:7210 · REDACTED:7232 · REDACTED:7257 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:7210
  • REDACTED:10316 · REDACTED:10370 · REDACTED:10384 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:10316
  • REDACTED:10372 · REDACTED:10386 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:10372
  • REDACTED:4826 · REDACTED:4932 · REDACTED:4972 · REDACTED:5223 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:4826
  • REDACTED:7247 · REDACTED:7272 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:7247
  • REDACTED:6606 · REDACTED:6614 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:6606
  • REDACTED:1505 · REDACTED:1518 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1505
  • REDACTED:1646 · REDACTED:1658 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1646
  • REDACTED:4630 · REDACTED:4736 · REDACTED:5158 — 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. — REDACTED:4630
  • REDACTED:7062 · REDACTED:7146 — 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. — REDACTED:7062
  • REDACTED:10571 · REDACTED:10578 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:10571
  • REDACTED:11138 · REDACTED:11180 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:11138
  • REDACTED:1627 · REDACTED:1633 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1627
  • REDACTED:3419 · REDACTED:3467 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:3419
  • REDACTED:3921 · REDACTED:3937 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:3921
  • REDACTED:4650 · REDACTED:4665 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:4650
  • REDACTED:5077 · REDACTED:5089 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:5077
  • REDACTED:7423 · REDACTED:7447 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:7423
  • REDACTED:10597 · REDACTED:10603 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:10597

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity1.0 / 10Critical✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • _generateHTML has cyclomatic complexity 91 and cognitive complexity 210; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8313
  • _doKeyDown has cyclomatic complexity 45 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:7392
  • drag has cyclomatic complexity 44 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1485
  • parseDate has cyclomatic complexity 41 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:7854
  • parseDate has cyclomatic complexity 36 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — application/common/js/calendar.js:4
  • _keyEvent has cyclomatic complexity 35 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — application/common/js/calendar.js:4
  • _generatePosition has cyclomatic complexity 32 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1161
  • _mouseDrag has cyclomatic complexity 32 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:3129
  • _clear has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:3870
  • onShow has cyclomatic complexity 31 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — application/common/ckeditor/plugins/base64image/dialogs/base64image.js:274
  • _generatePosition has cyclomatic complexity 30 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:3794
  • initialize has cyclomatic complexity 29 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. (×2) — application/common/js/window.js:7, REDACTED:8
  • _respectSize has cyclomatic complexity 29 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:2240
  • intersect has cyclomatic complexity 29 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1709
  • _tabify has cyclomatic complexity 28 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:10706
  • _generateMonthYearHeader has cyclomatic complexity 27 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8481
  • formatDate has cyclomatic complexity 27 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:8036
  • (anonymous) has cyclomatic complexity 27 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:4619
  • _showDatepicker has cyclomatic complexity 27 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:7503

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files8.0 / 10Strong✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • REDACTED has 9688 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 1472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • application/common/js/window.js has 1151 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — application/common/js/window.js:1
  • application/common/ckeditor/plugins/bbcode/plugin.js has 639 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — application/common/ckeditor/plugins/bbcode/plugin.js:1
  • application/common/ckeditor/plugins/base64image/dialogs/base64image.js has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — application/common/ckeditor/plugins/base64image/dialogs/base64image.js:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage0.0 / 10Critical✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 0% of 101 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R7 · Dead Code0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 2 application, 0 tooling and 0 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
  • no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×39) — REDACTED, REDACTED, application/common/js/window.js, …

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `https://ssl.captcha.qq.com/TCaptcha.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 15 such include(s) across the repository's markup. — application/account/newAccount.jsp:36

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

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

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

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

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

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

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

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

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

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

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

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

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

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

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

X24 · Document value interpolated into markup unescaped4.8 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `date` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — application/common/js/calendar-setup.js:85
  • `$` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — application/common/js/calendar.js:4
  • `this.getId()` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — application/common/js/window.js:181, application/common/js/window.js:206, REDACTED:182, …
  • `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — application/common/js/window.js:184, REDACTED:185
  • `className` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×4) — application/common/js/window.js:376, application/common/js/window.js:377, REDACTED:377, …
  • `id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — application/common/js/window.js:380, REDACTED:381
  • `element` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — application/common/js/window.js:652, REDACTED:653
  • `parameters.className` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — application/common/js/window.js:925, REDACTED:926
  • `this` is text this program did not author, and it is written into a script or style context through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. — REDACTED:1
  • `xhr.responseText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — application/common/messageList12.js:6
  • `"有"+attcount+"个附件:"+insimag` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — application/forum/js/form.js:65

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated6.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen.

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

  • `subscriptionActions` is enumerated directly, and line 67 calls `subscriptionActions.remove(…)` inside the loop body — a structural change to a `ArrayList`. The loop's hidden iterator is fail-fast, so its next `next()` throws `ConcurrentModificationException`: every pass that reaches this call ends the loop by exception instead of by running out of elements, and the remaining elements are never seen. — src/main/java/com/jdon/jivejdon/spi/component/subscription/SubscriptionActionHolder.java:65

What to do

  • Each finding names the two spans that cannot both stand — the enhanced `for` source, and the call inside the body that structurally changes that same collection. Confirm from those two, then pick one: remove through the iterator itself (`Iterator<T> it = c.iterator(); … it.remove();`) or replace the loop with `c.removeIf(…)`; iterate a copy (`for (T x : new ArrayList<>(c))`); collect what needs changing and apply it after the loop; or — where the loop was only ever meant to act on the first match — `break` immediately after the mutation, which is the one shape that is already safe.
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.

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.

X3 · Exception handling6.2 / 10Adequate✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×31) — application/common/login2.js:5, application/common/form.js:10, REDACTED:342, …
  • `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×7) — src/main/java/com/jdon/jivejdon/domain/model/account/AccountState.java:122, src/main/java/com/jdon/jivejdon/domain/model/account/AccountState.java:130, src/main/java/com/jdon/jivejdon/infrastructure/repository/builder/ThreadDirector.java:74, …

What to do

  • Swallowed exception (empty catch)
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.

X4 · Structured logging3.9 / 10Weak✓ Tool-verified

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.

  • `error` at line 84 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/ForumServiceImp.java:84
  • `error` at line 157 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageServiceImpl.java:157
  • `error` at line 207 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageServiceImpl.java:207
  • `debug` at line 67 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:67
  • `error` at line 70 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:70
  • `debug` at line 77 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:77
  • `debug` at line 253 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:253
  • `debug` at line 262 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:262
  • `debug` at line 268 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:268
  • `error` at line 272 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:272
  • `debug` at line 284 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:284
  • `debug` at line 289 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:289
  • `debug` at line 191 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:191
  • `error` at line 232 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:232
  • `error` at line 251 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:251
  • `error` at line 90 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/subscription/SubscriptionServiceImp.java:90
  • `error` at line 140 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/subscription/SubscriptionServiceImp.java:140
  • `error` at line 143 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/subscription/SubscriptionServiceImp.java:143
  • `debug` at line 54 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/upload/UploadServiceShell.java:54
  • `error` at line 81 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/upload/UploadServiceShell.java:81
  • `error` at line 114 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/upload/UploadServiceShell.java:114
  • `debug` at line 166 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/upload/UploadServiceShell.java:166
  • `error` at line 97 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/impl/upload/UploadInfoVOServiceImp.java:97
  • `debug` at line 66 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/util/SessionContextUtil.java:66
  • `debug` at line 70 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/util/SessionContextUtil.java:70
  • `debug` at line 84 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/util/SessionContextUtil.java:84
  • `debug` at line 113 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/api/util/SessionContextUtil.java:113
  • `debug` at line 74 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/auth/ResourceAuthorization.java:74
  • `debug` at line 97 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/auth/PermissionInterceptor.java:97
  • `error` at line 105 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/auth/CUDInputInterceptor.java:105
  • `error` at line 158 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/RootMessage.java:158
  • `error` at line 172 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/RootMessage.java:172
  • `error` at line 167 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/ForumThread.java:167
  • `error` at line 198 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/ForumThread.java:198
  • `error` at line 255 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/ForumThread.java:255
  • `error` at line 289 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/ForumThread.java:289
  • `error` at line 152 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/ForumMessage.java:152
  • `error` at line 240 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/ForumMessage.java:240
  • `error` at line 270 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/ForumMessage.java:270
  • `error` at line 432 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/com/jdon/jivejdon/domain/model/ForumMessage.java:432

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

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

  • 0/114 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only
AC7 · A11y enforcementenforcement — no page criterionEnforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

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

LensScoreRatingImpact
Code Health23%Critical — gated by R1, R2, R7, X4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture87%Adequate — gated by D26Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity70%StrongSolid.
Readiness17%Critical — gated by D9, R4, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security72%Adequate — gated by D28, D29, D30Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling100%ExemplaryStrongest area.
Accessibility32%Weak — gated by AC1, AC3, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance62%AdequateAcceptable, with room to improve.
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.

  • X10 Duplicated predicate — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 9 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for

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

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 51 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • 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 JavaScript 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. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release. Install the buildx component to build images with BuildKit: https://docs.docker.com/go/bui…; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D10 Test Quality — ~264 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
  • 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 46 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D14 License Compliance — Not scored — this repository's 46 declared JVM dependency coordinate(s) were read from its 1 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 46 of them (HTTP 429 Too Many Requests from https://repo1.maven.org/maven2/org/jdon/jdonframework/6.9/jdonframework-6.9.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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+ projects each declaring an entity of their own. 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 — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • 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.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • 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.
  • D5 Coupling — Not applicable — this Maven 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
  • D8 Code Coverage — Coverage not measured
  • DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
  • DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
  • DM3 Integration-event coupling — no integration events detected — coupling check not applicable
  • DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
  • DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
  • DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
  • PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
  • R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
  • X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 120 finding(s)
AC1 · Text alternatives · <img> without a text alternative · ×40
  • <img> without a text alternative application/account/profileView.jsp:41 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/account/profileView.jsp:44 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/account/profileView.jsp:49 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/account/protected/upload/uploadUserFace.jsp:48 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/admin/forum/imageList.jsp:62 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/admin/tabs.jsp:28 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/admin/tabs.jsp:29 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/admin/tabs.jsp:30 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/admin/tabs.jsp:40 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/admin/tabs.jsp:45 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/blog/header.jsp:149 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/blog/header.jsp:204 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/blog/header.jsp:207 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/blog/header.jsp:213 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative REDACTED:7096 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative REDACTED:7099 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/message/upload/show.jsp:22 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/message/upload/upload.jsp:65 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/query/approvedThreadList.jsp:91 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/query/approvedThreadList3.jsp:42 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/query/authorList.jsp:35 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/query/authorList.jsp:38 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/query/authorList.jsp:42 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/query/others/newdiglist.jsp:21 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative application/query/others/st.jsp:53 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • + 15 more in this group — see findings.md.
AC2 · Forms & labels · <input> without a programmatic label · ×32
  • <input> without a programmatic label application/account/IncludeAccountFields.jsp:98 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/IncludeAccountFields.jsp:102 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/IncludeAccountFields.jsp:108 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/IncludeAccountFields.jsp:112 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/IncludeAccountFields.jsp:129 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/login.jsp:60 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/login.jsp:66 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/login.jsp:74 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/newAccount.jsp:69 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label application/account/newAccount.jsp:77 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/newAccount.jsp:84 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/newAccount.jsp:90 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label.
  • <input> without a programmatic label application/account/newAccount.jsp:99 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/newAccount.jsp:109 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/protected/profile.jsp:40 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/protected/profile.jsp:43 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/protected/sub/subAccountList.jsp:70 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/protected/sub/subForumList.jsp:69 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/protected/sub/subTagList.jsp:72 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/account/protected/sub/subThreadList.jsp:68 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/admin/cachekeys.jsp:34 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/admin/filters/filters.jsp:212 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/admin/filters/filters.jsp:216 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/admin/filters/filters.jsp:220 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label application/admin/filters/filters.jsp:255 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • + 7 more in this group — see findings.md.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×8
  • Clickable element isn't keyboard-operable application/forum/forumList.jsp:67 — The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable application/forum/forumList.jsp:132 — The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable application/forum/maxPopThreadlist.jsp:170 — The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable application/forum/randomThreadList.jsp:93 — The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable application/forum/threadDigSortedList.jsp:168 — The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable application/forum/threadList.jsp:257 — The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable application/message/randomThreadList.jsp:142 — The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable application/query/approvedThreadListOthers.jsp:167 — The repo's own CSS styles .linkblock with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
AC3 · Page structure · <html> without a lang · ×7
  • <html> without a lang application/503.jsp:6 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang application/account/login.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang application/account/login_error.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang application/account/protected/EditAccountForm.jsp:6 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang application/account/protected/onlineInfo.jsp:10 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang application/account/protected/upload/result.jsp — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang application/account/protected/upload/uploadUserFace.jsp:18 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D28 · Secrets (history) · REDACTED · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <label> that labels no control · ×6
  • <label> that labels no control application/account/newAccount.jsp:67 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control application/account/newAccount.jsp:75 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control application/account/newAccount.jsp:82 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control application/account/newAccount.jsp:88 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control application/account/newAccount.jsp:97 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
  • <label> that labels no control application/account/newAccount.jsp:107 — This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×6
  • Click handler on a non-interactive <div> application/common/js/window.js:375 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> application/common/js/window.js:376 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> application/common/js/window.js:377 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> REDACTED:376 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> REDACTED:377 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> REDACTED:378 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D30 · Dependency Vulnerabilities · High CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <select> without a programmatic label · ×1
  • <select> without a programmatic label application/admin/filters/filters.jsp:199 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels · <textarea> without a programmatic label · ×1
  • <textarea> without a programmatic label application/admin/filters/filters.jsp:224 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · Document without a <title> · ×1
  • Document without a <title> application/account/protected/upload/result.jsp — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×1
  • Click handler on a non-interactive <img> application/blog/header.jsp:149 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D31 · IaC & Container Security · High IaC · ×1
  • REDACTED
Serious — 657 finding(s)
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×37
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.dropdown-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.dropdown-menu>.active>a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.open>a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.btn-group>.btn:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.btn-group.open .dropdown-toggle` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.navbar-toggle:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.modal` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.modal-content` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `.carousel-control:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/js/jdon.css:2 — `footer .footer-1 input[type="text"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/js/styles/style.css:912 — `footer .footer-1 input[type="text"]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog.css:5 — `.cke_hc .cke_dialog_footer` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog.css:5 — `.cke_dialog a.cke_btn_over` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog.css:5 — `.cke_dialog_contents_body .cke_tpl_list a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie.css:5 — `.cke_hc .cke_dialog_footer` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie.css:5 — `.cke_dialog a.cke_btn_over` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie.css:5 — `.cke_dialog_contents_body .cke_tpl_list a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie8.css:5 — `.cke_hc .cke_dialog_footer` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie8.css:5 — `.cke_dialog a.cke_btn_over` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_ie8.css:5 — `.cke_dialog_contents_body .cke_tpl_list a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_iequirks.css:5 — `.cke_hc .cke_dialog_footer` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_iequirks.css:5 — `.cke_dialog a.cke_btn_over` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/dialog_iequirks.css:5 — `.cke_dialog_contents_body .cke_tpl_list a:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css:5 — `.cke_wysiwyg_div` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • Focus outline removed in CSS without a :focus replacement application/common/ckeditor/skins/moono-lisa/editor.css:5 — `.cke_panel_block:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
  • + 12 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×31
  • Swallowed exception (empty catch) application/common/login2.js:5 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) application/common/form.js:10 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:342 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:356 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:8197 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:11252 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:11266 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:66 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) application/common/ckeditor/plugins/bbcode/plugin.js:667 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:1 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) application/forum/js/form.js:10 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) application/message/js/messageEdit.js:60 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/api/impl/account/AccountServiceShell.java:127 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/api/util/JtaTransactionUtil.java:49 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/auth/ResourceAuthorization.java:64 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/auth/jaas/DefaultRolesProvider.java:74 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/domain/model/ForumThread.java:225 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/domain/model/account/AuditTimeline.java:25 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/domain/model/account/AccountVO.java:52 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java:102 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java:137 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java:160 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:116 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagHotList2Action.java:77 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadDigSortedListAction.java:59 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • + 6 more in this group — see findings.md.
AC3 · Page structure · Data table has no header cells · ×25
  • Data table has no header cells application/account/fwd.jsp:29 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/login.jsp:33 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/login.jsp:52 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/login.jsp:56 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/login.jsp:63 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/login_error.jsp:38 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/profileView.jsp:27 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/profileView.jsp:33 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/profileView.jsp:60 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/profileView.jsp:62 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/onlineInfo.jsp:23 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/profile.jsp:13 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/profile.jsp:16 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/profile.jsp:37 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/sub/subAccountList.jsp:37 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/sub/subAccountList.jsp:97 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/sub/subForumList.jsp:37 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/sub/subForumList.jsp:94 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/sub/subTagList.jsp:38 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/sub/subTagList.jsp:107 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/sub/subThreadList.jsp:38 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/account/protected/sub/subThreadList.jsp:92 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/admin/cachekeys.jsp:38 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/admin/cachekeys.jsp:42 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
  • Data table has no header cells application/admin/cachekeys.jsp:64 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×21
  • Untrusted text written into markup unescaped application/common/js/calendar-setup.js:85 — `date` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/calendar.js:4 — `$` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/window.js:181 — `this.getId()` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/window.js:184 — `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/window.js:206 — `this.getId()` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/window.js:376 — `className` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/window.js:377 — `className` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/window.js:380 — `id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/window.js:652 — `element` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/js/window.js:925 — `parameters.className` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:1 — `this` is text this program did not author, and it is written into a script or style context through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
  • Untrusted text written into markup unescaped REDACTED:182 — `this.getId()` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:185 — `html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:207 — `this.getId()` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:377 — `className` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:378 — `className` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:381 — `id` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:653 — `element` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped REDACTED:926 — `parameters.className` is text this program did not author, and it is written into a quoted attribute value through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/common/messageList12.js:6 — `xhr.responseText` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
  • Untrusted text written into markup unescaped application/forum/js/form.js:65 — `"有"+attcount+"个附件:"+insimag` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
R7 · Dead Code · Dead file (~12 LoC) · ×13
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/af.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ar.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/bg.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/bn.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/bs.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/ca.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/cs.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/cy.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/da.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/de-ch.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/de.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/el.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~12 LoC) application/common/ckeditor/plugins/base64image/lang/en-au.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×9
  • Duplicated block (9 lines × 2) src/main/java/com/jdon/jivejdon/api/impl/account/OAuthAccountServiceImp.java:99 — src/main/java/com/jdon/jivejdon/api/impl/account/OAuthAccountServiceImp.java:99-107 | src/main/java/com/jdon/jivejdon/api/impl/account/OAuthAccountServiceImp.java:228-236 — 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/java/com/jdon/jivejdon/domain/model/message/output/emotion/Emoticon.java:390 — src/main/java/com/jdon/jivejdon/domain/model/message/output/emotion/Emoticon.java:390-398 | src/main/java/com/jdon/jivejdon/domain/model/message/output/emotion/Emoticon.java:400-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:269 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:269-277 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageUtilSQL.java:39-47 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:269` 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 (9 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:620 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:620-628 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:641-649 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:620` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:629` calls `parseLong` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:650` 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 (9 lines × 2) REDACTED:35 — REDACTED:35-43 | REDACTED:41-49 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `REDACTED:40` calls `preventClientCache` and `REDACTED:34` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) src/main/java/com/jdon/jivejdon/presentation/filter/MessageEditAuthFilter.java:35 — src/main/java/com/jdon/jivejdon/presentation/filter/MessageEditAuthFilter.java:35-43 | src/main/java/com/jdon/jivejdon/presentation/filter/ThreadEditAuthFilter.java:29-37 — 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/com/jdon/jivejdon/presentation/filter/MessageEditAuthFilter.java:35` 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 (9 lines × 2) src/main/java/com/jdon/jivejdon/presentation/servlet/RegisterCodeAction.java:122 — src/main/java/com/jdon/jivejdon/presentation/servlet/RegisterCodeAction.java:122-130 | src/main/java/com/jdon/jivejdon/presentation/servlet/VerifySpammerAction.java:35-44 — 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/com/jdon/jivejdon/presentation/servlet/RegisterCodeAction.java:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/presentation/servlet/RegisterCodeAction.java:130` calls `sendError`, `logError` and `src/main/java/com/jdon/jivejdon/presentation/servlet/VerifySpammerAction.java:44` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/blog/UserFollowingThreadListAction.java:56 — src/main/java/com/jdon/jivejdon/presentation/action/blog/UserFollowingThreadListAction.java:56-64 | src/main/java/com/jdon/jivejdon/presentation/action/blog/UserThreadListAction.java:54-62 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/action/blog/UserFollowingThreadListAction.java` and `src/main/java/com/jdon/jivejdon/presentation/action/blog/UserThreadListAction.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. 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 (9 lines × 2) src/main/java/com/jdon/jivejdon/api/impl/ForumServiceImp.java:120 — src/main/java/com/jdon/jivejdon/api/impl/ForumServiceImp.java:120-128 | src/main/java/com/jdon/jivejdon/api/impl/upload/UploadInfoVOServiceImp.java:73-81 — 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. 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.
D3 · God Classes · TooManyMethods · ×8
  • TooManyMethods: JavaCodeViewer src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:31 — TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: JavaCodeHighlighter src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:30 — TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Account src/main/java/com/jdon/jivejdon/domain/model/account/Account.java:27 — TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ForumMessage src/main/java/com/jdon/jivejdon/domain/model/ForumMessage.java:66 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ForumThread src/main/java/com/jdon/jivejdon/domain/model/ForumThread.java:61 — TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MessageForm src/main/java/com/jdon/jivejdon/presentation/form/MessageForm.java:43 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AnemicMessageDTO src/main/java/com/jdon/jivejdon/infrastructure/dto/AnemicMessageDTO.java:16 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ToolsUtil REDACTED:43 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×8
  • Duplicated block (10 lines × 2) REDACTED:49 — REDACTED:49-58 | REDACTED:228-237 — 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 `REDACTED:49` 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 (10 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:365 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:365-374 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:384-393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:365` 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 (10 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java:82 — src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java:82-91 | src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java:116-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java: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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java:127` calls `Term`, `toString`, `getMessageId` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/search/MessageSearchProxy.java:93` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/MessageQueryUserAction.java:76 — src/main/java/com/jdon/jivejdon/presentation/action/query/MessageQueryUserAction.java:76-85 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadQueryUserAction.java:81-90 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) src/main/java/com/jdon/jivejdon/spi/component/sitemap/SitemapRepositoryImpl.java:222 — src/main/java/com/jdon/jivejdon/spi/component/sitemap/SitemapRepositoryImpl.java:222-231 | src/main/java/com/jdon/jivejdon/spi/component/sitemap/SitemapRepositoryImpl.java:287-296 — 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/com/jdon/jivejdon/spi/component/sitemap/SitemapRepositoryImpl.java:222` 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/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java:190 — src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java:190-199 | src/main/java/com/jdon/jivejdon/presentation/form/UpLoadFileForm.java:189-198 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java` and `src/main/java/com/jdon/jivejdon/presentation/form/UpLoadFileForm.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/presentation/form/UpLoadFileForm.java:203` calls `getFileTypes` and `src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java:204` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java:97 — src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java:97-106 | src/main/java/com/jdon/jivejdon/presentation/taglib/PrevTag.java:94-103 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java` and `src/main/java/com/jdon/jivejdon/presentation/taglib/PrevTag.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 (10 lines × 2) src/main/java/com/jdon/jivejdon/spi/component/email/EmailSender.java:48 — src/main/java/com/jdon/jivejdon/spi/component/email/EmailSender.java:48-57 | src/main/java/com/jdon/jivejdon/util/EmailTask.java:93-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×8
  • Duplicated block (6 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/subscription/SubscribedState.java:62 — src/main/java/com/jdon/jivejdon/domain/model/subscription/SubscribedState.java:62-67 | src/main/java/com/jdon/jivejdon/domain/model/subscription/SubscribedState.java:79-84 — 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/com/jdon/jivejdon/domain/model/subscription/SubscribedState.java:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/builder/MessageInitFactory.java:63 — src/main/java/com/jdon/jivejdon/infrastructure/repository/builder/MessageInitFactory.java:63-68 | src/main/java/com/jdon/jivejdon/infrastructure/repository/builder/MessageInitFactory.java:133-138 — 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 (6 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:251 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:251-257 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:141-146 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:251` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:556 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:556-561 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:598-603 — 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 (6 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:271 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:271-276 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:283-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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:277` calls `add` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:289` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:93 — src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:93-98 | src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:226-231 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:225` calls `clearApprovalCookie` and `src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:91` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:120 — src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:120-125 | src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:251-256 — 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/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:120` 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 (6 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/admin/UserMessageListAction.java:45 — src/main/java/com/jdon/jivejdon/presentation/action/admin/UserMessageListAction.java:45-50 | src/main/java/com/jdon/jivejdon/presentation/action/query/SearchThreadAction.java:70-75 — 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. 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.
AC3 · Page structure · Page without a main landmark · ×7
  • Page without a main landmark application/503.jsp:6 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark application/account/login.jsp — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark application/account/login_error.jsp — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark application/account/protected/EditAccountForm.jsp:6 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark application/account/protected/onlineInfo.jsp:10 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark application/account/protected/upload/result.jsp — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark application/account/protected/upload/uploadUserFace.jsp:18 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×7
  • Duplicated block (11 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:186 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:186-196 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:113-123 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:166 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:166-176 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:208-218 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:166` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:205` calls `add` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:163` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) REDACTED:125 — REDACTED:125-135 | REDACTED:174-184 — 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. 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 (11 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/blog/FollowerListAction.java:37 — src/main/java/com/jdon/jivejdon/presentation/action/blog/FollowerListAction.java:37-47 | src/main/java/com/jdon/jivejdon/presentation/action/blog/FollowingListAction.java:37-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11 lines × 2) src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:257 — src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:257-267 | src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:313-323 — 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 (11 lines × 2) src/main/java/com/jdon/jivejdon/util/XMLProperties.java:81 — src/main/java/com/jdon/jivejdon/util/XMLProperties.java:81-91 | src/main/java/com/jdon/jivejdon/util/XMLProperties.java:94-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java:156 — src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java:156-166 | src/main/java/com/jdon/jivejdon/presentation/form/UpLoadFileForm.java:162-172 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java` and `src/main/java/com/jdon/jivejdon/presentation/form/UpLoadFileForm.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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. 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×7
  • Duplicated block (8 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:120 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:120-127 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/util/OldUpdateNewUtil.java:133-140 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (8 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:484 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:484-491 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:525-532 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:484` 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 (8 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:355 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:355-362 | src/main/java/com/jdon/jivejdon/infrastructure/repository/search/ReBuildIndex.java:116-123 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:355` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/ThreadListAction.java:125 — src/main/java/com/jdon/jivejdon/presentation/action/ThreadListAction.java:125-132 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadDigSortedListAction.java:70-77 — 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/com/jdon/jivejdon/presentation/action/ThreadListAction.java:125` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:110 — src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:110-117 | src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:125-132 — 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 (8 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedHomeListAction.java:83 — src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedHomeListAction.java:83-90 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedNewListAction.java:57-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) src/main/java/com/jdon/jivejdon/spi/pubsub/subscriber/addReplyMessage/AddReplyMessage.java:52 — src/main/java/com/jdon/jivejdon/spi/pubsub/subscriber/addReplyMessage/AddReplyMessage.java:52-59 | src/main/java/com/jdon/jivejdon/spi/pubsub/subscriber/updatemessage/MessageRevisedListener.java:40-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×7
  • Duplicated block (7 lines × 2) src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:141 — src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:141-147 | src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:160-166 — 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/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:141` 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/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/CodeViewer.java:403 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/CodeViewer.java:403-409 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:1031-1037 — 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/com/jdon/jivejdon/domain/model/message/output/codeviewer/CodeViewer.java:403` 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/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:703 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:703-710 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:728-734 — 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/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:703` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:473 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:473-479 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:513-519 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/MaxThreadListAction.java:66 — src/main/java/com/jdon/jivejdon/presentation/action/MaxThreadListAction.java:66-72 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadDigSortedListAction.java:68-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (7 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/admin/UserMessageListAction.java:30 — src/main/java/com/jdon/jivejdon/presentation/action/admin/UserMessageListAction.java:30-36 | src/main/java/com/jdon/jivejdon/presentation/action/query/MessageQueryUserAction.java:59-65 — 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/com/jdon/jivejdon/presentation/action/admin/UserMessageListAction.java:30` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/DraftBoxListAction.java:48 — src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/DraftBoxListAction.java:48-54 | src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/SendBoxListAction.java:48-54 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/DraftBoxListAction.java` and `src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/SendBoxListAction.java` as WHOLE FILES: 88% 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. 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.
R10 · Code Duplication · Duplicated block (5 lines × 2 locations) · ×7
  • Duplicated block (5 lines × 2 locations) REDACTED:1627 — REDACTED:1627 · REDACTED:1633 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (5 lines × 2 locations) REDACTED:3419 — REDACTED:3419 · REDACTED:3467 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (5 lines × 2 locations) REDACTED:3921 — REDACTED:3921 · REDACTED:3937 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (5 lines × 2 locations) REDACTED:4650 — REDACTED:4650 · REDACTED:4665 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (5 lines × 2 locations) REDACTED:5077 — REDACTED:5077 · REDACTED:5089 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (5 lines × 2 locations) REDACTED:7423 — REDACTED:7423 · REDACTED:7447 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (5 lines × 2 locations) REDACTED:10597 — REDACTED:10597 · REDACTED:10603 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×7
  • Swallowed exception (caught, then discarded) src/main/java/com/jdon/jivejdon/domain/model/account/AccountState.java:122 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/main/java/com/jdon/jivejdon/domain/model/account/AccountState.java:130 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/main/java/com/jdon/jivejdon/infrastructure/repository/builder/ThreadDirector.java:74 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/main/java/com/jdon/jivejdon/infrastructure/repository/builder/ThreadDirector.java:99 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:358 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) src/main/java/com/jdon/jivejdon/presentation/sitemap/UrlForm.java:92 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:121 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
AC4 · Keyboard semantics · Anchor without href · ×6
  • Anchor without href REDACTED:131 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href REDACTED:6251 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href REDACTED:8354 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href REDACTED:8356 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href REDACTED:8362 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
  • Anchor without href REDACTED:8364 — An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action.
AC4 · Keyboard semantics · Positive tabindex (1) · ×5
  • Positive tabindex (1) application/account/login.jsp:60 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
  • Positive tabindex (1) application/blog/header.jsp:284 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
  • Positive tabindex (1) application/shortmessage/draftshortmessage.jsp:24 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
  • Positive tabindex (1) application/shortmessage/newshortmessage.jsp:50 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
  • Positive tabindex (1) application/shortmessage/receiveshortmessage.jsp:75 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC4 · Keyboard semantics · Link used as a button (placeholder href) · ×5
  • Link used as a button (placeholder href) application/blog/header.jsp:279 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) application/blog/header.jsp:304 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) application/common/bookmark.jsp:72 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) application/common/bookmark.jsp:83 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) application/forum/newLobbymessage.jsp:18 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
D17 · Explicit Debt · TodoComment · ×5
  • TodoComment src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:131 — // TODO Auto-generated catch block — 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/com/jdon/jivejdon/presentation/taglib/MPageTag.java:133 — // TODO Auto-generated catch block — 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/com/jdon/jivejdon/spi/component/shortmessage/ShortMessageFactory.java:178 — // TODO Auto-generated catch block — 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/com/jdon/jivejdon/infrastructure/repository/dao/filter/MessageDaoDecorator.java:71 — // todo refactor to domaine events — 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/com/jdon/jivejdon/spi/pubsub/subscriber/updatemessage/MessageSendEventBus.java:41 — // todo send to JMS or MQ — 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.
D30 · Dependency Vulnerabilities · Medium CVE · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×5
  • Duplicated block (6 lines × 2 locations) REDACTED:1505 — REDACTED:1505 · REDACTED:1518 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (6 lines × 2 locations) REDACTED:1646 — REDACTED:1646 · REDACTED:1658 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (6 lines × 2 locations) REDACTED:7062 — REDACTED:7062 · REDACTED:7146 — 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 (6 lines × 2 locations) REDACTED:10571 — REDACTED:10571 · REDACTED:10578 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (6 lines × 2 locations) REDACTED:11138 — REDACTED:11138 · REDACTED:11180 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×4
  • Duplicated block (15 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:655 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:655-669 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:670-684 — 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/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:655` 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 (15 lines × 2) src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java:69 — src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java:69-83 | src/main/java/com/jdon/jivejdon/presentation/taglib/PrevTag.java:65-79 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java` and `src/main/java/com/jdon/jivejdon/presentation/taglib/PrevTag.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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/java/com/jdon/jivejdon/presentation/taglib/NextTag.java:69` 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 (15 lines × 2) src/main/java/com/jdon/jivejdon/spi/component/query/HotThreadQueryManager.java:58 — src/main/java/com/jdon/jivejdon/spi/component/query/HotThreadQueryManager.java:58-72 | src/main/java/com/jdon/jivejdon/spi/component/query/HotThreadQueryManager.java:81-95 — 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/com/jdon/jivejdon/spi/component/query/HotThreadQueryManager.java:58` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 2) src/main/java/com/jdon/jivejdon/util/XMLProperties.java:267 — src/main/java/com/jdon/jivejdon/util/XMLProperties.java:267-281 | src/main/java/com/jdon/jivejdon/util/XMLProperties.java:284-298 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×4
  • Duplicated block (12 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:108 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:108-119 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:145-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (12 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:125 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:125-136 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:221-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:308 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:308-319 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:349-360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) src/main/java/com/jdon/jivejdon/util/ContainerUtil.java:100 — src/main/java/com/jdon/jivejdon/util/ContainerUtil.java:100-111 | src/main/java/com/jdon/jivejdon/util/ContainerUtil.java:126-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/util/ContainerUtil.java:100` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D17 · Explicit Debt · XxxComment · ×3
  • XxxComment src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:234 — // Markdown 删除线 ~~XXX~~ 转为 <del>XXX</del> — 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.
  • XxxComment src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:237 — // Markdown 行内代码块 ```XXX``` 转为 <code>XXX</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.
  • XxxComment src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:239 — // Markdown 行内代码 `XXX` 转为 <code>XXX</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.
D3 · God Classes · FileTooLong · ×3
  • FileTooLong: REDACTED REDACTED — FileTooLong — 7157 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 6657 over it, 14.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1406 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 906 over it, 2.81× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: codeviewer/JavaCodeViewer.java src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java — FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 102 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×3
  • Duplicated block (20 lines × 2) src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:120 — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:120-139 | src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:149-168 — 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/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:120` 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 (20 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:199 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:199-218 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java: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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (20 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/MessageQueryUserAction.java:30 — src/main/java/com/jdon/jivejdon/presentation/action/query/MessageQueryUserAction.java:30-49 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadQueryUserAction.java:34-53 — 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/com/jdon/jivejdon/presentation/action/query/MessageQueryUserAction.java:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×3
  • Duplicated block (19 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:140 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:140-158 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:180-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (19 lines × 2) src/main/java/com/jdon/jivejdon/spi/component/subscription/action/ShortMsgAction.java:40 — src/main/java/com/jdon/jivejdon/spi/component/subscription/action/ShortMsgAction.java:40-58 | src/main/java/com/jdon/jivejdon/spi/component/subscription/action/SinaWeiboAction.java:48-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (19 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/subscription/messsage/ThreadNotifyMessage.java:9 — src/main/java/com/jdon/jivejdon/domain/model/subscription/messsage/ThreadNotifyMessage.java:9-27 | src/main/java/com/jdon/jivejdon/domain/model/subscription/messsage/WeiboExpiredNotifyMessage.java:25-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×3
  • Duplicated block (13 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/acccount/AccountFactoryDao.java:41 — src/main/java/com/jdon/jivejdon/infrastructure/repository/acccount/AccountFactoryDao.java:41-53 | src/main/java/com/jdon/jivejdon/infrastructure/repository/builder/ForumDirector.java:31-43 — 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/com/jdon/jivejdon/infrastructure/repository/acccount/AccountFactoryDao.java:41` 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 (13 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:242 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:242-254 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:259-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:242` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:240` calls `add` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:258` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (13 lines × 2) src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java:136 — src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java:136-148 | src/main/java/com/jdon/jivejdon/presentation/form/UpLoadFileForm.java:142-154 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java` and `src/main/java/com/jdon/jivejdon/presentation/form/UpLoadFileForm.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×3
  • Duplicated block (10–11 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/JdbcTempSSOSource.java:42 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/JdbcTempSSOSource.java:42-52 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/JdbcTempSource.java:39-48 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/JdbcTempSSOSource.java` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/JdbcTempSource.java` as WHOLE FILES: 91% 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10–11 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:462 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:462-472 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:475-484 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10–11 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SetupDaoSql.java:49 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SetupDaoSql.java:49-59 | REDACTED:151-160 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/SetupDaoSql.java:49` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (8–9 lines × 6) · ×3
  • Duplicated block (8–9 lines × 6) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:149 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:149-156 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:278-286 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:81-89 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:148-156 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:209-217 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:229-237 — there are 6 copies across 4 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 6 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:149` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:157` calls `debug` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:287` 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 (8–9 lines × 6) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:240 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:240-248 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:87-94 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:171-178 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:189-196 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:164-171 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:206-213 — there are 6 copies across 3 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 6 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:240` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:249` calls `debug` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:179` 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 (8–9 lines × 6) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:282 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:282-289 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:85-92 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:152-160 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:213-220 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:233-240 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SequenceDaoSql.java:83-90 — there are 6 copies across 4 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 6 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:282` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×3
  • Duplicated block (7 lines × 5) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:112 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:112-118 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:149-155 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:188-195 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:251-260 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:430-438 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (7 lines × 5) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:114 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:114-120 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:147-153 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:303-309 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:348-354 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:381-387 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:114` 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 × 5) src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedHomeListAction.java:44 — src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedHomeListAction.java:44-51 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedNewListAction.java:25-31 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadDigListAction.java:47-53 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagHotList2Action.java:35-41 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagHotListAction.java:20-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 all 5 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×3
  • Duplicated block (7 lines × 4) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:186 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:186-192 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:259-267 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:113-119 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:150-156 — 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.
  • Duplicated block (7 lines × 4) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:364 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:364-370 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:383-389 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:312-318 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:357-363 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:364` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 4) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:89 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:89-95 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:173-179 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:191-197 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:336-342 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×3
  • Duplicated block (7 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SetupDaoSql.java:47 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SetupDaoSql.java:47-53 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:180-186 | REDACTED:149-155 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SetupDaoSql.java:47` 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 × 3) src/main/java/com/jdon/jivejdon/presentation/action/blog/UserMessageListAction.java:38 — src/main/java/com/jdon/jivejdon/presentation/action/blog/UserMessageListAction.java:38-44 | src/main/java/com/jdon/jivejdon/presentation/action/query/MessageQueryAction.java:45-53 | src/main/java/com/jdon/jivejdon/presentation/action/query/MessageQueryUserAction.java:67-73 — 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. 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 (7 lines × 3) src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/DraftBoxListAction.java:57 — src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/DraftBoxListAction.java:57-63 | src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/ReceiveBoxListAction.java:56-62 | src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/SendBoxListAction.java:57-63 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/DraftBoxListAction.java` and `src/main/java/com/jdon/jivejdon/presentation/action/shortmessage/ReceiveBoxListAction.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×3
  • Duplicated block (6 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:117 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:117-122 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:150-155 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:558-563 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:426 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:426-431 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:312-317 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:353-358 — there are 3 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 3 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:426` 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 × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:322 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:322-327 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:197-205 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/UploadFileDaoSql.java:216-225 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×3
  • Duplicated block (5 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:180 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:180-184 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:252-256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:179` calls `add`, `getUserIdLong` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountDaoSql.java:251` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/message/upload/UploadFileFilter.java:34 — src/main/java/com/jdon/jivejdon/domain/model/message/upload/UploadFileFilter.java:34-39 | src/main/java/com/jdon/jivejdon/domain/model/message/upload/UploadImageFilter.java:46-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) src/main/java/com/jdon/jivejdon/api/impl/account/OAuthAccountServiceImp.java:193 — src/main/java/com/jdon/jivejdon/api/impl/account/OAuthAccountServiceImp.java:193-197 | src/main/java/com/jdon/jivejdon/api/impl/account/OAuthAccountServiceImp.java:260-264 — 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.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×3
  • Duplicated block (10 lines × 2 locations) REDACTED:1198 — REDACTED:1198 · REDACTED:3828 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (10 lines × 2 locations) REDACTED:2739 — REDACTED:2739 · REDACTED:2843 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (10 lines × 2 locations) REDACTED:4673 — REDACTED:4673 · REDACTED:5181 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (9 lines × 3 locations) · ×3
  • Duplicated block (9 lines × 3 locations) REDACTED:4481 — REDACTED:4481 · REDACTED:4492 · REDACTED:4504 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (9 lines × 3 locations) REDACTED:7210 — REDACTED:7210 · REDACTED:7232 · REDACTED:7257 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (9 lines × 3 locations) REDACTED:10316 — REDACTED:10316 · REDACTED:10370 · REDACTED:10384 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
AC4 · Keyboard semantics · Positive tabindex (2) · ×2
  • Positive tabindex (2) application/account/login.jsp:74 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
  • Positive tabindex (2) application/blog/header.jsp:286 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC4 · Keyboard semantics · Positive tabindex (3) · ×2
  • Positive tabindex (3) application/account/login.jsp:77 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
  • Positive tabindex (3) application/blog/header.jsp:288 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC4 · Keyboard semantics · Positive tabindex (4) · ×2
  • Positive tabindex (4) application/blog/header.jsp:218 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
  • Positive tabindex (4) application/blog/header.jsp:290 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.9 · ×2
  • Low contrast colour pair in CSS (3.9:1) application/common/style/template/classic.css:30 — `tr:hover, tr.odd:hover` sets color: #ffffff on background-color: #3d80df — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.9:1) application/common/style/template/itunes.css:25 — `tr:hover, tr.odd:hover` sets color: #ffffff on background-color: #3d80df — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · initialize (cyclomatic 30) · ×2
  • initialize (cyclomatic 30) REDACTED:8 — initialize has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to 3 function items inside it that branch. 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.
  • initialize (cyclomatic 30) application/common/js/window.js:7 — initialize has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to 3 function items inside it that branch. 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.
D1 · Cyclomatic Complexity · setSize (cyclomatic 17) · ×2
  • setSize (cyclomatic 17) REDACTED:419 — setSize has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • setSize (cyclomatic 17) application/common/js/window.js:418 — setSize has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · maximize (cyclomatic 16) · ×2
  • maximize (cyclomatic 16) REDACTED:588 — maximize has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • maximize (cyclomatic 16) application/common/js/window.js:587 — maximize has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · initialize (cognitive 39) · ×2
  • initialize (cognitive 39) REDACTED:8 — initialize has cognitive complexity 39 (threshold 15). Drivers by points: if/else 25 (30 pts), ternaries 3 (5 pts), boolean chains 4 (nesting depth added 7). Of this number, 37 points are the body's own statements and 2 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • initialize (cognitive 39) application/common/js/window.js:7 — initialize has cognitive complexity 39 (threshold 15). Drivers by points: if/else 25 (30 pts), ternaries 3 (5 pts), boolean chains 4 (nesting depth added 7). Of this number, 37 points are the body's own statements and 2 belong to 3 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · maximize (cognitive 25) · ×2
  • maximize (cognitive 25) REDACTED:588 — maximize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 2 (6 pts), boolean chains 4 (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.
  • maximize (cognitive 25) application/common/js/window.js:587 — maximize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 2 (6 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · _saveCookie (cognitive 23) · ×2
  • _saveCookie (cognitive 23) REDACTED:720 — _saveCookie has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (16 pts), if/else 5 (7 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.
  • _saveCookie (cognitive 23) application/common/js/window.js:719 — _saveCookie has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (16 pts), if/else 5 (7 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.
D2 · Cognitive Complexity · FiltersUtils.getPropertyHTML (cognitive 19) · ×2
  • FiltersUtils.getPropertyHTML (cognitive 19) src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:18 — FiltersUtils.getPropertyHTML has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 2 (4 pts), boolean chains 1, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • FiltersUtils.getPropertyHTML (cognitive 19) src/main/java/com/jdon/jivejdon/util/FiltersUtils.java:32 — FiltersUtils.getPropertyHTML has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 2 (4 pts), boolean chains 1, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · getPageSize (cognitive 19) · ×2
  • getPageSize (cognitive 19) REDACTED:1018 — getPageSize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3 (nesting depth added 4). 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.
  • getPageSize (cognitive 19) application/common/js/window.js:1017 — getPageSize has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3 (nesting depth added 4). 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.
D2 · Cognitive Complexity · setSize (cognitive 17) · ×2
  • setSize (cognitive 17) REDACTED:419 — setSize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • setSize (cognitive 17) application/common/js/window.js:418 — setSize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · minimize (cognitive 17) · ×2
  • minimize (cognitive 17) REDACTED:554 — minimize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4 (nesting depth added 4). 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.
  • minimize (cognitive 17) application/common/js/window.js:553 — minimize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4 (nesting depth added 4). 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.
D2 · Cognitive Complexity · _openDialog (cognitive 17) · ×2
  • _openDialog (cognitive 17) REDACTED:935 — _openDialog has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
  • _openDialog (cognitive 17) application/common/js/window.js:934 — _openDialog has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (7 pts) (nesting depth added 1). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FunctionTooLong · ×2
  • FunctionTooLong: base64image.CKEDITOR.dialog.add("base64imageDialog") application/common/ckeditor/plugins/base64image/dialogs/base64image.js:5 — FunctionTooLong — CKEDITOR.dialog.add("base64imageDialog") runs 313 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 213 over it, 3.13× 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.
  • FunctionTooLong: plugin.CKEDITOR.htmlParser.fragment.fromBBCode application/common/ckeditor/plugins/bbcode/plugin.js:177 — FunctionTooLong — CKEDITOR.htmlParser.fragment.fromBBCode runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× 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.
D32 · Data Compliance (PII/GDPR) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • Duplicated block (22 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:60 — src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:60-81 | src/main/java/com/jdon/jivejdon/util/FiltersUtils.java:74-95 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java` and `src/main/java/com/jdon/jivejdon/util/FiltersUtils.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 94 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/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (22 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:102 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:102-123 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:135-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:102` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×2
  • Duplicated block (21 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/query/QueryCriteria.java:77 — src/main/java/com/jdon/jivejdon/domain/model/query/QueryCriteria.java:77-97 | src/main/java/com/jdon/jivejdon/domain/model/query/QueryCriteria.java:134-154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (21 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/util/Many2ManyDTO.java:16 — src/main/java/com/jdon/jivejdon/domain/model/util/Many2ManyDTO.java:16-36 | src/main/java/com/jdon/jivejdon/domain/model/util/OneManyDTO.java:31-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `parent` to `Collection` in one and `Object` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) src/main/java/com/jdon/jivejdon/api/impl/upload/UploadInfoVOServiceImp.java:52 — src/main/java/com/jdon/jivejdon/api/impl/upload/UploadInfoVOServiceImp.java:52-67 | src/main/java/com/jdon/jivejdon/spi/component/query/SlideImageQueryManager.java:84-99 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (16 lines × 2) src/main/java/com/jdon/jivejdon/spi/component/sitemap/SitemapRepositoryImpl.java:201 — src/main/java/com/jdon/jivejdon/spi/component/sitemap/SitemapRepositoryImpl.java:201-216 | src/main/java/com/jdon/jivejdon/spi/component/sitemap/SitemapRepositoryImpl.java:266-281 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×2
  • Duplicated block (14 lines × 2) src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:174 — src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:174-187 | src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:198-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/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:174` 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/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:625 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:625-638 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:640-653 — 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/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:625` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×2
  • Duplicated block (13–14 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/UploadFileDaoSql.java:155 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/UploadFileDaoSql.java:155-168 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/UploadFileDaoSql.java:171-183 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13–14 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadDigListAction.java:91 — src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadDigListAction.java:91-104 | src/main/java/com/jdon/jivejdon/spi/component/mapreduce/ThreadDigComparator.java:23-35 — 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. 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×2
  • Duplicated block (12–13 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/query/SearchAction.java:21 — src/main/java/com/jdon/jivejdon/presentation/action/query/SearchAction.java:21-32 | src/main/java/com/jdon/jivejdon/presentation/action/query/SearchThreadAction.java:50-62 — 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/com/jdon/jivejdon/presentation/action/query/SearchAction.java:21` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12–13 lines × 2) src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:87 — src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:87-99 | src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:111-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/com/jdon/jivejdon/presentation/taglib/IndexTag.java:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2
  • Duplicated block (11–12 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:256 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:256-266 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:452-463 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:256` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11–12 lines × 2) src/main/java/com/jdon/jivejdon/presentation/action/MaxThreadListAction.java:32 — src/main/java/com/jdon/jivejdon/presentation/action/MaxThreadListAction.java:32-42 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadDigSortedListAction.java:37-48 — 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. 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.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:218 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:218-227 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:243-252 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:260-269 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:216` calls `add` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:258` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:145 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:145-154 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:251-260 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:372-381 — 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/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:145` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×2
  • Duplicated block (9–10 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:199 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:199-208 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:226-234 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:199` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9–10 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:176 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:176-184 | REDACTED:144-153 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:176` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×2
  • Duplicated block (8 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/property/PropertyFactoryDao.java:53 — src/main/java/com/jdon/jivejdon/infrastructure/repository/property/PropertyFactoryDao.java:53-60 | src/main/java/com/jdon/jivejdon/infrastructure/repository/property/PropertyFactoryDao.java:78-85 | src/main/java/com/jdon/jivejdon/infrastructure/repository/property/PropertyFactoryDao.java:115-122 — 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/java/com/jdon/jivejdon/infrastructure/repository/property/PropertyFactoryDao.java:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/property/PropertyFactoryDao.java:63` calls `clearCache` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/property/PropertyFactoryDao.java:88` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) src/main/java/com/jdon/jivejdon/domain/model/message/output/html/FontStyle.java:20 — src/main/java/com/jdon/jivejdon/domain/model/message/output/html/FontStyle.java:20-28 | src/main/java/com/jdon/jivejdon/domain/model/message/output/html/ListStyle.java:41-48 | src/main/java/com/jdon/jivejdon/domain/model/message/output/html/URLConverter.java:62-70 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×2
  • Duplicated block (13 lines × 2 locations) REDACTED:1133 — REDACTED:1133 · REDACTED:3766 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (13 lines × 2 locations) application/common/form.js:11 — application/common/form.js:11 · application/common/messageList12.js:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×2
  • Duplicated block (11 lines × 2 locations) REDACTED:7232 — REDACTED:7232 · REDACTED:7257 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (11 lines × 2 locations) application/common/js/pagination.js:55 — application/common/js/pagination.js:55 · application/forum/js/threadList.js:3 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R2 · Cyclomatic Complexity · Complex function initialize (cyclomatic 29, cognitive 37) · ×2
  • Complex function initialize (cyclomatic 29, cognitive 37) application/common/js/window.js:7 — initialize has cyclomatic complexity 29 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
  • Complex function initialize (cyclomatic 29, cognitive 37) REDACTED:8 — initialize has cyclomatic complexity 29 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R7 · Dead Code · Dead file (~162 LoC) · ×2
  • Dead file (~162 LoC) application/common/ckeditor/plugins/autogrow/plugin.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~162 LoC) application/common/js/calendar.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~59 LoC) · ×2
  • Dead file (~59 LoC) application/common/js/upload.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
  • Dead file (~59 LoC) application/forum/js/newMessage.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC4 · Keyboard semantics · Positive tabindex (5) · ×1
  • Positive tabindex (5) application/message/messagePostReply2.jsp:33 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC4 · Keyboard semantics · Positive tabindex (6) · ×1
  • Positive tabindex (6) application/message/messagePostReply2.jsp:43 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC4 · Keyboard semantics · Positive tabindex (102) · ×1
  • Positive tabindex (102) application/shortmessage/messageform.jsp:58 — A positive tabindex forces a manual tab order that fights the DOM and is fragile. Use tabindex="0" (or restructure the DOM).
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.2 · ×1
  • Low contrast colour pair in CSS (2.2:1) application/js/jdon.css:2 — `.btn-warning:hover,.btn-warning:focus,.btn-warning:active,.btn-warning.active,.open .dropdown-toggle.btn-warning` sets color: #fff on background-color: #ed9c28 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from).
AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1
  • Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 193 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D1 · Cyclomatic Complexity · JavaCodeViewer.javaCodeFilter (cyclomatic 122) · ×1
  • JavaCodeViewer.javaCodeFilter (cyclomatic 122) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:303 — JavaCodeViewer.javaCodeFilter has cyclomatic complexity 122 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · (anonymous) (cyclomatic 100) · ×1
  • (anonymous) (cyclomatic 100) REDACTED:3973 — (anonymous) has cyclomatic complexity 100 (threshold 15). Most of this is not in the body itself: 1 of the 100 points is its own statement and the rest belongs to 45 function items inside it that branch (_normalizeArguments, getElementStyles, getRGB, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · _generateHTML (cyclomatic 91) · ×1
  • _generateHTML (cyclomatic 91) REDACTED:8313 — _generateHTML has cyclomatic complexity 91 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Emoticon.convertEmoticons (cyclomatic 83) · ×1
  • Emoticon.convertEmoticons (cyclomatic 83) src/main/java/com/jdon/jivejdon/domain/model/message/output/emotion/Emoticon.java:240 — Emoticon.convertEmoticons has cyclomatic complexity 83 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _tabify (cyclomatic 58) · ×1
  • _tabify (cyclomatic 58) REDACTED:10706 — _tabify has cyclomatic complexity 58 (threshold 15). Of this number, 28 points are the body's own statements and 30 belong to 25 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plugin.CKEDITOR.htmlParser.fragment.fromBBCode (cyclomatic 56) · ×1
  • plugin.CKEDITOR.htmlParser.fragment.fromBBCode (cyclomatic 56) application/common/ckeditor/plugins/bbcode/plugin.js:177 — plugin.CKEDITOR.htmlParser.fragment.fromBBCode has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 9 of the 56 points are its own statements and the rest belongs to 7 function items inside it that branch (checkPendingBrs, checkPending, a function literal at line 251, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · parseDate (cyclomatic 53) · ×1
  • parseDate (cyclomatic 53) REDACTED:7854 — parseDate has cyclomatic complexity 53 (threshold 15). Of this number, 41 points are the body's own statements and 12 belong to 7 function items inside it that branch. 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.
D1 · Cyclomatic Complexity · _doKeyDown (cyclomatic 45) · ×1
  • _doKeyDown (cyclomatic 45) REDACTED:7392 — _doKeyDown has cyclomatic complexity 45 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · drag (cyclomatic 44) · ×1
  • drag (cyclomatic 44) REDACTED:1485 — drag has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · login2.J (cyclomatic 41) · ×1
  • login2.J (cyclomatic 41) application/common/login2.js:5 — login2.J has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 2 of the 41 points are its own statements and the rest belongs to 12 function items inside it that branch (R, S, a function literal at line 5, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · _create (cyclomatic 38) · ×1
  • _create (cyclomatic 38) REDACTED:9993 — _create has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 12 of the 38 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 10073, 10049, 10056, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · calendar.Calendar.parseDate (cyclomatic 36) · ×1
  • calendar.Calendar.parseDate (cyclomatic 36) application/common/js/calendar.js:4 — calendar.Calendar.parseDate has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · calendar.Calendar._keyEvent (cyclomatic 35) · ×1
  • calendar.Calendar._keyEvent (cyclomatic 35) application/common/js/calendar.js:4 — calendar.Calendar._keyEvent has cyclomatic complexity 35 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · jquery-ui.$.fn.position (cyclomatic 33) · ×1
  • jquery-ui.$.fn.position (cyclomatic 33) REDACTED:9585 — jquery-ui.$.fn.position has cyclomatic complexity 33 (threshold 15). Of this number, 16 points are the body's own statements and 17 belong to 3 function literals inside it that branch. 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.
D1 · Cyclomatic Complexity · _generatePosition (cyclomatic 32) · ×1
  • _generatePosition (cyclomatic 32) REDACTED:1161 — _generatePosition has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _mouseDrag (cyclomatic 32) · ×1
  • _mouseDrag (cyclomatic 32) REDACTED:3129 — _mouseDrag has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _clear (cyclomatic 32) · ×1
  • _clear (cyclomatic 32) REDACTED:3870 — _clear has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · formatDate (cyclomatic 32) · ×1
  • formatDate (cyclomatic 32) REDACTED:8036 — formatDate has cyclomatic complexity 32 (threshold 15). Of this number, 27 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · base64image.CKEDITOR.dialog.add("base64imageDialog").onShow (cyclomatic 31) · ×1
  • base64image.CKEDITOR.dialog.add("base64imageDialog").onShow (cyclomatic 31) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:274 — base64image.CKEDITOR.dialog.add("base64imageDialog").onShow has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _refreshValue (cyclomatic 31) · ×1
  • _refreshValue (cyclomatic 31) REDACTED:10551 — _refreshValue has cyclomatic complexity 31 (threshold 15). Of this number, 19 points are the body's own statements and 12 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · (anonymous).onShow (cyclomatic 31) · ×1
  • (anonymous).onShow (cyclomatic 31) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:274 — (anonymous).onShow has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _create (cyclomatic 30) · ×1
  • _create (cyclomatic 30) REDACTED:1876 — _create has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 13 of the 30 points are its own statements and the rest belongs to 4 function items inside it that branch (_renderAxis, a function literal at line 1998, a function literal at line 2017, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · _generatePosition (cyclomatic 30) · ×1
  • _generatePosition (cyclomatic 30) REDACTED:3794 — _generatePosition has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _generateMonthYearHeader (cyclomatic 30) · ×1
  • _generateMonthYearHeader (cyclomatic 30) REDACTED:8481 — _generateMonthYearHeader has cyclomatic complexity 30 (threshold 15). Of this number, 27 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-ui.$.ui.intersect (cyclomatic 29) · ×1
  • jquery-ui.$.ui.intersect (cyclomatic 29) REDACTED:1709 — jquery-ui.$.ui.intersect has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · jquery-ui.$.effects.bounce (cyclomatic 29) · ×1
  • jquery-ui.$.effects.bounce (cyclomatic 29) REDACTED:4617 — jquery-ui.$.effects.bounce has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 1 of the 29 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 4619, 4660, 4669). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · _respectSize (cyclomatic 29) · ×1
  • _respectSize (cyclomatic 29) REDACTED:2240 — _respectSize has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · _create (cyclomatic 29) · ×1
  • _create (cyclomatic 29) REDACTED:5883 — _create has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 3 of the 29 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 5898, a function literal at line 5990, focus, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · _create (cyclomatic 28) · ×1
  • _create (cyclomatic 28) REDACTED:6519 — _create has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 6596, 6649, 6546, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · _showDatepicker (cyclomatic 28) · ×1
  • _showDatepicker (cyclomatic 28) REDACTED:7503 — _showDatepicker has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plugin.initIframeAutogrow (cyclomatic 27) · ×1
  • plugin.initIframeAutogrow (cyclomatic 27) application/common/ckeditor/plugins/autogrow/plugin.js:30 — plugin.initIframeAutogrow has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 7 of the 27 points are its own statements and the rest belongs to 6 function items inside it that branch (refreshCache, resizeEditor, a function literal at line 73, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · _mouseDrag (cyclomatic 27) · ×1
  • _mouseDrag (cyclomatic 27) REDACTED:2777 — _mouseDrag has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 2791). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · JavaCodeHighlighter.highlightCode (cyclomatic 26) · ×1
  • JavaCodeHighlighter.highlightCode (cyclomatic 26) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:608 — JavaCodeHighlighter.highlightCode has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · init · ×1
  • init::$ (cyclomatic 26) application/common/ckeditor/plugins/bbcode/plugin.js:622 — init::$ has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-ui.$.effects.size (cyclomatic 25) · ×1
  • jquery-ui.$.effects.size (cyclomatic 25) REDACTED:5046 — jquery-ui.$.effects.size has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 5048, 5128, 5106, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · calendar.Calendar._init (cyclomatic 25) · ×1
  • calendar.Calendar._init (cyclomatic 25) application/common/js/calendar.js:4 — calendar.Calendar._init has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _setContainment (cyclomatic 25) · ×1
  • _setContainment (cyclomatic 25) REDACTED:1107 — _setContainment has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · parse (cyclomatic 24) · ×1
  • parse (cyclomatic 24) application/common/ckeditor/plugins/bbcode/plugin.js:80 — parse 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.
D1 · Cyclomatic Complexity · calendar.Calendar.cellClick (cyclomatic 23) · ×1
  • calendar.Calendar.cellClick (cyclomatic 23) application/common/js/calendar.js:4 — calendar.Calendar.cellClick has cyclomatic complexity 23 (threshold 15). Of this number, 22 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · base64image.CKEDITOR.dialog.add("base64imageDialog").onOk (cyclomatic 22) · ×1
  • base64image.CKEDITOR.dialog.add("base64imageDialog").onOk (cyclomatic 22) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:346 — base64image.CKEDITOR.dialog.add("base64imageDialog").onOk has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · drag (cyclomatic 22) · ×1
  • drag (cyclomatic 22) REDACTED:1425 — drag has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · resize (cyclomatic 22) · ×1
  • resize (cyclomatic 22) REDACTED:2523 — resize has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _determineDate (cyclomatic 22) · ×1
  • _determineDate (cyclomatic 22) REDACTED:8186 — _determineDate has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 2 function items inside it that branch (offsetString, offsetNumeric). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · _setOption (cyclomatic 22) · ×1
  • _setOption (cyclomatic 22) REDACTED:9275 — _setOption has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · (anonymous).onOk (cyclomatic 22) · ×1
  • (anonymous).onOk (cyclomatic 22) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:346 — (anonymous).onOk has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AccountForm.doValidate (cyclomatic 21) · ×1
  • AccountForm.doValidate (cyclomatic 21) src/main/java/com/jdon/jivejdon/presentation/form/AccountForm.java:131 — AccountForm.doValidate has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · IndexTag.doStartTag (cyclomatic 20) · ×1
  • IndexTag.doStartTag (cyclomatic 20) src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:34 — IndexTag.doStartTag has cyclomatic complexity 20 (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.
D1 · Cyclomatic Complexity · base64image.CKEDITOR.dialog.add("base64imageDialog").imagePreview (cyclomatic 20) · ×1
  • base64image.CKEDITOR.dialog.add("base64imageDialog").imagePreview (cyclomatic 20) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:79 — base64image.CKEDITOR.dialog.add("base64imageDialog").imagePreview has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · calendar.Calendar.create (cyclomatic 20) · ×1
  • calendar.Calendar.create (cyclomatic 20) application/common/js/calendar.js:4 — calendar.Calendar.create has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
D1 · Cyclomatic Complexity · drag (cyclomatic 20) · ×1
  • drag (cyclomatic 20) REDACTED:1803 — drag has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 1809). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · (anonymous).imagePreview (cyclomatic 20) · ×1
  • (anonymous).imagePreview (cyclomatic 20) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:79 — (anonymous).imagePreview has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AuthorNameFilter.getUsernameFromBody (cyclomatic 19) · ×1
  • AuthorNameFilter.getUsernameFromBody (cyclomatic 19) src/main/java/com/jdon/jivejdon/domain/model/message/infilter/AuthorNameFilter.java:30 — AuthorNameFilter.getUsernameFromBody has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PasswordassitAction.execute (cyclomatic 19) · ×1
  • PasswordassitAction.execute (cyclomatic 19) src/main/java/com/jdon/jivejdon/presentation/action/account/PasswordassitAction.java:44 — PasswordassitAction.execute has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-ui.$.effects.explode (cyclomatic 19) · ×1
  • jquery-ui.$.effects.explode (cyclomatic 19) REDACTED:4766 — jquery-ui.$.effects.explode has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 4768, 4815). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · _contactContainers (cyclomatic 19) · ×1
  • _contactContainers (cyclomatic 19) REDACTED:3582 — _contactContainers has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _toggle (cyclomatic 19) · ×1
  • _toggle (cyclomatic 19) REDACTED:5642 — _toggle has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _mouseStop (cyclomatic 18) · ×1
  • _mouseStop (cyclomatic 18) REDACTED:937 — _mouseStop has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _mouseStart (cyclomatic 18) · ×1
  • _mouseStart (cyclomatic 18) REDACTED:3013 — _mouseStart has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · _setContainment (cyclomatic 18) · ×1
  • _setContainment (cyclomatic 18) REDACTED:3745 — _setContainment 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.
D1 · Cyclomatic Complexity · PinyinUtils.toPinyin (cyclomatic 17) · ×1
  • PinyinUtils.toPinyin (cyclomatic 17) src/main/java/com/jdon/jivejdon/util/PinyinUtils.java:10 — PinyinUtils.toPinyin has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-ui.$.effects.drop (cyclomatic 17) · ×1
  • jquery-ui.$.effects.drop (cyclomatic 17) REDACTED:4727 — jquery-ui.$.effects.drop has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 4729, 4751). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · jquery-ui.$.effects.slide (cyclomatic 17) · ×1
  • jquery-ui.$.effects.slide (cyclomatic 17) REDACTED:5192 — jquery-ui.$.effects.slide has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 5194, 5216). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · MessageForm.doValidate (cyclomatic 16) · ×1
  • MessageForm.doValidate (cyclomatic 16) src/main/java/com/jdon/jivejdon/presentation/form/MessageForm.java:260 — MessageForm.doValidate has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · jquery-ui.$.effects.shake (cyclomatic 16) · ×1
  • jquery-ui.$.effects.shake (cyclomatic 16) REDACTED:5146 — jquery-ui.$.effects.shake has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 5148, 5178). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · _convertPositionTo (cyclomatic 16) · ×1
  • _convertPositionTo (cyclomatic 16) REDACTED:1138 — _convertPositionTo has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · _drop (cyclomatic 16) · ×1
  • _drop (cyclomatic 16) REDACTED:1665 — _drop has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · _clickHandler (cyclomatic 16) · ×1
  • _clickHandler (cyclomatic 16) REDACTED:5556 — _clickHandler has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · _attachments (cyclomatic 16) · ×1
  • _attachments (cyclomatic 16) REDACTED:7077 — _attachments has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _optionDatepicker (cyclomatic 16) · ×1
  • _optionDatepicker (cyclomatic 16) REDACTED:7321 — _optionDatepicker has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · _hideDatepicker (cyclomatic 16) · ×1
  • _hideDatepicker (cyclomatic 16) REDACTED:7666 — _hideDatepicker has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt · HackComment · ×1
  • HackComment src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:706 — // hack — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D17 · Explicit Debt · TodoComment repeated across 14 files · ×1
  • TodoComment repeated across 14 files src/main/java/com/jdon/jivejdon/domain/model/realtime/NotificationLocator.java:65 — The identical TodoComment appears in 14 files (18 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 18 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO Auto-generated method stub". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
D2 · Cognitive Complexity · JavaCodeViewer.javaCodeFilter (cognitive 300) · ×1
  • JavaCodeViewer.javaCodeFilter (cognitive 300) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:303 — JavaCodeViewer.javaCodeFilter has cognitive complexity 300 (threshold 15). Drivers by points: if/else 125 (281 pts), boolean chains 16, match/switch 1 (2 pts), loops 1 (nesting depth added 157). 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.
D2 · Cognitive Complexity · _generateHTML (cognitive 210) · ×1
  • _generateHTML (cognitive 210) REDACTED:8313 — _generateHTML has cognitive complexity 210 (threshold 15). Drivers by points: ternaries 50 (149 pts), boolean chains 23, if/else 7 (18 pts), loops 6 (15 pts), match/switch 1 (5 pts) (nesting depth added 123). 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.
D2 · Cognitive Complexity · Emoticon.convertEmoticons (cognitive 179) · ×1
  • Emoticon.convertEmoticons (cognitive 179) src/main/java/com/jdon/jivejdon/domain/model/message/output/emotion/Emoticon.java:240 — Emoticon.convertEmoticons has cognitive complexity 179 (threshold 15). Drivers by points: ternaries 26 (112 pts), if/else 17 (45 pts), boolean chains 13, match/switch 3 (8 pts), loops 1 (nesting depth added 119). 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.
D2 · Cognitive Complexity · (anonymous) (cognitive 119) · ×1
  • (anonymous) (cognitive 119) REDACTED:3973 — (anonymous) has cognitive complexity 119 (threshold 15). Drivers by points: if/else 52 (67 pts), boolean chains 25, ternaries 10 (13 pts), loops 9 (11 pts), match/switch 2, error handling 1 (nesting depth added 20). None of this is in the body itself: all 119 points belong to 45 function items inside it that branch (getElementStyles, _normalizeArguments, toggleClass, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · JavaCodeHighlighter.highlightCode (cognitive 102) · ×1
  • JavaCodeHighlighter.highlightCode (cognitive 102) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeHighlighter.java:608 — JavaCodeHighlighter.highlightCode has cognitive complexity 102 (threshold 15). Drivers by points: if/else 30 (96 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 67). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · _tabify (cognitive 83) · ×1
  • _tabify (cognitive 83) REDACTED:10706 — _tabify has cognitive complexity 83 (threshold 15). Drivers by points: if/else 34 (55 pts), boolean chains 17, ternaries 6 (10 pts), loops 1 (nesting depth added 25). Of this number, 43 points are the body's own statements and 40 belong to 25 function items inside it that branch. 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.
D2 · Cognitive Complexity · _refreshValue (cognitive 80) · ×1
  • _refreshValue (cognitive 80) REDACTED:10551 — _refreshValue has cognitive complexity 80 (threshold 15). Drivers by points: ternaries 14 (43 pts), if/else 13 (32 pts), boolean chains 5 (nesting depth added 48). Of this number, 34 points are the body's own statements and 46 belong to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · _doKeyDown (cognitive 76) · ×1
  • _doKeyDown (cognitive 76) REDACTED:7392 — _doKeyDown has cognitive complexity 76 (threshold 15). Drivers by points: if/else 15 (35 pts), ternaries 7 (26 pts), boolean chains 13, match/switch 1 (2 pts) (nesting depth added 40). 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.
D2 · Cognitive Complexity · J (cognitive 66) · ×1
  • J (cognitive 66) application/common/login2.js:5 — J has cognitive complexity 66 (threshold 15). Drivers by points: if/else 28 (44 pts), loops 7 (10 pts), boolean chains 5, ternaries 3 (4 pts), error handling 1 (3 pts) (nesting depth added 22). Most of this is not in the body itself: 1 of the 66 points is its own statement and the rest belongs to 26 function items inside it that branch (a function literal at line 5, S, v::x, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · parseDate (cognitive 60) · ×1
  • parseDate (cognitive 60) REDACTED:7854 — parseDate has cognitive complexity 60 (threshold 15). Drivers by points: if/else 20 (28 pts), ternaries 13 (14 pts), boolean chains 10, loops 3 (5 pts), match/switch 1 (3 pts) (nesting depth added 13). Of this number, 47 points are the body's own statements and 13 belong to 7 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · parseDate (cognitive 58) · ×1
  • parseDate (cognitive 58) application/common/js/calendar.js:4 — parseDate has cognitive complexity 58 (threshold 15). Drivers by points: if/else 17 (34 pts), boolean chains 11, loops 4 (8 pts), ternaries 2 (5 pts) (nesting depth added 24). 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.
D2 · Cognitive Complexity · _generatePosition (cognitive 58) · ×1
  • _generatePosition (cognitive 58) REDACTED:1161 — _generatePosition has cognitive complexity 58 (threshold 15). Drivers by points: ternaries 15 (31 pts), if/else 9 (21 pts), boolean chains 6 (nesting depth added 28). 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.
D2 · Cognitive Complexity · _generateMonthYearHeader (cognitive 55) · ×1
  • _generateMonthYearHeader (cognitive 55) REDACTED:8481 — _generateMonthYearHeader has cognitive complexity 55 (threshold 15). Drivers by points: ternaries 9 (27 pts), boolean chains 12, if/else 8 (11 pts), loops 2 (5 pts) (nesting depth added 24). Of this number, 46 points are the body's own statements and 9 belong to one function item inside it that branches. 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.
D2 · Cognitive Complexity · _mouseDrag (cognitive 52) · ×1
  • _mouseDrag (cognitive 52) REDACTED:3129 — _mouseDrag has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (34 pts), ternaries 3 (9 pts), boolean chains 8, loops 1 (nesting depth added 20). 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.
D2 · Cognitive Complexity · _generatePosition (cognitive 51) · ×1
  • _generatePosition (cognitive 51) REDACTED:3794 — _generatePosition has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 13 (25 pts), if/else 8 (18 pts), boolean chains 8 (nesting depth added 22). 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.
D2 · Cognitive Complexity · drag (cognitive 49) · ×1
  • drag (cognitive 49) REDACTED:1485 — drag has cognitive complexity 49 (threshold 15). Drivers by points: if/else 13 (35 pts), boolean chains 13, loops 1 (nesting depth added 22). 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.
D2 · Cognitive Complexity · formatDate (cognitive 48) · ×1
  • formatDate (cognitive 48) REDACTED:8036 — formatDate has cognitive complexity 48 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 7 (15 pts), boolean chains 6, loops 2 (4 pts), match/switch 1 (4 pts) (nesting depth added 22). Of this number, 42 points are the body's own statements and 6 belong to 3 function items inside it that branch. 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.
D2 · Cognitive Complexity · _init (cognitive 46) · ×1
  • _init (cognitive 46) application/common/js/calendar.js:4 — _init has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (32 pts), boolean chains 6, ternaries 4 (5 pts), loops 2 (3 pts) (nesting depth added 22). 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.
D2 · Cognitive Complexity · _clear (cognitive 46) · ×1
  • _clear (cognitive 46) REDACTED:3870 — _clear has cognitive complexity 46 (threshold 15). Drivers by points: if/else 19 (27 pts), loops 5 (10 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _keyEvent (cognitive 44) · ×1
  • _keyEvent (cognitive 44) application/common/js/calendar.js:4 — _keyEvent has cognitive complexity 44 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 12, match/switch 3 (8 pts), ternaries 1 (5 pts) (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · parse (cognitive 43) · ×1
  • parse (cognitive 43) application/common/ckeditor/plugins/bbcode/plugin.js:80 — parse has cognitive complexity 43 (threshold 15). Drivers by points: if/else 15 (38 pts), boolean chains 4, loops 1 (nesting depth added 23). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · _create (cognitive 42) · ×1
  • _create (cognitive 42) REDACTED:6519 — _create has cognitive complexity 42 (threshold 15). Drivers by points: if/else 23 (36 pts), boolean chains 5, ternaries 1 (nesting depth added 13). Most of this is not in the body itself: 11 of the 42 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 6596, 6649, 6546, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · PasswordassitAction.execute (cognitive 41) · ×1
  • PasswordassitAction.execute (cognitive 41) src/main/java/com/jdon/jivejdon/presentation/action/account/PasswordassitAction.java:44 — PasswordassitAction.execute has cognitive complexity 41 (threshold 15). Drivers by points: if/else 19 (36 pts), loops 1 (3 pts), boolean chains 1, error handling 1 (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.
D2 · Cognitive Complexity · base64image.CKEDITOR.dialog.add("base64imageDialog").onShow (cognitive 41) · ×1
  • base64image.CKEDITOR.dialog.add("base64imageDialog").onShow (cognitive 41) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:274 — base64image.CKEDITOR.dialog.add("base64imageDialog").onShow has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (33 pts), boolean chains 5, match/switch 1 (3 pts) (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.
D2 · Cognitive Complexity · (anonymous).onShow (cognitive 41) · ×1
  • (anonymous).onShow (cognitive 41) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:274 — (anonymous).onShow has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (33 pts), boolean chains 5, match/switch 1 (3 pts) (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.
D2 · Cognitive Complexity · bounce (cognitive 39) · ×1
  • bounce (cognitive 39) REDACTED:4617 — bounce has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 11 (19 pts), if/else 9 (11 pts), boolean chains 8, loops 1 (nesting depth added 10). None of this is in the body itself: all 39 points belong to 4 function literals inside it that branch (lines 4619, 4660, 4669, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · _contactContainers (cognitive 38) · ×1
  • _contactContainers (cognitive 38) REDACTED:3582 — _contactContainers has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 4 (11 pts), loops 2 (3 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · init · ×1
  • init::$ (cognitive 38) application/common/ckeditor/plugins/bbcode/plugin.js:622 — init::$ has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 6, match/switch 1 (3 pts), error handling 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AccountForm.doValidate (cognitive 37) · ×1
  • AccountForm.doValidate (cognitive 37) src/main/java/com/jdon/jivejdon/presentation/form/AccountForm.java:131 — AccountForm.doValidate has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (34 pts), boolean chains 3 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _create (cognitive 36) · ×1
  • _create (cognitive 36) REDACTED:9993 — _create has cognitive complexity 36 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 5, ternaries 2 (3 pts), match/switch 2, loops 1 (nesting depth added 11). Of this number, 17 points are the body's own statements and 19 belong to 8 function literals inside it that branch. 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.
D2 · Cognitive Complexity · initIframeAutogrow (cognitive 36) · ×1
  • initIframeAutogrow (cognitive 36) application/common/ckeditor/plugins/autogrow/plugin.js:30 — initIframeAutogrow has cognitive complexity 36 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 8, ternaries 6 (7 pts), loops 1 (nesting depth added 8). Most of this is not in the body itself: 6 of the 36 points are its own statements and the rest belongs to 7 function items inside it that branch (resizeEditor, refreshCache, a function literal at line 73, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · _mouseDrag (cognitive 35) · ×1
  • _mouseDrag (cognitive 35) REDACTED:2777 — _mouseDrag has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (29 pts), boolean chains 6 (nesting depth added 12). Most of this is not in the body itself: 3 of the 35 points are its own statements and the rest belongs to one function literal inside it that branches (line 2791). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · _showDatepicker (cognitive 35) · ×1
  • _showDatepicker (cognitive 35) REDACTED:7503 — _showDatepicker has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 10, ternaries 4 (6 pts) (nesting depth added 7). Of this number, 33 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
D2 · Cognitive Complexity · position (cognitive 35) · ×1
  • position (cognitive 35) REDACTED:9585 — position has cognitive complexity 35 (threshold 15). Drivers by points: if/else 19, boolean chains 9, ternaries 5 (7 pts) (nesting depth added 2). Of this number, 16 points are the body's own statements and 19 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · cellClick (cognitive 34) · ×1
  • cellClick (cognitive 34) application/common/js/calendar.js:4 — cellClick has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (29 pts), match/switch 1 (2 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 16). Of this number, 32 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
D2 · Cognitive Complexity · (anonymous).onOk (cognitive 34) · ×1
  • (anonymous).onOk (cognitive 34) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:346 — (anonymous).onOk has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (27 pts), match/switch 1 (3 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuoteFilter.reformatText (cognitive 33) · ×1
  • QuoteFilter.reformatText (cognitive 33) src/main/java/com/jdon/jivejdon/domain/model/message/output/html/QuoteFilter.java:203 — QuoteFilter.reformatText has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 3 (6 pts), ternaries 1 (2 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · base64image.CKEDITOR.dialog.add("base64imageDialog").onOk (cognitive 33) · ×1
  • base64image.CKEDITOR.dialog.add("base64imageDialog").onOk (cognitive 33) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:346 — base64image.CKEDITOR.dialog.add("base64imageDialog").onOk has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (27 pts), match/switch 1 (3 pts), boolean chains 1, error handling 1, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · plugin.CKEDITOR.htmlParser.fragment.fromBBCode (cognitive 33) · ×1
  • plugin.CKEDITOR.htmlParser.fragment.fromBBCode (cognitive 33) application/common/ckeditor/plugins/bbcode/plugin.js:177 — plugin.CKEDITOR.htmlParser.fragment.fromBBCode has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 22, if/else 5 (7 pts), loops 3 (4 pts) (nesting depth added 3). Most of this is not in the body itself: 8 of the 33 points are its own statements and the rest belongs to 7 function items inside it that branch (checkPendingBrs, checkPending, addElement, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · _setContainment (cognitive 33) · ×1
  • _setContainment (cognitive 33) REDACTED:1107 — _setContainment has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 8 (16 pts), boolean chains 11, if/else 5 (6 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.
D2 · Cognitive Complexity · drag (cognitive 33) · ×1
  • drag (cognitive 33) REDACTED:1425 — drag has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 6 (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.
D2 · Cognitive Complexity · PinyinUtils.toPinyin (cognitive 32) · ×1
  • PinyinUtils.toPinyin (cognitive 32) src/main/java/com/jdon/jivejdon/util/PinyinUtils.java:10 — PinyinUtils.toPinyin has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 2 (5 pts), boolean chains 4, error handling 1 (3 pts) (nesting depth added 16). 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.
D2 · Cognitive Complexity · _hideDatepicker (cognitive 32) · ×1
  • _hideDatepicker (cognitive 32) REDACTED:7666 — _hideDatepicker has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 8 (14 pts), boolean chains 3 (nesting depth added 16). 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.
D2 · Cognitive Complexity · jquery-ui.$.effects.size (cognitive 31) · ×1
  • jquery-ui.$.effects.size (cognitive 31) REDACTED:5046 — jquery-ui.$.effects.size has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 8, ternaries 2 (nesting depth added 7). None of this is in the body itself: all 31 points belong to 4 function literals inside it that branch (lines 5048, 5128, 5106, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · resize (cognitive 31) · ×1
  • resize (cognitive 31) REDACTED:2523 — resize has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (14 pts), ternaries 8 (14 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · explode (cognitive 31) · ×1
  • explode (cognitive 31) REDACTED:4766 — explode has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 11 (23 pts), boolean chains 4, loops 2 (3 pts), if/else 1 (nesting depth added 13). None of this is in the body itself: all 31 points belong to 2 function literals inside it that branch (lines 4768, 4815). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · (anonymous).imagePreview (cognitive 30) · ×1
  • (anonymous).imagePreview (cognitive 30) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:79 — (anonymous).imagePreview has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · base64image.CKEDITOR.dialog.add("base64imageDialog").imagePreview (cognitive 29) · ×1
  • base64image.CKEDITOR.dialog.add("base64imageDialog").imagePreview (cognitive 29) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:79 — base64image.CKEDITOR.dialog.add("base64imageDialog").imagePreview has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _toggle (cognitive 28) · ×1
  • _toggle (cognitive 28) REDACTED:5642 — _toggle has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 6, ternaries 3 (5 pts) (nesting depth added 8). Of this number, 26 points are the body's own statements and 2 belong to 2 function items inside it that branch. 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.
D2 · Cognitive Complexity · _resetButton (cognitive 27) · ×1
  • _resetButton (cognitive 27) REDACTED:6778 — _resetButton has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 3 (9 pts), boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AuthorNameFilter.getUsernameFromBody (cognitive 26) · ×1
  • AuthorNameFilter.getUsernameFromBody (cognitive 26) src/main/java/com/jdon/jivejdon/domain/model/message/infilter/AuthorNameFilter.java:30 — AuthorNameFilter.getUsernameFromBody has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 7, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · URLConverter.convertURL (cognitive 25) · ×1
  • URLConverter.convertURL (cognitive 25) src/main/java/com/jdon/jivejdon/domain/model/message/output/html/URLConverter.java:150 — URLConverter.convertURL has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 3, loops 1 (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.
D2 · Cognitive Complexity · _create (cognitive 25) · ×1
  • _create (cognitive 25) REDACTED:5883 — _create has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 4, match/switch 1 (nesting depth added 5). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 5898, focus, a function literal at line 5990, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · MessageForm.doValidate (cognitive 24) · ×1
  • MessageForm.doValidate (cognitive 24) src/main/java/com/jdon/jivejdon/presentation/form/MessageForm.java:260 — MessageForm.doValidate has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 6 (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.
D2 · Cognitive Complexity · IndexTag.doStartTag (cognitive 24) · ×1
  • IndexTag.doStartTag (cognitive 24) src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:34 — IndexTag.doStartTag has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 3, loops 2, error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · P (cognitive 24) · ×1
  • P (cognitive 24) application/common/login2.js:5 — P has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 24 points belong to 5 function items inside it that branch (a function literal at line 5, (anonymous)::onreadystatechange, (anonymous)::onreadystatechange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · create (cognitive 24) · ×1
  • create (cognitive 24) application/common/js/calendar.js:4 — create has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (12 pts), loops 5 (6 pts), ternaries 4, boolean chains 2 (nesting depth added 3). Of this number, 22 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · _slide (cognitive 24) · ×1
  • _slide (cognitive 24) REDACTED:10328 — _slide has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 5, ternaries 2 (5 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BlockStrategyFixed.locate (cognitive 23) · ×1
  • BlockStrategyFixed.locate (cognitive 23) src/main/java/com/jdon/jivejdon/util/BlockStrategyFixed.java:23 — BlockStrategyFixed.locate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · calendar.Calendar.tableMouseOver (cognitive 22) · ×1
  • calendar.Calendar.tableMouseOver (cognitive 22) application/common/js/calendar.js:4 — calendar.Calendar.tableMouseOver has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · calendar.Calendar.hideShowCovered (cognitive 22) · ×1
  • calendar.Calendar.hideShowCovered (cognitive 22) application/common/js/calendar.js:4 — calendar.Calendar.hideShowCovered has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). Of this number, 16 points are the body's own statements and 6 belong to one function item inside it that branches. 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.
D2 · Cognitive Complexity · drag (cognitive 22) · ×1
  • drag (cognitive 22) REDACTED:1803 — drag has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 5 (7 pts) (nesting depth added 3). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 1809). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · _respectSize (cognitive 22) · ×1
  • _respectSize (cognitive 22) REDACTED:2240 — _respectSize has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 10. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · _refreshItems (cognitive 22) · ×1
  • _refreshItems (cognitive 22) REDACTED:3457 — _refreshItems has cognitive complexity 22 (threshold 15). Drivers by points: loops 4 (8 pts), ternaries 2 (6 pts), if/else 2 (5 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _mouseStop (cognitive 21) · ×1
  • _mouseStop (cognitive 21) REDACTED:937 — _mouseStop has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 9, loops 1 (nesting depth added 3). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · _create · ×1
  • _create::_renderAxis (cognitive 21) REDACTED:1955 — _create::_renderAxis has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _mouseStart (cognitive 21) · ×1
  • _mouseStart (cognitive 21) REDACTED:3013 — _mouseStart has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · _setContainment (cognitive 21) · ×1
  • _setContainment (cognitive 21) REDACTED:3745 — _setContainment has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, ternaries 4 (8 pts), if/else 3 (nesting depth added 4). 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.
D2 · Cognitive Complexity · _attachments (cognitive 21) · ×1
  • _attachments (cognitive 21) REDACTED:7077 — _attachments has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 4 (8 pts), boolean chains 4 (nesting depth added 5). Of this number, 15 points are the body's own statements and 6 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · initialize (cognitive 20) · ×1
  • initialize (cognitive 20) REDACTED:1 — initialize has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 1 (nesting depth added 9). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 1, a function literal at line 1, a function literal at line 1, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · _getItemsAsjQuery (cognitive 20) · ×1
  • _getItemsAsjQuery (cognitive 20) REDACTED:3411 — _getItemsAsjQuery has cognitive complexity 20 (threshold 15). Drivers by points: loops 3 (6 pts), ternaries 2 (6 pts), if/else 2 (5 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _setOption (cognitive 20) · ×1
  • _setOption (cognitive 20) REDACTED:9275 — _setOption has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ToolsUtil.convertTagsFirst (cognitive 19) · ×1
  • ToolsUtil.convertTagsFirst (cognitive 19) src/main/java/com/jdon/jivejdon/domain/model/message/output/html/ToolsUtil.java:40 — ToolsUtil.convertTagsFirst has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · jquery-ui.$.ui.intersect (cognitive 19) · ×1
  • jquery-ui.$.ui.intersect (cognitive 19) REDACTED:1709 — jquery-ui.$.ui.intersect has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 17, if/else 1, match/switch 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D2 · Cognitive Complexity · cancel (cognitive 19) · ×1
  • cancel (cognitive 19) REDACTED:3248 — cancel has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 2, 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.
D2 · Cognitive Complexity · _optionDatepicker (cognitive 19) · ×1
  • _optionDatepicker (cognitive 19) REDACTED:7321 — _optionDatepicker has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3 (6 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · QuoteFilter.parseQuotes (cognitive 18) · ×1
  • QuoteFilter.parseQuotes (cognitive 18) src/main/java/com/jdon/jivejdon/domain/model/message/output/html/QuoteFilter.java:122 — QuoteFilter.parseQuotes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (5 pts), boolean chains 2, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EmailTask.addMessage (cognitive 18) · ×1
  • EmailTask.addMessage (cognitive 18) src/main/java/com/jdon/jivejdon/util/EmailTask.java:164 — EmailTask.addMessage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, error handling 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.
D2 · Cognitive Complexity · ejiaA1 (cognitive 18) · ×1
  • ejiaA1 (cognitive 18) application/forum/js/threadList.js:47 — ejiaA1 has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 3 (8 pts), loops 1 (nesting depth added 9). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (onclick, onmouseout, onmouseover). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · setDimensions (cognitive 18) · ×1
  • setDimensions (cognitive 18) REDACTED:1 — setDimensions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (18 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.
D2 · Cognitive Complexity · _showTooltip (cognitive 18) · ×1
  • _showTooltip (cognitive 18) REDACTED:1408 — _showTooltip has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 2, loops 1 (nesting depth added 4). 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.
D2 · Cognitive Complexity · prepareOffsets (cognitive 18) · ×1
  • prepareOffsets (cognitive 18) REDACTED:1759 — prepareOffsets has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 5, loops 2 (3 pts), ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · slide (cognitive 18) · ×1
  • slide (cognitive 18) REDACTED:5192 — slide has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8 (10 pts), boolean chains 5, if/else 3 (nesting depth added 2). None of this is in the body itself: all 18 points belong to 2 function items inside it that branch (a function literal at line 5194, (anonymous)::complete). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · fromBBCode · ×1
  • fromBBCode::onTagOpen (cognitive 18) application/common/ckeditor/plugins/bbcode/plugin.js:251 — fromBBCode::onTagOpen has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 4, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · afterInit (cognitive 18) · ×1
  • afterInit (cognitive 18) application/common/ckeditor/plugins/bbcode/plugin.js:738 — afterInit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4 (nesting depth added 6). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to one function literal inside it that branches (line 743). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · CodeHighlighter.highlightCode (cognitive 17) · ×1
  • CodeHighlighter.highlightCode (cognitive 17) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/CodeHighlighter.java:181 — CodeHighlighter.highlightCode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 3, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Newline.convertNewlinesAroundCode (cognitive 17) · ×1
  • Newline.convertNewlinesAroundCode (cognitive 17) src/main/java/com/jdon/jivejdon/domain/model/message/output/html/Newline.java:151 — Newline.convertNewlinesAroundCode has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ThreadApprovedNewList.loadApprovedThreads (cognitive 17) · ×1
  • ThreadApprovedNewList.loadApprovedThreads (cognitive 17) src/main/java/com/jdon/jivejdon/spi/component/mapreduce/ThreadApprovedNewList.java:161 — ThreadApprovedNewList.loadApprovedThreads has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (3 pts), boolean chains 1, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _createPlaceholder (cognitive 17) · ×1
  • _createPlaceholder (cognitive 17) REDACTED:3540 — _createPlaceholder has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 8 (nesting depth added 4). Most of this is not in the body itself: 3 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (update, element). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · drop (cognitive 17) · ×1
  • drop (cognitive 17) REDACTED:4727 — drop has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 5, if/else 3 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 2 function items inside it that branch (a function literal at line 4729, (anonymous)::complete). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · _create (cognitive 17) · ×1
  • _create (cognitive 17) REDACTED:5285 — _create has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 2 (nesting depth added 3). Of this number, 13 points are the body's own statements and 4 belong to 6 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · _determineButtonType (cognitive 17) · ×1
  • _determineButtonType (cognitive 17) REDACTED:6678 — _determineButtonType has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · _autoSize (cognitive 17) · ×1
  • _autoSize (cognitive 17) REDACTED:7116 — _autoSize has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (6 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 10). Of this number, 10 points are the body's own statements and 7 belong to one function item inside it that branches. 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.
D2 · Cognitive Complexity · _possibleChars (cognitive 17) · ×1
  • _possibleChars (cognitive 17) REDACTED:8113 — _possibleChars has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 2 belong to one function item inside it that branches. 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.
D2 · Cognitive Complexity · _position (cognitive 17) · ×1
  • _position (cognitive 17) REDACTED:9202 — _position has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 7). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. 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.
D2 · Cognitive Complexity · CodeViewer.keywordFilter (cognitive 16) · ×1
  • CodeViewer.keywordFilter (cognitive 16) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/CodeViewer.java:272 — CodeViewer.keywordFilter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 4). 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.
D2 · Cognitive Complexity · ForumMessage.build (cognitive 16) · ×1
  • ForumMessage.build (cognitive 16) src/main/java/com/jdon/jivejdon/domain/model/ForumMessage.java:404 — ForumMessage.build has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 2 (8 pts), if/else 4 (7 pts), error handling 1 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · RefererCaptchaAction.verifyAndRedirect (cognitive 16) · ×1
  • RefererCaptchaAction.verifyAndRedirect (cognitive 16) src/main/java/com/jdon/jivejdon/presentation/action/query/RefererCaptchaAction.java:135 — RefererCaptchaAction.verifyAndRedirect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RSSGenServlet.checkModifiedEtagFilter (cognitive 16) · ×1
  • RSSGenServlet.checkModifiedEtagFilter (cognitive 16) src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:95 — RSSGenServlet.checkModifiedEtagFilter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3 (nesting depth added 4). 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.
D2 · Cognitive Complexity · setup (cognitive 16) · ×1
  • setup (cognitive 16) REDACTED:1 — setup has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5 (6 pts), ternaries 3 (4 pts) (nesting depth added 2). None of this is in the body itself: all 16 points belong to 4 function items inside it that branch (a function literal at line 1, a function literal at line 1, $, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · bridge (cognitive 16) · ×1
  • bridge (cognitive 16) REDACTED:409 — bridge has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 3). None of this is in the body itself: all 16 points belong to 3 function literals inside it that branch (lines 410, 426, 446). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · refreshPositions (cognitive 16) · ×1
  • refreshPositions (cognitive 16) REDACTED:3499 — refreshPositions has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 4). 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.
D2 · Cognitive Complexity · scale (cognitive 16) · ×1
  • scale (cognitive 16) REDACTED:5004 — scale has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), boolean chains 5, ternaries 5 (nesting depth added 2). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 5006). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · _clickHandler (cognitive 16) · ×1
  • _clickHandler (cognitive 16) REDACTED:5556 — _clickHandler has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5 (6 pts), ternaries 4 (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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · ClassTooLong · ×1
  • ClassTooLong: MessageQueryDaoSql src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:44 — ClassTooLong — 438 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 38 over it, 1.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D31 · IaC & Container Security · Medium IaC · ×1
  • REDACTED
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: ForumMessageQueryServiceImp.java ↔ MessageQueryDaoSql.java src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:1 — `src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java` 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 `f7eb535e` removed load full forumThread; `725f96d8` directly fetch modifiedDate from db, instead of a huge ForumThread; `4b4a8684` fixed order by threadId — run `git show` on any of 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/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:101 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:101-132 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:134-165 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:289-323 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:333-368 — 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 · Edited copy of a member (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/CodeViewer.java:355 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/CodeViewer.java:355-409 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:986-1037 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) src/main/java/com/jdon/jivejdon/domain/model/query/QueryCriteria.java:76 — src/main/java/com/jdon/jivejdon/domain/model/query/QueryCriteria.java:76-102 | src/main/java/com/jdon/jivejdon/domain/model/query/QueryCriteria.java:133-156 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:356 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:356-374 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:376-393 — 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 · Members sharing a duplicated core (9 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (9 members, 50+ identical tokens) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:213 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:213-229 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:237-254 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:256-271 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:84-99 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:167-183 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:185-201 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:160-176 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:201-218 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:329-362 — These 9 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 9 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 9 times.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java:17 — src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java:17-27 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubForumListAction.java:33-43 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubTagListAction.java:17-27 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubThreadListAction.java:17-27 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (42–46 lines × 2) · ×1
  • Duplicated block (42–46 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:337 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:337-382 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:766-807 — 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/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:337` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:21 — src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:21-57 | src/main/java/com/jdon/jivejdon/util/FiltersUtils.java:35-71 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java` and `src/main/java/com/jdon/jivejdon/util/FiltersUtils.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 94 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/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:21` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (35 lines × 3) · ×1
  • Duplicated block (35 lines × 3) src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:89 — src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:89-123 | src/main/java/com/jdon/jivejdon/domain/model/message/output/html/HTMLFilter.java:53-87 | src/main/java/com/jdon/jivejdon/util/FiltersUtils.java:103-137 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java` and `src/main/java/com/jdon/jivejdon/util/FiltersUtils.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 94 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×1
  • Duplicated block (23 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:82 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:82-104 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:108-130 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:134-156 — 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/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/PropertyDaoSql.java:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) src/main/java/com/jdon/jivejdon/spi/component/throttle/hitkey/HitConf.java:31 — src/main/java/com/jdon/jivejdon/spi/component/throttle/hitkey/HitConf.java:31-51 | src/main/java/com/jdon/jivejdon/spi/component/throttle/post/NewUserThrottleConf.java:36-56 | src/main/java/com/jdon/jivejdon/spi/component/throttle/post/VIPUserThrottleConf.java:41-61 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/spi/component/throttle/hitkey/HitConf.java` and `src/main/java/com/jdon/jivejdon/spi/component/throttle/post/VIPUserThrottleConf.java` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/spi/component/throttle/post/NewUserThrottleConf.java:58` calls `parseInt` and `src/main/java/com/jdon/jivejdon/spi/component/throttle/hitkey/HitConf.java:53` 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.
D4 · Code Duplication · Duplicated block (15–17 lines × 3) · ×1
  • Duplicated block (15–17 lines × 3) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:429 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:429-444 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:466-480 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:501-517 — 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/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:429` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11–17 lines × 2) · ×1
  • Duplicated block (11–17 lines × 2) src/main/java/com/jdon/jivejdon/spi/pubsub/subscriber/MessageMovingListener.java:82 — src/main/java/com/jdon/jivejdon/spi/pubsub/subscriber/MessageMovingListener.java:82-92 | src/main/java/com/jdon/jivejdon/spi/pubsub/subscriber/postThread/ThreadPostListener.java:75-91 — 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/com/jdon/jivejdon/spi/pubsub/subscriber/MessageMovingListener.java:82` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:720 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:720-734 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:736-749 — 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/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:720` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×1
  • Duplicated block (14 lines × 3) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:414 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:414-427 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:452-465 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:500-513 — 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/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:414` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–14 lines × 3) · ×1
  • Duplicated block (12–14 lines × 3) src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:36 — src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:36-47 | src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java:44-57 | src/main/java/com/jdon/jivejdon/presentation/taglib/PrevTag.java:44-55 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java` and `src/main/java/com/jdon/jivejdon/presentation/taglib/PrevTag.java` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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.
D4 · Code Duplication · Duplicated block (11–14 lines × 2) · ×1
  • Duplicated block (11–14 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:190 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:190-200 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:254-267 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:190` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12–13 lines × 5) · ×1
  • Duplicated block (12–13 lines × 5) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:279 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:279-290 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:82-93 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:149-161 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:210-221 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:230-241 — there are 5 copies across 3 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 5 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:279` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:208` calls `debug` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:277` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 4) · ×1
  • Duplicated block (12–13 lines × 4) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:681 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:681-692 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:716-728 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:732-743 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:747-758 — 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.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:302 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:302-314 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:347-359 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:380-392 — 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/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:302` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:621 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:621-632 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:636-647 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:651-662 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:666-677 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ShortMessageDaoSql.java:204 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ShortMessageDaoSql.java:204-215 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ShortMessageDaoSql.java:219-230 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ShortMessageDaoSql.java:233-244 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×1
  • Duplicated block (9–10 lines × 5) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:238 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:238-247 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:85-93 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:169-177 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:187-195 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/SubscriptionDaoSql.java:162-170 — there are 5 copies across 3 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 5 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/ForumDaoSql.java:249` calls `debug` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:179` 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.
D4 · Code Duplication · Duplicated block (8–10 lines × 3) · ×1
  • Duplicated block (8–10 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:188 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:188-195 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:251-260 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:430-438 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:292 — src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:292-300 | src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:302-310 | src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:312-320 | src/main/java/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:322-330 — 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/com/jdon/jivejdon/domain/model/message/output/html/TextStyle.java:292` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×1
  • Duplicated block (8–9 lines × 4) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:125 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:125-132 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:158-165 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:315-323 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:360-368 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:125` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×1
  • Duplicated block (8–9 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:186 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:186-193 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:224-231 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:428-436 — 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.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×1
  • Duplicated block (9 lines × 3) src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:271 — src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:271-279 | src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:301-309 | src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:326-335 — 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/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java:271` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:71 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:71-79 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:173-180 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:80` calls `debug` and `src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/AccountSSOSql.java:181` 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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java:18 — src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java:18-25 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubForumListAction.java:34-41 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubTagListAction.java:18-25 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubThreadListAction.java:18-25 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java` and `src/main/java/com/jdon/jivejdon/presentation/action/sub/SubForumListAction.java` as WHOLE FILES: 83% 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 7) · ×1
  • Duplicated block (6–7 lines × 7) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:601 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:601-606 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:619-624 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:633-639 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:648-654 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:714-719 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:729-735 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:744-750 — all 7 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/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:601` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×1
  • Duplicated block (6–7 lines × 2) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:68 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:68-74 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:254-259 — 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 9) · ×1
  • Duplicated block (6 lines × 9) src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:602 — src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:602-607 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:620-625 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:635-640 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:650-655 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:665-670 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:680-685 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:715-720 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:731-736 | src/main/java/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:746-751 — all 9 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/com/jdon/jivejdon/domain/model/message/output/codeviewer/JavaCodeViewer.java:602` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×1
  • Duplicated block (6 lines × 5) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:364 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:364-369 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:383-388 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:312-317 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:357-362 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:390-395 — there are 5 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 5 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:364` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 7) · ×1
  • Duplicated block (5 lines × 7) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:364 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:364-368 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageDaoSql.java:383-387 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:312-316 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:357-361 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:390-394 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:145-149 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:372-376 — there are 7 copies across 3 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 7 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:254 — src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:254-258 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:143-147 | src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/sql/TagDaoSql.java:370-374 — there are 3 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 3 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/com/jdon/jivejdon/infrastructure/repository/dao/sql/MessageQueryDaoSql.java:254` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1
  • Duplicated block (17 lines × 3) src/main/java/com/jdon/jivejdon/domain/model/subscription/messsage/AccountNotifyMessage.java:15 — src/main/java/com/jdon/jivejdon/domain/model/subscription/messsage/AccountNotifyMessage.java:15-31 | src/main/java/com/jdon/jivejdon/domain/model/subscription/messsage/ForumNotifyMessage.java:24-40 | src/main/java/com/jdon/jivejdon/domain/model/subscription/messsage/TagNotifyMessage.java:9-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 all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) src/main/java/com/jdon/jivejdon/domain/model/attachment/UploadInfoVO.java:1 — src/main/java/com/jdon/jivejdon/domain/model/attachment/UploadInfoVO.java:1-71 | src/main/java/com/jdon/jivejdon/presentation/form/ImageInfoForm.java:1-40 — 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/com/jdon/jivejdon/domain/model/attachment/UploadInfoVO.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.
D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1
  • Duplicated block (38 lines × 2) src/main/java/com/jdon/jivejdon/spi/component/email/EmailContent.java:28 — src/main/java/com/jdon/jivejdon/spi/component/email/EmailContent.java:28-65 | src/main/java/com/jdon/jivejdon/spi/component/email/EmailVO.java:28-73 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/spi/component/email/EmailContent.java` and `src/main/java/com/jdon/jivejdon/spi/component/email/EmailVO.java` as WHOLE FILES: 95% 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. 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.
D4 · Code Duplication · Duplicated block (71 lines × 2) · ×1
  • Duplicated block (71 lines × 2) src/main/java/com/jdon/jivejdon/spi/pubsub/publish/MessageEventSourcingRole.java:1 — src/main/java/com/jdon/jivejdon/spi/pubsub/publish/MessageEventSourcingRole.java:1-71 | src/main/java/com/jdon/jivejdon/spi/pubsub/reconstruction/LazyLoaderRole.java:1-100 — 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/com/jdon/jivejdon/spi/pubsub/publish/MessageEventSourcingRole.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.
D4 · Code Duplication · Duplicated block (5 lines × 15) · ×1
  • Duplicated block (5 lines × 15) src/main/java/com/jdon/jivejdon/presentation/action/MaxThreadListAction.java:25 — src/main/java/com/jdon/jivejdon/presentation/action/MaxThreadListAction.java:25-29 | src/main/java/com/jdon/jivejdon/presentation/action/MessageForumListAction.java:40-45 | src/main/java/com/jdon/jivejdon/presentation/action/StickyListAction.java:31-35 | src/main/java/com/jdon/jivejdon/presentation/action/blog/UserFollowingThreadListAction.java:36-40 | src/main/java/com/jdon/jivejdon/presentation/action/blog/UserThreadListAction.java:35-39 | src/main/java/com/jdon/jivejdon/presentation/action/query/StickyThreadList.java:43-47 | src/main/java/com/jdon/jivejdon/presentation/action/query/TaggedThreadListAction.java:46-50 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedHomeListAction.java:37-42 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedNewListAction.java:19-23 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadDigSortedListAction.java:25-30 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadQueryAction.java:51-55 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadQueryUserAction.java:26-30 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagHotList2Action.java:29-33 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagListAction.java:40-45 | src/main/java/com/jdon/jivejdon/presentation/action/util/ThreadEtagFilter.java:36-41 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/action/blog/UserFollowingThreadListAction.java` and `src/main/java/com/jdon/jivejdon/presentation/action/blog/UserThreadListAction.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagHotList2Action.java:24` calls `getName` and `src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadApprovedNewListAction.java:15` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×1
  • Duplicated block (9 lines × 7) src/main/java/com/jdon/jivejdon/presentation/action/MaxThreadListAction.java:54 — src/main/java/com/jdon/jivejdon/presentation/action/MaxThreadListAction.java:54-62 | src/main/java/com/jdon/jivejdon/presentation/action/ThreadListAction.java:108-116 | src/main/java/com/jdon/jivejdon/presentation/action/query/TaggedThreadListAction.java:91-99 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadQueryAction.java:74-82 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadQueryUserAction.java:70-78 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagHotList2Action.java:82-90 | src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagListAction.java:75-83 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 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 7 times. 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.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java:35 — src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java:35-40 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubForumListAction.java:52-57 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubTagListAction.java:36-41 | src/main/java/com/jdon/jivejdon/presentation/action/sub/SubThreadListAction.java:36-41 — before extracting anything, compare `src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java` and `src/main/java/com/jdon/jivejdon/presentation/action/sub/SubForumListAction.java` as WHOLE FILES: 83% 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. 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: UploadHelper (LCOM4 4) src/main/java/com/jdon/jivejdon/domain/model/message/upload/UploadHelper.java:25 — UploadHelper's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 101 plain JS — the untyped files are application/admin/js/admin.js, REDACTED, application/common/ckeditor/build-config.js, application/common/ckeditor/config.js, application/common/ckeditor/lang/vi.js, application/common/ckeditor/plugins/autogrow/plugin.js (+95 more).
R10 · Code Duplication · Wholesale file copy (1081 identical lines × 2 files) · ×1
  • Wholesale file copy (1081 identical lines × 2 files) application/common/js/window.js:2 — application/common/js/window.js:2 · REDACTED:3 — these 2 files are line-for-line copies of one another — 1081 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (124 lines × 2 locations) · ×1
  • Duplicated block (124 lines × 2 locations) REDACTED:1157 — REDACTED:1157 · application/common/js/window_effects.js:1 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (65 lines × 2 locations) · ×1
  • Duplicated block (65 lines × 2 locations) REDACTED:1024 — REDACTED:1024 · REDACTED:3663 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (59 lines × 2 locations) · ×1
  • Duplicated block (59 lines × 2 locations) application/common/js/calendar-setup.js:1 — application/common/js/calendar-setup.js:1 · application/common/js/calendar.js:55 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (39 lines × 2 locations) · ×1
  • Duplicated block (39 lines × 2 locations) application/common/js/calendar-zh.js:2 — application/common/js/calendar-zh.js:2 · application/common/js/calendar.js:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (33 lines × 2 locations) · ×1
  • Duplicated block (33 lines × 2 locations) application/common/form.js:54 — application/common/form.js:54 · application/forum/js/form.js:159 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×1
  • Duplicated block (21 lines × 2 locations) REDACTED:6410 — REDACTED:6410 · REDACTED:6437 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×1
  • Duplicated block (20 lines × 2 locations) REDACTED:9496 — REDACTED:9496 · REDACTED:9521 — 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.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) REDACTED:865 — REDACTED:865 · REDACTED:3039 — 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.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1
  • Duplicated block (12 lines × 2 locations) REDACTED:4603 — REDACTED:4603 · REDACTED:4886 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (10 lines × 6 locations) · ×1
  • Duplicated block (10 lines × 6 locations) REDACTED:4715 — REDACTED:4715 · REDACTED:4754 · REDACTED:4844 · REDACTED:4928 · +2 more site(s) not listed — all 6 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×1
  • Duplicated block (9 lines × 2 locations) REDACTED:10372 — REDACTED:10372 · REDACTED:10386 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (8 lines × 4 locations) · ×1
  • Duplicated block (8 lines × 4 locations) REDACTED:4826 — REDACTED:4826 · REDACTED:4932 · REDACTED:4972 · REDACTED:5223 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (8 lines × 2 locations) · ×1
  • Duplicated block (8 lines × 2 locations) REDACTED:7247 — REDACTED:7247 · REDACTED:7272 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×1
  • Duplicated block (7 lines × 2 locations) REDACTED:6606 — REDACTED:6606 · REDACTED:6614 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (6 lines × 3 locations) · ×1
  • Duplicated block (6 lines × 3 locations) REDACTED:4630 — REDACTED:4630 · REDACTED:4736 · REDACTED:5158 — 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.
R2 · Cyclomatic Complexity · Complex function _generateHTML (cyclomatic 91, cognitive 210) · ×1
  • Complex function _generateHTML (cyclomatic 91, cognitive 210) REDACTED:8313 — _generateHTML has cyclomatic complexity 91 and cognitive complexity 210; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _doKeyDown (cyclomatic 45, cognitive 76) · ×1
  • Complex function _doKeyDown (cyclomatic 45, cognitive 76) REDACTED:7392 — _doKeyDown has cyclomatic complexity 45 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function drag (cyclomatic 44, cognitive 49) · ×1
  • Complex function drag (cyclomatic 44, cognitive 49) REDACTED:1485 — drag has cyclomatic complexity 44 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parseDate (cyclomatic 41, cognitive 47) · ×1
  • Complex function parseDate (cyclomatic 41, cognitive 47) REDACTED:7854 — parseDate has cyclomatic complexity 41 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function parseDate (cyclomatic 36, cognitive 58) · ×1
  • Complex function parseDate (cyclomatic 36, cognitive 58) application/common/js/calendar.js:4 — parseDate has cyclomatic complexity 36 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _keyEvent (cyclomatic 35, cognitive 44) · ×1
  • Complex function _keyEvent (cyclomatic 35, cognitive 44) application/common/js/calendar.js:4 — _keyEvent has cyclomatic complexity 35 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _generatePosition (cyclomatic 32, cognitive 58) · ×1
  • Complex function _generatePosition (cyclomatic 32, cognitive 58) REDACTED:1161 — _generatePosition has cyclomatic complexity 32 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _mouseDrag (cyclomatic 32, cognitive 52) · ×1
  • Complex function _mouseDrag (cyclomatic 32, cognitive 52) REDACTED:3129 — _mouseDrag has cyclomatic complexity 32 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _clear (cyclomatic 32, cognitive 46) · ×1
  • Complex function _clear (cyclomatic 32, cognitive 46) REDACTED:3870 — _clear has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function onShow (cyclomatic 31, cognitive 41) · ×1
  • Complex function onShow (cyclomatic 31, cognitive 41) application/common/ckeditor/plugins/base64image/dialogs/base64image.js:274 — onShow has cyclomatic complexity 31 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _generatePosition (cyclomatic 30, cognitive 51) · ×1
  • Complex function _generatePosition (cyclomatic 30, cognitive 51) REDACTED:3794 — _generatePosition has cyclomatic complexity 30 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _respectSize (cyclomatic 29, cognitive 22) · ×1
  • Complex function _respectSize (cyclomatic 29, cognitive 22) REDACTED:2240 — _respectSize has cyclomatic complexity 29 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function intersect (cyclomatic 29, cognitive 17) · ×1
  • Complex function intersect (cyclomatic 29, cognitive 17) REDACTED:1709 — intersect has cyclomatic complexity 29 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _tabify (cyclomatic 28, cognitive 43) · ×1
  • Complex function _tabify (cyclomatic 28, cognitive 43) REDACTED:10706 — _tabify has cyclomatic complexity 28 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _generateMonthYearHeader (cyclomatic 27, cognitive 46) · ×1
  • Complex function _generateMonthYearHeader (cyclomatic 27, cognitive 46) REDACTED:8481 — _generateMonthYearHeader has cyclomatic complexity 27 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function formatDate (cyclomatic 27, cognitive 42) · ×1
  • Complex function formatDate (cyclomatic 27, cognitive 42) REDACTED:8036 — formatDate has cyclomatic complexity 27 and cognitive complexity 42; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 27, cognitive 35) · ×1
  • Complex function (anonymous) (cyclomatic 27, cognitive 35) REDACTED:4619 — (anonymous) has cyclomatic complexity 27 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function _showDatepicker (cyclomatic 27, cognitive 33) · ×1
  • Complex function _showDatepicker (cyclomatic 27, cognitive 33) REDACTED:7503 — _showDatepicker has cyclomatic complexity 27 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 9688 lines of code REDACTED:1 — REDACTED has 9688 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · REDACTED · ×1
  • REDACTED: 1472 lines of code REDACTED:1 — REDACTED has 1472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · application/common/js/window.js · ×1
  • application/common/js/window.js: 1151 lines of code application/common/js/window.js:1 — application/common/js/window.js has 1151 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · application/common/ckeditor/plugins/bbcode/plugin.js · ×1
  • application/common/ckeditor/plugins/bbcode/plugin.js: 639 lines of code application/common/ckeditor/plugins/bbcode/plugin.js:1 — application/common/ckeditor/plugins/bbcode/plugin.js has 639 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · application/common/ckeditor/plugins/base64image/dialogs/base64image.js · ×1
  • application/common/ckeditor/plugins/base64image/dialogs/base64image.js: 444 lines of code application/common/ckeditor/plugins/base64image/dialogs/base64image.js:1 — application/common/ckeditor/plugins/base64image/dialogs/base64image.js has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R4 · Test Coverage · Test Coverage · ×1
  • Test Coverage — 0% of 101 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
R7 · Dead Code · Dead file (~11363 LoC) · ×1
  • Dead file (~11363 LoC) REDACTED — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~1545 LoC) · ×1
  • Dead file (~1545 LoC) REDACTED — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~1152 LoC) · ×1
  • Dead file (~1152 LoC) application/common/js/window.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~771 LoC) · ×1
  • Dead file (~771 LoC) application/common/ckeditor/plugins/bbcode/plugin.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~203 LoC) · ×1
  • Dead file (~203 LoC) application/forum/js/form.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~182 LoC) · ×1
  • Dead file (~182 LoC) application/common/login2.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~166 LoC) · ×1
  • Dead file (~166 LoC) application/common/ckeditor/build-config.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~163 LoC) · ×1
  • Dead file (~163 LoC) application/common/js/waitingfor.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~156 LoC) · ×1
  • Dead file (~156 LoC) application/common/js/window_effects.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~140 LoC) · ×1
  • Dead file (~140 LoC) application/forum/js/threadList.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~136 LoC) · ×1
  • Dead file (~136 LoC) application/common/ckeditor/styles.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~108 LoC) · ×1
  • Dead file (~108 LoC) application/common/js/calendar-setup.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~100 LoC) · ×1
  • Dead file (~100 LoC) application/common/form.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~70 LoC) · ×1
  • Dead file (~70 LoC) application/common/ckeditor/plugins/autosave/plugin.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~67 LoC) · ×1
  • Dead file (~67 LoC) application/common/js/pagination.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~61 LoC) · ×1
  • Dead file (~61 LoC) application/message/js/messageEdit.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~57 LoC) · ×1
  • Dead file (~57 LoC) application/common/ckeditor/plugins/base64image/plugin.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~50 LoC) · ×1
  • Dead file (~50 LoC) application/common/messageList12.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~47 LoC) · ×1
  • Dead file (~47 LoC) application/common/ckeditor/plugins/fixed/plugin.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~45 LoC) · ×1
  • Dead file (~45 LoC) application/common/js/calendar-zh.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~38 LoC) · ×1
  • Dead file (~38 LoC) application/common/ckeditor/config.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~17 LoC) · ×1
  • Dead file (~17 LoC) application/common/js/index2.js — no import path from any entry point (2 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity application/account/newAccount.jsp:36 — `https://ssl.captcha.qq.com/TCaptcha.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 15 such include(s) across the repository's markup.
X27 · Collection changed while being enumerated · Collection is structurally changed while it is being enumerated · ×1
  • Collection is structurally changed while it is being enumerated src/main/java/com/jdon/jivejdon/spi/component/subscription/SubscriptionActionHolder.java:65 — `subscriptionActions` is enumerated directly, and line 67 calls `subscriptionActions.remove(…)` inside the loop body — a structural change to a `ArrayList`. The loop's hidden iterator is fail-fast, so its next `next()` throws `ConcurrentModificationException`: every pass that reaches this call ends the loop by exception instead of by running out of elements, and the remaining elements are never seen.
Minor — 99 finding(s)
X4 · Structured logging · Interpolated log message defeats structured logging · ×40
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/ForumServiceImp.java:84 — `error` at line 84 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageServiceImpl.java:157 — `error` at line 157 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageServiceImpl.java:207 — `error` at line 207 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:67 — `debug` at line 67 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:70 — `error` at line 70 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:77 — `debug` at line 77 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:253 — `debug` at line 253 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:262 — `debug` at line 262 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:268 — `debug` at line 268 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:272 — `error` at line 272 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:284 — `debug` at line 284 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/message/ForumMessageQueryServiceImp.java:289 — `debug` at line 289 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:191 — `debug` at line 191 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:232 — `error` at line 232 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/shortmessage/ShortMessageServiceImp.java:251 — `error` at line 251 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/subscription/SubscriptionServiceImp.java:90 — `error` at line 90 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/subscription/SubscriptionServiceImp.java:140 — `error` at line 140 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/subscription/SubscriptionServiceImp.java:143 — `error` at line 143 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/upload/UploadServiceShell.java:54 — `debug` at line 54 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/upload/UploadServiceShell.java:81 — `error` at line 81 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/upload/UploadServiceShell.java:114 — `error` at line 114 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/upload/UploadServiceShell.java:166 — `debug` at line 166 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/impl/upload/UploadInfoVOServiceImp.java:97 — `error` at line 97 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/util/SessionContextUtil.java:66 — `debug` at line 66 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • Interpolated log message defeats structured logging src/main/java/com/jdon/jivejdon/api/util/SessionContextUtil.java:70 — `debug` at line 70 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
  • + 15 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×18
  • Duplicated predicate src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java:41 — `"int".equals(className) || "double".equals(className) || "long".equals(className)` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/domain/model/message/output/beanutil/FiltersUtils.java, src/main/java/com/jdon/jivejdon/util/FiltersUtils.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/auth/CUDInputInterceptor.java:112 — `(arg != null) && arg.getClass().isAssignableFrom(EventModel.class)` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/auth/CUDInputInterceptor.java, src/main/java/com/jdon/jivejdon/auth/PermissionInterceptor.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java:37 — `(dispStrs != null) && (!dispStrs.equals(""))` appears character-identically in 3 files — src/main/java/com/jdon/jivejdon/presentation/taglib/IndexTag.java, src/main/java/com/jdon/jivejdon/presentation/taglib/NextTag.java, src/main/java/com/jdon/jivejdon/presentation/taglib/PrevTag.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java:137 — `(maxLengthExceeded != null) && (maxLengthExceeded.booleanValue())` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/presentation/form/AccountFaceFileForm.java, src/main/java/com/jdon/jivejdon/presentation/form/UpLoadFileForm.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/action/MessageListOwnerAction.java:55 — `(threadId == null) || (!StringUtils.isNumeric(threadId)) || threadId.length() > 10` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/presentation/action/MessageListOwnerAction.java, src/main/java/com/jdon/jivejdon/presentation/action/util/ThreadEtagFilter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/domain/model/message/upload/UploadFileFilter.java:50 — `(uploadFiles == null) || (uploadFiles.size() == 0)` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/domain/model/message/upload/UploadFileFilter.java, src/main/java/com/jdon/jivejdon/domain/model/message/upload/UploadImageFilter.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java:20 — `(userId == null) || (!StringUtils.isNumeric(userId))` appears character-identically in 4 files — src/main/java/com/jdon/jivejdon/presentation/action/sub/SubAccountListAction.java, src/main/java/com/jdon/jivejdon/presentation/action/sub/SubForumListAction.java, src/main/java/com/jdon/jivejdon/presentation/action/sub/SubTagListAction.java, src/main/java/com/jdon/jivejdon/presentation/action/sub/SubThreadListAction.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/spi/component/throttle/hitkey/HitKeyDiff.java:56 — `UtilValidate.isEmpty(ip) || UtilValidate.isEmpty(id)` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/spi/component/throttle/hitkey/HitKeyDiff.java, src/main/java/com/jdon/jivejdon/spi/component/throttle/hitkey/HitKeySame.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/action/util/ForumEtagFilterAction.java:48 — `forumId != null && StringUtils.isNumeric(forumId) && forumId.length() <= 10` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/presentation/action/util/ForumEtagFilterAction.java, src/main/java/com/jdon/jivejdon/presentation/servlet/RSSGenServlet.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/domain/model/ForumThread.java:357 — `pinyinFromName != null && !pinyinFromName.trim().isEmpty()` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/domain/model/ForumThread.java, src/main/java/com/jdon/jivejdon/presentation/action/ThreadRedirectAction.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/servlet/RegisterCodeAction.java:114 — `registerCode == null || registerCode.length() == 0` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/presentation/servlet/RegisterCodeAction.java, src/main/java/com/jdon/jivejdon/presentation/servlet/VerifySpammerAction.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/action/query/TaggedThreadListAction.java:63 — `tagID == null || !StringUtils.isNumeric(tagID) || tagID.length() > 10` appears character-identically in 3 files — src/main/java/com/jdon/jivejdon/presentation/action/query/TaggedThreadListAction.java, src/main/java/com/jdon/jivejdon/presentation/action/query/ThreadTagHotList2Action.java, src/main/java/com/jdon/jivejdon/presentation/action/util/TagEtagFilterAction.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/action/ThreadRedirectAction.java:35 — `threadId == null || threadId.length() == 0 || !StringUtils.isNumeric(threadId) || threadId.length() > 20` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/presentation/action/ThreadRedirectAction.java, src/main/java/com/jdon/jivejdon/presentation/servlet/CounterServlet.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/spi/component/email/EmailVO.java:68 — `toEmail == null || fromEmail == null || subject == null || body == null` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/spi/component/email/EmailVO.java, src/main/java/com/jdon/jivejdon/util/EmailTask.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:71 — `userAgent != null && userAgent.length() > 0 && robotPattern.matcher(userAgent.toLowerCase()).matches()` appears character-identically in 2 files — REDACTED, src/main/java/com/jdon/jivejdon/presentation/servlet/RegisterCodeAction.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate src/main/java/com/jdon/jivejdon/presentation/form/BaseForm.java:65 — `value == null || value.trim().length() < 1` appears character-identically in 2 files — src/main/java/com/jdon/jivejdon/presentation/form/BaseForm.java, src/main/java/com/jdon/jivejdon/presentation/sitemap/UrlForm.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate application/common/form.js:18 — `document.getElementById('forumId_select') != null && document.getElementById('forumId_select').value == ""` appears character-identically in 2 files — application/common/form.js, application/forum/js/form.js. 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 application/common/form.js:69 — `myField.selectionStart || myField.selectionStart == '0'` appears character-identically in 2 files — application/common/form.js, application/forum/js/form.js. 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.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×9
  • Hand-rolled JSON/XML parsing via regex application/common/ckeditor/ckeditor.js:307 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex application/common/ckeditor/ckeditor.js:319 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex application/common/ckeditor/ckeditor.js:378 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex application/common/ckeditor/ckeditor.js:679 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex application/common/ckeditor/ckeditor.js:680 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex application/common/ckeditor/ckeditor.js:704 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex application/common/ckeditor/ckeditor.js:936 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex application/common/ckeditor/ckeditor.js:1179 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex src/main/java/com/jdon/jivejdon/util/TitleExtractor.java:34 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JVM code already uses a real parser in the same package; use it here too.
D31 · IaC & Container Security · Low IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX6 · Interface segregation · Fat interface · ×6
  • Fat interface: AccountService (21 abstract methods) src/main/java/com/jdon/jivejdon/api/account/AccountService.java:29 — `AccountService` declares 21 abstract methods: `checkUser`, `createAccount`, `deleteAccount`, `deletePasswordassit`, `forgetPasswd`, `getAccount`, `getAccountByName`, `getAccountByNameLike`, `getAccounts`, `getLoginAccountByName`, `getPasswordassit`, `getUserpropertys`, `getloginAccount`, `initAccount`, `insertPasswordassit`, `saveUserpropertys`, `update`, `updateAccount`, `updateAccountAttachment`, `updateAccountEmailValidate`, `updatePasswordassit`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ForumMessageQueryService (17 abstract methods) src/main/java/com/jdon/jivejdon/api/query/ForumMessageQueryService.java:11 — `ForumMessageQueryService` declares 17 abstract methods under just 14 distinct name(s): `getDigThreads`, `getHotThreads`, `getMesageListByUser`, `getMessage`, `getMessages`, `getMessages`, `getRecursiveMessages`, `getThread`, `getThreadListByUser`, `getThreadModifiedDate`, `getThreadName`, `getThreads`, `getThreads`, `getThreads`, `getThreadsPrevNext`, `searchMessages`, `searchThreads`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 14 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
  • Fat interface: ShortMessageService (17 abstract methods) src/main/java/com/jdon/jivejdon/api/shortmessage/ShortMessageService.java:38 — `ShortMessageService` declares 17 abstract methods: `checkReceiveShortMessages`, `deleInDraftMessage`, `deleteShortMessage`, `deleteUserAllShortMessage`, `deleteUserRecAllShortMessage`, `getFromShortMessage`, `getReceiveShortMessages`, `getSaveShortMessages`, `getSendShortMessages`, `getShortMessages`, `getToShortMessage`, `initShortMessage`, `saveInDraftMessage`, `saveShortMessage`, `sendInDraftMessage`, `sendShortMessage`, `updateShortMessage`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MessageDao (18 abstract methods) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/MessageDao.java:30 — `MessageDao` declares 18 abstract methods: `createMessage`, `createMessageReply`, `createThread`, `delReBlog`, `deleteMessage`, `deleteThread`, `getAnemicMessage`, `getMessageVOCore`, `getReBlogByFrom`, `getReBlogByTo`, `getThreadCore`, `getThreadRootMessageId`, `saveReBlog`, `updateForum`, `updateMessage`, `updateMovingForum`, `updateThread`, `updateThreadName`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MessageQueryDao (23 abstract methods) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/MessageQueryDao.java:33 — `MessageQueryDao` declares 23 abstract methods: `find`, `findThread`, `findThreadsAllCount`, `getDigThreadIDs`, `getForumLatestPostMessageId`, `getForumLatestThreadIds`, `getForumMessageCount`, `getHotThreadIDs`, `getLatestPostMessageId`, `getMesageListByUser`, `getMessageCount`, `getMessageCountOfUser`, `getMessages`, `getMessages`, `getThreadListByUser`, `getThreadModifiedDate`, `getThreadName`, `getThreads`, `getThreads`, `getThreads`, `getThreads`, `getThreadsPrevNext`, `getTreeModel`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 23 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: TagDao (17 abstract methods) src/main/java/com/jdon/jivejdon/infrastructure/repository/dao/TagDao.java:25 — `TagDao` declares 17 abstract methods under just 15 distinct name(s): `addThreadTag`, `checkThreadTagRelation`, `createTag`, `createThreadToken`, `delThreadTag`, `delThreadTag`, `delThreadToken`, `deleteTag`, `getTaggedThread`, `getTaggedThread`, `getThreadTag`, `getThreadTagByTitle`, `getThreadTagIDs`, `getThreadTags`, `getThreadToken`, `searchTitle`, `updateTag`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 17 separate responsibilities: a caller binds to 15 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 17 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch src/main/java/com/jdon/jivejdon/domain/model/account/AccountState.java:130 — `getSubscribedCount` swallows every exception into `return -1` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
  • Silent fallback default in catch src/main/java/com/jdon/jivejdon/domain/model/account/AccountState.java:122 — `getSubscriptionCount` swallows every exception into `return -1` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the Javadoc, and the row stops firing.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (64543 LoC, 588 module-visible types across 124 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D9 · Test Distribution · No tests found · ×1
  • No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (JUnit (with Kotest or MockK on Kotlin)) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M3 · Folder & project structure · No tests/ separation · ×1
  • No tests/ separation — Tests aren't grouped in a dedicated test folder — the test surface isn't separable from production code at a glance.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — 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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 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.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/114 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×1
  • Silent fallback default on parse failure src/main/java/com/jdon/jivejdon/domain/model/attachment/UploadFile.java:64 — `getOid` returns `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 Javadoc, 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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a091cc6235c74da2911fb819f65bcdf2/history.json --exit-code 0 --source .9artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a091cc6235c74da2911fb819f65bcdf2/tree.json --exit-code 0 --source .1artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .26artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .12artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .10artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep --config /opt/semgrep-rules/gdpr.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .2artifacts/raw/semgrep-gdpr.json
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a16529-2642-7144-9ef4-4770a3b26452 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 120 · Warnings: 657 · Recommendations: 99 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 19:49 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.

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