WormaCeptor — Watchdog Audit

Executive summary

Band capped at Weak: the weakest category (Security, 0%) reads Critical — the cover never out-promises the category table.

The system holds a weak overall standing at 51%, presenting a workable asset that carries significant operational risk. While the underlying code is clean and well-structured, the low readiness score indicates the platform is fragile in production, threatening delivery speed and reliability. This is a medium-sized investment, with approximately 77,000 lines of production code and 22,000 lines of tests, representing a rebuild cost of roughly €130,000. The value tied up here is substantial, and the low boilerplate ratio suggests the logic is custom and complex, making it expensive to change if not managed carefully.

The primary risk lies in operational fragility. With a readiness score of just 34%, the system lacks the necessary testing, observability, and security controls to be safely operated at scale. This gap exposes the business to potential outages, increased defect rates, and slower incident response times. The architecture is strong at 96%, meaning changes do not ripple uncontrollably, but without readiness, deploying those changes is hazardous. The maturity score of 67% suggests that while a new team could eventually pick it up, the current documentation and process gaps create friction and increase the cost of maintenance.

A critical, immediate threat is the exposure of sensitive credentials. Three leaked secrets were detected in the codebase, including files related to push token handling. This is not a theoretical risk; it is an active security vulnerability that could lead to data breaches or unauthorized access. Resolving these leaks is the highest-leverage action available, offering immediate protection with minimal effort. The security score of 58% reflects this exposure, but fixing these specific findings will significantly improve the overall security posture.

The system’s strength is its clean, maintainable code. A code health score of 91% and architecture score of 96% indicate that the foundation is solid, and the logic is well-organized. This is a genuine asset that reduces long-term technical debt. However, this strength is undermined by the lack of operational safeguards. The focus must be on stabilizing the platform before adding new features. The first step is to remove the leaked secrets and integrate automated security scanning into the CI pipeline to prevent future regressions. This will secure the asset and build confidence in its reliability. Without this, the strong code base remains a liability in production.

Code Health 91% ★ Exemplary Architecture 96% ★ Exemplary Maturity 67% Adequate · gated by M2 Readiness 34% Weak · gated by D13, P3 Security 58% Adequate · gated by D36 Domain Modelling 70% Adequate · gated by DM11

How the score is built — each lens's share of the headline Width 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.

Readiness 34% · 46% weightSecurity 58% · 25% weightMaturity 67% · 14% weightDomain Modelling 70% · 8% weightCode Health 91% · 4% weightArchitecture 96% · 2% weight

Raise Readiness 34 → 70 (the Healthy floor) ⇒ headline 51 → ~65.

Code composition — where the lines go

Tests 100%

Rebuild cost & value ~ Modeled — €43,000–€210,000

Cost to rebuild	€43,000–€210,000 (0.4–1.3 person-years (710–2,253 h), ~1–2 engineers)
Domain complexity	REDACTED — harder problems cost more per line
Quality factor	0.7× (at 51% quality) — the last 20% of quality is most of the work
Size & shape	REDACTED · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)

This codebase represents roughly ~0.9 person-years of build effort (about ~€130,000 to rebuild). Its weakest lens is Readiness at 34% — the part of that asset most exposed by the findings below.

How we model this: boilerplate at a scaffolding rate + logic × domain REDACTED (×1.4) — DDD/clean architecture, domain model × 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.

Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.

+15.8 pts · Low effort · REDACTED Scanning

Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.

+15.8 pts · REDACTED effort · Security & performance tooling

Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

+15.0 pts · REDACTED effort · Release Hygiene

Diagnosis — what's actually going on

Value concentrated against a weak lens · REDACTED · Value at risk

This is a REDACTED asset (~0.9 person-years to rebuild), and its weakest lens is Readiness at 34%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.

Evidence: valuation: REDACTED, ~0.9 person-years rebuild (77,183 LoC) · weakest lens: Readiness 34%

→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.

Highest-leverage move · REDACTED · Leverage

Of everything flagged, the best return on effort is: Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED. The rest can wait behind it.

Evidence: priority ranking: top of 5 ranked by impact/effort

→ Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.

Architecture — module dependency matrix

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

434 modules, 562 dependencies. 6 dependency cycles across 21 modules, marked above the diagonal.

Showing the 40 most-connected modules; 394 more are not drawn.

Module dependency matrix. The row depends on the column; the number is how many type pairs create the dependency. A cell above the diagonal is part of a dependency cycle.
depends on →	1 common.presentation	4 domain.entities.mock	6 domain.entities.LeakInfo	7 domain.entities.LoadedLibrary	8 domain.entities.RateLimitConfig	9 domain.entities.SecureStorageEntry	10 domain.entities.ThreadViolation	11 feature.database.vm.DatabaseViewEvent	12 feature.viewer.vm.TransactionDetailViewEvent	13 domain.entities	14 domain.contracts	16 feature.viewer.ui.components	17 api	18 core.engine	19 feature.database.vm	24 feature.crypto.vm	36 feature.viewer.vm	40 feature.viewer.ui
1 common.presentation
2 core.ui.navigation
3 core.ui.theme.tokens.ToolColors
4 domain.entities.mock
5 studio.model
6 domain.entities.LeakInfo										1
7 domain.entities.LoadedLibrary										1
8 domain.entities.RateLimitConfig										1
9 domain.entities.SecureStorageEntry										1
10 domain.entities.ThreadViolation										1
11 feature.database.vm.DatabaseViewEvent															4
12 feature.viewer.vm.TransactionDetailViewEvent																	6
13 domain.entities			1	1	1	1	1
14 domain.contracts		1								24
15 feature.deviceinfo.vm	1									9
16 feature.viewer.ui.components										7							3
17 api											1
18 core.engine		4	1	1	1	1	1			37	22
19 feature.database.vm	1							4		6	1
20 feature.filebrowser.vm	1									4	1
21 feature.preferences.vm	1									4	1
22 infra.persistence.sqlite		2								26	18
23 api.internal										3	2		2	3
24 feature.crypto.vm	1									2				1
25 feature.leakdetection.vm	1		2							3				1
26 feature.loadedlibraries.vm	1			2						3				1
27 feature.location.vm	1									4	1			1
28 feature.logs.vm	1									4				1
29 feature.memory.vm	1									1				1
30 feature.mockrules.vm	1	3									1			1
31 feature.pushsimulator.vm	1									5	1			1
32 feature.pushtoken.vm	1									2				1
33 feature.ratelimit.vm	1				2					2				1
34 feature.securestorage.vm	1					2				5				1
35 feature.threadviolation.vm	1						2			3				1
36 feature.viewer.vm	6								5	11	1	2		4				2
37 feature.websocket.vm	1									6				1
38 feature.webviewmonitor.vm	1									5				1
39 feature.crypto.vm.CryptoViewEvent																6
40 feature.viewer.ui										10	2		2				36

Dependency, pointing down the layeringAbove the diagonal — part of a cycleThe module itself

At a glance — Code Health · 91% · Exemplary ·

The Good

D1 · Kotlin Cyclomatic Complexity 8.3 D2 · Kotlin Cognitive Complexity 7.2 D3 · Kotlin God Classes 8.7 D4 · Kotlin Code Duplication 9.5 D17 · Kotlin Explicit Debt 10.0

At a glance — Architecture · 96% · Exemplary ·

The Good

D35 · Kotlin Change Coupling 10.0 AX10 · Repo Code composition 9.0 AX5 · Repo Architecture & structure 10.0

At a glance — Maturity · 67% · Adequate · gated by M2 ·

The Good

D15 · Kotlin Churn × Complexity Hotspots 9.9 D19 · Kotlin Documentation Quality 7.0 D21 · Kotlin Naming Consistency 10.0 D34 · Kotlin Knowledge Freshness 10.0 M1 · Repo Documentation (README) 7.3 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Ugly

D20 · Kotlin ADR Quality 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 34% · Weak · gated by D13, P3 ·

The Good

P1 · Repo CI/CD gates 10.0

The Bad

P6 · Repo Release Hygiene 5.0

The Ugly

D13 · Kotlin REDACTED Scanning 0.0 P3 · Repo Security & performance tooling 3.0

At a glance — Security · 58% · Adequate · gated by D36 ·

The Good

D28 · Kotlin Secrets (history) 7.0 D29 · Kotlin Static Analysis (SAST) 8.0

The Ugly

D36 · Kotlin Supply-chain Provenance & Signing 2.5

At a glance — Domain Modelling · 70% · Adequate · gated by DM11 ·

The Good

DM12 · Repo Ambient inputs in the domain 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM8 · Repo Value-object opportunities 10.0

The Ugly

DM11 · Repo Constructible invalid state 3.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A03:2021 — Injection	30	REDACTED / Critical
A02:2021 — Cryptographic Failures	7	REDACTED / Critical

Roadmap

