Public report of Blankj/AndroidUtilCode, published 13 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.3). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 13 November 2026, 12:59 UTC · Survey ID cd_cf5595868e2a42a283d46f94dc570b37

Blankj/AndroidUtilCode

Measured 13 November 2026, 12:58 UTC, at code version 7b4caf9

CAI score 51out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 1 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.

A medium codebase: 56,820 lines of product code in 21 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Maturity, 43

Findings by how serious they are

12 critical 398 serious 206 minor

19 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
13 November 2026, 12:58 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

42of 42 dimensions measured by tools.
604of 616 findings point to an exact file and line, so you can open each one in the code. The other 12 concern the repository as a whole, such as missing documentation.
42dimensions across 5 lenses, read from 56,820 lines of product code in 21 projects.
Chapters

Executive summary

Blankj/AndroidUtilCode falls short of our standard for production, in part because 173 files are no longer known to anyone active in the project. It scores 51 out of 100 and is rated Adequate, and eight of its 12 critical findings are security problems.

Maturity, at 43, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 9 points. Fixing the password or key in the code comes next, worth about 4 points. Raising Maturity to 70 would lift the score to about 57.

Four passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one place turns outside data straight into objects, which an attacker could use. Replacing each exposed password or key, pinning each tool to an exact version and reading outside data into plain values would close these risks. The four tests that check nothing need to check the result they produce.

The product code is 56,820 lines, about €60,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.

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.
Maturity 43 · counts for 47%Production Readiness 49 · counts for 26%Code Health 60 · counts for 14%Security and Compliance 61 · counts for 8%Architecture 97 · counts for 4%

If Maturity rose from 43 to 70, the lowest score rated Strong, the score would rise from 51 to about 57.

