Public report of pingapi/apigo, published 16 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.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 16 November 2026, 22:55 UTC · Survey ID cd_f531b82991de4c68a5c8dd9d068a9150

pingapi/apigo

Measured 16 November 2026, 22:55 UTC, at code version aecf501

First survey, so nothing to compare with yet
CAI score 45.2out of 100 Weak
CriticalWeakAdequateStrongExemplary

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

A small codebase: 16,590 lines of product code in 6 projects, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 26.5

Findings by how serious they are

9 critical 107 serious 28 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
16 November 2026, 22:55 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 ▸

55of 55 dimensions measured by tools.
130of 144 findings point to an exact file and line, so you can open each one in the code. The other 14 concern the repository as a whole, such as missing documentation.
55dimensions across 5 lenses, read from 16,590 lines of product code in 6 projects.
Chapters

Executive summary

pingapi/apigo falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 45.2 out of 100 and is rated Weak, and eight of its nine critical findings are security problems.

Production Readiness, at 26.5, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the package under a licence on your banned list, worth about 4.7 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 5.5 points. Raising Production Readiness to 70 would lift the score to about 60.5.

Four passwords or keys are open to anyone who can read the repository. Three settings leave the servers or containers unsafe, and one known security hole in a package the code depends on can be used by attackers. Replacing each exposed password or key, correcting the unsafe settings and updating the vulnerable packages would close these risks. The package under a licence on your banned list needs replacing, or clearing with your legal team.

The product code is 16,590 lines, about €17,000 to rebuild.

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 26.5 · counts for 47%Code Health 50.9 · counts for 26%Maturity 59.7 · counts for 14%Security and Compliance 84.7 · counts for 8%Architecture 94.7 · counts for 4%

If Production Readiness rose from 26.5 to 70, the lowest score rated Strong, the score would rise from 45.2 to about 60.5.

Code composition: what the lines of code are
Product code 86%Tests 14%
Rebuild cost: about €17,000 · Estimate
Cost to rebuild€5,700 to €29,000, for 95 to 300 hours of work, about 0.1 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 45. 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.
SizeSmall: 16,590 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 Banned license finding(s) in License Compliance.
Raises the score by about 4.7 points · Low effort · License Compliance
2
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
Raises the score by about 4.2 points · Low effort · ADR Quality
3
Add a CI workflow that builds and runs the test suite on every push/PR.
Raises the score by about 5.5 points · Medium effort · CI/CD gates

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 €17,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 26.5 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Banned license finding(s) in License Compliance. Of all the actions in this report, it raises the score most for the work it takes: about 4.7 points for low effort, because it clears the 1 License Compliance findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.

arch apigo-admin apigo-admin apigo-core apigo-core apigo-admin->apigo-core apigo-datasource apigo-datasource apigo-core->apigo-datasource apigo-plugin apigo-plugin apigo-core->apigo-plugin apigo-spi apigo-spi apigo-datasource->apigo-spi apigo-spring-boot-starter apigo-spring-boot-starter apigo-spring-boot-starter->apigo-core

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.