Immediately resolve the three leaked secrets in the push token files to eliminate critical security exposure. Strengthen the build pipeline by integrating automated security scanning to prevent regressions from merging, while simultaneously establishing a changelog to track release history. Finally, create an architecture decision record to document key design choices and their consequences, ensuring future maintainability and clarity.

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

Do this	Helps	Effort	Dimension
Resolve the 3 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED, REDACTED, REDACTED.	+15.8 pts	Low	REDACTED Scanning
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.	+15.8 pts	REDACTED	Security & performance tooling
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.	+15.0 pts	REDACTED	Release Hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+2.3 pts	Low	ADR Quality
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED.	+1.9 pts	Low	Secrets (history)
Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 28 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.	+1.7 pts	Low	Static Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.	+1.3 pts	Low	Supply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.	+1.3 pts	Low	Supply-chain Provenance & Signing

File quality

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

File	Score	Band	Worst signal
REDACTED	4.3	Mixed	Secrets (history): REDACTED: REDACTED
REDACTED	4.4	Mixed	Static Analysis (SAST): REDACTED: REDACTED
features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenImageViewer.kt	6.3	Mixed	God Classes: MethodTooLong: FullscreenImageViewerKt.FullscreenImageContent
features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt	7.0	Mixed	Cyclomatic Complexity: TransactionRequestSectionKt.RequestTab (cyclomatic 25)
features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt	7.1	Mixed	God Classes: MethodTooLong: HomeScreenKt.HomeScreen
features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt	7.1	Mixed	Cognitive Complexity: JsonTreeViewKt.JsonArrayNode (cognitive 16)
features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt	7.2	Mixed	Code Duplication: Near-duplicate member pair (40 shared lines)
features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt	7.2	Mixed	Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
REDACTED	7.2	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	7.2	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	7.2	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	7.2	Mixed	Secrets (history): REDACTED: REDACTED
features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt	7.4	Mixed	Cyclomatic Complexity: TransactionResponseSectionKt.ResponseTab (cyclomatic 32)
core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt	7.4	Mixed	Cyclomatic Complexity: DependenciesInspectorEngine.categorizePackage (cyclomatic 27)
features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/tools/PerformanceOverlayToggle.kt	7.4	Mixed	Cyclomatic Complexity: PerformanceOverlayToggleKt.PerformanceOverlayToggle (cyclomatic 17)
features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/filter/GridFilterCard.kt	7.4	Mixed	Cyclomatic Complexity: GridFilterCardKt.GridFilterCard (cyclomatic 16)
features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt	7.4	Mixed	Cognitive Complexity: MultipartViewKt.MultipartPartCard (cognitive 16)
features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt	7.4	Mixed	God Classes: MethodTooLong: WebSocketDetailScreenKt.WebSocketDetailScreen
features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt	7.4	Mixed	Code Duplication: Duplicated block (17 lines × 3)
features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt	7.4	Mixed	Code Duplication: Duplicated block (16 lines × 2)

How the grades work

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

Critical — 35

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

Serious — 170

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 11

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

Could not be resolved — 47

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 25 of 28 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

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

What we checked — 28 dimensions across the health lenses

D1D2D3D4D13D15D17D19D20D21D28D29D34D35D36AX10AX5DM11DM12DM6DM8M1M2M3M4P1P3P6

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, 206 of 216 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a0c4ff-0cdb-75f0-98c8-2f3aa60f6055.

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

Run transparency — what happened this run

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

D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.kt) 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 — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.kt) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Dependency Hygiene ran out of its 5-minute budget before it had finished, so what it reports here is a floor rather than a complete count. The rows above are real and stand; what is not known is how many more there are. This is a limit of the analysis run, not a finding about this repository.
D14 License Compliance — evaluation did not complete — License Compliance not included (check did not complete) — excluded from the score.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 430 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: D22 has no public-API collector for any other ecosystem, and the remedy is to write one — no change to the scan image can close it.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (go.mod, a Gemfile's ruby directive, a Dockerfile) is simply not read here yet.
AX3 Project dependency cycles — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which project references which — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
AX4 Dependency direction — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the direction each project reference points — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX8 Test isolation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over which projects are test projects, and what they reference — facts that live in .csproj references. This repository either commits no MSBuild project at all (its C# may still have been parsed as syntax-only projects, which carry no references between them) or its projects failed to load, so there was no graph to read. That is a gap in this analyzer's reach — not a finding that the repository is free of what this check looks for.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
DM9 Scattered domain decisions — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
ED5 Idempotency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds retry-prone mutations by walking the repository's declared types, and NONE was loaded on this run, so it had nothing to look at. That is a limit of the analyzer's reach — it reads .NET projects — not a finding that this repository has no command handlers or message consumers.
GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X12 Unreachable branch — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X13 Undrained process stream — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X14 Bypassable address classification — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X15 Unvalidated length from an untrusted reader — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X19 Unrestored process-global state — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X20 Mistyped argument guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X22 Contradicted release guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X23 Unguarded diagnostic materialisation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X24 Document value interpolated into markup unescaped — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X25 Inert configuration knob — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X26 Unsynchronised callback handoff — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X27 Collection changed while being enumerated — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X28 Index access outside its own emptiness guard — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X30 Support guard that admits what it rejects — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X32 Type resolved by simple name across every loaded assembly — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity8.3 / 10Strong✓ Tool-verified

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

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

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

11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TransactionResponseSectionKt.ResponseTab at 32. A further 16 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DeepLinkHandler.parseToolsDeepLink at 36 — they are counted neither in the figure above nor in this dimension's score. 15 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/navigation/DeepLinkHandler.kt (DeepLinkHandler.parseToolsDeepLink at 36), features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/vm/TransactionListViewModel.kt (TransactionListViewModel.handleEvent at 28), domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/WebViewRequest.kt (WebViewResourceType.fromUrl at 25), core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DefaultParserRegistry.kt (DefaultParserRegistry.detectFromHeader at 20), features/location/src/main/java/com/azikar24/wormaceptor/feature/location/vm/LocationViewModel.kt (LocationViewModel.handleEvent at 19), and 10 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

TransactionResponseSectionKt.ResponseTab (cyclomatic 32)features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:64

HtmlBodyParser.formatHtml (cyclomatic 30)infra/parser/html/src/main/java/com/azikar24/wormaceptor/infra/parser/html/HtmlBodyParser.kt:87

CryptoViewModel.handleEvent (cyclomatic 30)features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/vm/CryptoViewModel.kt:23

GetDeviceInfoUseCase.getNetworkDetails (cyclomatic 29)features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/GetDeviceInfoUseCase.kt:238

DependenciesInspectorEngine.categorizePackage (cyclomatic 27)core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt:315

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

What to do

Resolve the 1 TransactionResponseSectionKt.ResponseTab (cyclomatic 32) finding(s) in Cyclomatic Complexity — start with TransactionResponseSection.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 HtmlBodyParser.formatHtml (cyclomatic 30) finding(s) in Cyclomatic Complexity — start with HtmlBodyParser.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CryptoViewModel.handleEvent (cyclomatic 30) finding(s) in Cyclomatic Complexity — start with CryptoViewModel.kt. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — 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.

Do you agree with this assessment?

D2 · Cognitive Complexity7.2 / 10Strong✓ Tool-verified

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

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

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

13 method(s) exceeded the cognitive complexity threshold of 15; the worst was TransactionResponseSectionKt.ResponseTab at 77.

TransactionResponseSectionKt.ResponseTab (cognitive 77)features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:64

HtmlBodyParser.formatHtml (cognitive 64)infra/parser/html/src/main/java/com/azikar24/wormaceptor/infra/parser/html/HtmlBodyParser.kt:87

TransactionRequestSectionKt.RequestTab (cognitive 46)features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:57

JsonBodyParser.cleanJson5Syntax (cognitive 33)infra/parser/json/src/main/java/com/azikar24/wormaceptor/infra/parser/json/JsonBodyParser.kt:117

ImageMetadataExtractorImpl.extractJpegMetadata (cognitive 25)infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageMetadataExtractorImpl.kt:82

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

What to do

Resolve the 1 TransactionResponseSectionKt.ResponseTab (cognitive 77) finding(s) in Cognitive Complexity — start with TransactionResponseSection.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 HtmlBodyParser.formatHtml (cognitive 64) finding(s) in Cognitive Complexity — start with HtmlBodyParser.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TransactionRequestSectionKt.RequestTab (cognitive 46) finding(s) in Cognitive Complexity — start with TransactionRequestSection.kt. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — 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 Classes8.7 / 10Strong✓ Tool-verified

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

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

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

23 god class(es) detected.

MethodTooLong: TransactionResponseSectionKt.ResponseTab · ×20features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:64

FileTooLong: engine/DependenciesInspectorEngine.ktcore/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt

TooManyMethods: PerformanceOverlayEnginecore/engine/src/main/java/com/azikar24/wormaceptor/core/engine/PerformanceOverlayEngine.kt:60

ClassTooLong: PerformanceOverlayEnginecore/engine/src/main/java/com/azikar24/wormaceptor/core/engine/PerformanceOverlayEngine.kt:60

What to do

Resolve the 20 MethodTooLong finding(s) in God Classes — start with HomeScreen.kt (2), TransactionResponseSection.kt, ImagePreviewCard.kt. — One of this dimension's main actionable groups (20 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with DependenciesInspectorEngine.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 TooManyMethods finding(s) in God Classes — start with PerformanceOverlayEngine.kt. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D4 · Code Duplication9.5 / 10Stronggated by 83 serious findings✓ Tool-verified

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

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

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

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

Duplicated block (15 lines × 2) · ×7features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:219

Duplicated block (16 lines × 2) · ×5features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:232

Duplicated block (14 lines × 2) · ×5features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/WebViewMonitorScreen.kt:23

Duplicated block (19 lines × 2) · ×4features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:206

Duplicated block (13 lines × 2) · ×4features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:342

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

What to do

Resolve the 7 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with CrashDetailScreen.kt, WebSocketDetailScreen.kt, HomeScreen.kt. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 5 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with CpuChartSection.kt, WormaCeptorCard.kt, WormaCeptorDetailSection.kt. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 5 Duplicated block (14 lines × 2) finding(s) in Code Duplication — start with WebViewMonitorScreen.kt, HomeTopBar.kt, FullscreenTopControlBar.kt. — One of this dimension's main actionable groups (5 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

3 secret(s) detected.

REDACTED

What to do

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

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

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 28 serious findings✓ Tool-verified

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

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

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

Top hotspots: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt (14×18=252); features/location/src/main/java/com/azikar24/wormaceptor/feature/location/vm/LocationViewModel.kt (9×19=171); features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt (11×15=165) Repeated repair below the complexity floor: features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ListContent.kt (3 of 5 changes were fixes)

Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt · ×27features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt:69

Repeated repair: features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ListContent.ktfeatures/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ListContent.kt:26

What to do

Resolve the 27 Hotspot finding(s) in Churn × Complexity Hotspots — start with ViewerActivity.kt, LocationViewModel.kt, MultipartView.kt. — One of this dimension's main actionable groups (27 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ListContent.kt. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

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

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

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

WormaCeptor's README is clear and well-illustrated: it shows the project badge, a one-line description of what it does (23 debug tools in one library), a demo showing network inspection, system tools, and performance monitoring side by side, and links to Google Play and a YouTube Shorts demo. It begins with Quick Start instructions for declaring mavenCentral() in settings.gradle.kts and adding the dependencies in build.gradle.kts, then covers Features, How It Works, Redacting Sensitive Data, Documentation, Contributing, and License sections (the full outline is visible).

Documentation: no installation or build instructions · ×3README.md

What to do

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

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

Do you agree with this assessment?

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

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

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

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

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

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

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)8.0 / 10Adequategated by 29 critical findings✓ Tool-verified

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

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

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

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

30 finding(s): 0 critical, 29 high, 1 medium, 0 low. 28 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `gradlew` (line 72, line 178), `plugins/android-studio/gradlew` (line 72, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 28 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (29 issue-level, 1 of them charged here).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

Strongest change-coupling: FullscreenImageViewer.kt↔PdfViewerScreen.kt 80%

Change coupling: FullscreenImageViewer.kt ↔ PdfViewerScreen.ktfeatures/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenImageViewer.kt

What to do

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

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

Do you agree with this assessment?

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

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.0 / 10Strong✓ Tool-verified

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

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

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

What to do

The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).

Do you agree with this assessment?

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

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

DM11 · Constructible invalid state3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

`CrashEntity`'s public constructor takes `exceptionType`, `message`, `stackTrace` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CrashEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/CrashEntity.kt:17
`LeakEntity`'s public constructor takes `objectClass`, `leakDescription`, `severity` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `LeakEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/LeakEntity.kt:20
`LocationPresetEntity`'s public constructor takes `id`, `name`, `latitude`, `longitude`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `LocationPresetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/LocationPresetEntity.kt:23
`MockLocationEntity`'s public constructor takes `latitude`, `longitude`, `altitude`, `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `MockLocationEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/MockLocationEntity.kt:21
`MockRuleEntity`'s public constructor takes `id`, `name`, `urlPattern`, `matchType`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `MockRuleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/MockRuleEntity.kt:16
`PushTemplateEntity`'s public constructor takes `id`, `name`, `notificationId`, `title`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `PushTemplateEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/PushTemplateEntity.kt:30
`TransactionEntity`'s public constructor takes `reqUrl`, `reqMethod`, `reqBodyRef`, `resMessage`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TransactionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/TransactionEntity.kt:49
`WebViewRequestEntity`'s public constructor takes `id`, `url`, `method`, `headersJson`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `WebViewRequestEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/WebViewRequestEntity.kt:32

What to do

Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

What to do

Add a 'Testing' section to the root README — how to run the test suite.
Add a README to the 50 of 50 project(s) that lack one — worth up to 2 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

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 each file named `NNNN-title` in whatever markup those docs already use, is the most discoverable form).

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

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

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

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7710 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.

