Public report — DoKit, published 6 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
207findings with an exact file:lineof 213 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
39/107dimensions across the health lenses147835 LoC — wide & deep
Executive summary
Read through the Preview lens: this repo is pre-1.0 / in development, so the colour bands are relaxed to what a preview needs — *green* means good enough for a preview, not yet production-stable. Code correctness and security stay near-strict even here; the score itself is absolute and comparable across repos.
didi/DoKit carries serious gaps (37%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Architecture (87%) — the structure is clean and changes stay contained.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (28%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Accessibility (30%) is the next concern — it raises ongoing delivery and operational cost.
Leadership focus, highest impact first: CI workflow that builds and runs the test suite on every push/PR (CI/CD gates); Run what this repository's stack ships (Security & performance tooling); eslint and type checking (adopt TypeScript (Tooling).
For scale: Large (~147,835 production lines); rebuilding it from scratch would take roughly ~0.9 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (87%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.7× (at 37% quality) — the last 20% of quality is most of the work
Size & shape
Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
Dead frontend code
~259 LoC unreachable (7 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~0.9 person-years of build effort (about ~€130,000 to rebuild). Its weakest lens is Readiness at 28% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
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.
Value concentrated against a weak lens · High · Value at risk
This is a Large asset (~0.9 person-years to rebuild), and its weakest lens is Readiness at 28%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a CI workflow that builds and runs the test suite on every push/PR. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a CI workflow that builds and runs the test suite on every push/PR.
Architecture — module dependency matrix
140 modules, 177 dependencies — 4 dependency cycles, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 60% · Adequate · gated by R1
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A06:2021 — Vulnerable & Outdated Components
47
High / Critical
A03:2021 — Injection
8
High / Critical
Roadmap
First, establish a continuous integration pipeline to automatically build the code and run the test suite on every change. Integrate security scanning into this workflow to ensure that security regressions fail the build immediately. Next, add linting and type checking to the build process to enforce code quality and catch errors early. Finally, remove unused dependencies and ensure all form controls and buttons have proper programmatic labels for accessibility.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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 a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 37 of 39 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 39 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 207 of 213 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — 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.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
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").
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
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.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
+ 14 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 ScalpelFrameLayout.onTouchEvent (cyclomatic 32) finding(s) in Cyclomatic Complexity — start with ScalpelFrameLayout.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 NetWorkMockFragment.filterAndNotifyData (cyclomatic 27) finding(s) in Cyclomatic Complexity — start with NetWorkMockFragment.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 SeekRangeBar.onTouchEvent (cyclomatic 27) finding(s) in Cyclomatic Complexity — start with SeekRangeBar.java. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cyclomatic Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 45 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 NetWorkMockFragment.filterAndNotifyData (cognitive 82) finding(s) in Cognitive Complexity — start with NetWorkMockFragment.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 SeekRangeBar.onTouchEvent (cognitive 80) finding(s) in Cognitive Complexity — start with SeekRangeBar.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ScalpelFrameLayout.onTouchEvent (cognitive 74) finding(s) in Cognitive Complexity — start with ScalpelFrameLayout.java. — One of this dimension's main actionable groups (1 warning-level).
Stand up a CI pipeline, then gate Cognitive Complexity in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.5 / 10Exemplary✓ 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.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
DoKit的文档体系非常全面，包含7个README文件和6个架构/设计文档，内容覆盖了简介、领域生态、使用手册、更新日志、社区活动、开发背景、功能模块（平台工具、常用工具、性能检测、视觉工具、Weex专项工具、自定义业务集成）、相关文档、交流群、QQ群、微信公众号、项目成员、使用提醒、友情链接、协议，以及iOS和Flutter的接入指南。文档结构清晰，每个主要部分都列出了子项，并且更新日志文件详细记录了版本迭代内容。 The DoraemonKit-Android release notes are comprehensive and well-organized for the versioned changelog (3.5.x, 3.4.x, 3.3.x), covering each minor release with bug fixes, DoKit plugin versions, migration notes, and a dedicated alpha02 section that lists groupId changes, AS4.2 support, removed AndroidUtil, new LBS, and icon updates plus an explicit tips list. The outline is clipped mid-3.3.5 (dokitx corresponds to androidx/support) before the body ends, so any listed sections are present in the document but not shown; this does not affect quality.
What to do
Improve Documentation Quality — currently 7.9/10. — DoKit的文档体系非常全面，包含7个README文件和6个架构/设计文档，内容覆盖了简介、领域生态、使用手册、更新日志、社区活动、开发背景、功能模块（平台工具、常用工具、性能检测、视觉工具、Weex专项工具、自定义业务集成）、相关文档、交流群、QQ群、微信公众号、项目成员、使用提醒、友情链接、协议，以及iOS和Flutter的接入指南。文档结构清晰，每个主要部分都列出了子项，并且更新日志文件详细记录了版本迭代内容。 The DoraemonKit-Android release notes are comprehensive and well-organized for the versioned changelog (3.5.x, 3.4.x, 3.3.x), covering each minor release with bug fixes, DoKit plugin versions, migration notes, and a dedicated alpha02 section that lists groupId changes, AS4.2 support, removed AndroidUtil, new LBS, and icon updates plus an explicit tips list. The outline is clipped mid-3.3.5 (dokitx corresponds to androidx/support) before the body ends, so any listed sections are present in the document but not shown; this does not affect quality.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
High: object-deserialization · ×3Android/dokit-leakcanary/src/main/java/com/squareup/leakcanary/AnalyzedHeap.java:45detected by semgrep finding
Medium: use-of-md5 · ×3Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/EncryptUtils.java:181detected by semgrep finding
Low: insecure-trust-manager · ×2Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/MyTrustManager.java:28detected by semgrep finding
What to do
Resolve the 3 High finding(s) in Static Analysis (SAST) — start with AnalyzedHeap.java, ConvertUtils.java, DoKitCacheUtils.java. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 3 Medium finding(s) in Static Analysis (SAST) — start with EncryptUtils.java, FileUtils.java, MyTrustManager.java. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Low finding(s) in Static Analysis (SAST) — start with MyTrustManager.java (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
570 of 570 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/PinyinUtils.java.
Largest orphaned file · ×3Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/PinyinUtils.java
Dormant codebase
What to do
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with PinyinUtils.java, ActivityUtils.java, ImageUtils.java. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×25Flutter/pubspec.lockdetected by osv-scanner finding
Critical CVE: [GHSA redacted] · ×5miniapp/package-lock.jsondetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×13miniapp/package-lock.jsondetected by osv-scanner finding
Low CVE: [GHSA redacted] · ×4miniapp/package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 25 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (24), pubspec.lock. — One of this dimension's main actionable groups (25 issue-level).
Resolve the 13 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (13). — One of this dimension's main actionable groups (13 warning-level).
Resolve the 5 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (5). — One of this dimension's main actionable groups (5 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives3.1 / 10Weak✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×11) — card.vue:9, top-bar.vue:4, version.vue:7, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels2.5 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×12) — index.html:48, index.html:69, elementContainer.vue:24, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×4) — op-command.vue:4, ToolH5Door.vue:4, ToolH5Door.vue:19, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×7) — index.html:2, independent.html:2, index.html:2, …
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×2) — info-card.vue:15, ElementAttributes.vue:5
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×25) — card.vue:7, top-bar.vue:3, app.vue:3, …
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. (×2) — FPS.vue:9, IndependPluginDemo.vue:7
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 19 of 26 project(s) that lack one — worth up to 1.5 pts.
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 `NNNN-title.md` documents 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/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
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.
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 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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
What to do
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 112 plain JS — the untyped files are Web/packages/core/__tests__/index.test.js, Web/packages/core/src/common/components/card.vue, Web/packages/core/src/common/components/dokit-ui/index.js, Web/packages/core/src/common/components/dokit-ui/layout/col.js, Web/packages/core/src/common/components/dokit-ui/layout/index.js, Web/packages/core/src/common/components/dokit-ui/layout/row.js (+106 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).
Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.
Web/packages/web/src/plugins/storage/local-storage.vue:8 · Web/packages/web/src/plugins/storage/session-storage.vue:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — local-storage.vue:8
Web/packages/core/src/common/js/util.js:19 · Web/packages/web/src/assets/util.js:24 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — util.js:19
Web/packages/utils/src/deepClone.js:60 · Web/packages/web/src/assets/deepClone.js:60 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — deepClone.js:60
Web/packages/web/src/common/info-card.vue:34 · Web/packages/web/src/plugins/storage/info-card.vue:39 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — info-card.vue:34
Web/packages/web/src/plugins/console/console-tap.vue:45 · Web/packages/web/src/plugins/resources/resource-tap.vue:48 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — console-tap.vue:45
Web/packages/core/src/common/js/util.js:83 · Web/packages/web/src/assets/util.js:90 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — util.js:83
Web/packages/core/src/common/js/finder/index.js:190 · Web/packages/core/src/common/js/xpath/index.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — index.js:190
Web/packages/web/src/common/info-card.vue:75 · Web/packages/web/src/plugins/storage/info-card.vue:79 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — info-card.vue:75
What to do
Extract the duplicated blocks into shared functions/components.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
Web/packages/web-independent/src/index.js:2 reaches into another package with a relative path (../../web/src/feature) — import the package by name instead. — index.js:2
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
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.
Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×8) — EventRecorder.js:205, index.js:53, index.js:456, …
Do you agree with this assessment?
R3 · Large Files8.9 / 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.
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D33 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D33). Deterministic.
Do you agree with this assessment?
R6 · Tooling3.4 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✗
What to do
Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code8.6 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 11 application, 5 tooling and 3 test entry point(s) detected in this repo. Gate removals on your build/type-check — an undetected custom entry would make these reachable.
no import path from any entry point (11 application, 5 tooling, 3 test roots considered) (×7) — FPS.vue, ToolsContainer.vue, top-bar.vue, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×3) — home.vue:14, app.vue:27, index.js:1
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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.
Break each cycle by extracting the shared piece into a module both sides can import.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 68 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.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set 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
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
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
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface 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 — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
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.
D10 Test Quality — ~5081 lines of test source are present (.java, .kt, .js) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (a Gradle version catalogue, package.json and a Dart pubspec.yaml), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.dart, .java, .kt, .swift) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle version catalogue, package.json and a Dart pubspec.yaml — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .dart, .java, .kt, .swift, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
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
D9 Test Distribution — Test source is present (.java, .kt, .js) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 121 value object(s); a JPA/Axon/DDD domain-annotation stack (@Entity/@Aggregate/@Embeddable)
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
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 check looks for
GD1 Unfinished & placeholder code — no source files
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — no CI workflow found
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, 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
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
R4 Test Coverage — 3 test file(s) reach none of 97 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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.
Issue — 33 finding(s)
D38 · OSV Dependency Vulnerabilities· High CVE · ×25
High CVE: [GHSA redacted] Flutter/pubspec.lock— archive 3.1.2: [GHSA redacted] — upgrade to 3.3.8. This one row stands for the 2 advisories this scan raises against archive 3.1.2: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— brace-expansion 1.1.11: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.16 with an `overrides` entry). This is 1 of 5 advisories with a published fix this scan raises against brace-expansion 1.1.11, and their fixed versions do not agree — anything below 1.1.18 still leaves at least one of them open. Take this package to 1.1.18 or later: that is the floor for the package, not this row's target alone. This one row stands for the 5 advisories this scan raises against brace-expansion 1.1.11: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— braces 2.3.2: [GHSA redacted] — braces is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 3.0.3 is a MAJOR ahead of the resolved 2.3.2, so an `overrides` pin would force a breaking version under a dependent written against 2.3.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] miniapp/package-lock.json— braces 3.0.2: [GHSA redacted] — braces is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin braces to 3.0.3 with an `overrides` entry).
High CVE: [GHSA redacted] miniapp/package-lock.json— copy-props 2.0.4: [GHSA redacted] — copy-props is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin copy-props to 2.0.5 with an `overrides` entry).
High CVE: [GHSA redacted] miniapp/package-lock.json— cross-spawn 3.0.1: [GHSA redacted] — cross-spawn is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 6.0.6 is a MAJOR ahead of the resolved 3.0.1, so an `overrides` pin would force a breaking version under a dependent written against 3.0.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] miniapp/package-lock.json— decode-uri-component 0.2.0: [GHSA redacted] — decode-uri-component is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin decode-uri-component to 0.2.1 with an `overrides` entry).
High CVE: [GHSA redacted] miniapp/package-lock.json— glob-parent 5.1.1: [GHSA redacted] — glob-parent is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin glob-parent to 5.1.2 with an `overrides` entry).
High CVE: [GHSA redacted] miniapp/package-lock.json— hawk 3.1.3: [GHSA redacted] — hawk is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 9.0.1 is a MAJOR ahead of the resolved 3.1.3, so an `overrides` pin would force a breaking version under a dependent written against 3.1.3; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] miniapp/package-lock.json— hoek 2.16.3: [GHSA redacted] — no fixed version has been published yet. Track the advisory; hoek is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent. This one row stands for the 2 advisories this scan raises against hoek 2.16.3: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— ini 1.3.5: [GHSA redacted] — ini is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ini to 1.3.6 with an `overrides` entry).
High CVE: [GHSA redacted] miniapp/package-lock.json— is-svg 2.1.0: [GHSA redacted] — is-svg is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.2.2 is a MAJOR ahead of the resolved 2.1.0, so an `overrides` pin would force a breaking version under a dependent written against 2.1.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories with a published fix this scan raises against is-svg 2.1.0, and their fixed versions do not agree — anything below 4.3.0 still leaves at least one of them open. Take this package to 4.3.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against is-svg 2.1.0: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— js-yaml 3.7.0: [GHSA redacted] — js-yaml is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin js-yaml to 3.15.0 with an `overrides` entry). This is 1 of 5 advisories with a published fix this scan raises against js-yaml 3.7.0, and their fixed versions do not agree — anything below 3.15.0 still leaves at least one of them open. Take this package to 3.15.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 5 advisories this scan raises against js-yaml 3.7.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— json5 2.1.3: [GHSA redacted] — json5 is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin json5 to 2.2.2 with an `overrides` entry).
High CVE: [GHSA redacted] miniapp/package-lock.json— lodash 4.17.15: [GHSA redacted] — lodash is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin lodash to 4.17.21 with an `overrides` entry). This is 1 of 4 advisories with a published fix this scan raises against lodash 4.17.15, and their fixed versions do not agree — anything below 4.18.0 still leaves at least one of them open. Take this package to 4.18.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against lodash 4.17.15: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— lodash.pick 4.4.0: [GHSA redacted] — no fixed version has been published yet. Track the advisory; lodash.pick is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent.
High CVE: [GHSA redacted] miniapp/package-lock.json— lodash.template 3.6.2: [GHSA redacted] — no fixed version has been published yet. Track the advisory; lodash.template is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent.
High CVE: [GHSA redacted] miniapp/package-lock.json— minimatch 3.0.4: [GHSA redacted] — minimatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimatch to 3.1.4 with an `overrides` entry). This is 1 of 4 advisories with a published fix this scan raises against minimatch 3.0.4, and their fixed versions do not agree — anything below 3.1.4 still leaves at least one of them open. Take this package to 3.1.4 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against minimatch 3.0.4: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— picomatch 2.2.2: [GHSA redacted] — picomatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin picomatch to 2.3.2 with an `overrides` entry). This one row stands for the 2 advisories this scan raises against picomatch 2.2.2: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— postcss 5.2.18: [GHSA redacted] — postcss is not declared by the manifests that govern this lockfile: it is pulled in transitively here (the ^8.2.12 this repo declares for it belongs to a separate install root and does not reach this one), so upgrade the dependency that requires it (— 8.5.12 is a MAJOR ahead of the resolved 5.2.18, so an `overrides` pin would force a breaking version under a dependent written against 5.2.18; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 6 advisories with a published fix this scan raises against postcss 5.2.18, and their fixed versions do not agree — anything below 8.5.23 still leaves at least one of them open. Take this package to 8.5.23 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against postcss 5.2.18: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— postcss 6.0.23: [GHSA redacted] — postcss is not declared by the manifests that govern this lockfile: it is pulled in transitively here (the ^8.2.12 this repo declares for it belongs to a separate install root and does not reach this one), so upgrade the dependency that requires it (— 8.5.12 is a MAJOR ahead of the resolved 6.0.23, so an `overrides` pin would force a breaking version under a dependent written against 6.0.23; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 6 advisories with a published fix this scan raises against postcss 6.0.23, and their fixed versions do not agree — anything below 8.5.23 still leaves at least one of them open. Take this package to 8.5.23 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against postcss 6.0.23: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— qs 6.4.0: [GHSA redacted] — qs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin qs to 6.4.1 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against qs 6.4.0, and their fixed versions do not agree — anything below 6.14.1 still leaves at least one of them open. Take this package to 6.14.1 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against qs 6.4.0: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] miniapp/package-lock.json— semver 5.7.1: [GHSA redacted] — semver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin semver to 5.7.2 with an `overrides` entry).
High CVE: [GHSA redacted] miniapp/package-lock.json— semver 7.0.0: [GHSA redacted] — semver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin semver to 7.5.2 with an `overrides` entry).
High CVE: [GHSA redacted] miniapp/package-lock.json— y18n 3.2.1: [GHSA redacted] — y18n is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin y18n to 3.2.2 with an `overrides` entry).
Critical CVE: [GHSA redacted] miniapp/package-lock.json— @babel/traverse 7.9.5: [GHSA redacted] — @babel/traverse is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/traverse to 7.23.2 with an `overrides` entry).
Critical CVE: [GHSA redacted] miniapp/package-lock.json— form-data 2.1.4: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin form-data to 2.5.4 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against form-data 2.1.4, and their fixed versions do not agree — anything below 2.5.6 still leaves at least one of them open. Take this package to 2.5.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against form-data 2.1.4: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] miniapp/package-lock.json— json-schema 0.2.3: [GHSA redacted] — json-schema is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin json-schema to 0.4.0 with an `overrides` entry).
Critical CVE: [GHSA redacted] miniapp/package-lock.json— minimist 1.2.5: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 1.2.6 with an `overrides` entry).
Critical CVE: [GHSA redacted] miniapp/package-lock.json— tar 4.4.13: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 7.5.19 is a MAJOR ahead of the resolved 4.4.13, so an `overrides` pin would force a breaking version under a dependent written against 4.4.13; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 18 advisories with a published fix this scan raises against tar 4.4.13, and their fixed versions do not agree — anything below 4.4.18 still leaves at least one of them open. Take this package to 4.4.18 or later: that is the floor for the package, not this row's target alone. This one row stands for the 18 advisories this scan raises against tar 4.4.13: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High: object-deserialization Android/dokit-leakcanary/src/main/java/com/squareup/leakcanary/AnalyzedHeap.java:45— Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data stream to make sure it is not tampered with, or consider only transmitting object fields and populating a new object. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
High: object-deserialization Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/ConvertUtils.java:327— Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data stream to make sure it is not tampered with, or consider only transmitting object fields and populating a new object. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
High: object-deserialization Android/dokit/src/main/java/com/didichuxing/doraemonkit/util/DoKitCacheUtils.java:76— Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data stream to make sure it is not tampered with, or consider only transmitting object fields and populating a new object. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
TooManyMethods: DelegatingHttpsURLConnection Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/ObsoleteUrlFactory.java:937— TooManyMethods — 65 methods. 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: TencentLocationImp Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/TencentLocationImp.java:10— TooManyMethods — 63 methods. 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: EasyRefreshLayout Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/easyrefresh/EasyRefreshLayout.java:34— TooManyMethods — 57 methods. 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: GpsMockFragment Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/GpsMockFragment.java:83— TooManyMethods — 54 methods. 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: AMapNaviListenerProxyNoOp Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapNaviListenerProxyNoOp.java:34— TooManyMethods — 47 methods. 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: MultiLineRadioGroup Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/MultiLineRadioGroup.java:33— TooManyMethods — 47 methods. 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: SmartTable Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/component/SmartTable.java:32— TooManyMethods — 41 methods. 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: MatrixHelper Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/utils/MatrixHelper.java:30— TooManyMethods — 36 methods. 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: TableConfig Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/TableConfig.java:9— TooManyMethods — 35 methods. 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: PerformanceDataManager Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:42— TooManyMethods — 34 methods. 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: OkHttpURLConnection Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/ObsoleteUrlFactory.java:315— TooManyMethods — 33 methods. 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: ByteCountBufferedSinkV4 Android/dokit-okhttp-v4/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV4.java:26— TooManyMethods — 32 methods. 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: DokitDeviceUtils Android/dokit/src/main/java/com/didichuxing/doraemonkit/util/DokitDeviceUtils.java:33— TooManyMethods — 31 methods. 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: TableData Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/bean/TableData.java:14— TooManyMethods — 31 methods. 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.
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×13
Medium CVE: [GHSA redacted] miniapp/package-lock.json— @babel/helpers 7.9.2: [GHSA redacted] — @babel/helpers is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/helpers to 7.26.10 with an `overrides` entry).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— @babel/runtime 7.9.2: [GHSA redacted] — @babel/runtime is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/runtime to 7.26.10 with an `overrides` entry).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— ajv 4.11.8: [GHSA redacted] — ajv is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 6.14.0 is a MAJOR ahead of the resolved 4.11.8, so an `overrides` pin would force a breaking version under a dependent written against 4.11.8; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories with a published fix this scan raises against ajv 4.11.8, and their fixed versions do not agree — anything below 6.14.0 still leaves at least one of them open. Take this package to 6.14.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against ajv 4.11.8: [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] miniapp/package-lock.json— browserslist 4.12.0: [GHSA redacted] — browserslist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin browserslist to 4.16.5 with an `overrides` entry).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— color-string 0.3.0: [GHSA redacted] — color-string is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 1.5.5 is a MAJOR ahead of the resolved 0.3.0, so an `overrides` pin would force a breaking version under a dependent written against 0.3.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— hosted-git-info 2.8.8: [GHSA redacted] — hosted-git-info is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin hosted-git-info to 2.8.9 with an `overrides` entry).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— micromatch 3.1.10: [GHSA redacted] — micromatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.0.8 is a MAJOR ahead of the resolved 3.1.10, so an `overrides` pin would force a breaking version under a dependent written against 3.1.10; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— micromatch 4.0.2: [GHSA redacted] — micromatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin micromatch to 4.0.8 with an `overrides` entry).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— path-parse 1.0.6: [GHSA redacted] — path-parse is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin path-parse to 1.0.7 with an `overrides` entry).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— request 2.81.0: [GHSA redacted] — no fixed version has been published yet. Track the advisory; request is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent.
Medium CVE: [GHSA redacted] miniapp/package-lock.json— tough-cookie 2.3.4: [GHSA redacted] — tough-cookie is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.1.3 is a MAJOR ahead of the resolved 2.3.4, so an `overrides` pin would force a breaking version under a dependent written against 2.3.4; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— uuid 3.4.0: [GHSA redacted] — uuid is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 11.1.1 is a MAJOR ahead of the resolved 3.4.0, so an `overrides` pin would force a breaking version under a dependent written against 3.4.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Medium CVE: [GHSA redacted] miniapp/package-lock.json— yargs-parser 5.0.0: [GHSA redacted] — yargs-parser is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin yargs-parser to 5.0.1 with an `overrides` entry).
Duplicated block (8 lines × 2) Android/dokit-mc/src/main/java/com/didichuxing/doraemonkit/kit/mc/ui/BorderDoKitView.java:59— Android/dokit-mc/src/main/java/com/didichuxing/doraemonkit/kit/mc/ui/BorderDoKitView.java:59-66 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/viewcheck/ViewCheckDrawDoKitView.java:86-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit-mc/src/main/java/com/didichuxing/doraemonkit/kit/mc/ui/BorderDoKitView.java:59` 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 (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/InterceptTitleNodeProvider.java:50— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/InterceptTitleNodeProvider.java:50-57 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/TemplateTitleNodeProvider.java:48-55 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/InterceptTitleNodeProvider.java:50` 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 (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:405— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:405-412 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:431-438 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:405` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:552— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:552-559 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:588-595 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:552` 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.
Duplicated block (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:101— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:101-108 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterListAdapter.java:110-117 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:101` 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 (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:122— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:122-129 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterListAdapter.java:98-105 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:166— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:166-174 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:222-229 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:166` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:71— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:71-78 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:69-76 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:71` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:128— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:128-135 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:129-136 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:128` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/uiperformance/UIPerformanceManager.java:73— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/uiperformance/UIPerformanceManager.java:73-80 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/uiperformance/UIPerformanceUtil.java:47-54 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/uiperformance/UIPerformanceManager.java:73` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/GpsMockManager.java:230— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/GpsMockManager.java:230-237 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/GpsMockManager.java:258-265 — 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) Android/dokit-okhttp-v3/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV3.java:35— Android/dokit-okhttp-v3/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV3.java:35-42 | Android/dokit-okhttp-v4/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV4.java:40-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit-okhttp-v3/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV3.java:35` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/InterceptDetailNodeProvider.java:53— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/InterceptDetailNodeProvider.java:53-62 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/TemplateDetailNodeProvider.java:65-74 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/InterceptDetailNodeProvider.java:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:201— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:201-210 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:254-263 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:201` 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.
Duplicated block (10 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:176— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:176-185 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:172-181 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:176` 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.
Duplicated block (10 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/uiperformance/UIPerformanceManager.java:54— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/uiperformance/UIPerformanceManager.java:54-63 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/uiperformance/UIPerformanceUtil.java:28-37 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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 (10 lines × 2) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/BDAbsLocationListenerProxy.java:32— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/BDAbsLocationListenerProxy.java:32-41 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/BDLocationListenerProxy.java:31-40 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/BDAbsLocationListenerProxy.java:32` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/widget/OverlayManager.java:299— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/widget/OverlayManager.java:299-308 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/widget/OverlayManager.java:325-334 — 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 `Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/widget/OverlayManager.java:299` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/util/DoKitNotificationUtils.java:77— Android/dokit/src/main/java/com/didichuxing/doraemonkit/util/DoKitNotificationUtils.java:77-86 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/util/DoKitNotificationUtils.java:110-119 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/util/DoKitNotificationUtils.java:77` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/jsonviewer/adapter/JsonViewerAdapter.java:74— Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/jsonviewer/adapter/JsonViewerAdapter.java:74-83 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/jsonviewer/adapter/JsonViewerAdapter.java:98-107 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/jsonviewer/adapter/JsonViewerAdapter.java:74` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:83— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:83-88 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:112-117 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/MockTemplatePreviewFragment.java:76— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/MockTemplatePreviewFragment.java:76-81 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/TemplateDetailNodeProvider.java:108-113 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/MockTemplatePreviewFragment.java:76` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:740— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:740-745 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:790-795 — 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) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetworkDetailView.java:245— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetworkDetailView.java:245-250 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/loginfo/LogInfoDoKitView.java:251-256 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetworkDetailView.java:245` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/colorpick/ColorPickerView.java:147— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/colorpick/ColorPickerView.java:147-152 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/colorpick/ColorPickerView.java:155-160 — 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) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:184— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:184-189 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:240-245 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:184` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:202— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:202-207 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:201-206 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:202` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/viewcheck/ViewCheckInfoDoKitView.java:238— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/viewcheck/ViewCheckInfoDoKitView.java:238-243 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/viewcheck/ViewCheckInfoDoKitView.java:262-267 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/okhttp/interceptor/DokitCapInterceptor.java:47— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/okhttp/interceptor/DokitCapInterceptor.java:47-53 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/okhttp/interceptor/DokitCapInterceptor.java:66-72 — 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 (7 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/utils/ByteUtil.java:33— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/utils/ByteUtil.java:33-39 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/utils/ByteUtil.java:40-46 — 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 (7 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/health/AppHealthInfoUtil.java:147— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/health/AppHealthInfoUtil.java:147-153 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/health/AppHealthInfoUtil.java:167-173 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/health/AppHealthInfoUtil.java:147` 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.
Duplicated block (7 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:93— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:93-99 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:156-162 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:93` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/LocationHookHandler.java:78— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/LocationHookHandler.java:78-84 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/LocationHookHandler.java:86-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. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/LocationHookHandler.java:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/LocationHooker.java:98— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/LocationHooker.java:98-104 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/LocationHooker.java:120-126 — 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 `Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/LocationHooker.java:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) Android/dokit-okhttp-v3/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV3.java:46— Android/dokit-okhttp-v3/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV3.java:46-52 | Android/dokit-okhttp-v4/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV4.java:51-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit-okhttp-v3/src/main/java/com/didichuxing/doraemonkit/okhttp_api/ByteCountBufferedSinkV3.java:46` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/utils/ByteUtil.java:50— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/utils/ByteUtil.java:50-54 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/utils/ByteUtil.java:57-61 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/utils/ByteUtil.java:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:111— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:111-115 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterListAdapter.java:86-90 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterDoKitView.java:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:35— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:35-39 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:35-39 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (5 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/weaknetwork/WeakNetworkManager.java:89— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/weaknetwork/WeakNetworkManager.java:89-93 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/weaknetwork/WeakNetworkManager.java:106-110 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/common/Utils.java:111— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/common/Utils.java:111-115 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/common/Utils.java:137-141 — 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) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapLocationChangedListenerProxy.java:36— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapLocationChangedListenerProxy.java:36-40 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapLocationClientProxy.java:37-41 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapLocationChangedListenerProxy.java:36` 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 (5 lines × 2) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapLocationClientProxy.java:36— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapLocationClientProxy.java:36-40 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapLocationListenerProxy.java:39-43 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (9 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/core/SettingItemAdapter.java:78— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/core/SettingItemAdapter.java:78-86 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureItemAdapter.java:68-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/core/SettingItemAdapter.java:78` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/blockmonitor/BlockMonitorFragment.java:39— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/blockmonitor/BlockMonitorFragment.java:39-47 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/timecounter/TimeCounterFragment.java:36-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureFragment.java:132— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureFragment.java:132-140 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/parameter/AbsParameterFragment.java:78-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:89— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:89-97 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:153-161 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:89` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/titlebar/HomeTitleBar.java:77— Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/titlebar/HomeTitleBar.java:77-85 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/titlebar/LogTitleBar.java:91-99 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/titlebar/HomeTitleBar.java:77` 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.
FileTooLong: urlconnection/ObsoleteUrlFactory.java Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/ObsoleteUrlFactory.java:0— FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: ObsoleteUrlFactory (82-1346). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: gpsmock/GpsMockFragment.java Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/GpsMockFragment.java:0— FileTooLong — 718 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: GpsMockFragment (83-1092). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: easyrefresh/EasyRefreshLayout.java Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/easyrefresh/EasyRefreshLayout.java:0— FileTooLong — 637 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: EasyRefreshLayout (34-1116). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: ui/NetWorkMockFragment.java Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:0— FileTooLong — 616 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: NetWorkMockFragment (58-1056). 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.
Medium: use-of-md5 Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/EncryptUtils.java:181— Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use HMAC instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Medium: use-of-md5 Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/FileUtils.java:1263— Detected MD5 hash algorithm which is considered insecure. MD5 is not collision resistant and is therefore not suitable as a cryptographic signature. Use HMAC instead. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Medium: weak-ssl-context Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/MyTrustManager.java:51— An insecure SSL context was detected. TLS versions 1.0, 1.1, and all SSL versions are considered weak encryption and are deprecated. Use SSLContext.getInstance("TLSv1.2") for the best security. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Duplicated block (17 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:432— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:432-448 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:489-505 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:432` 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 (17 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetworkDetailView.java:255— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetworkDetailView.java:255-271 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/loginfo/LogInfoDoKitView.java:264-280 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetworkDetailView.java:255` 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 (14 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureFragment.java:58— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureFragment.java:58-71 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureFragment.java:92-106 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureFragment.java:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/HttpsUtil.java:115— Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/HttpsUtil.java:115-128 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/util/DoKitCacheUtils.java:52-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/HttpsUtil.java:115` 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 (11 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureManager.java:70— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureManager.java:70-80 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureManager.java:94-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/largepicture/LargePictureManager.java:70` 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 (11 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:145— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:145-155 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:141-151 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:145` 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.
ScalpelFrameLayout.onTouchEvent (cyclomatic 32) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/layoutborder/ScalpelFrameLayout.java:222— ScalpelFrameLayout.onTouchEvent has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NetWorkMockFragment.filterAndNotifyData (cyclomatic 27) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:226— NetWorkMockFragment.filterAndNotifyData has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SeekRangeBar.onTouchEvent (cyclomatic 27) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/widget/SeekRangeBar.java:171— SeekRangeBar.onTouchEvent has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EasyRefreshLayout.dispatchTouchEvent (cyclomatic 20) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/easyrefresh/EasyRefreshLayout.java:277— EasyRefreshLayout.dispatchTouchEvent has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MatrixHelper.onDisallowInterceptEvent (cyclomatic 20) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/utils/MatrixHelper.java:89— MatrixHelper.onDisallowInterceptEvent has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_recordEvent (cyclomatic 20) Web/packages/core/src/common/js/EventRecorder.js:205— _recordEvent has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
MatrixHelper.getZoomProviderRect (cyclomatic 19) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/utils/MatrixHelper.java:421— MatrixHelper.getZoomProviderRect has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EasyRefreshLayout.moveSpinner (cyclomatic 18) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/easyrefresh/EasyRefreshLayout.java:402— EasyRefreshLayout.moveSpinner has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
bottomUpSearch (cyclomatic 18) Web/packages/core/src/common/js/finder/index.js:53— bottomUpSearch has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
PerformanceDataManager.addPerformanceDataInAppHealth (cyclomatic 17) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:538— PerformanceDataManager.addPerformanceDataInAppHealth has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SeekRangeBar.getAreaFlag (cyclomatic 17) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/widget/SeekRangeBar.java:268— SeekRangeBar.getAreaFlag has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
fetchClientQuery (cyclomatic 17) Web/packages/web/src/plugins/one-machine-with-multiple-controls/index.js:456— fetchClientQuery has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
DokitDbManager.bodyMatched (cyclomatic 16) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:483— DokitDbManager.bodyMatched has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
DokitDbManager.queriesMatched (cyclomatic 16) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:426— DokitDbManager.queriesMatched has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
HorizontalDividerItemDecoration.alignRightEdge (cyclomatic 16) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:127— HorizontalDividerItemDecoration.alignRightEdge has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ELog.log2console (cyclomatic 16) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/easyrefresh/ELog.java:71— ELog.log2console has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TableProvider.drawContent (cyclomatic 16) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/TableProvider.java:240— TableProvider.drawContent has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
xhrHostRequest (cyclomatic 16) Web/packages/web/src/plugins/one-machine-with-multiple-controls/index.js:29— xhrHostRequest has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
fetchHostRequest (cyclomatic 16) Web/packages/web/src/plugins/one-machine-with-multiple-controls/index.js:332— fetchHostRequest has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
dormant codebase — no living knowledge left to concentrate — All 225 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
NetWorkMockFragment.filterAndNotifyData (cognitive 82) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:226— NetWorkMockFragment.filterAndNotifyData has cognitive complexity 82 (threshold 15). Drivers by points: if/else 75, loops 5, boolean chains 2 (nesting depth added 46). 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.
SeekRangeBar.onTouchEvent (cognitive 80) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/widget/SeekRangeBar.java:171— SeekRangeBar.onTouchEvent has cognitive complexity 80 (threshold 15). Drivers by points: if/else 62, ternaries 15, boolean chains 3 (nesting depth added 50). 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.
ScalpelFrameLayout.onTouchEvent (cognitive 74) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/layoutborder/ScalpelFrameLayout.java:222— ScalpelFrameLayout.onTouchEvent has cognitive complexity 74 (threshold 15). Drivers by points: if/else 65, ternaries 4, loops 3, boolean chains 1, match/switch 1 (nesting depth added 44). 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.
VerticalDividerItemDecoration.alignBottomEdge (cognitive 51) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:128— VerticalDividerItemDecoration.alignBottomEdge has cognitive complexity 51 (threshold 15). Drivers by points: if/else 41, loops 9, boolean chains 1 (nesting depth added 33). 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.
MatrixHelper.getZoomProviderRect (cognitive 50) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/utils/MatrixHelper.java:421— MatrixHelper.getZoomProviderRect has cognitive complexity 50 (threshold 15). Drivers by points: if/else 33, ternaries 16, boolean chains 1 (nesting depth added 26). 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.
HorizontalDividerItemDecoration.alignRightEdge (cognitive 47) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:127— HorizontalDividerItemDecoration.alignRightEdge has cognitive complexity 47 (threshold 15). Drivers by points: if/else 37, loops 9, boolean chains 1 (nesting depth added 30). 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.
TableProvider.drawContent (cognitive 44) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/TableProvider.java:240— TableProvider.drawContent has cognitive complexity 44 (threshold 15). Drivers by points: if/else 34, loops 9, boolean chains 1 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlexibleDividerDecoration.hasHorizontalDivider (cognitive 43) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:220— FlexibleDividerDecoration.hasHorizontalDivider has cognitive complexity 43 (threshold 15). Drivers by points: if/else 37, loops 5, boolean chains 1 (nesting depth added 26). 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.
VerticalDividerItemDecoration.alignTopEdge (cognitive 42) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:68— VerticalDividerItemDecoration.alignTopEdge has cognitive complexity 42 (threshold 15). Drivers by points: if/else 36, loops 5, boolean chains 1 (nesting depth added 26). 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.
FlexibleDividerDecoration.hasVerticalDivider (cognitive 37) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:164— FlexibleDividerDecoration.hasVerticalDivider has cognitive complexity 37 (threshold 15). Drivers by points: if/else 32, loops 4, boolean chains 1 (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.
HorizontalDividerItemDecoration.alignLeftEdge (cognitive 34) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:70— HorizontalDividerItemDecoration.alignLeftEdge has cognitive complexity 34 (threshold 15). Drivers by points: if/else 28, loops 5, boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AMapNaviListenerProxyDelegate.onCalculateRouteSuccess (cognitive 34) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/map/AMapNaviListenerProxyDelegate.java:50— AMapNaviListenerProxyDelegate.onCalculateRouteSuccess has cognitive complexity 34 (threshold 15). Drivers by points: if/else 22, loops 9, error handling 2, boolean chains 1 (nesting depth added 23). 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.
ScalpelFrameLayout.draw (cognitive 32) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/layoutborder/ScalpelFrameLayout.java:358— ScalpelFrameLayout.draw has cognitive complexity 32 (threshold 15). Drivers by points: if/else 24, loops 8 (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.
ELog.log2console (cognitive 30) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/easyrefresh/ELog.java:71— ELog.log2console has cognitive complexity 30 (threshold 15). Drivers by points: if/else 28, match/switch 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SmartTable.onDraw (cognitive 29) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/component/SmartTable.java:100— SmartTable.onDraw has cognitive complexity 29 (threshold 15). Drivers by points: if/else 29 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fetchClientQuery (cognitive 29) Web/packages/web/src/plugins/one-machine-with-multiple-controls/index.js:456— fetchClientQuery has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PerformanceDataManager.addPerformanceDataInAppHealth (cognitive 28) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:538— PerformanceDataManager.addPerformanceDataInAppHealth has cognitive complexity 28 (threshold 15). Drivers by points: if/else 23, boolean chains 4, 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.
GpsMockFragment.onClick (cognitive 28) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/GpsMockFragment.java:440— GpsMockFragment.onClick has cognitive complexity 28 (threshold 15). Drivers by points: if/else 25, boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous) (cognitive 27) Web/packages/core/src/common/js/EventPlayback.js:16— (anonymous) has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SlideBar.onTouchEvent (cognitive 26) Android/app/src/main/java/com/didichuxing/doraemondemo/mc/SlideBar.java:119— SlideBar.onTouchEvent has cognitive complexity 26 (threshold 15). Drivers by points: if/else 23, boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DkDropDownMenu.switchMenu (cognitive 26) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/dropdown/DkDropDownMenu.java:326— DkDropDownMenu.switchMenu has cognitive complexity 26 (threshold 15). Drivers by points: if/else 25, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TableMeasurer.getTableWidth (cognitive 26) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/TableMeasurer.java:125— TableMeasurer.getTableWidth has cognitive complexity 26 (threshold 15). Drivers by points: if/else 19, loops 5, boolean chains 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fetchHostRequest (cognitive 26) Web/packages/web/src/plugins/one-machine-with-multiple-controls/index.js:332— fetchHostRequest has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bottomUpSearch (cognitive 25) Web/packages/core/src/common/js/finder/index.js:53— bottomUpSearch has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
InterceptDetailNodeProvider.convert (cognitive 24) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/InterceptDetailNodeProvider.java:41— InterceptDetailNodeProvider.convert has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13, loops 6, error handling 4, boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
YSequence.onDraw (cognitive 23) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/component/YSequence.java:50— YSequence.onDraw has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16, loops 3, boolean chains 2, ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EasyRefreshLayout.dispatchTouchEvent (cognitive 22) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/easyrefresh/EasyRefreshLayout.java:277— EasyRefreshLayout.dispatchTouchEvent has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16, boolean chains 5, match/switch 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.
JsonItemClickListener.onClick (cognitive 22) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/jsonviewer/adapter/JsonViewerAdapter.java:235— JsonItemClickListener.onClick has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 11, if/else 6, loops 4, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DokitDbManager.bodyMatched (cognitive 21) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:483— DokitDbManager.bodyMatched has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9, boolean chains 6, loops 4, error handling 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DokitDbManager.queriesMatched (cognitive 21) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/DokitDbManager.java:426— DokitDbManager.queriesMatched has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9, boolean chains 6, loops 4, error handling 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
xhrHostRequest (cognitive 21) Web/packages/web/src/plugins/one-machine-with-multiple-controls/index.js:29— xhrHostRequest has cognitive complexity 21 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
24459.onResponse (cognitive 20) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:600— 24459.onResponse has cognitive complexity 20 (threshold 15). Drivers by points: if/else 19, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewCheckInfoDoKitView.getVisibleFragment (cognitive 20) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/viewcheck/ViewCheckInfoDoKitView.java:226— ViewCheckInfoDoKitView.getVisibleFragment has cognitive complexity 20 (threshold 15). Drivers by points: if/else 15, loops 3, boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EasyRefreshLayout.moveSpinner (cognitive 20) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/easyrefresh/EasyRefreshLayout.java:402— EasyRefreshLayout.moveSpinner has cognitive complexity 20 (threshold 15). Drivers by points: if/else 14, boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MatrixHelper.onDisallowInterceptEvent (cognitive 20) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/utils/MatrixHelper.java:89— MatrixHelper.onDisallowInterceptEvent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12, boolean chains 7, match/switch 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.
PerformanceDataManager.getCpuDataForO (cognitive 18) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:121— PerformanceDataManager.getCpuDataForO has cognitive complexity 18 (threshold 15). Drivers by points: if/else 16, error handling 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PerformanceDataManager.parseMemoryData (cognitive 18) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/performance/PerformanceDataManager.java:403— PerformanceDataManager.parseMemoryData has cognitive complexity 18 (threshold 15). Drivers by points: if/else 15, boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
xhrClientQuery (cognitive 18) Web/packages/web/src/plugins/one-machine-with-multiple-controls/index.js:140— xhrClientQuery has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TouchProxy.onTouchEvent (cognitive 17) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/core/TouchProxy.java:36— TouchProxy.onTouchEvent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14, boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
DokitMockInterceptor.transformRequestBody (cognitive 17) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/okhttp/interceptor/DokitMockInterceptor.java:121— DokitMockInterceptor.transformRequestBody has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, error handling 5, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AlignRulerLineDoKitView.onPositionChanged (cognitive 17) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerLineDoKitView.java:65— AlignRulerLineDoKitView.onPositionChanged has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17 (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.
LogCatchRunnable.run (cognitive 17) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/loginfo/LogInfoManager.java:112— LogCatchRunnable.run has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14, boolean chains 1, error handling 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ViewCheckInfoDoKitView.getFragmentForActivity (cognitive 17) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/viewcheck/ViewCheckInfoDoKitView.java:254— ViewCheckInfoDoKitView.getFragmentForActivity has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, loops 3, boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GpsMockFragment.drawAndMockRoute (cognitive 17) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/GpsMockFragment.java:481— GpsMockFragment.drawAndMockRoute has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17 (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.
GpsMockFragment.getPoiInfo (cognitive 17) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/GpsMockFragment.java:852— GpsMockFragment.getPoiInfo has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, loops 4, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SeekRangeBar.getAreaFlag (cognitive 17) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/widget/SeekRangeBar.java:268— SeekRangeBar.getAreaFlag has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 6. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
OkHttpURLConnection.buildCall (cognitive 17) Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/ObsoleteUrlFactory.java:548— OkHttpURLConnection.buildCall has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, ternaries 2, boolean chains 1, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OkHttpURLConnection.getResponse (cognitive 17) Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/ObsoleteUrlFactory.java:622— OkHttpURLConnection.getResponse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, error handling 4, boolean chains 2, loops 2 (nesting depth added 4). 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.
TableProvider.correctCellRect (cognitive 16) Android/dokit/src/main/java/com/didichuxing/doraemonkit/widget/tableview/TableProvider.java:431— TableProvider.correctCellRect has cognitive complexity 16 (threshold 15). Drivers by points: loops 8, if/else 6, boolean chains 2 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
xhrHostResponse (cognitive 16) Web/packages/web/src/plugins/one-machine-with-multiple-controls/index.js:86— xhrHostResponse has cognitive complexity 16 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (18 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:256— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:256-273 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:313-330 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:256` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/loginfo/LogInfoDoKitView.java:109— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/loginfo/LogInfoDoKitView.java:109-123 | Android/dokit-weex/src/main/java/com/didichuxing/doraemonkit/weex/log/WeexLogInfoDoKitView.java:36-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:752— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:752-764 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:802-814 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/ui/NetWorkMockFragment.java:752` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:109— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:109-120 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:107-118 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:109` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 3) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/MockInterceptApiBean.java:69— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/MockInterceptApiBean.java:69-78 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/network/room_db/MockTemplateApiBean.java:85-94 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/picasso/StatsSnapshot.java:46-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Note what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
Duplicated block (9 lines × 3) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerSettingFragment.java:37— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerSettingFragment.java:37-45 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/layoutborder/LayoutBorderSettingFragment.java:37-45 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/loginfo/LogInfoSettingFragment.java:37-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerSettingFragment.java:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:248— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:248-254 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/HorizontalDividerItemDecoration.java:170-176 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/VerticalDividerItemDecoration.java:166-172 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/toolpanel/decoration/FlexibleDividerDecoration.java:248` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/CordTransformUtil.java:24— Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/CordTransformUtil.java:24-29 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/CordTransformUtil.java:41-46 | Android/dokit-gps-mock/src/main/java/com/didichuxing/doraemonkit/gps_mock/gpsmock/CordTransformUtil.java:61-66 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (5 lines × 3) Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerMarkerDoKitView.java:56— Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerMarkerDoKitView.java:56-60 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerMarkerDoKitView.java:69-73 | Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerMarkerDoKitView.java:86-90 — 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 `Android/dokit/src/main/java/com/didichuxing/doraemonkit/kit/alignruler/AlignRulerMarkerDoKitView.java:56` 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.
Low CVE: [GHSA redacted] miniapp/package-lock.json— @babel/core 7.9.0: [GHSA redacted] — this repo declares @babel/core ^7.5.0, a range that ALREADY admits the fixed 7.29.6, so there is no manifest edit to make here. Re-resolve the lock so @babel/core moves onto 7.29.6 or later; if the flagged 7.9.0 comes back, a dependency is pinning it — upgrade that dependent, or pin @babel/core with an `overrides` entry so only one copy resolves.
Low CVE: [GHSA redacted] miniapp/package-lock.json— debug 3.2.6: [GHSA redacted] — debug is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin debug to 3.2.7 with an `overrides` entry).
Low CVE: [GHSA redacted] miniapp/package-lock.json— debug 4.1.1: [GHSA redacted] — debug is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin debug to 4.3.1 with an `overrides` entry).
Low CVE: [GHSA redacted] miniapp/package-lock.json— es5-ext 0.10.53: [GHSA redacted] — es5-ext is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin es5-ext to 0.10.63 with an `overrides` entry).
D34 · Knowledge Freshness· Largest orphaned file · ×3
Largest orphaned file Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/PinyinUtils.java— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/ActivityUtils.java— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file Android/dokit-util/src/main/java/com/didichuxing/doraemonkit/util/ImageUtils.java— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Low: insecure-trust-manager Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/MyTrustManager.java:28— Detected empty trust manager implementations. This is dangerous because it accepts any certificate, enabling man-in-the-middle attacks. Consider using a KeyStore and TrustManagerFactory instead. See https://stackoverflow.com/questions/2642777/trusting-all-certificates-using-httpclient-over-https for more information. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
Low: insecure-trust-manager Android/dokit/src/main/java/com/didichuxing/doraemonkit/aop/urlconnection/MyTrustManager.java:33— Detected empty trust manager implementations. This is dangerous because it accepts any certificate, enabling man-in-the-middle attacks. Consider using a KeyStore and TrustManagerFactory instead. See https://stackoverflow.com/questions/2642777/trusting-all-certificates-using-httpclient-over-https for more information. This is a semgrep security-AUDIT rule: it reports that a sensitive pattern is present, not that it is exploitable here. Confirm whether the flagged value reaches a security decision — a credential, token, nonce, key, salt or session id, or an externally reachable surface — and apply the change where it does; where it provably does not (cosmetic, simulation, or deliberately reproducible use), record the review and leave the code as it is.
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.java, .kt, .js) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
Dormant codebase — 570 of 570 significant files have no living knowledge — the codebase as a whole is dormant, not 570 separate risks. Re-engage owners or document before change.
Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.java, .kt, .js) 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. To have real coverage read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report` or the Gradle `jacocoTestReport` task, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 2 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifests (a Gradle version catalogue, package.json and a Dart pubspec.yaml) were found, but this pass cannot parse them for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D38 wherever the manifest is OSV-readable.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
0
—
Run 019fd74d-4f89-7946-b9d5-55f03735755e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 33 · Warnings: 166 · Recommendations: 12 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 06-08-2026 @ 13:39 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.