39 modules, with 89 dependencies between them. One loop runs through 4 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 apigo-api.apigo-core.src.main.resources.static.assets2 cn.crabc.core.admin3 cn.crabc.core.admin.config4 cn.crabc.core.app.enums5 cn.crabc.core.app.mcp.auth6 cn.crabc.core.app.mcp.support7 cn.crabc.core.app.support8 cn.crabc.core.datasource.config9 cn.crabc.core.datasource.constant10 cn.crabc.core.datasource.enums11 cn.crabc.core.datasource.exception12 cn.crabc.core.datasource.interceptor13 cn.crabc.core.datasource.mapper14 cn.crabc.core.datasource.util15 cn.crabc.core.plugin16 cn.crabc.core.plugin.util17 cn.crabc.core.spi.bean18 cn.crabc.core.starter19 cn.crabc.core.app.entity20 cn.crabc.core.app.mcp.config21 cn.crabc.core.plugin.impl22 cn.crabc.core.spi23 cn.crabc.core.app.entity.dto24 cn.crabc.core.app.entity.param25 cn.crabc.core.app.entity.vo26 cn.crabc.core.datasource.driver27 cn.crabc.core.datasource.driver.jdbc28 cn.crabc.core.app.mapper29 cn.crabc.core.app.service.core30 cn.crabc.core.app.service.system31 cn.crabc.core.app.mcp.tools32 cn.crabc.core.app.service.core.impl33 cn.crabc.core.app.service.system.impl34 cn.crabc.core.app.filter35 cn.crabc.core.app.config36 cn.crabc.core.app.util37 cn.crabc.core.app.api38 cn.crabc.core.app.controller39 cn.crabc.core.app.exception
1 apigo-api.apigo-core.src.main.resources.static.assets
2 cn.crabc.core.admin
3 cn.crabc.core.admin.config
4 cn.crabc.core.app.enums
5 cn.crabc.core.app.mcp.auth
6 cn.crabc.core.app.mcp.support
7 cn.crabc.core.app.support
8 cn.crabc.core.datasource.config
9 cn.crabc.core.datasource.constant
10 cn.crabc.core.datasource.enums
11 cn.crabc.core.datasource.exception
12 cn.crabc.core.datasource.interceptor
13 cn.crabc.core.datasource.mapper
14 cn.crabc.core.datasource.util
15 cn.crabc.core.plugin
16 cn.crabc.core.plugin.util
17 cn.crabc.core.spi.bean
18 cn.crabc.core.starter
19 cn.crabc.core.app.entity1
20 cn.crabc.core.app.mcp.config1
21 cn.crabc.core.plugin.impl4
22 cn.crabc.core.spi4
23 cn.crabc.core.app.entity.dto3
24 cn.crabc.core.app.entity.param3
25 cn.crabc.core.app.entity.vo5
26 cn.crabc.core.datasource.driver13
27 cn.crabc.core.datasource.driver.jdbc2155
28 cn.crabc.core.app.mapper18118
29 cn.crabc.core.app.service.core311
30 cn.crabc.core.app.service.system5171310
31 cn.crabc.core.app.mcp.tools711514129
32 cn.crabc.core.app.service.core.impl1111
33 cn.crabc.core.app.service.system.impl151284312111174
34 cn.crabc.core.app.filter1311211
35 cn.crabc.core.app.config11111141
36 cn.crabc.core.app.util42141
37 cn.crabc.core.app.api11111
38 cn.crabc.core.app.controller155221012
39 cn.crabc.core.app.exception1111
Uses a module listed above itPart of a loopThe module itself
1 apigo-api.apigo-core.src.main.resources.static.assets2 cn.crabc.core.admin3 cn.crabc.core.admin.config4 cn.crabc.core.app.enums5 cn.crabc.core.app.mcp.auth6 cn.crabc.core.app.mcp.support7 cn.crabc.core.app.support8 cn.crabc.core.datasource.config9 cn.crabc.core.datasource.constant10 cn.crabc.core.datasource.enums11 cn.crabc.core.datasource.exception12 cn.crabc.core.datasource.interceptor13 cn.crabc.core.datasource.mapper14 cn.crabc.core.datasource.util15 cn.crabc.core.plugin16 cn.crabc.core.plugin.util17 cn.crabc.core.spi.bean18 cn.crabc.core.starter19 cn.crabc.core.app.entity20 cn.crabc.core.app.mcp.config21 cn.crabc.core.plugin.impl22 cn.crabc.core.spi23 cn.crabc.core.app.entity.dto24 cn.crabc.core.app.entity.param25 cn.crabc.core.app.entity.vo26 cn.crabc.core.datasource.driver27 cn.crabc.core.datasource.driver.jdbc28 cn.crabc.core.app.mapper29 cn.crabc.core.app.service.core30 cn.crabc.core.app.service.system31 cn.crabc.core.app.mcp.tools32 cn.crabc.core.app.service.core.impl33 cn.crabc.core.app.service.system.impl34 cn.crabc.core.app.filter35 cn.crabc.core.app.config36 cn.crabc.core.app.util37 cn.crabc.core.app.api38 cn.crabc.core.app.controller39 cn.crabc.core.app.exceptionapigo-api.apigo-core.src.main.resources.static.assets1cn.crabc.core.admin2cn.crabc.core.admin.config3cn.crabc.core.app.enums4cn.crabc.core.app.mcp.auth5cn.crabc.core.app.mcp.support6cn.crabc.core.app.support7cn.crabc.core.datasource.config8cn.crabc.core.datasource.constant9cn.crabc.core.datasource.enums10cn.crabc.core.datasource.exception11cn.crabc.core.datasource.interceptor12cn.crabc.core.datasource.mapper13cn.crabc.core.datasource.util14cn.crabc.core.plugin15cn.crabc.core.plugin.util16cn.crabc.core.spi.bean17cn.crabc.core.starter18cn.crabc.core.app.entity19cn.crabc.core.app.mcp.config20cn.crabc.core.plugin.impl21cn.crabc.core.spi22cn.crabc.core.app.entity.dto23cn.crabc.core.app.entity.param24cn.crabc.core.app.entity.vo25cn.crabc.core.datasource.driver26cn.crabc.core.datasource.driver.jdbc27cn.crabc.core.app.mapper28cn.crabc.core.app.service.core29cn.crabc.core.app.service.system30cn.crabc.core.app.mcp.tools31cn.crabc.core.app.service.core.impl32cn.crabc.core.app.service.system.impl33cn.crabc.core.app.filter34cn.crabc.core.app.config35cn.crabc.core.app.util36cn.crabc.core.app.api37cn.crabc.core.app.controller38cn.crabc.core.app.exception391144335132155181183115171310711514129111115128431211117413112111111114142141111111552210121111

At a glance — Code Health · 50.9 · Adequate · gated by R1, X5 ·

At a glance — Architecture · 94.7 · Exemplary ·

At a glance — Maturity · 59.7 · Adequate · gated by M2 ·

At a glance — Readiness · 26.5 · Weak · gated by R4, P1, P3 ·

At a glance — Security · 84.7 · Checked 4 of 10 ·

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
A07:2025 — Authentication Failures5High / Critical
A02:2025 — Security Misconfiguration5High / Critical
A05:2025 — Injection2Medium
A03:2025 — Software Supply Chain Failures1High / Critical

Roadmap

Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing; Add tests that import the unreached modules (directly or through their public entry).

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

Do thisHelpsEffortDimension
Resolve the 1 Banned license finding(s) in License Compliance.+4.7 ptsLowLicense Compliance
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.+4.2 ptsLowADR Quality
Add a CI workflow that builds and runs the test suite on every push/PR.+5.5 ptsMediumCI/CD gates
Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.+5.5 ptsMediumSecurity & performance tooling
Add tests that import the unreached modules (directly or through their public entry).+5.5 ptsMediumTest Coverage
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.+4.0 ptsMediumArchitecture documentation
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.+3.7 ptsMediumType Safety
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).+2.9 ptsMediumNullable reference types

File quality

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

FileScoreBandWorst signal
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED5.3MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedSecrets (history): High secret: REDACTED
REDACTED5.8MixedIaC & Container Security: High IaC: REDACTED
apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java5.9MixedCognitive Complexity: ApiServiceController.checkParams (cognitive 23)
apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java5.9MixedCode Duplication: Edited copy of a member (13 corresponding lines)
apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java6.0MixedExplicit Debt: TodoComment
apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java6.3MixedCode Duplication: Edited copy of a member (33 corresponding lines)
apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java7.0MixedCyclomatic Complexity: ApiDevTools.apiUpdate (cyclomatic 29)
apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java7.0MixedCyclomatic Complexity: JdbcStatement.stripCommentsAndLiterals (cyclomatic 21)
apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java7.2MixedGod Classes: TooManyMethods: BaseApiInfoServiceImpl
REDACTED7.2MixedSecrets (history): REDACTED: REDACTED
REDACTED7.2MixedSecrets (history): High secret: REDACTED
REDACTED7.2MixedDependency Vulnerabilities: High CVE: REDACTED
apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java7.4MixedCyclomatic Complexity: ApiTestController.buildParamsMap (cyclomatic 26)
apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java7.4MixedCognitive Complexity: DataProcessPlugin.calculate (cognitive 23)
apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/util/PluginUtils.java7.8MixedCyclomatic Complexity: PluginUtils.matches (cyclomatic 29)
apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/TreeTransformPlugin.java7.8MixedCyclomatic Complexity: TreeTransformPlugin.apply (cyclomatic 23)
apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/RequestUtils.java7.8MixedCyclomatic Complexity: RequestUtils.getIp (cyclomatic 19)
apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java7.8MixedCyclomatic Complexity: DataPluginConfigValidator.validateDataProcess (cyclomatic 18)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 9

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 107

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

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 55 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

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