Do you agree with this assessment?

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	91%	Exemplary	Solid.
Architecture	96%	Exemplary	Strongest area.
Maturity	67%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	34%	Weak — gated by D13, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	58%	Adequate — gated by D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	70%	Adequate — gated by DM11	Capped at Fair by a Critical contributor — resolve it before relying on this lens.

Not evidenced — 5 control(s) we could not find positive evidence for

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

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

Not included — 92 check(s) not relevant to this codebase

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

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — no DI registrations detected
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
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
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~22699 lines of test source are present (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — 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 — no .kt test runner
D12 Dependency Hygiene — Dependency Hygiene incomplete (time budget)
D14 License Compliance — License Compliance not included (check did not complete)
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — Production source is present (.kt) 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 — symbol resolution incomplete — navigability not assessed
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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 CS/VB/GO/SCALA/SWIFT/DART class graph, and this repository's production source is .kt, 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 (.kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — 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 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — This check finds retry-prone mutations (command handlers and message/event consumers) by walking the repository's declared types, and none was loaded here, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C# syntax, and none was loaded for this repository. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
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.
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 — the Gradle `jacocoTestReport` task) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — 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.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not 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
X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
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
X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X28 Index access outside its own emptiness guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
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
X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
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
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 35 finding(s)

D29 · Static Analysis (SAST) · REDACTED · ×29

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 4 more in this group — see findings.md.

D13 · REDACTED Scanning · Leaked secret · ×3

REDACTED
REDACTED
REDACTED

D28 · Secrets (history) · REDACTED · ×3

REDACTED
REDACTED
REDACTED

Serious — 170 finding(s)