Code composition: what the lines of code are
Product code 90%Tests 10%
New since the last survey: 84 findings

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

  • Code Duplication · Edited copy of a member (34 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java
  • Code Duplication · Edited copy of a member (34 corresponding lines) lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java
  • Code Duplication · Edited copy of a member (33 corresponding lines) lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/fileExplorer/FileContentView.java
  • Code Duplication · Edited copy of a member (28 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java
  • Code Duplication · Edited copy of a member (16 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java
  • Code Duplication · Edited copy of a member (16 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java
  • Code Duplication · Edited copy of a member (29 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java
  • Code Duplication · Edited copy of a member (25 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java
  • Code Duplication · Edited copy of a member (26 corresponding lines) REDACTED
  • Code Duplication · Edited copy of a member (7 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java
  • Code Duplication · Edited copy of a member (27 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java
  • Code Duplication · Edited copy of a member (20 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java
  • Code Duplication · Edited copy of a member (23 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt
  • Code Duplication · Edited copy of a member (14 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java
  • Code Duplication · Edited copy of a member (20 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java
  • Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/helper/DialogHelper.kt
  • Code Duplication · Edited copy of a member (17 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java
  • Code Duplication · Edited copy of a member (17 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java
  • Code Duplication · Edited copy of a member (20 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java
  • Code Duplication · Edited copy of a member (18 corresponding lines) REDACTED
  • Code Duplication · Edited copy of a member (17 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/JsonUtils.java
  • Code Duplication · Edited copy of a member (19 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/BusUtils.java
  • Code Duplication · Edited copy of a member (22 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java
  • Code Duplication · Edited copy of a member (10 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java
  • Code Duplication · Edited copy of a member (19 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java
  • Code Duplication · Edited copy of a member (16 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java
  • Code Duplication · Edited copy of a member (15 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java
  • Code Duplication · Edited copy of a member (18 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java
  • Code Duplication · Edited copy of a member (17 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/brightness/BrightnessActivity.kt
  • Code Duplication · Edited copies of one member (8 members, 13+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java
  • Code Duplication · Edited copy of a member (14 corresponding lines) REDACTED
  • Code Duplication · Edited copy of a member (13 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/KeyboardUtils.java
  • Code Duplication · Edited copy of a member (15 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ResourceUtils.java
  • Code Duplication · Edited copy of a member (12 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java
  • Code Duplication · Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java
  • Code Duplication · Edited copy of a member (7 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java
  • Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java
  • Code Duplication · Edited copy of a member (16 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java
  • Code Duplication · Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java
  • Code Duplication · Edited copy of a member (16 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java
  • Code Duplication · Edited copies of one member (8 members, 12+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java
  • Code Duplication · Edited copies of one member (7 members, 12+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java
  • Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) REDACTED
  • Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java
  • Code Duplication · Edited copy of a member (10 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ClickUtils.java
  • Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/MetaDataUtils.java
  • Code Duplication · Edited copy of a member (10 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ServiceUtils.java
  • Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) lib/common/src/main/java/com/blankj/common/helper/PermissionHelper.kt
  • Code Duplication · Edited copy of a member (12 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ClickUtils.java
  • Code Duplication · Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java
  • Code Duplication · Edited copy of a member (15 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt
  • Code Duplication · Edited copy of a member (9 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java
  • Code Duplication · Edited copy of a member (15 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java
  • Code Duplication · Edited copies of one member (7 members, 11+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java
  • Code Duplication · Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java
  • Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/PhoneUtils.java
  • Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityAlpha.kt
  • Code Duplication · Edited copy of a member (12 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java
  • Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java
  • Code Duplication · Edited copies of one member (5 members, 9+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) REDACTED
  • Code Duplication · Edited copy of a member (12 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/PermissionUtils.java
  • Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java
  • Code Duplication · Edited copy of a member (5 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java
  • Code Duplication · Edited copies of one member (6 members, 7+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java
  • Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java
  • Code Duplication · Edited copy of a member (8 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java
  • Code Duplication · Edited copy of a member (6 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java
  • Code Duplication · Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/MessengerUtils.java
  • Code Duplication · Edited copy of a member (7 corresponding lines) lib/common/src/main/java/com/blankj/common/activity/CommonActivity.java
  • Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) feature/subutil/pkg/src/main/java/com/blankj/subutil/pkg/feature/dangerous/DangerousActivity.kt
  • Code Duplication · Edited copy of a member (9 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityColor.kt
  • Code Duplication · Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/BrightnessUtils.java
  • Code Duplication · Edited copy of a member (10 corresponding lines) lib/base/src/main/java/com/blankj/base/dialog/BaseDialog.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java
  • Code Duplication · Edited copy of a member (8 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AdaptScreenUtils.java
  • Code Duplication · Edited copy of a member (9 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java
  • Code Duplication · Edited copy of a member (4 corresponding lines) lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java
  • Code Duplication · Edited copy of a member (6 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/fragment/ChildFragment.kt
  • Code Duplication · Duplicated block (11 lines × 2) feature/subutil/pkg/src/main/java/com/blankj/subutil/pkg/feature/location/LocationActivity.kt
  • Code Duplication · Duplicated block (9 lines × 2) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt

We compare 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: 3 findings

These 3 critical or serious findings were in the previous survey, on 24 October 2026, and are gone from this one.

  • Code Duplication · Duplicated block (7 lines × 2) lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java
  • Code Duplication · Duplicated block (7 lines × 2) lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java
  • Code Duplication · Duplicated block (9 lines × 2) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt
Rebuild cost: about €60,000 · Estimate
Cost to rebuild€20,000 to €100,000, for 330 to 1,048 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 56,820 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
Raises the score by about 9 points · Low effort · Documentation Quality
2
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 4 points · Low effort · REDACTED Scanning
3
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with ArrayUtilsTest.java, TimeUtilsTest.java.
Raises the score by about 4 points · Low effort · Test Quality

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 €60,000 to build again, about 0.4 person-years of work. Its weakest lens is Maturity, at 43 (Weak). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Documentation finding(s) in Documentation Quality. Of all the actions in this report, it raises the score most for the work it takes: about 9 points for low effort, because it clears the 1 Documentation Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

180 modules, with 133 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 140 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 base.dialog2 base.mvp3 base.rv4 utilcode.util5 utildebug.base.rv6 utildebug.debug7 base8 common.dialog9 common.item10 subutil.export.api11 subutil.pkg.feature.location.LocationService12 utilcode.export.api13 utilcode.pkg.feature.api.other.export14 utildebug.base.view.listener15 utildebug.debug.tool16 common17 common.activity18 mock.subutil19 mock.utilcode20 utildebug.base.view21 utildebug.debug.tool.clearCache22 common.fragment23 launcher.app24 main.app25 main.pkg26 subutil.app27 subutil.pkg.feature.location28 utilcode.app29 utilcode.pkg.feature.activity30 utilcode.pkg.feature.click31 utilcode.pkg.feature.mvp32 utildebug.debug.tool.appInfo33 utildebug.debug.tool.deviceInfo34 utildebug.debug.tool.fileExplorer35 utildebug.menu36 subutil.app.SubUtilApp37 utilcode.pkg.feature.bar.status.fragment38 utilcode.pkg.feature.fragment39 utildebug.debug.tool.fileExplorer.image40 utildebug.debug.tool.fileExplorer.sp
1 base.dialog
2 base.mvp
3 base.rv
4 utilcode.util
5 utildebug.base.rv
6 utildebug.debug
7 base3
8 common.dialog4
9 common.item115
10 subutil.export.api1
11 subutil.pkg.feature.location.LocationService1
12 utilcode.export.api1
13 utilcode.pkg.feature.api.other.export1
14 utildebug.base.view.listener1
15 utildebug.debug.tool1
16 common1
17 common.activity2112
18 mock.subutil1
19 mock.utilcode2
20 utildebug.base.view43
21 utildebug.debug.tool.clearCache31
22 common.fragment1111
23 launcher.app1
24 main.app1
25 main.pkg2
26 subutil.app1
27 subutil.pkg.feature.location11
28 utilcode.app1
29 utilcode.pkg.feature.activity12
30 utilcode.pkg.feature.click11
31 utilcode.pkg.feature.mvp351
32 utildebug.debug.tool.appInfo211
33 utildebug.debug.tool.deviceInfo2112
34 utildebug.debug.tool.fileExplorer43115
35 utildebug.menu2552
36 subutil.app.SubUtilApp1
37 utilcode.pkg.feature.bar.status.fragment14
38 utilcode.pkg.feature.fragment113
39 utildebug.debug.tool.fileExplorer.image11
40 utildebug.debug.tool.fileExplorer.sp5332
Uses a module listed above itPart of a loopThe module itself
1 base.dialog2 base.mvp3 base.rv4 utilcode.util5 utildebug.base.rv6 utildebug.debug7 base8 common.dialog9 common.item10 subutil.export.api11 subutil.pkg.feature.location.LocationService12 utilcode.export.api13 utilcode.pkg.feature.api.other.export14 utildebug.base.view.listener15 utildebug.debug.tool16 common17 common.activity18 mock.subutil19 mock.utilcode20 utildebug.base.view21 utildebug.debug.tool.clearCache22 common.fragment23 launcher.app24 main.app25 main.pkg26 subutil.app27 subutil.pkg.feature.location28 utilcode.app29 utilcode.pkg.feature.activity30 utilcode.pkg.feature.click31 utilcode.pkg.feature.mvp32 utildebug.debug.tool.appInfo33 utildebug.debug.tool.deviceInfo34 utildebug.debug.tool.fileExplorer35 utildebug.menu36 subutil.app.SubUtilApp37 utilcode.pkg.feature.bar.status.fragment38 utilcode.pkg.feature.fragment39 utildebug.debug.tool.fileExplorer.image40 utildebug.debug.tool.fileExplorer.spbase.dialog1base.mvp2base.rv3utilcode.util4utildebug.base.rv5utildebug.debug6base7common.dialog8common.item9subutil.export.api10subutil.pkg.feature.location.LocationService11utilcode.export.api12utilcode.pkg.feature.api.other.export13utildebug.base.view.listener14utildebug.debug.tool15common16common.activity17mock.subutil18mock.utilcode19utildebug.base.view20utildebug.debug.tool.clearCache21common.fragment22launcher.app23main.app24main.pkg25subutil.app26subutil.pkg.feature.location27utilcode.app28utilcode.pkg.feature.activity29utilcode.pkg.feature.click30utilcode.pkg.feature.mvp31utildebug.debug.tool.appInfo32utildebug.debug.tool.deviceInfo33utildebug.debug.tool.fileExplorer34utildebug.menu35subutil.app.SubUtilApp36utilcode.pkg.feature.bar.status.fragment37utilcode.pkg.feature.fragment38utildebug.debug.tool.fileExplorer.image39utildebug.debug.tool.fileExplorer.sp4034115111111121121243311111112111112113512112112431152552114113115332+140 more modules (most-connected shown)

At a glance — Code Health · 60% · Adequate · gated by X5 ·

At a glance — Architecture · 97% · Exemplary ·

At a glance — Maturity · 43% · Weak · gated by D34, M2 ·

At a glance — Readiness · 49% · Weak · gated by P3 ·

At a glance — Security · 61% · Checked 4 of 10 · gated by D36 ·

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 — Injection16High / Critical
A07:2025 — Authentication Failures6High / Critical
A03:2025 — Software Supply Chain Failures5Medium

Roadmap

Top priorities: Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md; Resolve the 173 Orphaned file finding(s) in Knowledge Freshness — start with ZipUtils.java (2), BaseItemAdapter.java (2), BaseItem.java (2); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

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

Do thisHelpsEffortDimension
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.+9.1 ptsLowDocumentation Quality
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.+4.0 ptsLowREDACTED Scanning
Resolve the 2 Assertions commented out finding(s) in Test Quality — start with ArrayUtilsTest.java, TimeUtilsTest.java.+3.6 ptsLowTest Quality
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with BaseTest.java (2).+3.6 ptsLowTest Quality
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.+7.0 ptsMediumArchitecture documentation
Resolve the 85 No assertions finding(s) in Test Quality — start with LogUtilsTest.java (15), ThreadUtilsTest.java (14), BusUtilsTest.java (11).+4.9 ptsMediumTest Quality
Resolve the 173 Orphaned file finding(s) in Knowledge Freshness — start with ZipUtils.java (2), BaseItemAdapter.java (2), BaseItem.java (2).+8.5 ptsHighKnowledge Freshness
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+3.9 ptsMediumSecurity & performance tooling

File quality

Per-file score 0–10 — a quality signature. Of 113 files carrying findings, judged against the Production bar: 1% slop · 59% mixed · 40% near-clean.

FileScoreBandWorst signal
REDACTED2.1SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedREDACTED Scanning: Leaked secret: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): Medium: REDACTED
lib/utilcode/src/test/java/com/blankj/utilcode/util/ArrayUtilsTest.java5.4MixedTest Quality: Assertions commented out: asList
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
lib/utilcode/src/main/java/com/blankj/utilcode/util/ToastUtils.java5.9MixedCognitive Complexity: ActivityToast.cancel (cognitive 19)
lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java7.0MixedCyclomatic Complexity: LogFormatter.intent2String (cyclomatic 27)
lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java7.0MixedCyclomatic Complexity: ArrayUtils.forAllDo (cyclomatic 22)
lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java7.0MixedCognitive Complexity: ImageUtils.stackBlur (cognitive 30)
lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java7.0MixedCognitive Complexity: ZipUtils.unzipFileByKeyword (cognitive 24)
lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java7.0MixedTest Quality: No assertions: post
lib/utilcode/src/test/java/com/blankj/utilcode/util/LogUtilsTest.java7.0MixedTest Quality: No assertions: testA
lib/utilcode/src/test/java/com/blankj/utilcode/util/ThreadUtilsTest.java7.0MixedTest Quality: No assertions: cancelPoolTask
lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java7.0MixedCyclomatic Complexity: FragmentUtils.operate (cyclomatic 27)
lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java7.0MixedCyclomatic Complexity: NetworkUtils.getNetworkType (cyclomatic 27)
lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java7.0MixedCognitive Complexity: AppUtils.isAppRunning (cognitive 27)
lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java7.0MixedGod Classes: TooManyMethods: BaseItemAdapter
lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java7.0MixedCognitive Complexity: CollectionUtils.get (cognitive 23)

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

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

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

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

Could not be resolved — 19

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 42 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 42 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D17D19D26D27D28D29D34D35D36D44AX10AX3AX4AX6IC1M1M2M3P1P2P3P6X16X18X20X21X25X27X28X3X30X5

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, 604 of 616 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 or a scanner, 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
Canine Code Analyzer 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 · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1d4fd-622e-72a3-965b-8855778404ec.

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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because jcenter.bintray.com — the registry that answers it — was asked and did not reply (the build stopped because jcenter.bintray.com, a repository this project declares, refused it with HTTP 403 — what this scan's egress allowlist returns for a host that is not on it, so the dependency graph was not resolved). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add jcenter.bintray.com to the allowlist and re-run — not to build anything.
  • 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 (49 contributor(s) across 1433 commit(s) sampled, automation and bot accounts excluded). One of them holds 93% of the history; the other 48 hold 0.1% 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.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D20 ADR Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The ADR expectation is gated on whether a repository ships a deployable product. Our repo-kind classifier reads .NET project files and the host and package markers of the other ecosystems it knows (a Go `package main`, a Cargo binary, a package.json `bin`, `start` script or application dev server such as Vite or Next, Python console scripts or a Django/WSGI entry point, a Spring Boot / WAR / Gradle application build, a Rack or Rails app, a Composer project, an OTP release or escript, a Dockerfile, a Procfile, a Platform.sh `.platform/routes.yaml`, and the corresponding published-package manifests, including an OTP `*.app.src`, a Drupal module's `*.info` and a Claude Code `.claude-plugin/plugin.json`), and found none here, so we could not tell what kind of repository this is and did not assess its ADR log. This is a gap in our analyzer, not a finding about this repository. Read, stating neither a host nor a published package: `build.gradle`, `plugin/lib/base-transform/build.gradle`, `plugin/bus-gradle-plugin/build.gradle`, `plugin/buildSrc-plugin/build.gradle`, `plugin/api-gradle-plugin/build.gradle`, ….
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: a native UI project (lib/utildebug-no-op/src/main/AndroidManifest.xml). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java, Kotlin, groovy is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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.

Dimensions

D1 · Cyclomatic Complexity7.8 / 10Strong✓ 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 7.8 / 10 · rule-coverage 100% · ceiling Prevented

14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was UriUtils.uri2FileReal at 40.

UriUtils.uri2FileReal (cyclomatic 40)lib/utilcode/src/main/java/com/blankj/utilcode/util/UriUtils.java:97
SpanUtils.updateCharCharSequence (cyclomatic 31)lib/utilcode/src/main/java/com/blankj/utilcode/util/SpanUtils.java:857
FragmentUtils.operate (cyclomatic 27)lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1459
LogFormatter.intent2String (cyclomatic 27)lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:956
NetworkUtils.getNetworkType (cyclomatic 27)lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:440

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

What to do

  1. Bring the 14 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with UriUtils.uri2FileReal (cyclomatic 40), SpanUtils.updateCharCharSequence (cyclomatic 31), FragmentUtils.operate (cyclomatic 27). — 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 14 together lifts Cyclomatic Complexity from 7.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity6.1 / 10Adequate✓ 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 6.1 / 10 · rule-coverage 100% · ceiling Prevented

43 method(s) exceeded the cognitive complexity threshold of 15; the worst was UriUtils.uri2FileReal at 89.

ZipUtils.unzipFileByKeyword (cognitive 24) · ×2lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:284
ZipUtils.zipFile (cognitive 18) · ×2lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:191
UriUtils.uri2FileReal (cognitive 89)lib/utilcode/src/main/java/com/blankj/utilcode/util/UriUtils.java:97
PhoneUtils.getImeiOrMeid (cognitive 50)lib/utilcode/src/main/java/com/blankj/utilcode/util/PhoneUtils.java:112
FileUtils.isUtf8 (cognitive 47)REDACTED:983

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

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with UriUtils.uri2FileReal (cognitive 89). — Refactoring it lifts Cognitive Complexity from 6.1 to about 6.5/10.

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

D3 · God Classes6.9 / 10Adequate✓ 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 6.9 / 10 · rule-coverage 100% · ceiling Prevented

60 god class(es) detected.

TooManyMethods: ActivityUtils · ×36lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:37
ClassTooLong: ArrayUtils · ×12lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:22
FileTooLong: util/ArrayUtils.java · ×9lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java
MethodTooLong: ImageUtils.stackBlur · ×3lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1403

What to do

  1. Resolve the 36 TooManyMethods finding(s) in God Classes — start with LogUtils.java (2), BaseItemAdapter.java (2), ActivityUtils.java. — One of this dimension's main actionable groups (36 warning-level).
  2. Resolve the 12 ClassTooLong finding(s) in God Classes — start with ArrayUtils.java, ImageUtils.java, LogUtils.java. — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 9 FileTooLong finding(s) in God Classes — start with ArrayUtils.java, ImageUtils.java, LogUtils.java. — One of this dimension's main actionable groups (9 warning-level).

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

D4 · Code Duplication9.3 / 10Stronggated by 165 serious findings✓ 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 9.3 / 10 · rule-coverage 100% · ceiling Verified

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

Duplicated block (7 lines × 2) · ×15lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1601
Duplicated block (8 lines × 2) · ×9lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:867
Edited copy of a member (9 corresponding lines) · ×8lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:394
Duplicated block (11 lines × 2) · ×8lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:117
Edited copy of a member (11 corresponding lines) · ×6lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java:43

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

What to do

  1. Resolve the 15 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ArrayUtils.java (8), ShadowUtils.java, SwipeRightMenu.java. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 9 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with BaseItemAdapter.java (4), FileIOUtils.java, PhoneUtils.java. — One of this dimension's main actionable groups (9 warning-level).
  3. Resolve the 8 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with BatteryUtils.java (2), AppUtils.java, PhoneUtils.java. — One of this dimension's main actionable groups (8 warning-level).

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

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

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

21 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 19 of the 21 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.7 / 10Stronggated by 2 serious findings✓ 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.7 / 10 · rule-coverage 100% · ceiling Verified

2 of 81 classes have LCOM4 above 3.

Low cohesion: ToastUtils (LCOM4 8) · ×2lib/utilcode/src/main/java/com/blankj/utilcode/util/ToastUtils.java:53

What to do

  1. Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with ToastUtils.java, BaseFloatView.java. — One of this dimension's main actionable groups (2 warning-level).

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

D10 · Test Quality6.1 / 10Adequate✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 89 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 359 tests.

No assertions (empty test): test · ×2lib/subutil/src/test/java/com/blankj/subutil/util/BaseTest.java:32
Assertions commented out: asList · ×2lib/utilcode/src/test/java/com/blankj/utilcode/util/ArrayUtilsTest.java:185
No assertions: lunar2Solar · ×85lib/subutil/src/test/java/com/blankj/subutil/util/LunarUtilsTest.java:21
Test project verifies nothing: api-gradle-plugin · ×2plugin/api-gradle-plugin/src/test/java/com/blankj/api/ApiTest.java:27

What to do

  1. Resolve the 85 No assertions finding(s) in Test Quality — start with LogUtilsTest.java (15), ThreadUtilsTest.java (14), BusUtilsTest.java (11). — One of this dimension's main actionable groups (85 warning-level).
  2. Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with BaseTest.java (2). — One of this dimension's main actionable groups (2 issue-level).
  3. Resolve the 2 Assertions commented out finding(s) in Test Quality — start with ArrayUtilsTest.java, TimeUtilsTest.java. — One of this dimension's main actionable groups (2 issue-level).

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

D13 · REDACTED Scanning5.0 / 10Adequate✓ Tool-verified

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 5.0 / 10 · rule-coverage 100% · ceiling Prevented

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

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

0 of 1 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 22 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure.

✓ On the Gold path — maintain.

Detailed fixes: d14_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 Debt10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 deducted task-comment markers across 56820 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation Quality0.0 / 10Critical✓ Tool-verified

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

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

0 of 1 documentation facets pass in full; short on: F2 example. 9 document(s) read across 1 unit(s).

Documentation: no build, run or usage exampleREADME.md:1

What to do

  1. Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).

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

D26 · Project Cohesion7.9 / 10Strong✓ 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.

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

2 of 19 build units (Gradle) 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 · Navigability9.6 / 10Exemplary✓ 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 9.6 / 10 · rule-coverage 100% · ceiling Documented

38 % of calls cross a namespace and 9 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. 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)6.0 / 10Adequate✓ 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 6.0 / 10 · rule-coverage 100% · ceiling Documented

16 finding(s): 0 critical, 3 high, 4 medium, 9 low. 2 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (lines 160–161, line 162, line 163, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
  3. No action in Static Analysis (SAST) — all 2 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (2 issue-level, 0 of them charged here).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

176 of 176 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/subutil/src/main/java/com/blankj/subutil/util/PinyinUtils.java. Counted over 176 of the 324 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×173lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1
Most significant orphaned file · ×3lib/subutil/src/main/java/com/blankj/subutil/util/PinyinUtils.java:1
Dormant codebase

What to do

  1. Resolve the 173 Orphaned file finding(s) in Knowledge Freshness — start with ZipUtils.java (2), BaseItemAdapter.java (2), BaseItem.java (2). — One of this dimension's main actionable groups (173 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with PinyinUtils.java, ActivityUtils.java, ImageUtils.java. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

D35 · Change Coupling10.0 / 10Exemplary✓ 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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

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 1 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.

AX10 · Code composition9.8 / 10Exemplary✓ 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.

AX6 · Interface segregation10.0 / 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.

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)6.5 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • 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 documentation0.0 / 10Critical✓ 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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

What to do

  • Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability6.0 / 10Adequate✓ 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.

  • Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `lib/subutil`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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

  • Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene10.0 / 10Exemplary✓ 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.

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.

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.

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.

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.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.

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

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.

X3 · Exception handling6.1 / 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. (×7) — lib/utildebug/src/main/java/com/blankj/utildebug/base/view/BaseFloatView.java:66, lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:138, lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:578, …
  • `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. (×14) — lib/utilcode/src/main/java/com/blankj/utilcode/util/AdaptScreenUtils.java:161, lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:399, lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:414, …

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.

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/53 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).

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 Health60%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture97%ExemplaryStrongest area.
Maturity43%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness49%Weak — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security61%Checked 4 of 10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 2 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 — 6 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 — 5 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.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
  • D12 Dependency Hygiene — Dependency currency not established — jcenter.bintray.com did not answer
  • 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.
  • D20 ADR Quality — Repository kind not determined
  • D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, Kotlin not measured.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (5 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • 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.
  • M4 Documentation accuracy — Not applicable: the 9 current-state document(s) make no claim of a kind M4 checks. 2 claim(s) of kinds M4 does not check were not checked (path 2); M4 checks only links and versions and artefact counts.
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X12 Unreachable branch — X12 reached only 10% of this repository's production lines — java (50,744 lines), groovy (1,284 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • 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 — 12 finding(s)
D28 · Secrets (history) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · No assertions (empty test) · ×2
  • No assertions (empty test): test lib/subutil/src/test/java/com/blankj/subutil/util/BaseTest.java:32 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): test lib/utilcode/src/test/java/com/blankj/utilcode/util/BaseTest.java:43 — Test method has an empty body — it asserts nothing and exercises no code.
D10 · Test Quality · Assertions commented out · ×2
  • Assertions commented out: asList lib/utilcode/src/test/java/com/blankj/utilcode/util/ArrayUtilsTest.java:185 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
  • Assertions commented out: getFitTimeSpanByNow lib/utilcode/src/test/java/com/blankj/utilcode/util/TimeUtilsTest.java:128 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D13 · REDACTED Scanning · Leaked secret · ×1
  • REDACTED
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 398 finding(s)
D10 · Test Quality · No assertions · ×85
  • No assertions: lunar2Solar lib/subutil/src/test/java/com/blankj/subutil/util/LunarUtilsTest.java:21 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: lunarYear2GanZhi lib/subutil/src/test/java/com/blankj/subutil/util/LunarUtilsTest.java:16 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: solar2Lunar lib/subutil/src/test/java/com/blankj/subutil/util/LunarUtilsTest.java:26 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: getApi lib/utilcode/src/test/java/com/blankj/utilcode/util/ApiUtilsTest.java:22 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: toString_ lib/utilcode/src/test/java/com/blankj/utilcode/util/ApiUtilsTest.java:27 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: forAllDo lib/utilcode/src/test/java/com/blankj/utilcode/util/ArrayUtilsTest.java:200 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: newArray lib/utilcode/src/test/java/com/blankj/utilcode/util/ArrayUtilsTest.java:19 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: sort lib/utilcode/src/test/java/com/blankj/utilcode/util/ArrayUtilsTest.java:193 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: post lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:210 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: postSticky lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:225 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: registerAndUnregister lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:192 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: removeSticky lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:259 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testBase lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:306 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testEventBusSticky lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:112 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testMultiThread lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:144 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSameTag lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:316 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testSticky lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:128 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: testThreadMode lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:286 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: toString_ lib/utilcode/src/test/java/com/blankj/utilcode/util/BusUtilsTest.java:301 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: forAllDo lib/utilcode/src/test/java/com/blankj/utilcode/util/CollectionUtilsTest.java:181 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: getCardinalityMap lib/utilcode/src/test/java/com/blankj/utilcode/util/CollectionUtilsTest.java:105 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: intersection lib/utilcode/src/test/java/com/blankj/utilcode/util/CollectionUtilsTest.java:41 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: rc4 lib/utilcode/src/test/java/com/blankj/utilcode/util/EncryptUtilsTest.java:414 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: readFile2Bytes lib/utilcode/src/test/java/com/blankj/utilcode/util/FileIOUtilsTest.java:77 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: readFile2List lib/utilcode/src/test/java/com/blankj/utilcode/util/FileIOUtilsTest.java:63 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 60 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×36
  • TooManyMethods: ActivityUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:37 — TooManyMethods — 135 methods. The bar is 30 methods; this is 105 over it, 4.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ArrayUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:22 — TooManyMethods — 125 methods. The bar is 30 methods; this is 95 over it, 4.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ImageUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:67 — TooManyMethods — 114 methods. The bar is 30 methods; this is 84 over it, 3.80× 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: UtilsBridge lib/utilcode/src/main/java/com/blankj/utilcode/util/UtilsBridge.java:48 — TooManyMethods — 114 methods. The bar is 30 methods; this is 84 over it, 3.80× 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: TimeUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/TimeUtils.java:29 — TooManyMethods — 106 methods. The bar is 30 methods; this is 76 over it, 3.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FragmentUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:33 — TooManyMethods — 103 methods. The bar is 30 methods; this is 73 over it, 3.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: FileUtils REDACTED:37 — TooManyMethods — 92 methods. The bar is 30 methods; this is 62 over it, 3.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CacheDoubleStaticUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDoubleStaticUtils.java:22 — TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: EncryptUtils REDACTED:34 — TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CacheDiskStaticUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskStaticUtils.java:23 — TooManyMethods — 74 methods. The bar is 30 methods; this is 44 over it, 2.47× 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: ThreadUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ThreadUtils.java:37 — TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: AppUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:32 — TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SPStaticUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/SPStaticUtils.java:17 — TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SpanUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/SpanUtils.java:73 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× 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: ConvertUtils REDACTED:39 — TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LogUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:62 — 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: BaseItemAdapter lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:21 — 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: FileIOUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:36 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BarUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:40 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: NetworkUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:54 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× 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: CacheDiskUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java:34 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× 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: CollectionUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:28 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: UtilsActivityLifecycleImpl lib/utilcode/src/main/java/com/blankj/utilcode/util/UtilsActivityLifecycleImpl.java:31 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: BaseItemAdapter lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java:21 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PathUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/PathUtils.java:17 — TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× 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.
  • + 11 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×15
  • Duplicated block (7 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1601 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1601-1607 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1615-1621 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1601` 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1648 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1648-1654 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1662-1668 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1648` 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1695 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1695-1701 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1709-1715 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1695` 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1742 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1742-1748 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1756-1762 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1742` 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1789 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1789-1795 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1803-1809 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1789` 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1836 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1836-1842 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1850-1856 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1836` 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1883 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1883-1889 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1897-1903 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1883` 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1930 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1930-1936 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1944-1950 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1930` 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:384 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:384-390 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:398-404 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:384` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java:231 — lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java:231-237 | lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java:266-272 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:294 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:294-300 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:304-310 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:294` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:311` calls `contains` and `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:301` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:137 — lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:137-143 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java:128-134 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 2) lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:131 — lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:131-137 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.java:132-138 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:143 — lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:143-149 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:358-364 — 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 (7 lines × 2) lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:130 — lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:130-136 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:903-909 — 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×14
  • Swallowed exception (caught, then discarded) lib/utilcode/src/main/java/com/blankj/utilcode/util/AdaptScreenUtils.java:161 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:399 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:414 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:131 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:592 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1966 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/LanguageUtils.java:279 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ProcessUtils.java:248 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ServiceUtils.java:234 — `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) lib/utilcode/src/main/java/com/blankj/utilcode/util/UriUtils.java:207 — `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) lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:64 — `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) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:236 — `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) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:258 — `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) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:278 — `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.
D3 · God Classes · ClassTooLong · ×12
  • ClassTooLong: ArrayUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:22 — ClassTooLong — 1201 significant lines (blank, comment-only and punctuation-only lines excluded), 125 methods. The bar is 400 significant lines; this is 801 over it, 3.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ImageUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:67 — ClassTooLong — 1096 significant lines (blank, comment-only and punctuation-only lines excluded), 114 methods. The bar is 400 significant lines; this is 696 over it, 2.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: LogUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:62 — ClassTooLong — 812 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 412 over it, 2.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ActivityUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:37 — ClassTooLong — 809 significant lines (blank, comment-only and punctuation-only lines excluded), 135 methods. The bar is 400 significant lines; this is 409 over it, 2.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: FragmentUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:33 — ClassTooLong — 739 significant lines (blank, comment-only and punctuation-only lines excluded), 103 methods. The bar is 400 significant lines; this is 339 over it, 1.85× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SpanUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/SpanUtils.java:73 — ClassTooLong — 703 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 400 significant lines; this is 303 over it, 1.76× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ThreadUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ThreadUtils.java:37 — ClassTooLong — 572 significant lines (blank, comment-only and punctuation-only lines excluded), 70 methods. The bar is 400 significant lines; this is 172 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.
  • ClassTooLong: FileUtils REDACTED:37 — ClassTooLong — 550 significant lines (blank, comment-only and punctuation-only lines excluded), 92 methods. The bar is 400 significant lines; this is 150 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: NetworkUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:54 — ClassTooLong — 473 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 73 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ToastUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ToastUtils.java:53 — ClassTooLong — 448 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. The bar is 400 significant lines; this is 48 over it, 1.12× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: AppUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:32 — ClassTooLong — 435 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 400 significant lines; this is 35 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ShadowUtils lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:34 — ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 9 over it, 1.02× 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.
D3 · God Classes · FileTooLong · ×9
  • FileTooLong: util/ArrayUtils.java lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java — FileTooLong — 1211 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: ArrayUtils (22-2143). The bar is 500 significant lines; this is 711 over it, 2.42× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: util/ImageUtils.java lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java — FileTooLong — 1150 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ImageUtils (67-2374). The bar is 500 significant lines; this is 650 over it, 2.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: util/LogUtils.java lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java — FileTooLong — 859 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: LogUtils (62-1231). The bar is 500 significant lines; this is 359 over it, 1.72× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: util/ActivityUtils.java lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java — FileTooLong — 833 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ActivityUtils (37-2136). The bar is 500 significant lines; this is 333 over it, 1.67× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: util/SpanUtils.java lib/utilcode/src/main/java/com/blankj/utilcode/util/SpanUtils.java — FileTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: SpanUtils (73-1465). The bar is 500 significant lines; this is 262 over it, 1.52× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: util/FragmentUtils.java lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java — FileTooLong — 759 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: FragmentUtils (33-1881). The bar is 500 significant lines; this is 259 over it, 1.52× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: util/ThreadUtils.java lib/utilcode/src/main/java/com/blankj/utilcode/util/ThreadUtils.java — FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: ThreadUtils (37-1391). The bar is 500 significant lines; this is 96 over it, 1.19× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: FileUtils (37-1456). The bar is 500 significant lines; this is 74 over it, 1.15× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: util/NetworkUtils.java lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java — FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: NetworkUtils (54-1063). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×9
  • Duplicated block (8 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:867 — lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:867-874 | lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:911-918 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:867` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/PhoneUtils.java:195 — lib/utilcode/src/main/java/com/blankj/utilcode/util/PhoneUtils.java:195-202 | lib/utilcode/src/main/java/com/blankj/utilcode/util/RomUtils.java:429-436 — 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 (8 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java:44 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java:44-51 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java:61-68 — 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 (8 lines × 2) lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:72 — lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:72-79 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java:63-70 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:111 — lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:111-118 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java:102-109 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:120 — lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:120-127 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java:111-118 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:282 — lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:282-289 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java:246-253 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/fileExplorer/FileItem.java:236 — lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/fileExplorer/FileItem.java:236-243 | lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/fileExplorer/sp/SpItem.java:134-141 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `items` to `List<FileItem>` in one and `List<SpItem>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (8 lines × 2) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/messenger/MessengerActivity.kt:58 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/messenger/MessengerActivity.kt:58-65 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/messenger/MessengerRemoteActivity.kt:62-69 — 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 after the matched lines, `feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/messenger/MessengerRemoteActivity.kt:73` calls `unsubscribe` and `feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/messenger/MessengerActivity.kt:69` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×8
  • Edited copy of a member (9 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:394 — lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:394-402 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:409-417 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/PhoneUtils.java:194 — lib/utilcode/src/main/java/com/blankj/utilcode/util/PhoneUtils.java:194-202 | lib/utilcode/src/main/java/com/blankj/utilcode/util/RomUtils.java:428-436 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:109 — lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:109-117 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:882-890 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) REDACTED:120 — REDACTED:120-129 | REDACTED:137-145 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/PermissionUtils.java:156 — lib/utilcode/src/main/java/com/blankj/utilcode/util/PermissionUtils.java:156-164 | lib/utilcode/src/main/java/com/blankj/utilcode/util/PermissionUtils.java:187-195 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityColor.kt:34 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityColor.kt:34-42 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/fragment/BarStatusFragmentColor.kt:46-54 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:59 — lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:59-67 | lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:273-281 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:820 — lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:820-831 | lib/utilcode/src/main/java/com/blankj/utilcode/util/UtilsActivityLifecycleImpl.java:118-126 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×8
  • Duplicated block (11 lines × 2) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:117 — lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:117-127 | lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:173-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. Read the line range as the matched WINDOW rather than a finished unit: at `lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:117` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:204 — lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:204-214 | lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:54-64 — 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 (11 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:464 — lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:464-474 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NotificationUtils.java:161-171 — 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 (11 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/MessengerUtils.java:135 — lib/utilcode/src/main/java/com/blankj/utilcode/util/MessengerUtils.java:135-145 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ServiceUtils.java:74-84 — 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 (11 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:372 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:372-382 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:386-396 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:179 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:179-189 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:177-187 — before extracting anything, compare `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java` and `plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:414 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:414-424 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:412-422 — before extracting anything, compare `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java` and `plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (11 lines × 2) feature/subutil/pkg/src/main/java/com/blankj/subutil/pkg/feature/location/LocationActivity.kt:36 — feature/subutil/pkg/src/main/java/com/blankj/subutil/pkg/feature/location/LocationActivity.kt:36-46 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/network/NetworkActivity.kt:30-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.
X3 · Exception handling · Swallowed exception (empty catch) · ×7
  • Swallowed exception (empty catch) lib/utildebug/src/main/java/com/blankj/utildebug/base/view/BaseFloatView.java: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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:138 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:578 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/MessengerUtils.java:231 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/UriUtils.java:224 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/UtilsActivityLifecycleImpl.java:326 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/UtilsActivityLifecycleImpl.java:331 — 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.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×6
  • Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java:43 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java:43-53 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java:60-70 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:167 — lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:167-178 | lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:185-195 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:146 — lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:146-156 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:173-183 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:689 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:689-699 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:817-827 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/MessengerUtils.java:155 — lib/utilcode/src/main/java/com/blankj/utilcode/util/MessengerUtils.java:155-165 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MessengerUtils.java:338-349 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/BrightnessUtils.java:64 — lib/utilcode/src/main/java/com/blankj/utilcode/util/BrightnessUtils.java:64-74 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ScreenUtils.java:351-361 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×6
  • Duplicated block (10 lines × 2) lib/base/src/main/java/com/blankj/base/rv/BaseItem.java:30 — lib/base/src/main/java/com/blankj/base/rv/BaseItem.java:30-39 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItem.java:27-36 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/BaseItem.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItem.java` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (10 lines × 2) REDACTED:181 — REDACTED:181-190 | REDACTED:1263-1272 — 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 `REDACTED:181` 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.
  • Duplicated block (10 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:384 — lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:384-393 | lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:470-479 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:384` 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.
  • Duplicated block (10 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1186 — lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1186-1195 | lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1218-1227 — 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 (10 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:398 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:398-407 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:411-420 — 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) lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:63 — lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:63-72 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.java:64-73 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×5
  • Edited copy of a member (16 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:58 — lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:58-73 | lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:82-97 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:165 — lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:165-180 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:235-251 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:63 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:63-78 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:61-76 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1999 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1999-2014 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:2075-2091 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1430 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1430-1445 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1472-1489 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×5
  • Duplicated block (9 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1455 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1455-1463 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1534-1542 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:429 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:429-437 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:459-467 — 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) lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:149 — lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:149-157 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java:140-148 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:453 — lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:453-461 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NotificationUtils.java:150-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:91 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:91-99 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:116-124 — 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 `feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:91` 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 × 2) · ×5
  • Duplicated block (6 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:274 — lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:274-279 | lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:291-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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:197 — lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:197-202 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:239-244 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:197` 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) REDACTED:1414 — REDACTED:1414-1419 | REDACTED:1435-1440 — 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 `REDACTED:1414` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:864 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:864-869 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1032-1037 — 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:129 — lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:129-134 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:344-349 — 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 · Edited copy of a member (17 corresponding lines) · ×4
  • Edited copy of a member (17 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1571 — lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1571-1587 | lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1611-1630 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:375 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:375-391 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:373-389 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/JsonUtils.java:238 — lib/utilcode/src/main/java/com/blankj/utilcode/util/JsonUtils.java:238-254 | lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1116-1132 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/brightness/BrightnessActivity.kt:25 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/brightness/BrightnessActivity.kt:25-41 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/screen/ScreenActivity.kt:29-45 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×4
  • Edited copy of a member (10 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:2250 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:2250-2259 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:2287-2299 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ClickUtils.java:71 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ClickUtils.java:71-82 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ClickUtils.java:114-123 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ServiceUtils.java:35 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ServiceUtils.java:35-44 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ServiceUtils.java:225-237 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) lib/base/src/main/java/com/blankj/base/dialog/BaseDialog.java:56 — lib/base/src/main/java/com/blankj/base/dialog/BaseDialog.java:56-65 | lib/base/src/main/java/com/blankj/base/dialog/BaseDialogFragment.java:147-156 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×4
  • Edited copy of a member (15 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:112 — lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:112-127 | lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:169-183 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ResourceUtils.java:186 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ResourceUtils.java:186-205 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ResourceUtils.java:266-280 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:155 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:155-169 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:171-185 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:243 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:243-257 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:319-333 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×4
  • Edited copy of a member (12 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1675 — lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1675-1686 | lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1699-1713 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ClickUtils.java:180 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ClickUtils.java:180-191 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:45-56 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:124 — lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:124-135 | lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:681-692 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (12 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java:273 — lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java:273-284 | lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java:293-304 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×4
  • Duplicated block (21 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:2118 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:2118-2138 | lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1150-1170 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:2118` 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 (21 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:333 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:333-353 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:331-351 — before extracting anything, compare `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java` and `plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:333` 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 (21 lines × 2) plugin/api-gradle-plugin/src/main/java/com/blankj/api/ApiUtilsClassVisitor.java:34 — plugin/api-gradle-plugin/src/main/java/com/blankj/api/ApiUtilsClassVisitor.java:34-54 | plugin/bus-gradle-plugin/src/main/java/com/blankj/bus/BusUtilsClassVisitor.java:33-53 — 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 `plugin/api-gradle-plugin/src/main/java/com/blankj/api/ApiUtilsClassVisitor.java:34` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (21 lines × 2) lib/base/src/main/java/com/blankj/base/rv/ItemViewHolder.java:22 — lib/base/src/main/java/com/blankj/base/rv/ItemViewHolder.java:22-42 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/ItemViewHolder.java:21-41 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/ItemViewHolder.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/ItemViewHolder.java` as WHOLE FILES: 82% 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.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:562 — lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:562-566 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:591-595 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:562` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (5 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/KeyboardUtils.java:197 — lib/utilcode/src/main/java/com/blankj/utilcode/util/KeyboardUtils.java:197-201 | lib/utilcode/src/main/java/com/blankj/utilcode/util/KeyboardUtils.java:313-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:548 — lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:548-552 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:588-592 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:548` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (5 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:376 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:376-380 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:374-378 — before extracting anything, compare `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java` and `plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:376` 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.
D3 · God Classes · MethodTooLong · ×3
  • MethodTooLong: ImageUtils.stackBlur lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1403 — MethodTooLong — stackBlur runs 144 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 44 over it, 1.44× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: UriUtils.uri2FileReal lib/utilcode/src/main/java/com/blankj/utilcode/util/UriUtils.java:97 — MethodTooLong — uri2FileReal runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LogActivity.bindItems feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/log/LogActivity.kt:115 — MethodTooLong — bindItems runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:152 — lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:152-158 | lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:160-166 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:26 — lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:26-34 | lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:43-49 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) lib/common/src/main/java/com/blankj/common/activity/CommonActivity.java:247 — lib/common/src/main/java/com/blankj/common/activity/CommonActivity.java:247-253 | lib/common/src/main/java/com/blankj/common/fragment/CommonFragment.java:94-100 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×3
  • Edited copy of a member (20 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:160 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:160-179 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:365-384 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:620 — lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:620-644 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:653-672 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:218 — lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:218-237 | lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:239-259 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:2032 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:2032-2043 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:2080-2091 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:2080` 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 (12 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:742 — lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:742-753 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ResourceUtils.java:269-280 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:742` 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 (12 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1473 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1473-1484 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1554-1565 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1473` 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.
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: api-gradle-plugin plugin/api-gradle-plugin/src/test/java/com/blankj/api/ApiTest.java:27 — No conventional assertion call was detected in 1 of 1 tests in `api-gradle-plugin` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: bus-gradle-plugin plugin/bus-gradle-plugin/src/test/java/com/blankj/bus/BusTest.java:90 — No conventional assertion call was detected in 1 of 1 tests in `bus-gradle-plugin` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D2 · Cognitive Complexity · ZipUtils.unzipFileByKeyword (cognitive 24) · ×2
  • ZipUtils.unzipFileByKeyword (cognitive 24) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:284 — ZipUtils.unzipFileByKeyword has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • ZipUtils.unzipFileByKeyword (cognitive 24) plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:282 — ZipUtils.unzipFileByKeyword has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ZipUtils.zipFile (cognitive 18) · ×2
  • ZipUtils.zipFile (cognitive 18) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:191 — ZipUtils.zipFile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (5 pts), boolean chains 1, ternaries 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.
  • ZipUtils.zipFile (cognitive 18) plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:189 — ZipUtils.zipFile has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (5 pts), boolean chains 1, ternaries 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:193 — lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:193-201 | lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:108-116 | lib/utilcode/src/main/java/com/blankj/utilcode/util/SPUtils.java:437-445 | lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java:50-58 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:444-452 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1171 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1171-1184 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1219-1232 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1267-1280 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1315-1328 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1363-1376 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×2
  • Edited copy of a member (34 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:287 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:287-320 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:285-318 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (34 corresponding lines) lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java:216 — lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java:216-249 | lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java:251-284 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×2
  • Edited copy of a member (14 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java:165 — lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java:165-178 | lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java:186-199 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) REDACTED:1413 — REDACTED:1413-1426 | REDACTED:1434-1447 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×2
  • Edited copy of a member (18 corresponding lines) REDACTED:504 — REDACTED:504-521 | REDACTED:602-621 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:315 — lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:315-332 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:247-265 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×2
  • Edited copy of a member (19 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/BusUtils.java:168 — lib/utilcode/src/main/java/com/blankj/utilcode/util/BusUtils.java:168-190 | lib/utilcode/src/main/java/com/blankj/utilcode/util/BusUtils.java:371-389 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:118 — lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:118-136 | REDACTED:544-564 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 13+ corresponding lines) lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:105 — lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:105-119 | lib/subutil/src/main/java/com/blankj/subutil/util/BatteryUtils.java:126-138 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:877-892 | lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:899-911 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 13+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1684 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1684-1696 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1711-1723 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1745-1757 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1772-1784 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×2
  • Edited copy of a member (8 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java:226 — lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java:226-233 | lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java:313-320 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AdaptScreenUtils.java:58 — lib/utilcode/src/main/java/com/blankj/utilcode/util/AdaptScreenUtils.java:58-65 | lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:485-493 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×2
  • Edited copy of a member (6 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java:813 — lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java:813-819 | REDACTED:1178-1183 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/fragment/ChildFragment.kt:42 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/fragment/ChildFragment.kt:42-47 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/fragment/ContainerFragment.kt:45-50 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×2
  • Duplicated block (25 lines × 2) lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:76 — lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:76-100 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.java:77-101 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (25 lines × 2) lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:104 — lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:104-128 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.java:105-129 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 67 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 (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:106 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:106-120 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:104-118 — before extracting anything, compare `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java` and `plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (15 lines × 2) lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/appInfo/AppInfoItem.java:51 — lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/appInfo/AppInfoItem.java:51-65 | lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/deviceInfo/DeviceInfoItem.java:56-70 — 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.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) lib/base/src/main/java/com/blankj/base/view/EmptyGoneTextView.java:23 — lib/base/src/main/java/com/blankj/base/view/EmptyGoneTextView.java:23-40 | lib/utildebug/src/main/java/com/blankj/utildebug/base/view/EmptyGoneTextView.java:23-40 — before extracting anything, compare `lib/base/src/main/java/com/blankj/base/view/EmptyGoneTextView.java` and `lib/utildebug/src/main/java/com/blankj/utildebug/base/view/EmptyGoneTextView.java` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (18 lines × 2) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/fragment/ChildFragment.kt:50 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/fragment/ChildFragment.kt:50-67 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/fragment/ContainerFragment.kt:54-71 — 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 `feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/fragment/ChildFragment.kt:50` 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 (10–11 lines × 2) · ×2
  • Duplicated block (10–11 lines × 2) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityAlpha.kt:47 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityAlpha.kt:47-56 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityImageView.kt:46-56 — before extracting anything, compare `feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityAlpha.kt` and `feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityImageView.kt` 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. 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 `feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityAlpha.kt: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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note 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 (10–11 lines × 2) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/fragment/BarStatusFragmentAlpha.kt:49 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/fragment/BarStatusFragmentAlpha.kt:49-58 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/fragment/BarStatusFragmentImageView.kt:48-58 — 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 `feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/fragment/BarStatusFragmentAlpha.kt:49` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note 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.
D6 · Cohesion (LCOM4) · Low cohesion · ×2
  • Low cohesion: ToastUtils (LCOM4 8) lib/utilcode/src/main/java/com/blankj/utilcode/util/ToastUtils.java:53 — ToastUtils's methods fall into 8 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 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: BaseFloatView (LCOM4 5) lib/utildebug/src/main/java/com/blankj/utildebug/base/view/BaseFloatView.java:27 — BaseFloatView's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D1 · Cyclomatic Complexity · UriUtils.uri2FileReal (cyclomatic 40) · ×1
  • UriUtils.uri2FileReal (cyclomatic 40) lib/utilcode/src/main/java/com/blankj/utilcode/util/UriUtils.java:97 — UriUtils.uri2FileReal has cyclomatic complexity 40 (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 · SpanUtils.updateCharCharSequence (cyclomatic 31) · ×1
  • SpanUtils.updateCharCharSequence (cyclomatic 31) lib/utilcode/src/main/java/com/blankj/utilcode/util/SpanUtils.java:857 — SpanUtils.updateCharCharSequence has cyclomatic complexity 31 (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 · FragmentUtils.operate (cyclomatic 27) · ×1
  • FragmentUtils.operate (cyclomatic 27) lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1459 — FragmentUtils.operate has cyclomatic complexity 27 (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 · LogFormatter.intent2String (cyclomatic 27) · ×1
  • LogFormatter.intent2String (cyclomatic 27) lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:956 — LogFormatter.intent2String has cyclomatic complexity 27 (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 · NetworkUtils.getNetworkType (cyclomatic 27) · ×1
  • NetworkUtils.getNetworkType (cyclomatic 27) lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:440 — NetworkUtils.getNetworkType has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · ObjectUtils.isEmpty (cyclomatic 26) · ×1
  • ObjectUtils.isEmpty (cyclomatic 26) lib/utilcode/src/main/java/com/blankj/utilcode/util/ObjectUtils.java:40 — ObjectUtils.isEmpty has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PhoneUtils.getImeiOrMeid (cyclomatic 26) · ×1
  • PhoneUtils.getImeiOrMeid (cyclomatic 26) lib/utilcode/src/main/java/com/blankj/utilcode/util/PhoneUtils.java:112 — PhoneUtils.getImeiOrMeid 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 · RomUtils.getRomInfo (cyclomatic 23) · ×1
  • RomUtils.getRomInfo (cyclomatic 23) lib/utilcode/src/main/java/com/blankj/utilcode/util/RomUtils.java:249 — RomUtils.getRomInfo has cyclomatic complexity 23 (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 · ArrayUtils.forAllDo (cyclomatic 22) · ×1
  • ArrayUtils.forAllDo (cyclomatic 22) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:2048 — ArrayUtils.forAllDo has cyclomatic complexity 22 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D1 · Cyclomatic Complexity · ShellUtils.execCmd (cyclomatic 21) · ×1
  • ShellUtils.execCmd (cyclomatic 21) lib/utilcode/src/main/java/com/blankj/utilcode/util/ShellUtils.java:281 — ShellUtils.execCmd has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Body.getCharsetFromMediaType (cyclomatic 20) · ×1
  • Body.getCharsetFromMediaType (cyclomatic 20) lib/subutil/src/main/java/com/blankj/subutil/util/http/Request.java:84 — Body.getCharsetFromMediaType 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 · FileUtils.isUtf8 (cyclomatic 20) · ×1
  • FileUtils.isUtf8 (cyclomatic 20) REDACTED:983 — FileUtils.isUtf8 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 · SwipeRightMenu.dispatchTouchEvent (cyclomatic 19) · ×1
  • SwipeRightMenu.dispatchTouchEvent (cyclomatic 19) lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java:117 — SwipeRightMenu.dispatchTouchEvent 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 · ProcessUtils.getForegroundProcessName (cyclomatic 17) · ×1
  • ProcessUtils.getForegroundProcessName (cyclomatic 17) lib/utilcode/src/main/java/com/blankj/utilcode/util/ProcessUtils.java:54 — ProcessUtils.getForegroundProcessName 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.
D2 · Cognitive Complexity · UriUtils.uri2FileReal (cognitive 89) · ×1
  • UriUtils.uri2FileReal (cognitive 89) lib/utilcode/src/main/java/com/blankj/utilcode/util/UriUtils.java:97 — UriUtils.uri2FileReal has cognitive complexity 89 (threshold 15). Drivers by points: if/else 31 (63 pts), error handling 3 (11 pts), loops 3 (9 pts), boolean chains 6 (nesting depth added 46). 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 · PhoneUtils.getImeiOrMeid (cognitive 50) · ×1
  • PhoneUtils.getImeiOrMeid (cognitive 50) lib/utilcode/src/main/java/com/blankj/utilcode/util/PhoneUtils.java:112 — PhoneUtils.getImeiOrMeid has cognitive complexity 50 (threshold 15). Drivers by points: if/else 18 (34 pts), boolean chains 6, error handling 3 (6 pts), ternaries 2 (4 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileUtils.isUtf8 (cognitive 47) · ×1
  • FileUtils.isUtf8 (cognitive 47) REDACTED:983 — FileUtils.isUtf8 has cognitive complexity 47 (threshold 15). Drivers by points: if/else 14 (32 pts), loops 3 (8 pts), boolean chains 4, ternaries 1 (3 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FragmentUtils.operate (cognitive 45) · ×1
  • FragmentUtils.operate (cognitive 45) lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1459 — FragmentUtils.operate has cognitive complexity 45 (threshold 15). Drivers by points: if/else 11 (30 pts), loops 6 (12 pts), boolean chains 2, match/switch 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LogFormatter.intent2String (cognitive 45) · ×1
  • LogFormatter.intent2String (cognitive 45) lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:956 — LogFormatter.intent2String has cognitive complexity 45 (threshold 15). Drivers by points: if/else 24 (40 pts), ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SwipeRightMenu.dispatchTouchEvent (cognitive 38) · ×1
  • SwipeRightMenu.dispatchTouchEvent (cognitive 38) lib/utildebug/src/main/java/com/blankj/utildebug/base/view/SwipeRightMenu.java:117 — SwipeRightMenu.dispatchTouchEvent has cognitive complexity 38 (threshold 15). Drivers by points: if/else 16 (35 pts), boolean chains 2, match/switch 1 (nesting depth added 19). 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 · ArrayUtils.forAllDo (cognitive 33) · ×1
  • ArrayUtils.forAllDo (cognitive 33) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:2048 — ArrayUtils.forAllDo has cognitive complexity 33 (threshold 15). Drivers by points: loops 9 (18 pts), if/else 11, ternaries 1 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SpanUtils.updateCharCharSequence (cognitive 31) · ×1
  • SpanUtils.updateCharCharSequence (cognitive 31) lib/utilcode/src/main/java/com/blankj/utilcode/util/SpanUtils.java:857 — SpanUtils.updateCharCharSequence has cognitive complexity 31 (threshold 15). Drivers by points: if/else 28, loops 1 (2 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ImageUtils.stackBlur (cognitive 30) · ×1
  • ImageUtils.stackBlur (cognitive 30) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1403 — ImageUtils.stackBlur has cognitive complexity 30 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 7 (11 pts), ternaries 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 · LogUtils.processTagAndHead (cognitive 29) · ×1
  • LogUtils.processTagAndHead (cognitive 29) lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:252 — LogUtils.processTagAndHead has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 2 (7 pts), loops 1 (4 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · ProcessUtils.getForegroundProcessName (cognitive 29) · ×1
  • ProcessUtils.getForegroundProcessName (cognitive 29) lib/utilcode/src/main/java/com/blankj/utilcode/util/ProcessUtils.java:54 — ProcessUtils.getForegroundProcessName has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (2 pts), ternaries 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 · Body.getCharsetFromMediaType (cognitive 27) · ×1
  • Body.getCharsetFromMediaType (cognitive 27) lib/subutil/src/main/java/com/blankj/subutil/util/http/Request.java:84 — Body.getCharsetFromMediaType has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 8, 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 · AppUtils.isAppRunning (cognitive 27) · ×1
  • AppUtils.isAppRunning (cognitive 27) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:212 — AppUtils.isAppRunning has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (19 pts), loops 2 (6 pts), boolean chains 2 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · ObjectUtils.isEmpty (cognitive 27) · ×1
  • ObjectUtils.isEmpty (cognitive 27) lib/utilcode/src/main/java/com/blankj/utilcode/util/ObjectUtils.java:40 — ObjectUtils.isEmpty has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (16 pts), boolean chains 11 (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.
D2 · Cognitive Complexity · ShellUtils.execCmd (cognitive 27) · ×1
  • ShellUtils.execCmd (cognitive 27) lib/utilcode/src/main/java/com/blankj/utilcode/util/ShellUtils.java:281 — ShellUtils.execCmd has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (12 pts), loops 3 (7 pts), error handling 4, ternaries 3, boolean chains 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · FileUtils.deleteFilesInDirWithFilter (cognitive 26) · ×1
  • FileUtils.deleteFilesInDirWithFilter (cognitive 26) REDACTED:602 — FileUtils.deleteFilesInDirWithFilter has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 14). 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 · RomUtils.getRomInfo (cognitive 25) · ×1
  • RomUtils.getRomInfo (cognitive 25) lib/utilcode/src/main/java/com/blankj/utilcode/util/RomUtils.java:249 — RomUtils.getRomInfo has cognitive complexity 25 (threshold 15). Drivers by points: if/else 24 (25 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · Task.run (cognitive 25) · ×1
  • Task.run (cognitive 25) lib/utilcode/src/main/java/com/blankj/utilcode/util/ThreadUtils.java:1198 — Task.run has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (23 pts), error handling 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UiMessageUtils.logMessageHandling (cognitive 25) · ×1
  • UiMessageUtils.logMessageHandling (cognitive 25) lib/utilcode/src/main/java/com/blankj/utilcode/util/UiMessageUtils.java:193 — UiMessageUtils.logMessageHandling has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (6 pts), boolean chains 3 (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 · CollectionUtils.get (cognitive 23) · ×1
  • CollectionUtils.get (cognitive 23) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:707 — CollectionUtils.get has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (17 pts), loops 2 (4 pts), error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · FileUtils.copyOrMoveDir (cognitive 23) · ×1
  • FileUtils.copyOrMoveDir (cognitive 23) REDACTED:421 — FileUtils.copyOrMoveDir has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileUtils.getFileLines (cognitive 23) · ×1
  • FileUtils.getFileLines (cognitive 23) REDACTED:1060 — FileUtils.getFileLines has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (10 pts), error handling 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NetworkUtils.getIPAddress (cognitive 22) · ×1
  • NetworkUtils.getIPAddress (cognitive 22) lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:547 — NetworkUtils.getIPAddress has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (4 pts), ternaries 1 (4 pts), boolean chains 1, error handling 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 · AdaptScreenUtils.applyOtherDisplayMetrics (cognitive 21) · ×1
  • AdaptScreenUtils.applyOtherDisplayMetrics (cognitive 21) lib/utilcode/src/main/java/com/blankj/utilcode/util/AdaptScreenUtils.java:119 — AdaptScreenUtils.applyOtherDisplayMetrics has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (5 pts), boolean chains 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 · ImageUtils.compressByQuality (cognitive 21) · ×1
  • ImageUtils.compressByQuality (cognitive 21) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:2185 — ImageUtils.compressByQuality has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 1 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SDCardUtils.getSDCardInfo (cognitive 21) · ×1
  • SDCardUtils.getSDCardInfo (cognitive 21) lib/utilcode/src/main/java/com/blankj/utilcode/util/SDCardUtils.java:55 — SDCardUtils.getSDCardInfo has cognitive complexity 21 (threshold 15). Drivers by points: error handling 7 (14 pts), loops 2 (4 pts), if/else 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BusUtils.recordTags (cognitive 20) · ×1
  • BusUtils.recordTags (cognitive 20) lib/utilcode/src/main/java/com/blankj/utilcode/util/BusUtils.java:133 — BusUtils.recordTags has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 2 (7 pts), error handling 1 (5 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 · FileUtils.deleteDir (cognitive 19) · ×1
  • FileUtils.deleteDir (cognitive 19) REDACTED:504 — FileUtils.deleteDir has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (2 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 · ImageUtils.save2Album (cognitive 19) · ×1
  • ImageUtils.save2Album (cognitive 19) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1879 — ImageUtils.save2Album has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 2 (4 pts), ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SnackbarUtils.show (cognitive 19) · ×1
  • SnackbarUtils.show (cognitive 19) lib/utilcode/src/main/java/com/blankj/utilcode/util/SnackbarUtils.java:203 — SnackbarUtils.show has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), loops 1 (2 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 · ActivityToast.cancel (cognitive 19) · ×1
  • ActivityToast.cancel (cognitive 19) lib/utilcode/src/main/java/com/blankj/utilcode/util/ToastUtils.java:702 — ActivityToast.cancel has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 1 (5 pts), loops 1 (2 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 · EncryptUtils.rsaTemplate (cognitive 18) · ×1
  • EncryptUtils.rsaTemplate (cognitive 18) REDACTED:1076 — EncryptUtils.rsaTemplate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (13 pts), loops 1 (2 pts), boolean chains 1, error handling 1, 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 · LogUtils.printSingleTagMsg (cognitive 18) · ×1
  • LogUtils.printSingleTagMsg (cognitive 18) lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:460 — LogUtils.printSingleTagMsg has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (6 pts), ternaries 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 · AppStoreUtils.getAppStoreIntent (cognitive 17) · ×1
  • AppStoreUtils.getAppStoreIntent (cognitive 17) lib/subutil/src/main/java/com/blankj/subutil/util/AppStoreUtils.java:66 — AppStoreUtils.getAppStoreIntent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, loops 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 · FileUtils.copyOrMoveFile (cognitive 17) · ×1
  • FileUtils.copyOrMoveFile (cognitive 17) REDACTED:446 — FileUtils.copyOrMoveFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 5, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CollectionUtils.cardinality (cognitive 16) · ×1
  • CollectionUtils.cardinality (cognitive 16) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:418 — CollectionUtils.cardinality has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 2 (4 pts), ternaries 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 · LogUtils.getClassFromObject (cognitive 16) · ×1
  • LogUtils.getClassFromObject (cognitive 16) lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1199 — LogUtils.getClassFromObject has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 2 (6 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NetworkUtils.getNetworkType (cognitive 16) · ×1
  • NetworkUtils.getNetworkType (cognitive 16) lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:440 — NetworkUtils.getNetworkType has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UriUtils.getFileFromUri (cognitive 16) · ×1
  • UriUtils.getFileFromUri (cognitive 16) lib/utilcode/src/main/java/com/blankj/utilcode/util/UriUtils.java:271 — UriUtils.getFileFromUri has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (15 pts), error handling 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1190 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1190-1205 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1238-1253 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1286-1301 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1334-1349 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1382-1397 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1455-1470 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1526-1541 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1574-1589 — These 8 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 8 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 8 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) lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:40 — lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:40-50 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:53-63 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:67-80 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:83-93 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/fileExplorer/FileContentView.java:52 — lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/fileExplorer/FileContentView.java:52-84 | lib/utildebug/src/main/java/com/blankj/utildebug/debug/tool/fileExplorer/sp/SpViewerContentView.java:58-90 — These two members are one piece of code written twice and then edited apart: 33 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 (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:326 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:326-353 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:324-351 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:378 — lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:378-410 | lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:468-496 — These two members are one piece of code written twice and then edited apart: 29 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 (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1173 — lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1173-1197 | lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1199-1230 — These two members are one piece of code written twice and then edited apart: 25 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 (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) REDACTED:175 — REDACTED:175-201 | REDACTED:1258-1283 — These two members are one piece of code written twice and then edited apart: 26 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 (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:866 — lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:866-892 | lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:910-936 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:87 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:87-110 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/permission/PermissionActivity.kt:112-134 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 23+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 23+ corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/helper/DialogHelper.kt:86 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/helper/DialogHelper.kt:86-109 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/helper/DialogHelper.kt:111-133 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/helper/DialogHelper.kt:135-157 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1107 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1107-1128 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1134-1157 — 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 copies of one member (8 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 13+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1614 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1614-1626 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1661-1673 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1708-1720 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1755-1767 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1802-1814 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1849-1861 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1896-1908 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1943-1955 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/KeyboardUtils.java:195 — lib/utilcode/src/main/java/com/blankj/utilcode/util/KeyboardUtils.java:195-207 | lib/utilcode/src/main/java/com/blankj/utilcode/util/KeyboardUtils.java:308-322 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 8+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:496 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:496-503 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:608-615 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:647-655 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 12+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1600 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1600-1611 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1647-1658 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1694-1705 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1741-1752 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1788-1799 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1835-1846 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1882-1893 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1929-1940 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 12+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1629 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1629-1640 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1676-1687 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1723-1734 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1770-1781 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1817-1828 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1864-1875 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1911-1922 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 19+ corresponding lines) REDACTED:322 — REDACTED:322-340 | REDACTED:345-365 | REDACTED:601-620 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 12+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/MetaDataUtils.java:33 — lib/utilcode/src/main/java/com/blankj/utilcode/util/MetaDataUtils.java:33-44 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MetaDataUtils.java:66-77 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MetaDataUtils.java:99-110 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MetaDataUtils.java:132-143 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 11+ corresponding lines) lib/common/src/main/java/com/blankj/common/helper/PermissionHelper.kt:58 — lib/common/src/main/java/com/blankj/common/helper/PermissionHelper.kt:58-69 | lib/common/src/main/java/com/blankj/common/helper/PermissionHelper.kt:71-83 | lib/common/src/main/java/com/blankj/common/helper/PermissionHelper.kt:85-95 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 11+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:349 — lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:349-359 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:376-386 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:447-457 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:476-486 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:505-515 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:532-542 | lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:589-601 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java:130 — lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java:130-143 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDoubleUtils.java:49-62 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheMemoryUtils.java:54-66 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 14+ corresponding lines) feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityAlpha.kt:46 — feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityAlpha.kt:46-61 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/BarStatusActivityImageView.kt:45-58 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/fragment/BarStatusFragmentAlpha.kt:48-63 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/bar/status/fragment/BarStatusFragmentImageView.kt:47-60 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 10+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:505 — lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:505-514 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:527-536 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:879-888 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 9+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:238 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:238-246 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:267-275 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:296-304 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:330-338 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:402-410 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java:120 — lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java:120-124 | lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java:132-136 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 7+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:194 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:194-201 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:302-309 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:416-422 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:533-539 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:648-657 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1366-1372 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 9+ corresponding lines) lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:71 — lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:71-79 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:92-100 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:113-121 | lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:134-142 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 11+ corresponding lines) feature/subutil/pkg/src/main/java/com/blankj/subutil/pkg/feature/dangerous/DangerousActivity.kt:27 — feature/subutil/pkg/src/main/java/com/blankj/subutil/pkg/feature/dangerous/DangerousActivity.kt:27-37 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/app/AppActivity.kt:27-37 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/image/ImageActivity.kt:37-47 | feature/utilcode/pkg/src/main/java/com/blankj/utilcode/pkg/feature/phone/PhoneActivity.kt:27-37 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:223 — lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:223-226 | lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.java:187-190 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×1
  • Duplicated block (33 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:197 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:197-229 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:195-227 — before extracting anything, compare `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java` and `plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 96 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:197` 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 (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:148 — lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:148-166 | lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:182-200 — 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 `lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:148` 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 lines × 8) · ×1
  • Duplicated block (14 lines × 8) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1192 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1192-1205 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1240-1253 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1288-1301 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1336-1349 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1384-1397 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1457-1470 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1528-1541 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1576-1589 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1192` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `array` to `long[]` in one and `int[]` 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 (13 lines × 5) · ×1
  • Duplicated block (13 lines × 5) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1172 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1172-1184 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1220-1232 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1268-1280 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1316-1328 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1364-1376 — 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `array` to `long[]` in one and `int[]` 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 (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1416 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1416-1428 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1508-1520 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1556-1568 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `array` to `double[]` in one and `float[]` 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) · ×1
  • Duplicated block (16 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:164 — lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:164-179 | lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:369-384 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/ReflectUtils.java:164` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `o1` to `Constructor<?>` in one and `Method` 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 (10 lines × 3) · ×1
  • Duplicated block (10 lines × 3) lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:169 — lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:169-178 | REDACTED:213-222 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:429-438 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:224 — lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:224-232 | lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:245-254 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:224` 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 (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:42 — lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:42-50 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:55-63 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:72-80 | lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:85-93 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/MapUtils.java:42` 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 (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:59 — lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:59-71 | lib/subutil/src/main/java/com/blankj/subutil/util/CoordinateUtils.java:83-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.
D4 · Code Duplication · Duplicated block (8 lines × 5) · ×1
  • Duplicated block (8 lines × 5) lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:194 — lib/subutil/src/main/java/com/blankj/subutil/util/DangerousUtils.java:194-201 | lib/subutil/src/main/java/com/blankj/subutil/util/http/HttpUtils.java:109-116 | lib/utilcode/src/main/java/com/blankj/utilcode/util/SPUtils.java:438-445 | lib/utilcode/src/main/java/com/blankj/utilcode/util/StringUtils.java:51-58 | plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.java:445-452 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (5–6 lines × 2) · ×1
  • Duplicated block (5–6 lines × 2) lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1613 — lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1613-1617 | lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1762-1767 — 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 `lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1613` 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.
Minor — 206 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×173
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/FragmentUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/ArrayUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/TimeUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/ThreadUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/SpanUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/NetworkUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/CollectionUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDoubleStaticUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskStaticUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/AppUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/FileIOUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/ToastUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/ShadowUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/UtilsBridge.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/SPStaticUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/PermissionUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/ClickUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/DeviceUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/IntentUtils.java:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 148 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X10 · Duplicated predicate · Duplicated predicate · ×6
  • Duplicated predicate lib/utilcode/src/main/java/com/blankj/utilcode/util/CrashUtils.java:82 — `UtilsBridge.isSDCardEnableByEnvironment() && Utils.getApp().getExternalFilesDir(null) != null` appears character-identically in 2 files — lib/utilcode/src/main/java/com/blankj/utilcode/util/CrashUtils.java, lib/utilcode/src/main/java/com/blankj/utilcode/util/LogUtils.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 lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:199 — `fileList == null || fileList.length <= 0` appears character-identically in 2 files — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java, plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.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 lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:91 — `i == childCount - 1 && !mShowFooterDivider` appears character-identically in 2 files — lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java, lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.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 lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java:55 — `orientation != HORIZONTAL && orientation != VERTICAL` appears character-identically in 2 files — lib/base/src/main/java/com/blankj/base/rv/RecycleViewDivider.java, lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/RecycleViewDivider.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 lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java:75 — `position < 0 || position >= mItems.size()` appears character-identically in 2 files — lib/base/src/main/java/com/blankj/base/rv/BaseItemAdapter.java, lib/utildebug/src/main/java/com/blankj/utildebug/base/rv/BaseItemAdapter.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 lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java:64 — `srcFilePaths == null || zipFilePath == null` appears character-identically in 2 files — lib/utilcode/src/main/java/com/blankj/utilcode/util/ZipUtils.java, plugin/lib/base-transform/src/main/java/com/blankj/base_transform/util/ZipUtils.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.
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file lib/subutil/src/main/java/com/blankj/subutil/util/PinyinUtils.java:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/ActivityUtils.java:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file lib/utilcode/src/main/java/com/blankj/utilcode/util/ImageUtils.java:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
X7 · Silent fallback defaults · Silent fallback default in catch · ×2
  • Silent fallback default in catch lib/utilcode/src/main/java/com/blankj/utilcode/util/BarUtils.java:592 — `getResNameById` swallows every exception into `return ""` — 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 lib/utilcode/src/main/java/com/blankj/utilcode/util/ProcessUtils.java:248 — `getCurrentProcessNameByAms` swallows every exception into `return ""` — 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.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no build, run or usage example README.md:1 — the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 2 of 19 project(s) overshoot their size bounds, lowering Project Cohesion to 7.9/10. The most over is `lib/utilcode` (40289 LoC, 157 module-visible types across 2 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
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 176 of 176 significant files have no living knowledge — the codebase as a whole is dormant, not 176 separate risks. Counted over 176 of the 324 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `lib/subutil`.
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) as a CI step. What was searched, so you can tell an absence from a miss: the 1 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.
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/53 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 lib/utilcode/src/main/java/com/blankj/utilcode/util/CacheDiskUtils.java:844 — `getDueTime` returns `-1` 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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ce18b226c6764537acd419a1042fa6e5/history.json --exit-code 0 --source .3artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ce18b226c6764537acd419a1042fa6e5/tree.json --exit-code 0 --source .0artifacts/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .16artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.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 Dependenciesnone (dependency manifest found, not scanned for vulnerabilities here)—none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).0—

Run 01a1d4fd-622e-72a3-965b-8855778404ec · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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