What we checked — 55 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D17D19D20D21D26D27D28D29D30D31D34D35D43D44AX1AX10AX2AX3AX4AX6GD1IC1M1M2M3M4P1P10P2P3P4P6R1R10R2R3R4R7R9X16X23X27X3X4X5

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, 130 of 144 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 · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1e692-35d6-7ef1-a3e6-5b861cbb34a6.

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, Maven), 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. Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 12 dependency(ies) and leaving 28 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (7 contributor(s) across 501 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 6 hold 2.3% 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.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (apigo-spring-boot-starter/pom.xml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • AC1 Text alternatives — 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 builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
  • AC2 Forms & labels — 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 builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
  • AC3 Page structure — 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 builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
  • AC4 Keyboard semantics — 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 builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
  • AC5 ARIA correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
  • AC6 Visual & motion safety — 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 builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 15 — the compose project is invalid) — error while interpolating services.crabc-api.environment.[]: required variable JWT_SECRET is missing a value: 请先设置 JWT_SECRET 环境变量; runtime evidence skipped.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • 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.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity8.3 / 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 8.3 / 10 · rule-coverage 100% · ceiling Prevented

10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SQLUtil.splitSqlStatements at 37. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being McpToolSupport.buildJdbcUrl at 22 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java (McpToolSupport.buildJdbcUrl at 22), apigo-api/apigo-core/src/main/java/cn/crabc/core/app/support/DatasourceGuard.java (DatasourceGuard.defaultPort at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

SQLUtil.splitSqlStatements (cyclomatic 37)apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:263
ApiDevTools.apiUpdate (cyclomatic 29)apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324
PluginUtils.matches (cyclomatic 29)apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/util/PluginUtils.java:76
ApiTestController.buildParamsMap (cyclomatic 26)apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:215
TreeTransformPlugin.apply (cyclomatic 23)apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/TreeTransformPlugin.java:38

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

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with SQLUtil.splitSqlStatements (cyclomatic 37). — Refactoring it lifts Cyclomatic Complexity from 8.3 to about 8.5/10.

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

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

21 method(s) exceeded the cognitive complexity threshold of 15; the worst was SQLUtil.splitSqlStatements at 64.

SQLUtil.splitSqlStatements (cognitive 64)apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:263
ApiTestController.buildParamsMap (cognitive 44)apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:215
JdbcStatement.stripCommentsAndLiterals (cognitive 41)apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:586
ApiDevTools.apiUpdate (cognitive 36)apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324
TreeTransformPlugin.apply (cognitive 28)apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/TreeTransformPlugin.java:38

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

What to do

  1. Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with SQLUtil.splitSqlStatements (cognitive 64), ApiTestController.buildParamsMap (cognitive 44), JdbcStatement.stripCommentsAndLiterals (cognitive 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 6.8 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

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

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

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

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

7 god class(es) detected.

ClassTooLong: ApiDevTools · ×3apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:44
TooManyMethods: BaseApiInfoServiceImpl · ×2apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:47
FileTooLong: tools/ApiDevTools.javaapigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java
MethodTooLong: ApiDevTools.apiUpdateapigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324

What to do

  1. Resolve the 3 ClassTooLong finding(s) in God Classes — start with ApiDevTools.java, BaseApiInfoServiceImpl.java, SQLUtil.java. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 TooManyMethods finding(s) in God Classes — start with BaseApiInfoServiceImpl.java, BaseDataSource.java. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 FileTooLong finding(s) in God Classes — start with ApiDevTools.java. — One of this dimension's main actionable groups (1 warning-level).

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

D4 · Code Duplication7.9 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

27 duplicated block group(s) detected. 5.2 % of the production lines (867 of 16,590) are in a reported copy. A further 20 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (5 lines × 2) · ×5REDACTED:25
Duplicated block (7 lines × 2) · ×4apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:259
Duplicated block (8 lines × 2) · ×3apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/SysUserController.java:43
Duplicated block (6 lines × 2) · ×3apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:198
Edited copy of a member (7 corresponding lines) · ×2apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:222

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

What to do

  1. Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), ApiDevTools.java (2), DataSourceTools.java. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with DataProcessPlugin.java (2), BaseApiInfoServiceImpl.java, ApiTestController.java. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SysUserController.java, SQLUtil.java, ResultTypeEnum.java. — One of this dimension's main actionable groups (3 warning-level).

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

D5 · Coupling8.7 / 10Strong✓ 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 8.7 / 10 · rule-coverage 100% · ceiling Prevented

6 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.

Off the main sequence: apigo-plugin

What to do

  1. Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

1 of 45 classes have LCOM4 above 3.

Low cohesion: McpToolSupport (LCOM4 6)apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:33

What to do

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

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

D10 · Test Quality10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Prevented

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

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

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

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance8.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

1 of 11 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 8 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. 28 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.

Banned license: com.mysql:mysql-connector-j

What to do

  1. Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).

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

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 2 serious findings✓ 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

Top hotspots: apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java (4×21=84); apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java (3×16=48)

Hotspot: apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java · ×2apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:586

What to do

  1. Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with JdbcStatement.java, AuthInterceptor.java. — One of this dimension's main actionable groups (2 warning-level).

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

D17 · Explicit Debt10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 deducted task-comment markers across 16590 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.

TodoCommentapigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:480

What to do

  1. Resolve the 1 TodoComment finding(s) in Explicit Debt — start with SQLUtil.java. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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

1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundapigo-api/apigo-admin/pom.xml:28

What to do

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

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

D21 · Naming Consistency4.4 / 10Weak✓ Tool-verified

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

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

2 naming inconsistencies among 36 declarations measured against a convention their peers follow.

`ColumnParseVo` spells `Vo` where 18 names in the project spell it `VO`apigo-api/apigo-core/src/main/java/cn/crabc/core/app/entity/vo/ColumnParseVo.java:8
`analyzeSQL` spells `SQL` where 16 names in the project spell it `Sql`apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:113

What to do

  1. Resolve the 1 `ColumnParseVo` spells `Vo` where 18 names in the project spell it `VO` finding(s) in Naming Consistency — start with ColumnParseVo.java. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 `analyzeSQL` spells `SQL` where 16 names in the project spell it `Sql` finding(s) in Naming Consistency — start with SQLUtil.java. — One of this dimension's main actionable groups (1 recommendation-level).

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

D26 · Project Cohesion6.7 / 10Adequate✓ 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 6.7 / 10 · rule-coverage 100% · ceiling Documented

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

Projects may be oversized for their cohesionapigo-api/apigo-core/pom.xml:1

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — 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.4 / 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.4 / 10 · rule-coverage 100% · ceiling Documented

75 % of calls cross a namespace and 13 % 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 High secret finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 1 REDACTED 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)9.0 / 10Stronggated by 2 serious findings✓ 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 9.0 / 10 · rule-coverage 100% · ceiling Documented