D15 · Churn × Complexity Hotspots · Hotspot · ×27

Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt:69 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt changed 14 times in last 90 days, max cyclomatic complexity 18 in ViewerActivity.onCreate at line 69. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/location/src/main/java/com/azikar24/wormaceptor/feature/location/vm/LocationViewModel.kt features/location/src/main/java/com/azikar24/wormaceptor/feature/location/vm/LocationViewModel.kt:104 — features/location/src/main/java/com/azikar24/wormaceptor/feature/location/vm/LocationViewModel.kt changed 9 times in last 90 days, max cyclomatic complexity 19 in LocationViewModel.handleEvent at line 104. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/location/src/main/java/com/azikar24/wormaceptor/feature/location/vm/LocationViewModel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt:132 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt changed 11 times in last 90 days, max cyclomatic complexity 15 in MultipartViewKt.MultipartPartCard at line 132. 1 of those changes was a fix/bug commit, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt:315 — core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt changed 6 times in last 90 days, max cyclomatic complexity 27 in DependenciesInspectorEngine.categorizePackage at line 315. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:64 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt changed 5 times in last 90 days, max cyclomatic complexity 32 in TransactionResponseSectionKt.ResponseTab at line 64. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/vm/CryptoViewModel.kt features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/vm/CryptoViewModel.kt:23 — features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/vm/CryptoViewModel.kt changed 5 times in last 90 days, max cyclomatic complexity 30 in CryptoViewModel.handleEvent at line 23. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/vm/CryptoViewModel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: infra/parser/html/src/main/java/com/azikar24/wormaceptor/infra/parser/html/HtmlBodyParser.kt infra/parser/html/src/main/java/com/azikar24/wormaceptor/infra/parser/html/HtmlBodyParser.kt:87 — infra/parser/html/src/main/java/com/azikar24/wormaceptor/infra/parser/html/HtmlBodyParser.kt changed 5 times in last 90 days, max cyclomatic complexity 30 in HtmlBodyParser.formatHtml at line 87. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- infra/parser/html/src/main/java/com/azikar24/wormaceptor/infra/parser/html/HtmlBodyParser.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/vm/TransactionListViewModel.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/vm/TransactionListViewModel.kt:119 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/vm/TransactionListViewModel.kt changed 5 times in last 90 days, max cyclomatic complexity 28 in TransactionListViewModel.handleEvent at line 119. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/vm/TransactionListViewModel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/ratelimit/src/main/java/com/azikar24/wormaceptor/feature/ratelimit/ui/components/NetworkPresetsCard.kt features/ratelimit/src/main/java/com/azikar24/wormaceptor/feature/ratelimit/ui/components/NetworkPresetsCard.kt:127 — features/ratelimit/src/main/java/com/azikar24/wormaceptor/feature/ratelimit/ui/components/NetworkPresetsCard.kt changed 8 times in last 90 days, max cyclomatic complexity 17 in NetworkPresetsCardKt.PresetChip at line 127. 2 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/ratelimit/src/main/java/com/azikar24/wormaceptor/feature/ratelimit/ui/components/NetworkPresetsCard.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/preferences/src/main/java/com/azikar24/wormaceptor/feature/preferences/vm/PreferencesViewModel.kt features/preferences/src/main/java/com/azikar24/wormaceptor/feature/preferences/vm/PreferencesViewModel.kt:107 — features/preferences/src/main/java/com/azikar24/wormaceptor/feature/preferences/vm/PreferencesViewModel.kt changed 9 times in last 90 days, max cyclomatic complexity 15 in PreferencesViewModel.handleEditorEvent at line 107. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/preferences/src/main/java/com/azikar24/wormaceptor/feature/preferences/vm/PreferencesViewModel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/ContentTypeChip.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/ContentTypeChip.kt:113 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/ContentTypeChip.kt changed 7 times in last 90 days, max cyclomatic complexity 19 in ContentTypeChipKt.getContentTypeChipInfo at line 113. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/ContentTypeChip.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:57 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt changed 5 times in last 90 days, max cyclomatic complexity 25 in TransactionRequestSectionKt.RequestTab at line 57. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/GetDeviceInfoUseCase.kt features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/GetDeviceInfoUseCase.kt:238 — features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/GetDeviceInfoUseCase.kt changed 4 times in last 90 days, max cyclomatic complexity 29 in GetDeviceInfoUseCase.getNetworkDetails at line 238. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/GetDeviceInfoUseCase.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/navigation/DeepLinkHandler.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/navigation/DeepLinkHandler.kt:94 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/navigation/DeepLinkHandler.kt changed 3 times in last 90 days, max cyclomatic complexity 36 in DeepLinkHandler.parseToolsDeepLink at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/navigation/DeepLinkHandler.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/vm/PushSimulatorViewModel.kt features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/vm/PushSimulatorViewModel.kt:36 — features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/vm/PushSimulatorViewModel.kt changed 6 times in last 90 days, max cyclomatic complexity 17 in PushSimulatorViewModel.handleEvent at line 36. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/vm/PushSimulatorViewModel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/WebViewRequest.kt domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/WebViewRequest.kt:166 — domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/WebViewRequest.kt changed 4 times in last 90 days, max cyclomatic complexity 25 in WebViewResourceType.fromUrl at line 166. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/WebViewRequest.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/theme/tokens/ToolColors.kt core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/theme/tokens/ToolColors.kt:72 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/theme/tokens/ToolColors.kt changed 5 times in last 90 days, max cyclomatic complexity 18 in Database.forDataType at line 72. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/theme/tokens/ToolColors.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/tools/PerformanceOverlayToggle.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/tools/PerformanceOverlayToggle.kt:42 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/tools/PerformanceOverlayToggle.kt changed 5 times in last 90 days, max cyclomatic complexity 17 in PerformanceOverlayToggleKt.PerformanceOverlayToggle at line 42. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/tools/PerformanceOverlayToggle.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/mockrules/src/main/java/com/azikar24/wormaceptor/feature/mockrules/vm/MockRulesViewModel.kt features/mockrules/src/main/java/com/azikar24/wormaceptor/feature/mockrules/vm/MockRulesViewModel.kt:87 — features/mockrules/src/main/java/com/azikar24/wormaceptor/feature/mockrules/vm/MockRulesViewModel.kt changed 5 times in last 90 days, max cyclomatic complexity 17 in MockRulesViewModel.handleEditorEvent at line 87. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/mockrules/src/main/java/com/azikar24/wormaceptor/feature/mockrules/vm/MockRulesViewModel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/com/azikar24/wormaceptorapp/main/viewmodel/MainViewModel.kt app/src/main/java/com/azikar24/wormaceptorapp/main/viewmodel/MainViewModel.kt:30 — app/src/main/java/com/azikar24/wormaceptorapp/main/viewmodel/MainViewModel.kt changed 4 times in last 90 days, max cyclomatic complexity 17 in MainViewModel.handleEvent at line 30. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- app/src/main/java/com/azikar24/wormaceptorapp/main/viewmodel/MainViewModel.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/filter/GridFilterCard.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/filter/GridFilterCard.kt:45 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/filter/GridFilterCard.kt changed 4 times in last 90 days, max cyclomatic complexity 16 in GridFilterCardKt.GridFilterCard at line 45. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/filter/GridFilterCard.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/data/FileSystemDataSource.kt features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/data/FileSystemDataSource.kt:100 — features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/data/FileSystemDataSource.kt changed 4 times in last 90 days, max cyclomatic complexity 16 in FileSystemDataSource.readFile at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/data/FileSystemDataSource.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: infra/parser/json/src/main/java/com/azikar24/wormaceptor/infra/parser/json/JsonBodyParser.kt infra/parser/json/src/main/java/com/azikar24/wormaceptor/infra/parser/json/JsonBodyParser.kt:117 — infra/parser/json/src/main/java/com/azikar24/wormaceptor/infra/parser/json/JsonBodyParser.kt changed 3 times in last 90 days, max cyclomatic complexity 17 in JsonBodyParser.cleanJson5Syntax at line 117. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- infra/parser/json/src/main/java/com/azikar24/wormaceptor/infra/parser/json/JsonBodyParser.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageMetadataExtractorImpl.kt infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageMetadataExtractorImpl.kt:82 — infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageMetadataExtractorImpl.kt changed 3 times in last 90 days, max cyclomatic complexity 16 in ImageMetadataExtractorImpl.extractJpegMetadata at line 82. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageMetadataExtractorImpl.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/DependencyInfo.kt domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/DependencyInfo.kt:94 — domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/DependencyInfo.kt changed 3 times in last 90 days, max cyclomatic complexity 16 in DependencyCategory.displayName at line 94. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- domain/entities/src/main/java/com/azikar24/wormaceptor/domain/entities/DependencyInfo.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
+ 2 more in this group — see findings.md.

D3 · God Classes · MethodTooLong · ×20

MethodTooLong: TransactionResponseSectionKt.ResponseTab features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:64 — MethodTooLong — ResponseTab runs 225 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 125 over it, 2.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ImagePreviewCardKt.ImagePreviewCard features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/ImagePreviewCard.kt:123 — MethodTooLong — ImagePreviewCard runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MetricsCardKt.MetricsCard features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/MetricsCard.kt:53 — MethodTooLong — MetricsCard runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TransactionRequestSectionKt.RequestTab features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:57 — MethodTooLong — RequestTab runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ViewerActivity.onCreate features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt:69 — MethodTooLong — onCreate runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MultipartViewKt.MultipartPartCard features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt:132 — MethodTooLong — MultipartPartCard runs 148 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HomeScreenKt.HomeScreen features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:72 — MethodTooLong — HomeScreen runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PdfPreviewSuccessKt.PdfPreviewSuccessContent features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/PdfPreviewSuccess.kt:53 — MethodTooLong — PdfPreviewSuccessContent runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PushSimulatorTemplatesSectionKt.TemplateCard features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorTemplatesSection.kt:141 — MethodTooLong — TemplateCard runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PushSimulatorPreviewSectionKt.NotificationPreview features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorPreviewSection.kt:51 — MethodTooLong — NotificationPreview runs 116 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 16 over it, 1.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HomeScreenKt.ActiveFiltersBanner features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:278 — MethodTooLong — ActiveFiltersBanner runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: GridFilterCardKt.GridFilterCard features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/filter/GridFilterCard.kt:45 — MethodTooLong — GridFilterCard runs 113 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 13 over it, 1.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PushSimulatorFormSectionKt.ActionButtonsSection features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorFormSection.kt:382 — MethodTooLong — ActionButtonsSection runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FullscreenImageViewerKt.FullscreenImageContent features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenImageViewer.kt:94 — MethodTooLong — FullscreenImageContent runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PerformanceOverlayToggleKt.PerformanceOverlayToggle features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/tools/PerformanceOverlayToggle.kt:42 — MethodTooLong — PerformanceOverlayToggle runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TransactionDetailScreenKt.TransactionDetailScaffold features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionDetailScreen.kt:100 — MethodTooLong — TransactionDetailScaffold runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WebSocketDetailScreenKt.WebSocketDetailScreen features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:50 — MethodTooLong — WebSocketDetailScreen runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WormaCeptorInterceptor.intercept api/client/src/main/java/com/azikar24/wormaceptor/api/WormaCeptorInterceptor.kt:92 — MethodTooLong — intercept runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ToolsTabKt.ToolsTab features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/ToolsTab.kt:49 — MethodTooLong — ToolsTab runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: PdfViewerScreenKt.PdfViewerContent features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/PdfViewerScreen.kt:104 — MethodTooLong — PdfViewerContent runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

DM11 · Constructible invalid state · Constructible in an invalid state · ×8

Constructible in an invalid state: CrashEntity infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/CrashEntity.kt:17 — `CrashEntity`'s public constructor takes `exceptionType`, `message`, `stackTrace` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `CrashEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: LeakEntity infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/LeakEntity.kt:20 — `LeakEntity`'s public constructor takes `objectClass`, `leakDescription`, `severity` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `LeakEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: LocationPresetEntity infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/LocationPresetEntity.kt:23 — `LocationPresetEntity`'s public constructor takes `id`, `name`, `latitude`, `longitude`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `LocationPresetEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: MockLocationEntity infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/MockLocationEntity.kt:21 — `MockLocationEntity`'s public constructor takes `latitude`, `longitude`, `altitude`, `name` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `MockLocationEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: MockRuleEntity infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/MockRuleEntity.kt:16 — `MockRuleEntity`'s public constructor takes `id`, `name`, `urlPattern`, `matchType`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `MockRuleEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: PushTemplateEntity infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/PushTemplateEntity.kt:30 — `PushTemplateEntity`'s public constructor takes `id`, `name`, `notificationId`, `title`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `PushTemplateEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: TransactionEntity infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/TransactionEntity.kt:49 — `TransactionEntity`'s public constructor takes `reqUrl`, `reqMethod`, `reqBodyRef`, `resMessage`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TransactionEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
Constructible in an invalid state: WebViewRequestEntity infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/WebViewRequestEntity.kt:32 — `WebViewRequestEntity`'s public constructor takes `id`, `url`, `method`, `headersJson`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `WebViewRequestEntity` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.

D4 · Code Duplication · Duplicated block (15 lines × 2) · ×7