2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep hit a parse error in 3 file(s) — `apigo-api/apigo-core/src/main/resources/static/assets/develop-cFFR-jwR.js`, `apigo-api/apigo-core/src/main/resources/static/assets/index-Bq7GivHf.js`, `apigo-api/apigo-core/src/main/resources/static/assets/index-CvHUAiMZ.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED

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 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D30 · Dependency Vulnerabilities9.4 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

D31 · IaC & Container Security8.9 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

5 finding(s): 0 critical, 3 high, 1 medium, 1 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

D34 · Knowledge Freshness9.1 / 10Exemplary✓ Tool-verified

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

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

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

6 of 71 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 71 of the 152 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×6REDACTED:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.8 / 10Stronggated by 6 serious findings✓ 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 9.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: BaseApiInfoMapper.java↔IBaseApiInfoService.java 91%; DataSourceManager.java↔DefaultDataSourceDriver.java 75%; ApiServiceController.java↔ApiTestController.java 59%

Change coupling: BaseApiInfoMapper.java ↔ IBaseApiInfoService.java · ×6apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java:1

What to do

  1. Resolve the 6 Change coupling finding(s) in Change Coupling — start with BaseDataServiceImpl.java (2), BaseApiInfoMapper.java, DataSourceManager.java. — One of this dimension's main actionable groups (6 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 15 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.

AX1 · Captive dependencies10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.

Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.

AX10 · Code composition9.4 / 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.

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

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 segregation9.6 / 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.

  • `BaseApiInfoMapper` declares 16 abstract methods: `checkApiPath`, `countApi`, `countOwnedReleasedApis`, `deleteApiInfo`, `getApiDetail`, `insertApiInfo`, `selectApiApp`, `selectApiById`, `selectApiDetail`, `selectApiGroup`, `selectBaseApi`, `selectList`, `updateApiInfo`, `updateApiState`, `updateDraftContent`, `updateRateLimit`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java:18
  • `IBaseApiInfoService` declares 20 abstract methods: `addApiInfo`, `addChooseApi`, `apiPublish`, `checkApiPath`, `deleteApi`, `destroyApiInfo`, `getApiCache`, `getApiDetail`, `getApiInfo`, `getApiInfoCache`, `getApiList`, `getApiListGroup`, `getApiListUser`, `getApiPage`, `getChooseApi`, `getNotChooseApi`, `getRateLimit`, `saveRateLimit`, `updateApiInfo`, `updateApiState`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/IBaseApiInfoService.java:22

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

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

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

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

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

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability9.2 / 10Exemplary✓ 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 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apigo-api/apigo-admin`.

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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
  • `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:38

What to do

  • Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

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

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

  • Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.

What to do

  • Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene5.0 / 10Adequate✓ 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.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
R1 · Type Safety0.0 / 10Critical✓ Tool-verified

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

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

  • 0 typed · 6 plain JS — the untyped files are apigo-api/apigo-core/src/main/resources/static/assets/403-D4TW9di3.js, apigo-api/apigo-core/src/main/resources/static/assets/BlankLayout-CMEBJCoa.js, apigo-api/apigo-core/src/main/resources/static/assets/UserLayout-BcViDKRQ.js, apigo-api/apigo-core/src/main/resources/static/assets/_plugin-vue_export-helper-DlAUqK2U.js, apigo-api/apigo-core/src/main/resources/static/assets/logo-BsuGIj-2.js, apigo-api/apigo-core/src/main/resources/static/assets/rangeDate-BTmavQEu.js.

What to do

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

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

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

R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

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

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

R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

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

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

R4 · Test Coverage0.0 / 10Critical✓ Tool-verified

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

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

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

What to do

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

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

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

R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

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

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

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.

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

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

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

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

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

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

X3 · Exception handling6.6 / 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. (×2) — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:78, apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:683
  • `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpAuditRecorder.java:60, apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:268
  • `catch (RuntimeException)` 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. — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:153

What to do

  • Swallowed exception (empty catch)
X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

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/38 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 Health50.9Adequate — gated by R1, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture94.7ExemplaryStrongest area.
Maturity59.7Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness26.5Weak — gated by R4, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security84.7Checked 4 of 10Solid.
Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

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

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

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 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 — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
  • AC2 Forms & labels — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
  • AC3 Page structure — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
  • AC4 Keyboard semantics — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
  • AC5 ARIA correctness — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
  • AC6 Visual & motion safety — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — error while interpolating services.crabc-api.environment.[]: required variable JWT_SECRET is missing a value: 请先设置 JWT_SECRET 环境变量; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
  • D12 Dependency Hygiene — Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 12 dependency(ies) and leaving 28 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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; comments in this repository's .java source were not judged.
  • D25 ADR Conformance — no ADRs to check
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not 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 (9 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — no CI workflow found
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript source (service entry point: apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:26 (@RestController))
  • 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • 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.
  • R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
  • R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
  • R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
  • 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • 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 — 9 finding(s)
D28 · Secrets (history) · High secret · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D14 · License Compliance · Banned license · ×1
  • Banned license: com.mysql:mysql-connector-j — `com.mysql:mysql-connector-j` 8.4.0 is published on Maven Central under `GPL-2.0`, which this policy bans, and this repository declares it in a Maven or Gradle manifest. The licence was read from the artifact's POM `<licenses>` block — following `<parent>` where the POM inherits them — and normalised to SPDX before it was judged, because Maven publishes the name as free text (`GNU Affero General Public License v3` is AGPL-3.0). Where a POM lists several licences they are read as a CHOICE, per Maven's own documentation, so this is charged only because EVERY listed licence is banned. Replace the dependency, or record an accepted exception.
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High CVE · ×1
  • REDACTED
Serious — 107 finding(s)
D35 · Change Coupling · Change coupling · ×6
  • Change coupling: BaseApiInfoMapper.java ↔ IBaseApiInfoService.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java:1 — `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java` and `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/IBaseApiInfoService.java` change together 91% of the time (10 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `ce0cafd2` 新增接口限流 (at that commit the files were still `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java` and `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/service/system/IBaseApiInfoService.java`); `25c6b497` 修复调用失效问题 (at that commit the files were still `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java` and `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/service/system/IBaseApiInfoService.java`); `c2dea565` 优化代码结构和功能 (at that commit the files were still `crabc-boot/crabc-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java` and `crabc-boot/crabc-core/src/main/java/cn/crabc/core/app/service/system/IBaseApiInfoService.java`) — run `git show` on any of them.
  • Change coupling: DataSourceManager.java ↔ DefaultDataSourceDriver.java apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/DataSourceManager.java:1 — `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/DataSourceManager.java` and `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/DefaultDataSourceDriver.java` change together 75% of the time (9 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `61bd7b93` 新增支持duckdb和dolphindb数据源 (at that commit the files were still `crabc-api/crabc-datasource/src/main/java/cn/crabc/core/datasource/driver/DataSourceManager.java` and `crabc-api/crabc-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/DefaultDataSourceDriver.java`); `2e8a930b` 修复ck链接问题 (at that commit the files were still `crabc-boot/crabc-datasource/src/main/java/cn/crabc/core/datasource/driver/DataSourceManager.java` and `crabc-boot/crabc-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/DefaultDataSourceDriver.java`); `5d901782` 优化代码 (at that commit the files were still `crabc-boot/crabc-datasource/src/main/java/cn/crabc/core/datasource/driver/DataSourceManager.java` and `crabc-boot/crabc-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/DefaultDataSourceDriver.java`) — run `git show` on any of them.
  • Change coupling: ApiServiceController.java ↔ ApiTestController.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:1 — `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java` and `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java` change together 59% of the time (10 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `a5bcf13c` 新增 SQL执行超时时间配置; `f40c28fe` 数据插件优化 (at that commit the files were still `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java` and `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java`); `56820d1d` 新增 数据插件功能 (at that commit the files were still `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java` and `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java`) — run `git show` on any of them.
  • Change coupling: ApiInfoController.java ↔ BaseApiInfoMapper.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:1 — `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java` and `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `ce0cafd2` 新增接口限流 (at that commit the files were still `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java` and `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java`); `c2dea565` 优化代码结构和功能 (at that commit the files were still `crabc-boot/crabc-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java` and `crabc-boot/crabc-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java`); `4f55ad5b` 接口和应用列表支持excel导入导出 (at that commit the files were still `crabc-boot/crabc-admin/src/main/java/cn/crabc/core/admin/controller/ApiInfoController.java` and `crabc-boot/crabc-admin/src/main/java/cn/crabc/core/admin/mapper/BaseApiInfoMapper.java`) — run `git show` on any of them.
  • Change coupling: BaseDataServiceImpl.java ↔ JdbcStatement.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java:1 — `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java` and `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `a5bcf13c` 新增 SQL执行超时时间配置; `0a16b238` 修复兼容性问题 (at that commit the files were still `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java` and `crabc-api/crabc-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java`); `b80d8b29` 数据源菜单拆分 (at that commit the files were still `crabc-api/crabc-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java` and `crabc-api/crabc-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java`) — run `git show` on any of them.
  • Change coupling: BaseDataServiceImpl.java ↔ JdbcDataSourceRouter.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java:1 — `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java` and `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/config/JdbcDataSourceRouter.java` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a5bcf13c` 新增 SQL执行超时时间配置; `46a0398a` 优化整体代码逻辑 (at that commit the files were still `crabc-boot/crabc-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java` and `crabc-boot/crabc-datasource/src/main/java/cn/crabc/core/datasource/config/JdbcDataSourceRouter.java`); `4d154939` 新增支持Sybase数据源 (at that commit the files were still `crabc-boot/crabc-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java` and `crabc-boot/crabc-datasource/src/main/java/cn/crabc/core/datasource/config/JdbcDataSourceRouter.java`) — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×5
  • Duplicated block (5 lines × 2) REDACTED:25 — REDACTED:25-29 | REDACTED:87-92 — 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) REDACTED:44 — REDACTED:44-48 | REDACTED:66-70 — 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:212 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:212-216 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:621-625 — 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:344 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:344-348 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiOpsTools.java:178-182 — 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 (5 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:147 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:147-151 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:293-297 — 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 (7 lines × 2) · ×4
  • Duplicated block (7 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:259 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:259-265 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:298-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:258` calls `setApiType` and `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:297` 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) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:45 — apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:45-51 | apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/FieldMappingPlugin.java:40-46 — 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 `apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:45` 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) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:37 — apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:37-43 | apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/FieldMappingPlugin.java:33-39 — 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:166 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:166-172 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/MetaDataController.java:75-81 — 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.
D3 · God Classes · ClassTooLong · ×3
  • ClassTooLong: ApiDevTools apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:44 — ClassTooLong — 493 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 93 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: BaseApiInfoServiceImpl apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:47 — ClassTooLong — 436 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 400 significant lines; this is 36 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: SQLUtil apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:40 — ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded), 28 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/SysUserController.java:43 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/SysUserController.java:43-50 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/SysUserController.java:105-112 — 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:713 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:713-720 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:723-730 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (8 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/enums/ResultTypeEnum.java:26 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/enums/ResultTypeEnum.java:26-33 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/enums/SqlTypeEnum.java:27-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×3
  • Duplicated block (6 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:198 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:198-203 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/GroupTools.java:94-99 — 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 `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:198` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseGroupServiceImpl.java:45 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseGroupServiceImpl.java:45-50 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseGroupServiceImpl.java:59-64 — 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiLogController.java:129 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiLogController.java:129-134 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/IBaseApiLogServiceImpl.java:200-205 — 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) · ×3
  • Swallowed exception (caught, then discarded) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpAuditRecorder.java:60 — `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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:153 — `catch (RuntimeException)` 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:268 — `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.
D15 · Churn × Complexity Hotspots · Hotspot · ×2
  • Hotspot: apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:586 — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in JdbcStatement.stripCommentsAndLiterals at line 586. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 21:40:24 +08:00' --until='2026-11-15 21:40:24 +08:00' --full-history --no-merges -- apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java:342 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in AuthInterceptor.preHandle at line 342. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-17..2026-11-15, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-17 21:40:24 +08:00' --until='2026-11-15 21:40:24 +08:00' --full-history --no-merges -- apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: BaseApiInfoServiceImpl apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:47 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: BaseDataSource apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/bean/BaseDataSource.java:25 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×2
  • Edited copy of a member (7 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:222 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:222-231 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:338-344 — 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/ApiContext.java:55 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/ApiContext.java:55-61 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/UserContext.java:91-97 — 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×2
  • Swallowed exception (empty catch) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:78 — 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:683 — 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.
D1 · Cyclomatic Complexity · SQLUtil.splitSqlStatements (cyclomatic 37) · ×1
  • SQLUtil.splitSqlStatements (cyclomatic 37) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:263 — SQLUtil.splitSqlStatements has cyclomatic complexity 37 (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 · ApiDevTools.apiUpdate (cyclomatic 29) · ×1
  • ApiDevTools.apiUpdate (cyclomatic 29) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324 — ApiDevTools.apiUpdate has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PluginUtils.matches (cyclomatic 29) · ×1
  • PluginUtils.matches (cyclomatic 29) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/util/PluginUtils.java:76 — PluginUtils.matches has cyclomatic complexity 29 (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 · ApiTestController.buildParamsMap (cyclomatic 26) · ×1
  • ApiTestController.buildParamsMap (cyclomatic 26) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:215 — ApiTestController.buildParamsMap 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 · TreeTransformPlugin.apply (cyclomatic 23) · ×1
  • TreeTransformPlugin.apply (cyclomatic 23) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/TreeTransformPlugin.java:38 — TreeTransformPlugin.apply has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JdbcStatement.stripCommentsAndLiterals (cyclomatic 21) · ×1
  • JdbcStatement.stripCommentsAndLiterals (cyclomatic 21) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:586 — JdbcStatement.stripCommentsAndLiterals has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · RequestUtils.getIp (cyclomatic 19) · ×1
  • RequestUtils.getIp (cyclomatic 19) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/RequestUtils.java:85 — RequestUtils.getIp has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PluginUtils.mask (cyclomatic 19) · ×1
  • PluginUtils.mask (cyclomatic 19) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/util/PluginUtils.java:162 — PluginUtils.mask has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · DataPluginConfigValidator.validateDataProcess (cyclomatic 18) · ×1
  • DataPluginConfigValidator.validateDataProcess (cyclomatic 18) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java:96 — DataPluginConfigValidator.validateDataProcess has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · AuthInterceptor.preHandle (cyclomatic 16) · ×1
  • AuthInterceptor.preHandle (cyclomatic 16) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java:342 — AuthInterceptor.preHandle has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D17 · Explicit Debt · TodoComment · ×1
  • TodoComment apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:480 — // TODO 暂不支持数组集合 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D2 · Cognitive Complexity · SQLUtil.splitSqlStatements (cognitive 64) · ×1
  • SQLUtil.splitSqlStatements (cognitive 64) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:263 — SQLUtil.splitSqlStatements has cognitive complexity 64 (threshold 15). Drivers by points: if/else 22 (47 pts), boolean chains 11, ternaries 2 (5 pts), loops 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ApiTestController.buildParamsMap (cognitive 44) · ×1
  • ApiTestController.buildParamsMap (cognitive 44) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:215 — ApiTestController.buildParamsMap has cognitive complexity 44 (threshold 15). Drivers by points: if/else 18 (33 pts), boolean chains 6, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · JdbcStatement.stripCommentsAndLiterals (cognitive 41) · ×1
  • JdbcStatement.stripCommentsAndLiterals (cognitive 41) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:586 — JdbcStatement.stripCommentsAndLiterals has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (23 pts), loops 4 (10 pts), boolean chains 8 (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 · ApiDevTools.apiUpdate (cognitive 36) · ×1
  • ApiDevTools.apiUpdate (cognitive 36) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324 — ApiDevTools.apiUpdate has cognitive complexity 36 (threshold 15). Drivers by points: if/else 19 (22 pts), ternaries 8 (11 pts), boolean chains 3 (nesting depth added 6). 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 · TreeTransformPlugin.apply (cognitive 28) · ×1
  • TreeTransformPlugin.apply (cognitive 28) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/TreeTransformPlugin.java:38 — TreeTransformPlugin.apply has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 8, loops 3, ternaries 2 (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 · DataPluginConfigValidator.validateDataProcess (cognitive 26) · ×1
  • DataPluginConfigValidator.validateDataProcess (cognitive 26) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java:96 — DataPluginConfigValidator.validateDataProcess has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlExceptionUtils.isTimeout (cognitive 25) · ×1
  • SqlExceptionUtils.isTimeout (cognitive 25) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/util/SqlExceptionUtils.java:63 — SqlExceptionUtils.isTimeout has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 5, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MetaDataTools.schemas (cognitive 24) · ×1
  • MetaDataTools.schemas (cognitive 24) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/MetaDataTools.java:64 — MetaDataTools.schemas has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (6 pts), ternaries 2 (4 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 · ApiServiceController.checkParams (cognitive 23) · ×1
  • ApiServiceController.checkParams (cognitive 23) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:125 — ApiServiceController.checkParams has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, error handling 1 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DataProcessPlugin.calculate (cognitive 23) · ×1
  • DataProcessPlugin.calculate (cognitive 23) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:172 — DataProcessPlugin.calculate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3 (8 pts), boolean chains 3, loops 2 (3 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 · JdbcStatement.selectPage (cognitive 21) · ×1
  • JdbcStatement.selectPage (cognitive 21) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:117 — JdbcStatement.selectPage has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 3 (6 pts), boolean chains 2, error handling 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 · FieldMappingPlugin.apply (cognitive 21) · ×1
  • FieldMappingPlugin.apply (cognitive 21) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/FieldMappingPlugin.java:32 — FieldMappingPlugin.apply has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DefaultDataSourceDriver.createHikariDataSource (cognitive 20) · ×1
  • DefaultDataSourceDriver.createHikariDataSource (cognitive 20) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/DefaultDataSourceDriver.java:126 — DefaultDataSourceDriver.createHikariDataSource has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 5 (7 pts), boolean chains 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 · RequestUtils.getIp (cognitive 19) · ×1
  • RequestUtils.getIp (cognitive 19) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/RequestUtils.java:85 — RequestUtils.getIp has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 8, ternaries 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 · SingleObjectPlugin.apply (cognitive 18) · ×1
  • SingleObjectPlugin.apply (cognitive 18) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/SingleObjectPlugin.java:36 — SingleObjectPlugin.apply has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 2 (5 pts), loops 1 (2 pts), boolean chains 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 · SqlPreviewGuard.lineCommentIndex (cognitive 17) · ×1
  • SqlPreviewGuard.lineCommentIndex (cognitive 17) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:222 — SqlPreviewGuard.lineCommentIndex has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 6, 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 · DataSourceTools.datasourceUpdate (cognitive 17) · ×1
  • DataSourceTools.datasourceUpdate (cognitive 17) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:166 — DataSourceTools.datasourceUpdate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 6, boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · SQLUtil.analyzeSQL (cognitive 17) · ×1
  • SQLUtil.analyzeSQL (cognitive 17) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:113 — SQLUtil.analyzeSQL has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · SQLUtil.findXmlTagEnd (cognitive 17) · ×1
  • SQLUtil.findXmlTagEnd (cognitive 17) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:588 — SQLUtil.findXmlTagEnd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DataPluginExecutor.execute (cognitive 17) · ×1
  • DataPluginExecutor.execute (cognitive 17) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginExecutor.java:68 — DataPluginExecutor.execute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 4 (6 pts), boolean chains 1, 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 · AppTools.currentAuthorized (cognitive 16) · ×1
  • AppTools.currentAuthorized (cognitive 16) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:221 — AppTools.currentAuthorized has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (3 pts), boolean chains 2, 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.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: tools/ApiDevTools.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java — FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: ApiDevTools (44-711). The bar is 500 significant lines; this is 28 over it, 1.06× 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.
D3 · God Classes · MethodTooLong · ×1
  • MethodTooLong: ApiDevTools.apiUpdate apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324 — MethodTooLong — apiUpdate runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
D31 · IaC & Container Security · Medium IaC · ×1
  • REDACTED
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:181 — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:181-202 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:205-226 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:229-250 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:256-323 — 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 (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:165 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:165-192 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:63-90 — 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 (26 corresponding lines) · ×1
  • Edited copy of a member (26 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/MetaDataTools.java:112 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/MetaDataTools.java:112-137 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/MetaDataTools.java:150-177 — 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 (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:141 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:141-187 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:459-491 — 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 (16 corresponding lines) · ×1
  • Edited copy of a member (16 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:405 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:405-420 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:449-466 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:56 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:56-78 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:88-116 — 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 copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiOpsTools.java:209 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiOpsTools.java:209-223 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/LogTools.java:188-201 — 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 (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:19 — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:19-37 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:40-58 — 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 copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java:602 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java:602-613 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java:621-632 — 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 · Edited copy of a member (10 corresponding lines) · ×1
  • Edited copy of a member (10 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseGroupServiceImpl.java:43 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseGroupServiceImpl.java:43-54 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseGroupServiceImpl.java:57-66 — 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 copies of one member (4 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 10+ corresponding lines) REDACTED:24 — REDACTED:24-33 | REDACTED:43-52 | REDACTED:62-74 | REDACTED:83-96 — These 4 members are one piece of code written 4 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 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/ResourceOwnerGuard.java:73 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/ResourceOwnerGuard.java:73-83 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/ResourceOwnerGuard.java:91-101 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/ResourceOwnerGuard.java:109-120 — 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 copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:277 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:277-289 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/support/DatasourceGuard.java:328-342 — 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, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:242 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:242-255 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:712-720 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:722-730 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×1
  • Edited copy of a member (9 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:196 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:196-204 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:730-739 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 7+ corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:699 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:699-706 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:265-271 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/MetaDataTools.java:214-220 — These 3 members are one piece of code written 3 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 3 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) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:147 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:147-151 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseDataSourceServiceImpl.java:142-146 — 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 copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:209 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:209-214 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/config/JdbcDataSourceRouter.java:53-61 — 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 (13–22 lines × 2) · ×1
  • Duplicated block (13–22 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:146 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:146-167 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:461-473 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:191 — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:191-202 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:215-226 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:239-250 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:191` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1
  • Duplicated block (12 lines × 2) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:23 — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:23-34 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:44-55 — 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 `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:23` 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 (11 lines × 2) · ×1
  • Duplicated block (11 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:182 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:182-192 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:80-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:182` 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 (9–10 lines × 4) · ×1
  • Duplicated block (9–10 lines × 4) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:193 — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:193-201 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:217-225 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:241-249 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:307-316 — 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 `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:193` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:293 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:293-302 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:304-313 — 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 `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:293` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:303` calls `isBackslashEscaped` and `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:292` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:182 — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:182-189 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:206-213 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:230-237 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:182` 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–7 lines × 3) · ×1
  • Duplicated block (6–7 lines × 3) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:185 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:185-190 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:83-88 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:281-287 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:281` 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. 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `pageNum` to `Integer` 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 (3–6 lines × 3) · ×1
  • Duplicated block (3–6 lines × 3) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:407 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:407-412 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:431-436 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:450-452 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:407` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/enums/ApiAuthEnum.java:16 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/enums/ApiAuthEnum.java:16-35 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/enums/ApiStateEnum.java:18-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/PageInfo.java:16 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/PageInfo.java:16-39 | apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/util/PageInfo.java:17-40 — before extracting anything, compare `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/PageInfo.java` and `apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/util/PageInfo.java` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 × 3) · ×1
  • Duplicated block (5 lines × 3) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:174 — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:174-178 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:610-614 | apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/LogTools.java:189-193 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:615` calls `putIfNotNull`, `getApiType`, `getAuthType` and `apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:179` 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.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: apigo-plugin — apigo-plugin: abstractness 0.08, instability 0.00, distance 0.92 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: McpToolSupport (LCOM4 6) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:33 — McpToolSupport's methods fall into 6 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 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 6 plain JS — the untyped files are apigo-api/apigo-core/src/main/resources/static/assets/403-D4TW9di3.js, apigo-api/apigo-core/src/main/resources/static/assets/BlankLayout-CMEBJCoa.js, apigo-api/apigo-core/src/main/resources/static/assets/UserLayout-BcViDKRQ.js, apigo-api/apigo-core/src/main/resources/static/assets/_plugin-vue_export-helper-DlAUqK2U.js, apigo-api/apigo-core/src/main/resources/static/assets/logo-BsuGIj-2.js, apigo-api/apigo-core/src/main/resources/static/assets/rangeDate-BTmavQEu.js.
R4 · Test Coverage · Test Coverage · ×1
  • Test Coverage — 0% of 6 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
Minor — 28 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×6
  • 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 apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/Result.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 apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/bean/Table.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 apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/DataSourceController.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 apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/StatementMapper.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 apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/bean/Column.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.
X10 · Duplicated predicate · Duplicated predicate · ×3
  • Duplicated predicate apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:205 — `detail == null || detail.getBaseInfo() == null || detail.getBaseInfo().getApiId() == null` appears character-identically in 2 files — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java, apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiOpsTools.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 apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java:236 — `enabled != null && Boolean.parseBoolean(enabled.toString())` appears character-identically in 2 files — apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java, apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginExecutor.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 apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:159 — `sql.contains("<if ") || sql.contains("<when ")` appears character-identically in 2 files — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java, apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.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.
AX6 · Interface segregation · Fat interface · ×2
  • Fat interface: BaseApiInfoMapper (16 abstract methods) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java:18 — `BaseApiInfoMapper` declares 16 abstract methods: `checkApiPath`, `countApi`, `countOwnedReleasedApis`, `deleteApiInfo`, `getApiDetail`, `insertApiInfo`, `selectApiApp`, `selectApiById`, `selectApiDetail`, `selectApiGroup`, `selectBaseApi`, `selectList`, `updateApiInfo`, `updateApiState`, `updateDraftContent`, `updateRateLimit`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IBaseApiInfoService (20 abstract methods) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/IBaseApiInfoService.java:22 — `IBaseApiInfoService` declares 20 abstract methods: `addApiInfo`, `addChooseApi`, `apiPublish`, `checkApiPath`, `deleteApi`, `destroyApiInfo`, `getApiCache`, `getApiDetail`, `getApiInfo`, `getApiInfoCache`, `getApiList`, `getApiListGroup`, `getApiListUser`, `getApiPage`, `getChooseApi`, `getNotChooseApi`, `getRateLimit`, `saveRateLimit`, `updateApiInfo`, `updateApiState`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found apigo-api/apigo-admin/pom.xml:28 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `apigo-api/apigo-admin/pom.xml` makes this repository a deployable product (line 28).
D21 · Naming Consistency · `ColumnParseVo` spells `Vo` where 18 names in the project spell it `VO` · ×1
  • `ColumnParseVo` spells `Vo` where 18 names in the project spell it `VO` apigo-api/apigo-core/src/main/java/cn/crabc/core/app/entity/vo/ColumnParseVo.java:8 — 18 of 19 names in project apigo-core spell the token `VO` (18 of 19; unit: names in project apigo-core containing `VO`). Peers: ApiTestController.applyPluginToPreview(previewVO) (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:76); cn.crabc.core.app.entity.vo.ApiComboBoxVO (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/entity/vo/ApiComboBoxVO.java:8); cn.crabc.core.app.entity.vo.ApiInfoVO (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/entity/vo/ApiInfoVO.java:17); cn.crabc.core.app.entity.vo.ApiLogDailyTrendVO (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/entity/vo/ApiLogDailyTrendVO.java:13); cn.crabc.core.app.entity.vo.ApiLogGroupCountVO (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/entity/vo/ApiLogGroupCountVO.java:13). Rename to `ColumnParseVO`. [rule N6]
D21 · Naming Consistency · `analyzeSQL` spells `SQL` where 16 names in the project spell it `Sql` · ×1
  • `analyzeSQL` spells `SQL` where 16 names in the project spell it `Sql` apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:113 — 16 of 17 names in project apigo-core spell the token `Sql` (16 of 17; unit: names in project apigo-core containing `Sql`). Peers: ApiTestController.runApiSql (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:58); ApiTestController.testApiSql (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:111); MetaDataController.getSqlTemplate (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/MetaDataController.java:115); cn.crabc.core.app.entity.BaseApiSql (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/entity/BaseApiSql.java:13); SqlPreviewGuard.validatePreviewSql (apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:125). Rename to `analyzeSql`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion apigo-api/apigo-core/pom.xml:1 — `apigo-api/apigo-core` (16771 LoC, 118 module-visible types across 22 directories) overshoots its size bounds. 1 of 6 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 6.7/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 6 of 71 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 71 of the 152 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: REDACTED, apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/Result.java, apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/bean/Table.java, apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/DataSourceController.java, apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/StatementMapper.java, apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/bean/Column.java. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
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 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apigo-api/apigo-admin`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation REDACTED:38 — `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/38 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`.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×1
  • Hand-rolled JSON/XML parsing via regex apigo-api/apigo-core/src/main/resources/static/assets/develop-cFFR-jwR.js:42 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
X7 · Silent fallback defaults · Silent fallback default in catch · ×1
  • Silent fallback default in catch apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpAuditRecorder.java:60 — `safeUserId` swallows every exception into `return "unknown"` — 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.

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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-d01f8760fb3446f9952eae486e8351ba/history.json --exit-code 0 --source .11artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=172" --report-format json --report-path /tmp/watchdog-gitleaks-d01f8760fb3446f9952eae486e8351ba/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=372 --max-count=134" --report-format json --report-path /tmp/watchdog-gitleaks-d01f8760fb3446f9952eae486e8351ba/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.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-d01f8760fb3446f9952eae486e8351ba/tree.json --exit-code 0 --source .2artifacts/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 .2artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .1artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .5artifacts/raw/trivy-config.json
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—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1e692-35d6-7ef1-a3e6-5b861cbb34a6 · 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