Duplicated block (15 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:219 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:219-233 | features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/WebViewRequestDetailScreen.kt:93-107 — 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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:219` 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) features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:197 — features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:197-211 | features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:241-255 — 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 `features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:197` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:455 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:455-469 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeTopBar.kt:244-258 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:455` 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 (15 lines × 2) REDACTED:111 — REDACTED:111-125 | REDACTED:164-178 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED: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 (15 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorInfoCard.kt:111 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorInfoCard.kt:111-125 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorInfoCard.kt:131-145 — 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 `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorInfoCard.kt:111` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/divider/WormaCeptorDivider.kt:66 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/divider/WormaCeptorDivider.kt:66-80 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/divider/WormaCeptorDivider.kt:86-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/divider/WormaCeptorDivider.kt:66` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/status/WormaCeptorStatusDot.kt:48 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/status/WormaCeptorStatusDot.kt:48-62 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/status/WormaCeptorStatusDot.kt:68-82 — 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 `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/status/WormaCeptorStatusDot.kt:48` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×5

Duplicated block (16 lines × 2) features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:232 — features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:232-247 | features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:178-193 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorCard.kt:165 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorCard.kt:165-180 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorCard.kt:194-209 — 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 `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorCard.kt:165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/detail/WormaCeptorDetailSection.kt:33 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/detail/WormaCeptorDetailSection.kt:33-48 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/detail/WormaCeptorDetailSection.kt:84-99 — 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 `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/detail/WormaCeptorDetailSection.kt:33` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/state/WormaCeptorEmptyState.kt:61 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/state/WormaCeptorEmptyState.kt:61-76 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/state/WormaCeptorErrorState.kt:63-78 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/state/WormaCeptorEmptyState.kt:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/CryptoEngine.kt:129 — core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/CryptoEngine.kt:129-144 | core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/CryptoEngine.kt:202-217 — 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 `core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/CryptoEngine.kt:129` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/CryptoEngine.kt:219` calls `decode` and `core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/CryptoEngine.kt:146` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (14 lines × 2) · ×5

Duplicated block (14 lines × 2) features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/WebViewMonitorScreen.kt:23 — features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/WebViewMonitorScreen.kt:23-36 | features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/WebViewMonitorScreen.kt:59-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. Read the line range as the matched WINDOW rather than a finished unit: at `features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/WebViewMonitorScreen.kt:23` 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) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeTopBar.kt:255 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeTopBar.kt:255-268 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeTopBar.kt:301-314 — 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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeTopBar.kt:255` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenTopControlBar.kt:69 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenTopControlBar.kt:69-82 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenTopControlBar.kt:91-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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenTopControlBar.kt:69` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:161 — features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:161-174 | features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:215-228 — 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 `features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:161` 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) features/database/src/main/java/com/azikar24/wormaceptor/feature/database/data/DatabaseDataSource.kt:141 — features/database/src/main/java/com/azikar24/wormaceptor/feature/database/data/DatabaseDataSource.kt:141-154 | features/database/src/main/java/com/azikar24/wormaceptor/feature/database/data/DatabaseDataSource.kt:167-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `features/database/src/main/java/com/azikar24/wormaceptor/feature/database/data/DatabaseDataSource.kt:141` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (19 lines × 2) · ×4

Duplicated block (19 lines × 2) features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:206 — features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:206-224 | features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/components/MessageList.kt:262-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 `features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketDetailScreen.kt:206` 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 (19 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:457 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:457-475 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeTopBar.kt:280-298 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:457` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeTopBar.kt:279` calls `setOf`, `randomUUID` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:456` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:187 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:187-205 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:254-272 — before extracting anything, compare `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:187` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorExpandableCard.kt:163 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorExpandableCard.kt:163-181 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorExpandableCard.kt:187-205 — 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 `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/card/WormaCeptorExpandableCard.kt:163` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (13 lines × 2) · ×4

Duplicated block (13 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:342 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:342-354 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:391-403 — 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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:342` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:389` calls `mutableStateOf` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/CrashDetailScreen.kt:341` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:189 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:189-201 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:321-333 — 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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:189` 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 (13 lines × 2) features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:260 — features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:260-272 | features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:182-194 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:260` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/list/WormaCeptorListItem.kt:183 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/list/WormaCeptorListItem.kt:183-195 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/list/WormaCeptorListItem.kt:271-283 — 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 `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/list/WormaCeptorListItem.kt:183` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×4

Duplicated block (6 lines × 2) infra/syntax/xml/src/main/java/com/azikar24/wormaceptor/infra/syntax/xml/XmlHighlighter.kt:54 — infra/syntax/xml/src/main/java/com/azikar24/wormaceptor/infra/syntax/xml/XmlHighlighter.kt:54-59 | infra/syntax/xml/src/main/java/com/azikar24/wormaceptor/infra/syntax/xml/XmlHighlighter.kt:105-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. Read the line range as the matched WINDOW rather than a finished unit: at `infra/syntax/xml/src/main/java/com/azikar24/wormaceptor/infra/syntax/xml/XmlHighlighter.kt:54` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:176 — features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:176-181 | features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:230-235 — 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 `features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:176` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (6 lines × 2) infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/InMemoryTransactionRepository.kt:168 — infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/InMemoryTransactionRepository.kt:168-173 | infra/persistence/sqlite/src/main/java/com/azikar24/wormaceptor/infra/persistence/sqlite/TransactionPagingSource.kt:50-55 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:36 — app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:36-41 | app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:59-64 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3

Duplicated block (12 lines × 2) features/leakdetection/src/main/java/com/azikar24/wormaceptor/feature/leakdetection/ui/LeakDetectionScreen.kt:133 — features/leakdetection/src/main/java/com/azikar24/wormaceptor/feature/leakdetection/ui/LeakDetectionScreen.kt:133-144 | features/threadviolation/src/main/java/com/azikar24/wormaceptor/feature/threadviolation/ui/ThreadViolationScreen.kt:93-104 — 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 `features/leakdetection/src/main/java/com/azikar24/wormaceptor/feature/leakdetection/ui/LeakDetectionScreen.kt:133` 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 (12 lines × 2) features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:235 — features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:235-246 | features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt:228-239 — before extracting anything, compare `features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt` and `features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:235` 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) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/chip/WormaCeptorChip.kt:140 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/chip/WormaCeptorChip.kt:140-151 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/chip/WormaCeptorChip.kt:157-168 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/chip/WormaCeptorChip.kt:140` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×3

Duplicated block (11 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:134 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:134-144 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:166-176 — before extracting anything, compare `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:134` 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 (11 lines × 2) features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuUsageGauge.kt:101 — features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuUsageGauge.kt:101-111 | features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/components/HeapUsageCard.kt:84-94 — 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 `features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuUsageGauge.kt:101` 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 (11 lines × 2) features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuUsageGauge.kt:145 — features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuUsageGauge.kt:145-155 | features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/components/HeapUsageCard.kt:118-128 — 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 `features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuUsageGauge.kt: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.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3

Duplicated block (10 lines × 2) plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/toolwindow/WormaCeptorToolWindowPanel.kt:173 — plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/toolwindow/WormaCeptorToolWindowPanel.kt:173-182 | plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/toolwindow/WormaCeptorToolWindowPanel.kt:209-218 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenImageViewer.kt:321 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenImageViewer.kt:321-330 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/ImagePreviewCard.kt:235-244 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenImageViewer.kt:321` 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 (10 lines × 2) features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/components/MemoryChartCard.kt:39 — features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/components/MemoryChartCard.kt:39-48 | features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/components/NativeHeapCard.kt:41-50 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/components/MemoryChartCard.kt:39` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (28 lines × 2) · ×2

Duplicated block (28 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:90 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:90-117 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:116-143 — before extracting anything, compare `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:86` calls `equals`, `firstOrNull` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:113` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (28 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/PdfPreviewStateContent.kt:163 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/PdfPreviewStateContent.kt:163-190 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/PdfPreviewSuccess.kt:208-235 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/PdfPreviewStateContent.kt:163` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (26 lines × 2) · ×2

Duplicated block (26 lines × 2) features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/QueryScreen.kt:336 — features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/QueryScreen.kt:336-361 | features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/TableDataScreen.kt:292-317 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/QueryScreen.kt:336` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/TableDataScreen.kt:291` calls `stringResource` and `features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/QueryScreen.kt:335` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (26 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/badge/WormaCeptorBadge.kt:73 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/badge/WormaCeptorBadge.kt:73-98 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/badge/WormaCeptorBadge.kt:104-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/badge/WormaCeptorBadge.kt:73` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (20 lines × 2) · ×2

Duplicated block (20 lines × 2) features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:183 — features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:183-202 | features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:237-256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:183` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (20 lines × 2) core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/LocationSimulatorEngine.kt:215 — core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/LocationSimulatorEngine.kt:215-234 | core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/LocationSimulatorEngine.kt:273-292 — 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 `core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/LocationSimulatorEngine.kt:215` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (17 lines × 3) · ×2

Duplicated block (17 lines × 3) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:463 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:463-479 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeTopBar.kt:286-302 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionListScreen.kt:169-185 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:463` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (17 lines × 3) features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:91 — features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:91-107 | features/fps/src/main/java/com/azikar24/wormaceptor/feature/fps/ui/FpsScreen.kt:97-113 | features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:76-92 — 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 `features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `state` to `CpuViewState` in one and `FpsViewState` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.

D4 · Code Duplication · Duplicated block (14 lines × 3) · ×2

Duplicated block (14 lines × 3) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:349 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:349-362 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:383-396 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:424-437 — 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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/HomeScreen.kt:349` 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 × 3) features/location/src/main/java/com/azikar24/wormaceptor/feature/location/ui/LocationStatusSection.kt:205 — features/location/src/main/java/com/azikar24/wormaceptor/feature/location/ui/LocationStatusSection.kt:205-218 | features/mockrules/src/main/java/com/azikar24/wormaceptor/feature/mockrules/ui/MockRulesScreen.kt:245-258 | features/ratelimit/src/main/java/com/azikar24/wormaceptor/feature/ratelimit/ui/components/EnableToggleCard.kt:76-89 — 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 `features/location/src/main/java/com/azikar24/wormaceptor/feature/location/ui/LocationStatusSection.kt:205` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×2

Duplicated block (11–12 lines × 2) features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorTemplatesSection.kt:177 — features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorTemplatesSection.kt:177-187 | features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorTemplatesSection.kt:205-216 — 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 `features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorTemplatesSection.kt:177` 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–12 lines × 2) features/preferences/src/main/java/com/azikar24/wormaceptor/feature/preferences/ui/PreferenceDetailScreen.kt:238 — features/preferences/src/main/java/com/azikar24/wormaceptor/feature/preferences/ui/PreferenceDetailScreen.kt:238-249 | features/preferences/src/main/java/com/azikar24/wormaceptor/feature/preferences/ui/PreferencesListScreen.kt:169-179 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/preferences/src/main/java/com/azikar24/wormaceptor/feature/preferences/ui/PreferenceDetailScreen.kt:238` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×2

Duplicated block (9 lines × 2) features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt:171 — features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt:171-179 | features/securestorage/src/main/java/com/azikar24/wormaceptor/feature/securestorage/ui/SecureStorageScreen.kt:149-157 — 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 `features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt:171` 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) features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/util/FileViewerUtils.kt:298 — features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/util/FileViewerUtils.kt:298-306 | features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/util/FileViewerUtils.kt:309-317 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/util/FileViewerUtils.kt:298` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2

Duplicated block (8 lines × 2) core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/button/WormaCeptorButton.kt:201 — core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/button/WormaCeptorButton.kt:201-208 | core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/button/WormaCeptorButton.kt: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 `core/ui/src/main/java/com/azikar24/wormaceptor/core/ui/components/button/WormaCeptorButton.kt:201` 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) core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/PushTokenEngine.kt:252 — core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/PushTokenEngine.kt:252-259 | core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/PushTokenEngine.kt:293-300 — 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 `core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/PushTokenEngine.kt:293` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×2

Duplicated block (5 lines × 2) features/leakdetection/src/main/java/com/azikar24/wormaceptor/feature/leakdetection/ui/components/SeverityFilterChips.kt:29 — features/leakdetection/src/main/java/com/azikar24/wormaceptor/feature/leakdetection/ui/components/SeverityFilterChips.kt:29-33 | features/leakdetection/src/main/java/com/azikar24/wormaceptor/feature/leakdetection/ui/components/SeverityUtils.kt:10-14 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/actions/ClearTransactionsAction.kt:42 — plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/actions/ClearTransactionsAction.kt:42-46 | plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/actions/OpenViewerAction.kt:18-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2

Duplicated block (7 lines × 2) api/common/src/main/java/com/azikar24/wormaceptor/api/internal/LeakNotificationHelper.kt:70 — api/common/src/main/java/com/azikar24/wormaceptor/api/internal/LeakNotificationHelper.kt:70-76 | core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/SecureStorageEngine.kt:481-487 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/XmlTreeView.kt:113 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/XmlTreeView.kt:113-119 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/XmlTreeView.kt:125-131 — 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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/XmlTreeView.kt:113` 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.

D1 · Cyclomatic Complexity · TransactionResponseSectionKt.ResponseTab (cyclomatic 32) · ×1

TransactionResponseSectionKt.ResponseTab (cyclomatic 32) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:64 — TransactionResponseSectionKt.ResponseTab has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · HtmlBodyParser.formatHtml (cyclomatic 30) · ×1

HtmlBodyParser.formatHtml (cyclomatic 30) infra/parser/html/src/main/java/com/azikar24/wormaceptor/infra/parser/html/HtmlBodyParser.kt:87 — HtmlBodyParser.formatHtml has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CryptoViewModel.handleEvent (cyclomatic 30) · ×1

CryptoViewModel.handleEvent (cyclomatic 30) features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/vm/CryptoViewModel.kt:23 — CryptoViewModel.handleEvent has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · GetDeviceInfoUseCase.getNetworkDetails (cyclomatic 29) · ×1

GetDeviceInfoUseCase.getNetworkDetails (cyclomatic 29) features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/GetDeviceInfoUseCase.kt:238 — GetDeviceInfoUseCase.getNetworkDetails has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · DependenciesInspectorEngine.categorizePackage (cyclomatic 27) · ×1

DependenciesInspectorEngine.categorizePackage (cyclomatic 27) core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt:315 — DependenciesInspectorEngine.categorizePackage has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · TransactionRequestSectionKt.RequestTab (cyclomatic 25) · ×1

TransactionRequestSectionKt.RequestTab (cyclomatic 25) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:57 — TransactionRequestSectionKt.RequestTab has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ViewerActivity.onCreate (cyclomatic 18) · ×1

ViewerActivity.onCreate (cyclomatic 18) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ViewerActivity.kt:69 — ViewerActivity.onCreate has cyclomatic complexity 18 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.

D1 · Cyclomatic Complexity · JsonBodyParser.cleanJson5Syntax (cyclomatic 17) · ×1

JsonBodyParser.cleanJson5Syntax (cyclomatic 17) infra/parser/json/src/main/java/com/azikar24/wormaceptor/infra/parser/json/JsonBodyParser.kt:117 — JsonBodyParser.cleanJson5Syntax has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PerformanceOverlayToggleKt.PerformanceOverlayToggle (cyclomatic 17) · ×1

PerformanceOverlayToggleKt.PerformanceOverlayToggle (cyclomatic 17) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/tools/PerformanceOverlayToggle.kt:42 — PerformanceOverlayToggleKt.PerformanceOverlayToggle has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · ImageMetadataExtractorImpl.extractJpegMetadata (cyclomatic 16) · ×1

ImageMetadataExtractorImpl.extractJpegMetadata (cyclomatic 16) infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageMetadataExtractorImpl.kt:82 — ImageMetadataExtractorImpl.extractJpegMetadata has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GridFilterCardKt.GridFilterCard (cyclomatic 16) · ×1

GridFilterCardKt.GridFilterCard (cyclomatic 16) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/filter/GridFilterCard.kt:45 — GridFilterCardKt.GridFilterCard has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D15 · Churn × Complexity Hotspots · Repeated repair · ×1

Repeated repair: features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ListContent.kt features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ListContent.kt:26 — features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ListContent.kt changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is ListContentKt.ListContent at line 26), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(webviewmonitor): restore horizontal padding on filter row parent”; “refactor(ui): flatten webviewmonitor filters; fix prefs chip spacing”; “fix: resolve detekt issues in core modules”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-02-06..2026-05-07, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-02-06 23:37:01 +03:00' --until='2026-05-07 23:37:01 +03:00' --full-history --no-merges -- features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ListContent.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D2 · Cognitive Complexity · TransactionResponseSectionKt.ResponseTab (cognitive 77) · ×1

TransactionResponseSectionKt.ResponseTab (cognitive 77) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:64 — TransactionResponseSectionKt.ResponseTab has cognitive complexity 77 (threshold 15). Drivers by points: if/else 18 (46 pts), match/switch 2 (17 pts), error handling 2 (9 pts), boolean chains 5 (nesting depth added 50). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · HtmlBodyParser.formatHtml (cognitive 64) · ×1

HtmlBodyParser.formatHtml (cognitive 64) infra/parser/html/src/main/java/com/azikar24/wormaceptor/infra/parser/html/HtmlBodyParser.kt:87 — HtmlBodyParser.formatHtml has cognitive complexity 64 (threshold 15). Drivers by points: if/else 18 (54 pts), boolean chains 7, match/switch 1 (2 pts), loops 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TransactionRequestSectionKt.RequestTab (cognitive 46) · ×1

TransactionRequestSectionKt.RequestTab (cognitive 46) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:57 — TransactionRequestSectionKt.RequestTab has cognitive complexity 46 (threshold 15). Drivers by points: if/else 12 (25 pts), match/switch 2 (11 pts), error handling 2 (6 pts), boolean chains 4 (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.

D2 · Cognitive Complexity · JsonBodyParser.cleanJson5Syntax (cognitive 33) · ×1

JsonBodyParser.cleanJson5Syntax (cognitive 33) infra/parser/json/src/main/java/com/azikar24/wormaceptor/infra/parser/json/JsonBodyParser.kt:117 — JsonBodyParser.cleanJson5Syntax has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 3 (9 pts), boolean chains 6 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ImageMetadataExtractorImpl.extractJpegMetadata (cognitive 25) · ×1

ImageMetadataExtractorImpl.extractJpegMetadata (cognitive 25) infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageMetadataExtractorImpl.kt:82 — ImageMetadataExtractorImpl.extractJpegMetadata has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 1 (4 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · XmlBodyParser.format (cognitive 22) · ×1

XmlBodyParser.format (cognitive 22) infra/parser/xml/src/main/java/com/azikar24/wormaceptor/infra/parser/xml/XmlBodyParser.kt:53 — XmlBodyParser.format has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), match/switch 1 (3 pts), loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · WormaCeptorInterceptor.intercept (cognitive 20) · ×1

WormaCeptorInterceptor.intercept (cognitive 20) api/client/src/main/java/com/azikar24/wormaceptor/api/WormaCeptorInterceptor.kt:92 — WormaCeptorInterceptor.intercept has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 4 (7 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · XmlTreeViewKt.highlightXmlLine (cognitive 19) · ×1

XmlTreeViewKt.highlightXmlLine (cognitive 19) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/XmlTreeView.kt:105 — XmlTreeViewKt.highlightXmlLine has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PerformanceOverlayToggleKt.PerformanceOverlayToggle (cognitive 19) · ×1

PerformanceOverlayToggleKt.PerformanceOverlayToggle (cognitive 19) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/tools/PerformanceOverlayToggle.kt:42 — PerformanceOverlayToggleKt.PerformanceOverlayToggle has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3, match/switch 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · ProtobufBodyParser.formatHexDump (cognitive 18) · ×1

ProtobufBodyParser.formatHexDump (cognitive 18) infra/parser/protobuf/src/main/java/com/azikar24/wormaceptor/infra/parser/protobuf/ProtobufBodyParser.kt:266 — ProtobufBodyParser.formatHexDump has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 3 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GridFilterCardKt.GridFilterCard (cognitive 17) · ×1

GridFilterCardKt.GridFilterCard (cognitive 17) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/filter/GridFilterCard.kt:45 — GridFilterCardKt.GridFilterCard has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (16 pts), match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · JsonTreeViewKt.JsonArrayNode (cognitive 16) · ×1

JsonTreeViewKt.JsonArrayNode (cognitive 16) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:249 — JsonTreeViewKt.JsonArrayNode has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · MultipartViewKt.MultipartPartCard (cognitive 16) · ×1

MultipartViewKt.MultipartPartCard (cognitive 16) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt:132 — MultipartViewKt.MultipartPartCard has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, match/switch 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D3 · God Classes · FileTooLong · ×1

FileTooLong: engine/DependenciesInspectorEngine.kt core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt — FileTooLong — 908 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 408 over it, 1.82× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.

D3 · God Classes · TooManyMethods · ×1

TooManyMethods: PerformanceOverlayEngine core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/PerformanceOverlayEngine.kt:60 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · ClassTooLong · ×1

ClassTooLong: PerformanceOverlayEngine core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/PerformanceOverlayEngine.kt:60 — ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded), 37 methods. The bar is 400 significant lines; this is 37 over it, 1.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D35 · Change Coupling · Change coupling · ×1

Change coupling: FullscreenImageViewer.kt ↔ PdfViewerScreen.kt features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenImageViewer.kt — `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/FullscreenImageViewer.kt` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/PdfViewerScreen.kt` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `582593fe` refactor(ui): extend ComponentSize tokens and eliminate raw .dp literals; `4538fded` refactor: replace Toast with Snackbar across UI components; `33a1cf98` fix: revert FileProvider authority to original .fileprovider — run `git show` on any of them.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D4 · Code Duplication · Near-duplicate member pair (118 shared lines) · ×1

Near-duplicate member pair (118 shared lines) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:65 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:65-300 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:72-401 — These two members are variants of one another: 118 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (71 shared lines) · ×1

Near-duplicate member pair (71 shared lines) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:122 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:122-246 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:256-375 — These two members are variants of one another: 71 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Near-duplicate member pair (40 shared lines) · ×1

Near-duplicate member pair (40 shared lines) features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:158 — features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:158-209 | features/filebrowser/src/main/java/com/azikar24/wormaceptor/feature/filebrowser/ui/FileViewerScreen.kt:212-263 — These two members are variants of one another: 40 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.

D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1

Edited copy of a member (37 corresponding lines) features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:113 — features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:113-156 | features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:161-204 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.

D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1

Members sharing a duplicated core (4 members, 50+ identical tokens) features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:112 — features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:112-163 | features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt:148-193 | features/securestorage/src/main/java/com/azikar24/wormaceptor/feature/securestorage/ui/SecureStorageScreen.kt:120-171 | features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ExpandableSearchBar.kt:23-45 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.

D4 · Code Duplication · Duplicated block (40–41 lines × 2) · ×1

Duplicated block (40–41 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:133 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:133-173 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:266-305 — 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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (39 lines × 2) · ×1

Duplicated block (39 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:229 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:229-267 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:296-334 — before extracting anything, compare `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:229` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1

Duplicated block (35 lines × 2) features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:114 — features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:114-148 | features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:162-196 — 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 `features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (34–35 lines × 2) · ×1

Duplicated block (34–35 lines × 2) features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/QueryScreen.kt:296 — features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/QueryScreen.kt:296-330 | features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/TableDataScreen.kt:253-286 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/QueryScreen.kt:296` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/QueryScreen.kt:332` calls `stringResource` and `features/database/src/main/java/com/azikar24/wormaceptor/feature/database/ui/TableDataScreen.kt:288` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1

Duplicated block (29 lines × 2) features/mockrules/src/main/java/com/azikar24/wormaceptor/feature/mockrules/ui/MockRulesScreen.kt:239 — features/mockrules/src/main/java/com/azikar24/wormaceptor/feature/mockrules/ui/MockRulesScreen.kt:239-267 | features/ratelimit/src/main/java/com/azikar24/wormaceptor/feature/ratelimit/ui/components/EnableToggleCard.kt:70-98 — 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 `features/mockrules/src/main/java/com/azikar24/wormaceptor/feature/mockrules/ui/MockRulesScreen.kt:239` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1

Duplicated block (27–28 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt:164 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt:164-190 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/ProtobufView.kt:189-216 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/MultipartView.kt:164` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1

Duplicated block (21 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:207 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:207-227 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:274-294 — before extracting anything, compare `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:207` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1

Duplicated block (18–19 lines × 2) core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt:387 — core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt:387-404 | core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt:514-532 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `core/engine/src/main/java/com/azikar24/wormaceptor/core/engine/DependenciesInspectorEngine.kt:387` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (17 lines × 2) · ×1

Duplicated block (17 lines × 2) features/logs/src/main/java/com/azikar24/wormaceptor/feature/logs/ui/components/LogList.kt:149 — features/logs/src/main/java/com/azikar24/wormaceptor/feature/logs/ui/components/LogList.kt:149-165 | features/websocket/src/main/java/com/azikar24/wormaceptor/feature/websocket/ui/WebSocketListScreen.kt:269-285 — 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 `features/logs/src/main/java/com/azikar24/wormaceptor/feature/logs/ui/components/LogList.kt:149` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×1

Duplicated block (13–14 lines × 2) plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/toolwindow/WormaCeptorToolWindowPanel.kt:194 — plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/toolwindow/WormaCeptorToolWindowPanel.kt:194-206 | plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/toolwindow/WormaCeptorToolWindowPanel.kt:231-244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/toolwindow/WormaCeptorToolWindowPanel.kt:194` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.

D4 · Code Duplication · Duplicated block (4–14 lines × 3) · ×1

Duplicated block (4–14 lines × 3) app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:32 — app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:32-35 | app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:43-56 | app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:73-82 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:56` calls `close`, `moveTo` and `app/src/main/java/com/azikar24/wormaceptorapp/wormaceptorui/drawables/RememberWormaceptorLogo.kt:35` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (13 lines × 4) · ×1

Duplicated block (13 lines × 4) features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:91 — features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:91-103 | features/fps/src/main/java/com/azikar24/wormaceptor/feature/fps/ui/FpsScreen.kt:97-109 | features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:76-88 | features/ratelimit/src/main/java/com/azikar24/wormaceptor/feature/ratelimit/ui/RateLimitScreen.kt:80-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×1

Duplicated block (11–12 lines × 3) features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/ui/DeviceInfoScreen.kt:163 — features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/ui/DeviceInfoScreen.kt:163-174 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt:106-116 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt:132-142 — before extracting anything, compare `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionRequestSection.kt` and `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/TransactionResponseSection.kt` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 130 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/ui/DeviceInfoScreen.kt:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (9–11 lines × 3) · ×1

Duplicated block (9–11 lines × 3) features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:239 — features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:239-249 | features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt:232-241 | features/securestorage/src/main/java/com/azikar24/wormaceptor/feature/securestorage/ui/SecureStorageScreen.kt:243-251 — before extracting anything, compare `features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt` and `features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:239` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (10 lines × 3) · ×1

Duplicated block (10 lines × 3) features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:50 — features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:50-59 | features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuPerCoreSection.kt:42-51 | features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuSystemInfo.kt:43-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuChartSection.kt:50` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (8–9 lines × 13) · ×1

Duplicated block (8–9 lines × 13) features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:97 — features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:97-105 | features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/ui/CryptoScreen.kt:98-106 | features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/ui/DeviceInfoScreen.kt:168-176 | features/fps/src/main/java/com/azikar24/wormaceptor/feature/fps/ui/FpsScreen.kt:103-111 | features/leakdetection/src/main/java/com/azikar24/wormaceptor/feature/leakdetection/ui/LeakDetectionScreen.kt:138-146 | features/location/src/main/java/com/azikar24/wormaceptor/feature/location/ui/LocationScreen.kt:96-104 | features/memory/src/main/java/com/azikar24/wormaceptor/feature/memory/ui/MemoryScreen.kt:82-90 | features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorScreen.kt:157-165 | REDACTED:119-126 | features/ratelimit/src/main/java/com/azikar24/wormaceptor/feature/ratelimit/ui/RateLimitScreen.kt:86-94 | features/recomposition/src/main/java/com/azikar24/wormaceptor/feature/recomposition/ui/RecompositionSummaryScreen.kt:74-81 | features/threadviolation/src/main/java/com/azikar24/wormaceptor/feature/threadviolation/ui/ThreadViolationScreen.kt:98-106 | features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/WebViewRequestDetailScreen.kt:101-109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 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 13 times. Read the line range as the matched WINDOW rather than a finished unit: at `features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:97` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `features/cpu/src/main/java/com/azikar24/wormaceptor/feature/cpu/ui/CpuScreen.kt:94` calls `padding` and `features/deviceinfo/src/main/java/com/azikar24/wormaceptor/feature/deviceinfo/ui/DeviceInfoScreen.kt:165` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1

Duplicated block (8 lines × 4) features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:145 — features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:145-152 | features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt:175-182 | features/securestorage/src/main/java/com/azikar24/wormaceptor/feature/securestorage/ui/SecureStorageScreen.kt:153-160 | features/webviewmonitor/src/main/java/com/azikar24/wormaceptor/feature/webviewmonitor/ui/components/ExpandableSearchBar.kt:26-33 — before extracting anything, compare `features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt` and `features/loadedlibraries/src/main/java/com/azikar24/wormaceptor/feature/loadedlibraries/ui/LoadedLibrariesScreen.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `features/dependenciesinspector/src/main/java/com/azikar24/wormaceptor/feature/dependenciesinspector/ui/DependenciesInspectorScreen.kt:145` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (7–8 lines × 4) · ×1

Duplicated block (7–8 lines × 4) features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/ui/HistoryList.kt:26 — features/crypto/src/main/java/com/azikar24/wormaceptor/feature/crypto/ui/HistoryList.kt:26-33 | features/location/src/main/java/com/azikar24/wormaceptor/feature/location/ui/LocationScreen.kt:95-102 | features/pushsimulator/src/main/java/com/azikar24/wormaceptor/feature/pushsimulator/ui/PushSimulatorScreen.kt:156-163 | REDACTED:118-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.

D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1

Duplicated block (7 lines × 3) infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageParser.kt:148 — infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageParser.kt:148-154 | plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/ui/TransactionDetailPanel.kt:290-296 | plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/ui/TransactionDetailPanel.kt:441-447 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `infra/parser/image/src/main/java/com/azikar24/wormaceptor/infra/parser/image/ImageParser.kt:147` calls `Suppress` and `plugins/android-studio/src/main/kotlin/com/azikar24/wormaceptor/studio/ui/TransactionDetailPanel.kt:288` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1

Duplicated block (18 lines × 2) features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:229 — features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:229-246 | features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:358-375 — 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 `features/viewer/src/main/java/com/azikar24/wormaceptor/feature/viewer/ui/components/body/JsonTreeView.kt:229` 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.

Minor — 11 finding(s)

D19 · Documentation Quality · Documentation · ×3

Documentation: no installation or build instructions README.md — The Quick Start section gives only the dependency-resolution-management repository declaration and a one-line dependency line; no build.gradle.kts or gradle.properties setup steps for adding the library to an app. Add full Gradle dependency configuration for wormaceptor-client:2.3.1 in build.gradle.kts, plus any required properties (e.g. repositories) needed to resolve it.
Documentation: no usage examples README.md — The Quick Start is the only runnable example; no usage code or a 'how to run it' section. Add a Usage section showing how to call WormaCeptor's API from an activity, fragment, or service.
Documentation: no licence statement README.md — The README shows the license badge but no actual LICENSE file in the repository. Place the MIT-style license under a LICENSE file and link it.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

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

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 7710 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

P6 · Release Hygiene · No changelog · ×1

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

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9b7a2d30620141038be484c677bc3426/history.json --exit-code 0 --source .	3	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9b7a2d30620141038be484c677bc3426/tree.json --exit-code 0 --source .	2	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	30	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	none (dependency manifest found, not scanned for vulnerabilities here)	—	none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).	0	—
D31 · IaC & Container Security	trivy	—	trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.	0	—
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	none (dependency manifest found, not scanned for vulnerabilities here)	—	none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) and a Gradle version catalogue — not scanned yet).	0	—

Run 01a0c4ff-0cdb-75f0-98c8-2f3aa60f6055 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Azikar24/WormaCeptor

Findings by grade

This survey was produced by

Executive summary

Top priorities

Diagnosis — what's actually going on

Architecture — module dependency matrix

At a glance — Code Health · 91% · Exemplary ·

At a glance — Architecture · 96% · Exemplary ·

At a glance — Maturity · 67% · Adequate · gated by M2 ·

At a glance — Readiness · 34% · Weak · gated by D13, P3 ·

At a glance — Security · 58% · Adequate · gated by D36 ·

At a glance — Domain Modelling · 70% · Adequate · gated by DM11 ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts