Egonex-AI/Understand-Anything

Executive summary

Egonex-AI/Understand-Anything is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 48 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 42, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the three deprecated dependencies, worth about 4 points. Adopting a logging library would lift Production Readiness itself, worth about 5 points. Raising Production Readiness to 70 would lift the score to about 54.

Twenty-seven known security holes in the packages the code depends on can be used by attackers. Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and five weaknesses in the code could be used by an attacker. Updating the vulnerable packages, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. Setting a waiting period for automatic updates would fix the three automatic dependency updates that take new releases at once. The eight controls that only work with a mouse need to work with the keyboard, or to become a real button.

The product code is 38,772 lines, about €61,000 to rebuild.

Code Health 58 Adequate, capped by Cyclomatic Complexity and Cognitive Complexity Architecture 92 ★ Exemplary Maturity 61 Adequate, capped by Architecture documentation Production Readiness 42 Weak, capped by Observability and Security & performance tooling Security and Compliance 54 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Supply-chain Provenance & Signing Accessibility 49 Weak, capped by Keyboard semantics Performance 60 Adequate

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 42 · counts for 46%Accessibility 49 · counts for 25%Security and Compliance 54 · counts for 14%Code Health 58 · counts for 8%Performance 60 · counts for 4%Maturity 61 · counts for 2%Architecture 92 · counts for 1%

If Production Readiness rose from 42 to 70, the lowest score rated Strong, the score would rise from 48 to about 54.

Code composition: what the lines of code are

Product code 59%Tests 41%

New since the last survey: 62 findings

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

Dependency Hygiene · Deprecated: eslint REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Knowledge Freshness · Orphaned knowledge understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts
Supply-chain Provenance & Signing · REDACTED
Cyclomatic Complexity · Complex function resolvePythonImport (cyclomatic 28, cognitive 55) understand-anything-plugin/skills/understand/extract-import-map.mjs
Large Files · understand-anything-plugin/skills/understand/extract-import-map.mjs: 2022 lines of code understand-anything-plugin/skills/understand/extract-import-map.mjs
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/skills/understand-figma/figma-scan.mjs
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/skills/understand-figma/figma-scan.mjs
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/themes/ThemeContext.tsx
Exception handling · Swallowed exception (empty catch) understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts
Exception handling · Swallowed exception (caught, then discarded) understand-anything-plugin/hooks/post-tool-use-auto-update.mjs
Exception handling · Swallowed exception (empty catch) scripts/lib/large-repo-benchmark.mjs
Exception handling · Swallowed exception (empty catch) scripts/lib/large-repo-benchmark.mjs
Exception handling · Swallowed exception (empty catch) scripts/lib/large-repo-benchmark.mjs
Exception handling · Swallowed exception (empty catch) scripts/lib/large-repo-benchmark.mjs
Incompleteness & stubs · Guard cannot change the result — returns what the code already falls through to understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts
Incompleteness & stubs · Guard cannot change the result — returns what the code already falls through to understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts
Keyboard semantics · Modal dialog does not manage focus understand-anything-plugin/packages/dashboard/src/components/MobileDrawer.tsx
Keyboard semantics · Modal dialog does not manage focus understand-anything-plugin/packages/dashboard/src/components/OnboardingOverlay.tsx
Visual & motion safety · Focus outline removed inline understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx
Visual & motion safety · Focus outline removed inline understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx
Visual & motion safety · Focus outline removed inline understand-anything-plugin/packages/dashboard/src/components/SearchBar.tsx
Visual & motion safety · Focus outline removed inline understand-anything-plugin/packages/dashboard/src/components/TokenGate.tsx
Visual & motion safety · Animation without a prefers-reduced-motion guard understand-anything-plugin/packages/dashboard/src/index.css
Visual & motion safety · Animation without a prefers-reduced-motion guard understand-anything-plugin/packages/dashboard/src/index.css
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/packages/viewer/bin/viewer.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-structure.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-structure.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-structure.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/extract-structure.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/finalize-incremental.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/finalize-incremental.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/finalize-incremental.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/prepare-incremental.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/prepare-incremental.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/prepare-incremental.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs
Async & latency hygiene · Sync-over-async blocking understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs

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

Fixed since the last survey: 130 findings

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

Churn × Complexity Hotspots · Hotspot: understand-anything-plugin/skills/understand/compute-batches.mjs understand-anything-plugin/skills/understand/compute-batches.mjs
Churn × Complexity Hotspots · Hotspot: understand-anything-plugin/skills/understand/scan-project.mjs understand-anything-plugin/skills/understand/scan-project.mjs
Churn × Complexity Hotspots · Hotspot: understand-anything-plugin/skills/understand/extract-structure-result.mjs understand-anything-plugin/skills/understand/extract-structure-result.mjs
Churn × Complexity Hotspots · Repeated repair: understand-anything-plugin/skills/understand/extract-structure.mjs understand-anything-plugin/skills/understand/extract-structure.mjs
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Supply-chain Provenance & Signing REDACTED
Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx
Code Duplication · Duplicated block (16 lines × 2 locations) understand-anything-plugin/skills/understand/build-fingerprints.mjs
Code Duplication · Duplicated block (16 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs
Code Duplication · Duplicated block (15 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx
Code Duplication · Duplicated block (15 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/utils/elk-layout.ts
Code Duplication · Duplicated block (14 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts
Code Duplication · Duplicated block (14 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/parsers/protobuf-parser.ts
Code Duplication · Duplicated block (14 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/utils/edgeAggregation.ts
Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (14 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (14 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/core/src/analyzer/language-lesson.ts
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts
Code Duplication · Duplicated block (13 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/parsers/protobuf-parser.ts
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/core/src/schema.ts
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/App.tsx
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/KeyboardShortcutsHelp.tsx
Code Duplication · Duplicated block (13 lines × 3 locations) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx
Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx
Code Duplication · Duplicated block (13 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (13 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs
Code Duplication · Duplicated block (12 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts
Code Duplication · Duplicated block (12 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts
Code Duplication · Duplicated block (12 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts
Code Duplication · Duplicated block (12 lines × 4 locations) understand-anything-plugin/packages/core/src/plugins/parsers/dockerfile-parser.ts
Code Duplication · Duplicated block (12 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/parsers/graphql-parser.ts
Code Duplication · Duplicated block (12 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/parsers/markdown-parser.ts
Code Duplication · Duplicated block (12 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/parsers/protobuf-parser.ts
Code Duplication · Duplicated block (12 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/parsers/terraform-parser.ts
Code Duplication · Duplicated block (12 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx
Code Duplication · Duplicated block (12 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/store.ts
Code Duplication · Duplicated block (12 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (11 lines × 4 locations) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts
Code Duplication · Duplicated block (11 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts
Code Duplication · Duplicated block (11 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/parsers/sql-parser.ts
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/ProjectOverview.tsx
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/store.ts
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs
Code Duplication · Duplicated block (11 lines × 2 locations) understand-anything-plugin/skills/understand/prepare-incremental.mjs
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/packages/core/src/analyzer/graph-builder.ts
Code Duplication · Duplicated block (10 lines × 7 locations) understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/App.tsx
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx
Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/skills/understand/extract-structure-result.mjs
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/skills/understand/generate-ignore.mjs
Code Duplication · Duplicated block (10 lines × 2 locations) understand-anything-plugin/skills/understand/prepare-incremental.mjs
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/packages/core/src/schema.ts
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx
Code Duplication · Duplicated block (9 lines × 3 locations) understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx
Code Duplication · Duplicated block with local edits (9 matched lines × 2 locations) understand-anything-plugin/packages/viewer/bin/viewer.mjs
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs
Code Duplication · Duplicated block (9 lines × 2 locations) understand-anything-plugin/src/diff-analyzer.ts
Code Duplication · Duplicated block (8 lines × 2 locations) understand-anything-plugin/packages/core/src/analyzer/layer-detector.ts
Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/base-extractor.ts
Code Duplication · Duplicated block (8 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts
Code Duplication · Duplicated block (8 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/parsers/graphql-parser.ts
Code Duplication · Duplicated block (8 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/parsers/graphql-parser.ts
Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) understand-anything-plugin/packages/dashboard/src/App.tsx
Code Duplication · Duplicated block (8 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx
Code Duplication · Duplicated block (8 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx
Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs
Code Duplication · Duplicated block with local edits (8 matched lines × 2 locations) understand-anything-plugin/skills/understand/extract-structure.mjs
Code Duplication · Duplicated block (8 lines × 2 locations) understand-anything-plugin/src/diff-analyzer.ts
Code Duplication · Duplicated block (8 lines × 2 locations) understand-anything-plugin/src/onboard-builder.ts
Code Duplication · Duplicated block with local edits (7 matched lines × 2 locations) understand-anything-plugin/packages/core/src/analyzer/layer-detector.ts
Code Duplication · Duplicated block (7 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts
Code Duplication · Duplicated block (7 lines × 5 locations) understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts
Code Duplication · Duplicated block (7 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts
Code Duplication · Duplicated block (7 lines × 4 locations) understand-anything-plugin/packages/core/src/plugins/parsers/dockerfile-parser.ts

Rebuild cost: about €61,000 · Estimate

Cost to rebuild	€20,000 to €100,000, for 336 to 1,066 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem	Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor	×0.7 at a score of 48. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 38,772 lines of product code
What it is not	Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3).

Raises the score by about 4 points · Low effort · Dependency Hygiene

Adopt pino (or winston) and log at meaningful points in the services you run.

Raises the score by about 5 points · Medium effort · Observability

Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.

Raises the score by about 5 points · Medium effort · Security & performance tooling

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk

This code would cost about €61,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 42 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

If you do one thing first · First action

Resolve the 3 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 3 Dependency Hygiene findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

What hard-to-read code costs each year · Cost

Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.0 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 5% to 11% on every change. The history of the code shows how much it changes: about 9,845 lines over the last 90 days, which is about 39,927 lines a year. At that pace, the extra work comes to an estimated 5 to 30.2 engineer-days a year, and it grows as more code changes.

How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.

Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history

What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

Architecture: which parts of the code depend on which

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

116 modules, with 108 dependencies between them. Every module uses only modules listed above it, so there are no loops.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 packages.core.src.figma.source.types	2 packages.core.src.languages.language-registry	3 packages.core.src.plugins.symbol-scopes	4 packages.core.src.schema	5 packages.core.src.types	6 packages.dashboard.src.components.NodeTooltip	7 packages.dashboard.src.locales	8 packages.dashboard.src.themes.types	13 packages.core.src.plugins.extractors.types	14 packages.core.src.plugins.registry	15 packages.core.src.plugins.symbol-evidence	16 packages.dashboard.src.components.KnowledgeGraphView	18 packages.dashboard.src.store	19 packages.dashboard.src.themes.ThemeContext
1 packages.core.src.figma.source.types
2 packages.core.src.languages.language-registry
3 packages.core.src.plugins.symbol-scopes
4 packages.core.src.schema
5 packages.core.src.types
6 packages.dashboard.src.components.NodeTooltip
7 packages.dashboard.src.locales
8 packages.dashboard.src.themes.types
9 packages.core.src.analyzer					3
10 packages.core.src.analyzer.graph-builder		1			3
11 packages.core.src.figma				1	1
12 packages.core.src.figma.parse	3				1
13 packages.core.src.plugins.extractors.types					1
14 packages.core.src.plugins.registry		1			1
15 packages.core.src.plugins.symbol-evidence			1
16 packages.dashboard.src.components.KnowledgeGraphView					1
17 packages.dashboard.src.contexts.I18nContext							1
18 packages.dashboard.src.store					2
19 packages.dashboard.src.themes.ThemeContext					1			1
20 src					5
21 packages.core.src				2	5					1
22 packages.core.src.plugins			4		1					1	1
23 packages.core.src.plugins.extractors.cpp-extractor					1				1
24 packages.core.src.plugins.extractors.csharp-extractor					1				1
25 packages.core.src.plugins.extractors.dart-extractor					1				1
26 packages.core.src.plugins.extractors.go-extractor					1				1
27 packages.core.src.plugins.extractors.java-extractor					1				1
28 packages.core.src.plugins.extractors.kotlin-extractor					1				1
29 packages.core.src.plugins.extractors.php-extractor					1				1
30 packages.core.src.plugins.extractors.python-extractor					1				1
31 packages.core.src.plugins.extractors.ruby-extractor					1				1
32 packages.core.src.plugins.extractors.rust-extractor					1				1
33 packages.core.src.plugins.extractors.scala-extractor					1				1
34 packages.core.src.plugins.extractors.swift-extractor					1				1
35 packages.core.src.plugins.extractors.typescript-extractor					1				1
36 packages.core.src.plugins.tree-sitter-plugin					2				1
37 packages.dashboard.src					1		1						1
38 packages.dashboard.src.components					5	1						1
39 packages.dashboard.src.themes					2			2						2
40 packages.dashboard.src.utils				1	3								1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 58% · Adequate · gated by D1, D2 ·

The Good

D4 · TypeScript Code Duplication 9.9 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.1 R1 · React / TS Type Safety 8.9 R10 · React / TS Code Duplication 8.0 R7 · React / TS Dead Code 9.7 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X5 · Repo Nullable reference types 8.0

The Bad

D3 · TypeScript God Classes 6.3 R2 · React / TS Cyclomatic Complexity 6.0 R3 · React / TS Large Files 5.9 X3 · Repo Exception handling 5.5

The Ugly

D1 · TypeScript Cyclomatic Complexity 2.0 D2 · TypeScript Cognitive Complexity 2.0 X2 · Repo Cancellation propagation 4.0

At a glance — Architecture · 92% · Exemplary ·

The Good

D5 · TypeScript Coupling 10.0 D6 · TypeScript Cohesion (LCOM4) 10.0 D23 · TypeScript Boundary Type-Coupling 10.0 D35 · TypeScript Change Coupling 10.0 AX10 · Repo Code composition 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0 R11 · React / TS Import Boundaries 8.0 R9 · React / TS Circular Imports 10.0

The Bad

D26 · TypeScript Project Cohesion 6.0

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

The Good

D15 · TypeScript Churn × Complexity Hotspots 8.6 D19 · TypeScript Documentation Quality 10.0 D34 · TypeScript Knowledge Freshness 9.3 M1 · Repo Documentation (README) 7.2 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 8.0

The Bad

D16 · TypeScript Bus Factor 7.0

The Ugly

M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 42% · Weak · gated by P2, P3 ·

The Good

D8 · TypeScript Code Coverage 9.5 D9 · TypeScript Test Distribution 10.0 D10 · TypeScript Test Quality 10.0 D11 · TypeScript Test Reliability 10.0 D12 · TypeScript Dependency Hygiene 8.8 D13 · TypeScript Secret Scanning 10.0 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P4 · Repo Deployment & Rollback 8.0 R4 · React / TS Test Coverage 7.1 R6 · React / TS Tooling 10.0 R8 · React / TS Dependency Hygiene 9.5

The Bad

P6 · Repo Release Hygiene 5.0

The Ugly

P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 0.0

At a glance — Security · 54% · Adequate · gated by D29, D30, D36 ·

The Good

D28 · TypeScript Secrets (history) 10.0 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Ugly

D29 · TypeScript Static Analysis (SAST) 2.4 D30 · TypeScript Dependency Vulnerabilities 0.0 D36 · TypeScript Supply-chain Provenance & Signing 0.0

At a glance — Accessibility · 49% · Weak · gated by AC4 ·

The Good

AC1 · Repo Text alternatives 10.0 AC5 · Repo ARIA correctness 10.0

The Bad

AC2 · Repo Forms & labels 6.3 AC3 · Repo Page structure 6.5 AC6 · Repo Visual & motion safety 5.5

The Ugly

AC4 · Repo Keyboard semantics 2.1 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.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:2025 — Software Supply Chain Failures	39	High / Critical
A05:2025 — Injection	18	High / Critical

Roadmap

First, implement structured logging across all services to establish baseline observability and health monitoring. Next, integrate static analysis into the CI pipeline to block security regressions and resolve deprecated dependencies to ensure code hygiene. Finally, maintain a changelog for release tracking and fix keyboard accessibility issues in custom controls to improve usability.

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

Do this	Helps	Effort	Dimension
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3).	+3.7 pts	Low	Dependency Hygiene
Adopt pino (or winston) and log at meaningful points in the services you run.	+5.0 pts	Medium	Observability
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.	+5.0 pts	Medium	Security & performance tooling
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.	+2.4 pts	Medium	Release Hygiene
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.	+1.9 pts	Medium	Keyboard semantics
Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.	+1.6 pts	Medium	A11y enforcement
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.	+1.2 pts	Medium	Visual & motion safety
Add tests that import the unreached modules (directly or through their public entry).	+1.0 pts	Medium	Test Coverage

File quality

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

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical vulnerability: REDACTED
REDACTED	1.9	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	2.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx	5.5	Mixed	Cyclomatic Complexity: GraphView.useLayerDetailTopology (cyclomatic 59)
understand-anything-plugin/packages/dashboard/src/App.tsx	5.5	Mixed	Cyclomatic Complexity: App.DashboardContent (cyclomatic 52)
understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx	5.6	Mixed	Cyclomatic Complexity: NodeInfo.NodeInfo (cyclomatic 38)
REDACTED	5.7	Mixed	Static Analysis (SAST): Medium: REDACTED
understand-anything-plugin/packages/dashboard/src/store.ts	5.7	Mixed	Cyclomatic Complexity: store.useDashboardStore (cyclomatic 47)
understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx	5.9	Mixed	Cyclomatic Complexity: KnowledgeGraphView.KnowledgeGraphViewInner (cyclomatic 38)
understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx	5.9	Mixed	Cyclomatic Complexity: CodeViewer.CodeViewer (cyclomatic 30)
understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx	5.9	Mixed	Cyclomatic Complexity: WarningBanner.WarningBanner (cyclomatic 28)
understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx	5.9	Mixed	Cyclomatic Complexity: PathFinderModal.PathFinderModal (cyclomatic 26)
understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx	5.9	Mixed	Cyclomatic Complexity: ExportMenu.ExportMenu (cyclomatic 25)
understand-anything-plugin/packages/dashboard/src/components/MobileLayout.tsx	5.9	Mixed	Cyclomatic Complexity: MobileLayout.MobileLayout (cyclomatic 24)
understand-anything-plugin/packages/dashboard/src/hooks/useKeyboardShortcuts.ts	6.3	Mixed	Cyclomatic Complexity: useKeyboardShortcuts.useKeyboardShortcuts (cyclomatic 19)
understand-anything-plugin/packages/dashboard/src/components/MobileDrawer.tsx	6.3	Mixed	Cyclomatic Complexity: MobileDrawer.MobileDrawer (cyclomatic 17)
understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx	6.3	Mixed	Cognitive Complexity: FilterPanel.FilterPanel (cognitive 16)

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

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

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

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

Could not be resolved — 10

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

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

What we checked — 83 dimensions across the health lenses

D1D2D3D4D5D6D8D9D10D11D12D13D14D15D16D17D19D23D26D28D29D30D34D35D36D37D43AC1AC2AC3AC4AC5AC6AC7AX10AX3AX4AX6GD1IC1M1M2M3M4P1P10P2P3P4P6PF3R1R10R11R2R3R4R6R7R8R9X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X26X27X28X29X3X30X5

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, 588 of 619 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	—	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a17814-1a0a-744e-9976-d7300882b2bb.

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.

D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — 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. `understand-anything-plugin/packages/core/src/languages/configs/batch.ts`, `understand-anything-plugin/packages/core/src/languages/configs/c.ts`, `understand-anything-plugin/packages/core/src/languages/configs/cpp.ts`, `understand-anything-plugin/packages/core/src/languages/configs/csharp.ts`, `understand-anything-plugin/packages/core/src/languages/configs/css.ts`, … (+52 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover 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, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, 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 (Package.swift, a Dockerfile) is simply not read here yet.
AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via Dockerfile (understand-anything-plugin/skills/understand/languages/dockerfile.md). docker build failed (exit 1) — 6 | - **Layer Caching**: Each instruction creates a layer; order instructions from least to most frequently changing for cache efficiency 7 | - **Base Images**: `FROM image:tag` selects the starting image; prefer slim/alpine variants for smaller images -------------------- ERROR: failed to solve: dockerfile parse error on line 5: unknown instruction: -; runtime evidence skipped.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 109 further occurrence(s) are not listed individually; the score already reflects all 149.
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. 210 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

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.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Prevented

103 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was symbol-evidence.collectSymbolEvidence::visit at 142. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being validate-incremental-symbols.validSupplement at 21 — they are counted neither in the figure above nor in this dimension's score.

symbol-evidence.collectSymbolEvidence::visit (cyclomatic 142)understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:98

symbol-scopes.buildSymbolScopes.scan (cyclomatic 78)understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts:88

merge-knowledge-graph.merge (cyclomatic 64)understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:120

GraphView.useLayerDetailTopology (cyclomatic 59)understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:393

validateIncrementalSymbols (cyclomatic 56)understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:314

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

What to do

Bring the 3 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with symbol-evidence.collectSymbolEvidence::visit (cyclomatic 142), symbol-scopes.buildSymbolScopes.scan (cyclomatic 78), merge-knowledge-graph.merge (cyclomatic 64). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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 Complexity2.0 / 10Critical✓ 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 2.0 / 10 · rule-coverage 100% · ceiling Prevented

152 method(s) exceeded the cognitive complexity threshold of 15; the worst was symbol-evidence.collectSymbolEvidence::visit at 177.

symbol-evidence.collectSymbolEvidence::visit (cognitive 177)understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:98

merge-batch-graphs.production_candidates (cognitive 130)understand-anything-plugin/skills/understand/merge-batch-graphs.py:405

merge-knowledge-graph.merge (cognitive 128)understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:120

symbol-scopes.buildSymbolScopes.scan (cognitive 116)understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts:88

validateIncrementalSymbols (cognitive 107)understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:314

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

What to do

Bring the 13 bodies over 60 down to 60 or less in Cognitive Complexity — start with symbol-evidence.collectSymbolEvidence::visit (cognitive 177), merge-batch-graphs.production_candidates (cognitive 130), merge-knowledge-graph.merge (cognitive 128). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 13 together lifts Cognitive Complexity from 2.0 to about 3.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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 Classes6.3 / 10Adequate✓ Tool-verified

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

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

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

39 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: App.DashboardContent · ×30understand-anything-plugin/packages/dashboard/src/App.tsx:274

FileTooLong: lib/large-repo-benchmark.mjs · ×9scripts/lib/large-repo-benchmark.mjs

What to do

Resolve the 30 FunctionTooLong finding(s) in God Classes — start with GraphView.tsx (3), App.tsx (2), schema.ts (2). — One of this dimension's main actionable groups (30 warning-level).
Resolve the 9 FileTooLong finding(s) in God Classes — start with large-repo-benchmark.mjs, GraphView.tsx, extract-import-map.mjs. — One of this dimension's main actionable groups (9 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.9 / 10Stronggated by 5 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.9 / 10 · rule-coverage 100% · ceiling Verified

5 duplicated block group(s) detected. Measured on part of this repository only: .ts, .tsx (91% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.

Duplicated block (16–18 lines × 2)understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:35

Duplicated block (15–17 lines × 2)understand-anything-plugin/skills/understand/merge-batch-graphs.py:482

Duplicated block (8 lines × 3)understand-anything-plugin/skills/understand-domain/extract-domain-context.py:384

Duplicated block (7 lines × 2)understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:206

Duplicated block (6 lines × 2)understand-anything-plugin/skills/understand/merge-batch-graphs.py:190

What to do

Resolve the 1 Duplicated block (16–18 lines × 2) finding(s) in Code Duplication — start with merge-knowledge-graph.py. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicated block (15–17 lines × 2) finding(s) in Code Duplication — start with merge-batch-graphs.py. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicated block (8 lines × 3) finding(s) in Code Duplication — start with extract-domain-context.py. — One of this dimension's main actionable groups (1 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?

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

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

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

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

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

8 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 8 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 32 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D8 · Code Coverage9.5 / 10Stronggated by 49 serious findings✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

Line coverage 64.8% — 49 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in understand-anything-plugin/packages/core/; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in understand-anything-plugin/packages/dashboard/).

Low coverage: understand-anything-plugin/packages/core/src/index.ts · ×49understand-anything-plugin/packages/core/src/index.ts:1

What to do

Resolve the 49 Low coverage finding(s) in Code Coverage — start with index.ts (3), benchmark-aggregations.mjs, benchmark-layout.mjs. — One of this dimension's main actionable groups (49 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

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

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

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

1616 test methods: 1616 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 1510 `it`/`test` case(s) across 86 test file(s) declaring at least one; its tier split is read from package names and paths only. The Python suite contributes 106 test function(s) across 3 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

10 skipped (10 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1510 tests.

Skipped (documented): (unnamed test) · ×10understand-anything-plugin/packages/core/src/__tests__/change-classifier.test.ts:146

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (787 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in understand-anything-plugin/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in understand-anything-plugin/packages/core/ (1014 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in understand-anything-plugin/packages/dashboard/ (107 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene8.8 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

13 outdated direct production npm dependency(ies) of 33 graded, 0 pinning defect(s), across 5 REDACTED (5 of them the product) and 2 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: eslintREDACTED:40

Deprecated: glob · ×3REDACTED:1869

Outdated (npm): @dagrejs/dagre · ×13

What to do

Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 of 33 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 33 production dependency(ies) this repository's committed lockfile resolves, across 5 product REDACTED manifest(s). Its 24 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots8.6 / 10Strong✓ 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 8.6 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts (4×186=744); understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs (12×53=636); understand-anything-plugin/skills/understand/prepare-incremental.mjs (15×42=630) Repeated repair below the complexity floor: understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts (9 of 11 changes were fixes)

Hotspot: understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts · ×8understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:49

Repeated repair: understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.tsunderstand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts:62

What to do

Resolve the 8 Hotspot finding(s) in Churn × Complexity Hotspots — start with symbol-evidence.ts, validate-incremental-symbols.mjs, prepare-incremental.mjs. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with tree-sitter-plugin.ts. — 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?

D16 · Bus Factor7.0 / 10Adequate✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

35 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts. Counted over 117 of the 215 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

Further sole-owners (lower concentration)

What to do

Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D17 · Explicit Debt10.0 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

2 deducted task-comment markers across 29790 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.

TodoComment · ×2understand-anything-plugin/packages/core/src/languages/configs/json-schema.ts:3

What to do

Resolve the 2 TodoComment finding(s) in Explicit Debt — start with json-schema.ts, kubernetes.ts. — One of this dimension's main actionable groups (2 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

No domain types leak across context boundaries (4 contexts).

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion6.0 / 10Adequate✓ Tool-verified

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

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

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

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

Projects may be oversized for their cohesion

What to do

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

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

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)2.4 / 10Critical✓ Tool-verified

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

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

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

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

18 finding(s): 0 critical, 17 high, 1 medium, 0 low. 9 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 60 file(s) — `understand-anything-plugin/packages/core/src/languages/configs/batch.ts` (line 14), `understand-anything-plugin/packages/core/src/languages/configs/c.ts` (line 27), `understand-anything-plugin/packages/core/src/languages/configs/cpp.ts` (line 29), `understand-anything-plugin/packages/core/src/languages/configs/csharp.ts` (line 29), `understand-anything-plugin/packages/core/src/languages/configs/css.ts` (line 14), … (+55 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

33 finding(s): 3 critical, 24 high, 4 medium, 2 low.

REDACTED

What to do

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

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

Do you agree with this assessment?

D34 · Knowledge Freshness9.3 / 10Adequategated by 2 critical findings✓ Tool-verified

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

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

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

8 of 117 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts. Counted over 117 of the 215 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×2understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:1

Orphaned file · ×6understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:1

Further orphaned files (smaller)

What to do

Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with swift-extractor.ts, scala-extractor.ts. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with kotlin-extractor.ts, FilterPanel.tsx, freshness.ts. — One of this dimension's main actionable groups (6 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ 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 0.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED

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

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 — start with REDACTED. — 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?

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged

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

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

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

Do you agree with this assessment?

AC2 · Forms & labels6.3 / 10Adequate✓ Tool-verified

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

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

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

A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — understand-anything-plugin/packages/dashboard/src/components/KeyboardShortcutsHelp.tsx:52, understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:129
This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:147, understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:169
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:150, understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:172
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×2) — understand-anything-plugin/packages/dashboard/src/components/SearchBar.tsx:103, understand-anything-plugin/packages/dashboard/src/components/TokenGate.tsx:52

What to do

Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.

Do you agree with this assessment?

AC3 · Page structure6.5 / 10Adequate✓ Tool-verified

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

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

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

No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — homepage/src/layouts/Layout.astro:10
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it. — understand-anything-plugin/packages/dashboard/index.html:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — understand-anything-plugin/packages/dashboard/src/components/LearnPanel.tsx:160

What to do

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Do you agree with this assessment?

AC4 · Keyboard semantics2.1 / 10Critical✓ Tool-verified

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

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

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

A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×8) — understand-anything-plugin/packages/dashboard/src/components/CustomNode.tsx:147, understand-anything-plugin/packages/dashboard/src/components/DomainClusterNode.tsx:24, understand-anything-plugin/packages/dashboard/src/components/FlowNode.tsx:23, …
This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — understand-anything-plugin/packages/dashboard/src/components/MobileDrawer.tsx:101
This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — understand-anything-plugin/packages/dashboard/src/components/OnboardingOverlay.tsx:51

What to do

Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

Do you agree with this assessment?

AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

Do you agree with this assessment?

AC6 · Visual & motion safety5.5 / 10Adequate✓ Tool-verified

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

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

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

<select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:150, understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:172
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×2) — understand-anything-plugin/packages/dashboard/src/components/SearchBar.tsx:103, understand-anything-plugin/packages/dashboard/src/components/TokenGate.tsx:52
`.animate-fade-slide-in` moves (`animation: fadeSlideIn 0.3s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — understand-anything-plugin/packages/dashboard/src/index.css:182
`.animate-slide-up` moves (`animation: slideUp 0.3s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — understand-anything-plugin/packages/dashboard/src/index.css:186

What to do

Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.

Do you agree with this assessment?

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

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

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

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

No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 48 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

Enforce accessibility in the toolchain: add eslint-plugin-jsx-a11y, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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

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

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

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs8.1 / 10Strong✓ Tool-verified

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

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

The guard above `return funcNode.text;` also returns `funcNode.text`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. (×2) — understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:497, understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:218
`main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — understand-anything-plugin/skills/understand/scan-project.mjs:695

What to do

Remove the dead code that still moves this score: delete dead if(false) branches and either do the real async work or drop the async keyword from fake-async functions.

Do you agree with this assessment?

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

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

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

What to do

Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 5 of 7 project(s) that lack one — worth up to 1.4 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 your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

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 accuracy8.0 / 10Strong✓ Tool-verified

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.

CONTRIBUTING.md names React 18, but the manifest declares `react` ^19.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:186

What to do

Reconcile the README with reality: CONTRIBUTING.md names React 18, but the manifest declares `react` ^19.0.0.

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?

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

P2 · Observability0.0 / 10Critical✓ Tool-verified

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

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

No logging call was found in the 210 Python, JavaScript/TypeScript production file(s) this check read across 5 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

Adopt pino (or winston) and log at meaningful points in the services you run.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 3467 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: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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

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

What to do

Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.

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?

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

`fs.existsSync` in `readGraphFreshness` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — understand-anything-plugin/packages/viewer/bin/viewer.mjs:252, understand-anything-plugin/packages/viewer/bin/viewer.mjs:264
`existsSync` in `loadTsConfigs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — understand-anything-plugin/skills/understand/extract-import-map.mjs:337
`existsSync` in `loadGoModules` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — understand-anything-plugin/skills/understand/extract-import-map.mjs:410
`existsSync` in `loadSwiftPackageTargets` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — understand-anything-plugin/skills/understand/extract-import-map.mjs:524
`existsSync` in `loadPhpAutoloads` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — understand-anything-plugin/skills/understand/extract-import-map.mjs:1613
`readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — understand-anything-plugin/skills/understand/extract-import-map.mjs:1977, understand-anything-plugin/skills/understand/extract-import-map.mjs:2062, understand-anything-plugin/skills/understand/extract-structure.mjs:71, …
`writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — understand-anything-plugin/skills/understand/extract-import-map.mjs:1994, understand-anything-plugin/skills/understand/extract-import-map.mjs:2143, understand-anything-plugin/skills/understand/extract-structure.mjs:150, …
`existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×6) — understand-anything-plugin/skills/understand/extract-import-map.mjs:2145, understand-anything-plugin/skills/understand/extract-structure.mjs:152, understand-anything-plugin/skills/understand/finalize-incremental.mjs:446, …
`realpathSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — understand-anything-plugin/skills/understand/finalize-incremental.mjs:384, understand-anything-plugin/skills/understand/prepare-incremental.mjs:478
`mkdirSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — understand-anything-plugin/skills/understand/prepare-incremental.mjs:481
`unlinkSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — understand-anything-plugin/skills/understand/prepare-incremental.mjs:691
`statSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — understand-anything-plugin/skills/understand/scan-project.mjs:753
`lstatSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — understand-anything-plugin/skills/understand/scan-project.mjs:807
`existsSync` in `validateIncrementalSymbols` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:377, understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:379

What to do

TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.

Do you agree with this assessment?

R1 · Type Safety8.9 / 10Strong✓ Tool-verified

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

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

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication8.0 / 10Strong✓ Tool-verified

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

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

8 duplicated blocks under understand-anything-plugin/packages/ have copies in at least two of the sibling directories core, dashboard, viewer — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — understand-anything-plugin/packages/core/src/staleness.ts:9
understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:14 · understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:23 — the two spans are one implementation copied and then locally edited — 1397 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:14
understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:144 · understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:120 — the two spans are one implementation copied and then locally edited — 851 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:144
understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts:85 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:93 — the two spans are one implementation copied and then locally edited — 694 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts:85
understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:81 · understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:104 — the two spans are one implementation copied and then locally edited — 497 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:81
understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:79 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:23 — the two spans are one implementation copied and then locally edited — 431 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:79
understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:201 · understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:253 — the two spans are one implementation copied and then locally edited — 258 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:201
understand-anything-plugin/packages/core/src/staleness.ts:9 · understand-anything-plugin/packages/dashboard/src/freshness.ts:1 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — understand-anything-plugin/packages/core/src/staleness.ts:9
understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:222 · understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:175 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:222
understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:258 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:258
understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts:147 · understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:165 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts:147
understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:122 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:139 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:122
understand-anything-plugin/packages/dashboard/vite.config.demo.ts:18 · REDACTED:311 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/dashboard/vite.config.demo.ts:18
understand-anything-plugin/skills/understand/extract-import-map.mjs:2140 · understand-anything-plugin/skills/understand/scan-project.mjs:867 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/skills/understand/extract-import-map.mjs:2140
understand-anything-plugin/packages/dashboard/src/App.tsx:733 · understand-anything-plugin/packages/dashboard/src/components/MobileLayout.tsx:209 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — understand-anything-plugin/packages/dashboard/src/App.tsx:733
understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:304 · understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:331 — 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. — understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:304
understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:431 · understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:474 — 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. — understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:431
understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts:74 · understand-anything-plugin/packages/core/src/plugins/parsers/markdown-parser.ts:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts:74
understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:215 · understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:248 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:215
understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:107 · understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:129 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:107
understand-anything-plugin/skills/understand/extract-import-map.mjs:295 · understand-anything-plugin/skills/understand/extract-import-map.mjs:368 · understand-anything-plugin/skills/understand/extract-import-map.mjs:510 · understand-anything-plugin/skills/understand/extract-import-map.mjs:1584 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/skills/understand/extract-import-map.mjs:295
understand-anything-plugin/packages/core/src/analyzer/graph-builder.ts:131 · understand-anything-plugin/packages/core/src/analyzer/graph-builder.ts:155 — 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. — understand-anything-plugin/packages/core/src/analyzer/graph-builder.ts:131
understand-anything-plugin/packages/core/src/persistence/index.ts:100 · understand-anything-plugin/packages/core/src/persistence/index.ts:177 — 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. — understand-anything-plugin/packages/core/src/persistence/index.ts:100
understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:497 · understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:437 — the two spans are one implementation copied and then locally edited — 102 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:497
understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:132 · understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:154 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:132
understand-anything-plugin/skills/understand/compute-batches.mjs:655 · understand-anything-plugin/skills/understand/extract-import-map.mjs:2151 · understand-anything-plugin/skills/understand/scan-project.mjs:879 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/skills/understand/compute-batches.mjs:655
understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:169 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:169 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:169
understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:13 · understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:13
understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:143 · understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:165 — 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. — understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:143
REDACTED:45 · understand-anything-plugin/packages/viewer/bin/viewer.mjs:96 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — REDACTED:45
understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:104 · understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:123 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:104
understand-anything-plugin/skills/understand/finalize-incremental.mjs:484 · understand-anything-plugin/skills/understand/prepare-incremental.mjs:723 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/skills/understand/finalize-incremental.mjs:484
understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:392 · understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:297 · understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:326 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:392
understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:247 · understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:337 — 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. — understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:247
understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:171 · understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:190 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:171
understand-anything-plugin/packages/dashboard/src/utils/layout.ts:27 · understand-anything-plugin/packages/dashboard/src/utils/layout.worker.ts:18 — the two spans are one implementation copied and then locally edited — 95 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — understand-anything-plugin/packages/dashboard/src/utils/layout.ts:27
understand-anything-plugin/skills/understand/extract-import-map.mjs:353 · understand-anything-plugin/skills/understand/extract-import-map.mjs:1629 — 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. — understand-anything-plugin/skills/understand/extract-import-map.mjs:353
understand-anything-plugin/packages/core/src/fingerprint.ts:181 · understand-anything-plugin/packages/core/src/fingerprint.ts:219 — 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. — understand-anything-plugin/packages/core/src/fingerprint.ts:181
understand-anything-plugin/packages/core/src/plugins/parsers/env-parser.ts:10 · understand-anything-plugin/packages/core/src/plugins/parsers/makefile-parser.ts:10 · understand-anything-plugin/packages/core/src/plugins/parsers/toml-parser.ts:10 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — understand-anything-plugin/packages/core/src/plugins/parsers/env-parser.ts:10
understand-anything-plugin/packages/core/src/schema.ts:672 · understand-anything-plugin/packages/core/src/schema.ts:693 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — understand-anything-plugin/packages/core/src/schema.ts:672

What to do

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

Do you agree with this assessment?

R11 · Import Boundaries8.0 / 10Strong✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

tests/skill/understand/test_extract_structure_outcomes.test.mjs:3 reaches past another workspace package's public entry into its internals with a relative path (../../../understand-anything-plugin/skills/understand/extract-structure-result.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/skill/understand/test_extract_structure_outcomes.test.mjs:3
tests/skill/understand/test_incremental_symbols.test.mjs:3 reaches past another workspace package's public entry into its internals with a relative path (../../../understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/skill/understand/test_incremental_symbols.test.mjs:3
tests/skill/understand/test_symbol_evidence_matrix.test.mjs:3 reaches past another workspace package's public entry into its internals with a relative path (../../../understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — tests/skill/understand/test_symbol_evidence_matrix.test.mjs:3
understand-anything-plugin/packages/dashboard/scripts/benchmark-layout.mjs:17 imports elkjs/lib/elk.bundled.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — understand-anything-plugin/packages/dashboard/scripts/benchmark-layout.mjs:17
understand-anything-plugin/packages/dashboard/src/utils/elk-layout.ts:1 imports elkjs/lib/elk.bundled.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — understand-anything-plugin/packages/dashboard/src/utils/elk-layout.ts:1

What to do

Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.

Do you agree with this assessment?

R2 · Cyclomatic Complexity6.0 / 10Adequate✓ Tool-verified

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

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

visit has cyclomatic complexity 149 and cognitive complexity 193; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:98
scan has cyclomatic complexity 81 and cognitive complexity 116; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts:88
validateIncrementalSymbols has cyclomatic complexity 40 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:314
main has cyclomatic complexity 37 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/prepare-incremental.mjs:476
DashboardContent has cyclomatic complexity 35 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/dashboard/src/App.tsx:274
buildResult has cyclomatic complexity 34 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/extract-structure-result.mjs:216
NodeInfo has cyclomatic complexity 33 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:278
ProjectOverview has cyclomatic complexity 33 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/dashboard/src/components/ProjectOverview.tsx:4
normalizeBatchOutput has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/core/src/analyzer/normalize-graph.ts:202
main has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/compute-batches.mjs:395
main has cyclomatic complexity 32 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/finalize-incremental.mjs:379
validateGraph has cyclomatic complexity 30 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/core/src/schema.ts:563
compareFingerprints has cyclomatic complexity 30 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/core/src/fingerprint.ts:142
processExportStatement has cyclomatic complexity 29 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:385
normalizeJsonc has cyclomatic complexity 29 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/extract-import-map.mjs:210
generateHeuristicTour has cyclomatic complexity 29 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/packages/core/src/analyzer/tour-generator.ts:135
compareFileSymbols has cyclomatic complexity 29 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:200
main has cyclomatic complexity 28 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/extract-import-map.mjs:1970
resolvePythonImport has cyclomatic complexity 28 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/extract-import-map.mjs:948
main has cyclomatic complexity 28 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — understand-anything-plugin/skills/understand/scan-project.mjs:695

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files5.9 / 10Adequate✓ Tool-verified

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

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

understand-anything-plugin/skills/understand/extract-import-map.mjs has 2022 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/skills/understand/extract-import-map.mjs:1
understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx has 1485 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1
understand-anything-plugin/skills/understand/scan-project.mjs has 855 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/skills/understand/scan-project.mjs:1
understand-anything-plugin/packages/dashboard/src/App.tsx has 733 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/dashboard/src/App.tsx:1
understand-anything-plugin/packages/dashboard/src/store.ts has 714 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/dashboard/src/store.ts:1
understand-anything-plugin/skills/understand/prepare-incremental.mjs has 701 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/skills/understand/prepare-incremental.mjs:1
understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts has 685 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:1
understand-anything-plugin/packages/core/src/schema.ts has 665 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/schema.ts:1
understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:1
understand-anything-plugin/skills/understand/compute-batches.mjs has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/skills/understand/compute-batches.mjs:1
understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:1
understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:1
understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:1
understand-anything-plugin/skills/understand/finalize-incremental.mjs has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/skills/understand/finalize-incremental.mjs:1
understand-anything-plugin/packages/core/src/staleness.ts has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/staleness.ts:1
understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:1
understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts has 454 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:1
understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts has 449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:1
understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:1
understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:1
understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:1

What to do

Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.

Do you agree with this assessment?

R4 · Test Coverage7.1 / 10Strong✓ Tool-verified

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

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

REDACTED declares environment "node", and no package here declares a DOM implementation (jsdom / happy-dom), a component testing library or a browser runner — so none of the 27 unreached component module(s) can be tested as written, however the suite is authored: understand-anything-plugin/packages/dashboard/src/App.tsx, understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx, understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx, understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx, understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx, understand-anything-plugin/packages/dashboard/src/components/DomainGraphView.tsx and 21 more. Add a DOM environment and a component testing library (for example jsdom + @testing-library, or the runner's browser mode), then test the components. Reported once because these files share one cause, not one omission each. — REDACTED:1
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×14) — understand-anything-plugin/skills/understand/prepare-incremental.mjs:1, understand-anything-plugin/skills/understand/finalize-incremental.mjs:1, scripts/generate-large-graph.mjs:1, …

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

Do you agree with this assessment?

R7 · Dead Code9.7 / 10Exemplary✓ Tool-verified

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

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

1 file(s) (~7 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — homepage
2 file(s) (~425 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: understand-anything-plugin/packages/viewer/bin/viewer.mjs imports './dist/staleness.js', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — understand-anything-plugin/packages/viewer
Unreachable from the 91 application, 24 tooling and 89 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (91 application, 24 tooling, 89 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — understand-anything-plugin/packages/dashboard/src/components/NodeTooltip.tsx, understand-anything-plugin/hooks/post-tool-use-auto-update.mjs, understand-anything-plugin/packages/dashboard/src/utils/layout.worker.ts
Nothing ultimately consumes this binding: its only referrer is the re-export in understand-anything-plugin/packages/core/src/plugins/extractors/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in understand-anything-plugin/packages/core/src/plugins/extractors/index.ts in the same commit, or the barrel will import a name that no longer exists. — understand-anything-plugin/packages/core/src/plugins/extractors/base-extractor.ts:46
Nothing imports this binding — it is safe to review for removal. (×2) — understand-anything-plugin/packages/dashboard/src/locales/index.ts:38, understand-anything-plugin/packages/dashboard/src/utils/layout.ts:20

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene9.5 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

Declared in understand-anything-plugin/packages/dashboard/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`get` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — understand-anything-plugin/packages/core/src/figma/source/api-source.ts:25

What to do

Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen.

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

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling5.5 / 10Adequate✓ Tool-verified

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

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

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×9) — understand-anything-plugin/skills/understand-figma/figma-scan.mjs:52, understand-anything-plugin/skills/understand-figma/figma-scan.mjs:102, understand-anything-plugin/packages/dashboard/src/App.tsx:159, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×4) — understand-anything-plugin/packages/dashboard/src/App.tsx:135, understand-anything-plugin/packages/dashboard/src/App.tsx:141, understand-anything-plugin/packages/dashboard/src/App.tsx:239, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — understand-anything-plugin/hooks/post-tool-use-auto-update.mjs:29

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X5 · Nullable reference types8.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

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

4/5 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~1.1 `!` null assertions per 1k TypeScript source lines — 32 assertion(s) across the 29863 source line(s) of the 188 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts (5), understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts (5), understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

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

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC4 · Keyboard semantics	2.1.1, 2.4.3	Partial signal
AC5 · ARIA correctness	4.1.2	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

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

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	58%	Adequate — gated by D1, D2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	92%	Exemplary	Strongest area.
Maturity	61%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	42%	Weak — gated by P2, P3	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	54%	Adequate — gated by D29, D30, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	49%	Weak — gated by AC4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	60%	Adequate	Acceptable, with room to improve.

Unscored — 2 check(s) recorded observations but carry no score

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

X10 Duplicated predicate — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not evidenced — 1 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.

P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control

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

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

AX1 Captive dependencies — not 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
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — 6 | - **Layer Caching**: Each instruction creates a layer; order instructions from least to most frequently changing for cache efficiency 7 | - **Base Images**: `FROM image:tag` selects the starting image; prefer slim/alpine variants for smaller images -------------------- ERROR: failed to solve: dockerfile parse error on line 5: unknown instruction: -; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, Python, TypeScript not measured.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .ts, .tsx, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.mjs,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
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) — 57 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
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
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 181 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript and Python runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — Not assessed: 210 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — 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
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 62 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×24

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×8

Click handler on a non-interactive <div> understand-anything-plugin/packages/dashboard/src/components/CustomNode.tsx:147 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> understand-anything-plugin/packages/dashboard/src/components/DomainClusterNode.tsx:24 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> understand-anything-plugin/packages/dashboard/src/components/FlowNode.tsx:23 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> understand-anything-plugin/packages/dashboard/src/components/LayerClusterNode.tsx:33 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:499 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:540 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> understand-anything-plugin/packages/dashboard/src/components/PortalNode.tsx:22 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> understand-anything-plugin/packages/dashboard/src/components/StepNode.tsx:22 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.

AC2 · Forms & labels · <button> with no accessible text · ×2

<button> with no accessible text understand-anything-plugin/packages/dashboard/src/components/KeyboardShortcutsHelp.tsx:52 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:129 — A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).

AC2 · Forms & labels · <label> that labels no control · ×2

<label> that labels no control understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:147 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.
<label> that labels no control understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:169 — This <label> has no htmlFor and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label htmlFor="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id.

AC2 · Forms & labels · <select> without a programmatic label · ×2

<select> without a programmatic label understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:150 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<select> without a programmatic label understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:172 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

AC2 · Forms & labels · <input> without a programmatic label · ×2

<input> without a programmatic label understand-anything-plugin/packages/dashboard/src/components/SearchBar.tsx:103 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label understand-anything-plugin/packages/dashboard/src/components/TokenGate.tsx:52 — This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×2

REDACTED
REDACTED

D34 · Knowledge Freshness · Orphaned knowledge · ×2

Orphaned knowledge understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:1 — No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.

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

REDACTED

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

REDACTED

D30 · Dependency Vulnerabilities · Critical vulnerability · ×1

REDACTED

Serious — 483 finding(s)

D8 · Code Coverage · Low coverage · ×49

Low coverage: understand-anything-plugin/packages/core/src/index.ts understand-anything-plugin/packages/core/src/index.ts:1 — 0.0% line coverage (0/22).
Low coverage: understand-anything-plugin/packages/core/src/figma/index.ts understand-anything-plugin/packages/core/src/figma/index.ts:1 — 0.0% line coverage (0/5).
Low coverage: understand-anything-plugin/packages/core/src/languages/index.ts understand-anything-plugin/packages/core/src/languages/index.ts:1 — 0.0% line coverage (0/5).
Low coverage: understand-anything-plugin/packages/dashboard/scripts/benchmark-aggregations.mjs understand-anything-plugin/packages/dashboard/scripts/benchmark-aggregations.mjs:1 — 0.0% line coverage (0/91).
Low coverage: understand-anything-plugin/packages/dashboard/scripts/benchmark-layout.mjs understand-anything-plugin/packages/dashboard/scripts/benchmark-layout.mjs:1 — 0.0% line coverage (0/72).
Low coverage: understand-anything-plugin/packages/dashboard/src/App.tsx understand-anything-plugin/packages/dashboard/src/App.tsx:1 — 0.0% line coverage (0/645).
Low coverage: understand-anything-plugin/packages/dashboard/src/main.tsx understand-anything-plugin/packages/dashboard/src/main.tsx:1 — 0.0% line coverage (0/9).
Low coverage: understand-anything-plugin/packages/dashboard/src/store.ts understand-anything-plugin/packages/dashboard/src/store.ts:1 — 48.1% line coverage (248/516).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/Breadcrumb.tsx understand-anything-plugin/packages/dashboard/src/components/Breadcrumb.tsx:1 — 6.3% line coverage (2/32).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx:1 — 0.0% line coverage (0/281).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/ContainerNode.tsx understand-anything-plugin/packages/dashboard/src/components/ContainerNode.tsx:1 — 7.0% line coverage (5/71).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/CustomNode.tsx understand-anything-plugin/packages/dashboard/src/components/CustomNode.tsx:1 — 43.9% line coverage (68/155).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/DiffToggle.tsx understand-anything-plugin/packages/dashboard/src/components/DiffToggle.tsx:1 — 0.0% line coverage (0/59).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/DomainClusterNode.tsx understand-anything-plugin/packages/dashboard/src/components/DomainClusterNode.tsx:1 — 0.0% line coverage (0/44).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/DomainGraphView.tsx understand-anything-plugin/packages/dashboard/src/components/DomainGraphView.tsx:1 — 0.0% line coverage (0/219).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx:1 — 0.0% line coverage (0/235).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/FileExplorer.tsx understand-anything-plugin/packages/dashboard/src/components/FileExplorer.tsx:1 — 0.0% line coverage (0/171).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:1 — 0.0% line coverage (0/186).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/FlowNode.tsx understand-anything-plugin/packages/dashboard/src/components/FlowNode.tsx:1 — 0.0% line coverage (0/33).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1 — 4.1% line coverage (48/1177).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/KeyboardShortcutsHelp.tsx understand-anything-plugin/packages/dashboard/src/components/KeyboardShortcutsHelp.tsx:1 — 0.0% line coverage (0/82).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx:1 — 0.0% line coverage (0/329).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/LayerClusterNode.tsx understand-anything-plugin/packages/dashboard/src/components/LayerClusterNode.tsx:1 — 12.9% line coverage (9/70).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/LayerLegend.tsx understand-anything-plugin/packages/dashboard/src/components/LayerLegend.tsx:1 — 20.0% line coverage (12/60).
Low coverage: understand-anything-plugin/packages/dashboard/src/components/LearnPanel.tsx understand-anything-plugin/packages/dashboard/src/components/LearnPanel.tsx:1 — 0.0% line coverage (0/180).
+ 24 more in this group — see findings.md.

D3 · God Classes · FunctionTooLong · ×30

FunctionTooLong: App.DashboardContent understand-anything-plugin/packages/dashboard/src/App.tsx:274 — FunctionTooLong — DashboardContent runs 411 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 311 over it, 4.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: store.useDashboardStore understand-anything-plugin/packages/dashboard/src/store.ts:290 — FunctionTooLong — useDashboardStore runs 378 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 278 over it, 3.78× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: GraphView.useLayerDetailTopology understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:393 — FunctionTooLong — useLayerDetailTopology runs 361 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 261 over it, 3.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: large-repo-benchmark.runBenchmark scripts/lib/large-repo-benchmark.mjs:1671 — FunctionTooLong — runBenchmark runs 313 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 213 over it, 3.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PathFinderModal.PathFinderModal understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:9 — FunctionTooLong — PathFinderModal runs 243 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 143 over it, 2.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: NodeInfo.NodeInfo understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:278 — FunctionTooLong — NodeInfo runs 229 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 129 over it, 2.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: GraphView.useLayerDetailGraph understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:982 — FunctionTooLong — useLayerDetailGraph runs 228 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: KnowledgeGraphView.KnowledgeGraphViewInner understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx:119 — FunctionTooLong — KnowledgeGraphViewInner runs 223 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 123 over it, 2.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MobileDrawer.MobileDrawer understand-anything-plugin/packages/dashboard/src/components/MobileDrawer.tsx:34 — FunctionTooLong — MobileDrawer runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.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.
FunctionTooLong: ExportMenu.ExportMenu understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx:22 — FunctionTooLong — ExportMenu runs 198 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 98 over it, 1.98× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: GraphView.GraphViewInner understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1321 — FunctionTooLong — GraphViewInner runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: symbol-evidence.collectSymbolEvidence understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:49 — FunctionTooLong — collectSymbolEvidence runs 194 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: CodeViewer.CodeViewer understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx:121 — FunctionTooLong — CodeViewer runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: LearnPanel.LearnPanel understand-anything-plugin/packages/dashboard/src/components/LearnPanel.tsx:6 — FunctionTooLong — LearnPanel runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: prepare-incremental.main understand-anything-plugin/skills/understand/prepare-incremental.mjs:476 — FunctionTooLong — main runs 185 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 85 over it, 1.85× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: WarningBanner.WarningBanner understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:45 — FunctionTooLong — WarningBanner runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: FilterPanel.FilterPanel understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:6 — FunctionTooLong — FilterPanel runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ProjectOverview.ProjectOverview understand-anything-plugin/packages/dashboard/src/components/ProjectOverview.tsx:4 — FunctionTooLong — ProjectOverview runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MobileLayout.MobileLayout understand-anything-plugin/packages/dashboard/src/components/MobileLayout.tsx:34 — FunctionTooLong — MobileLayout runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: compute-batches.main understand-anything-plugin/skills/understand/compute-batches.mjs:395 — FunctionTooLong — main runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ThemePicker.ThemePicker understand-anything-plugin/packages/dashboard/src/components/ThemePicker.tsx:6 — FunctionTooLong — ThemePicker runs 151 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 51 over it, 1.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: symbol-scopes.buildSymbolScopes understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts:39 — FunctionTooLong — buildSymbolScopes runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: SearchBar.SearchBar understand-anything-plugin/packages/dashboard/src/components/SearchBar.tsx:24 — FunctionTooLong — SearchBar runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: scan-project.main understand-anything-plugin/skills/understand/scan-project.mjs:695 — FunctionTooLong — main runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: validate-incremental-symbols.validateIncrementalSymbols understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:314 — FunctionTooLong — validateIncrementalSymbols runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× 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.
+ 5 more in this group — see findings.md.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×28

Sync-over-async blocking understand-anything-plugin/packages/viewer/bin/viewer.mjs:252 — `fs.existsSync` in `readGraphFreshness` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/packages/viewer/bin/viewer.mjs:264 — `fs.existsSync` in `readGraphFreshness` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:337 — `existsSync` in `loadTsConfigs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:410 — `existsSync` in `loadGoModules` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:524 — `existsSync` in `loadSwiftPackageTargets` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:1613 — `existsSync` in `loadPhpAutoloads` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:1977 — `readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:1994 — `writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:2062 — `readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:2143 — `writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-import-map.mjs:2145 — `existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-structure.mjs:71 — `readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-structure.mjs:103 — `readFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-structure.mjs:150 — `writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/extract-structure.mjs:152 — `existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/finalize-incremental.mjs:384 — `realpathSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/finalize-incremental.mjs:446 — `existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/finalize-incremental.mjs:449 — `existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/prepare-incremental.mjs:478 — `realpathSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/prepare-incremental.mjs:481 — `mkdirSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/prepare-incremental.mjs:691 — `unlinkSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs:747 — `existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs:753 — `statSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs:807 — `lstatSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking understand-anything-plugin/skills/understand/scan-project.mjs:870 — `writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
+ 3 more in this group — see findings.md.

R4 · Test Coverage · No test reaches this file · ×14

No test reaches this file understand-anything-plugin/skills/understand/prepare-incremental.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/skills/understand/finalize-incremental.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file scripts/generate-large-graph.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/skills/understand-figma/figma-scan.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/skills/understand/build-fingerprints.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/packages/dashboard/src/hooks/useKeyboardShortcuts.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/skills/understand/generate-ignore.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/hooks/post-tool-use-auto-update.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/packages/dashboard/src/utils/layout.worker.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/skills/understand-figma/figma-merge.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/packages/viewer/build.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/packages/dashboard/src/utils/force-layout.worker.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file understand-anything-plugin/packages/dashboard/src/hooks/useIsMobile.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.

X3 · Exception handling · Swallowed exception (empty catch) · ×13

Swallowed exception (empty catch) understand-anything-plugin/skills/understand-figma/figma-scan.mjs:52 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) understand-anything-plugin/skills/understand-figma/figma-scan.mjs:102 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx:135 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx:141 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx:159 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx:239 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/App.tsx:257 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) understand-anything-plugin/packages/dashboard/src/themes/ThemeContext.tsx:44 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts:163 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/lib/large-repo-benchmark.mjs:159 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/lib/large-repo-benchmark.mjs:385 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/lib/large-repo-benchmark.mjs:400 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) scripts/lib/large-repo-benchmark.mjs:566 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.

D3 · God Classes · FileTooLong · ×9

FileTooLong: lib/large-repo-benchmark.mjs scripts/lib/large-repo-benchmark.mjs — FileTooLong — 1572 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1072 over it, 3.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: components/GraphView.tsx understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx — FileTooLong — 1066 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 566 over it, 2.13× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: understand/extract-import-map.mjs understand-anything-plugin/skills/understand/extract-import-map.mjs — FileTooLong — 991 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 491 over it, 1.98× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: understand/merge-batch-graphs.py understand-anything-plugin/skills/understand/merge-batch-graphs.py — FileTooLong — 837 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 337 over it, 1.67× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/App.tsx understand-anything-plugin/packages/dashboard/src/App.tsx — FileTooLong — 611 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: DashboardContent (274-771). The bar is 500 significant lines; this is 111 over it, 1.22× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: src/store.ts understand-anything-plugin/packages/dashboard/src/store.ts — FileTooLong — 564 significant lines (blank, comment-only and punctuation-only lines excluded), about 67% of them inside a single declaration: useDashboardStore (290-796). The bar is 500 significant lines; this is 64 over it, 1.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: understand/prepare-incremental.mjs understand-anything-plugin/skills/understand/prepare-incremental.mjs — FileTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 46 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/schema.ts understand-anything-plugin/packages/core/src/schema.ts — FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 14 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: extractors/swift-extractor.ts understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts — FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), about 68% of them inside a single declaration: SwiftExtractor (268-722). The bar is 500 significant lines; this is 12 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.

D15 · Churn × Complexity Hotspots · Hotspot · ×8

Hotspot: understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:49 — understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 186 in symbol-evidence.collectSymbolEvidence at line 49. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts`: 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: understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:314 — understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in validate-incremental-symbols.validateIncrementalSymbols at line 314. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs`: 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: understand-anything-plugin/skills/understand/prepare-incremental.mjs understand-anything-plugin/skills/understand/prepare-incremental.mjs:476 — understand-anything-plugin/skills/understand/prepare-incremental.mjs changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in prepare-incremental.main at line 476. 14 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/skills/understand/prepare-incremental.mjs`: 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: understand-anything-plugin/skills/understand/merge-batch-graphs.py understand-anything-plugin/skills/understand/merge-batch-graphs.py:808 — understand-anything-plugin/skills/understand/merge-batch-graphs.py changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in merge-batch-graphs.merge_and_normalize at line 808. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/skills/understand/merge-batch-graphs.py`: 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: understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs:17 — understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in prepare-symbol-retry.main at line 17. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs`: 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: understand-anything-plugin/skills/understand/extract-import-map.mjs understand-anything-plugin/skills/understand/extract-import-map.mjs:1970 — understand-anything-plugin/skills/understand/extract-import-map.mjs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in extract-import-map.main at line 1970. 5 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/skills/understand/extract-import-map.mjs`: 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: understand-anything-plugin/skills/understand/finalize-incremental.mjs understand-anything-plugin/skills/understand/finalize-incremental.mjs:379 — understand-anything-plugin/skills/understand/finalize-incremental.mjs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in finalize-incremental.main at line 379. 6 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/skills/understand/finalize-incremental.mjs`: 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: understand-anything-plugin/packages/core/src/fingerprint.ts understand-anything-plugin/packages/core/src/fingerprint.ts:142 — understand-anything-plugin/packages/core/src/fingerprint.ts changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in fingerprint.compareFingerprints at line 142. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/packages/core/src/fingerprint.ts`: 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.

R11 · Import Boundaries · Boundary violation [package · ×5

Boundary violation [package:test-cross-package-internals] tests/skill/understand/test_extract_structure_outcomes.test.mjs:3 — tests/skill/understand/test_extract_structure_outcomes.test.mjs:3 reaches past another workspace package's public entry into its internals with a relative path (../../../understand-anything-plugin/skills/understand/extract-structure-result.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/skill/understand/test_incremental_symbols.test.mjs:3 — tests/skill/understand/test_incremental_symbols.test.mjs:3 reaches past another workspace package's public entry into its internals with a relative path (../../../understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] tests/skill/understand/test_symbol_evidence_matrix.test.mjs:3 — tests/skill/understand/test_symbol_evidence_matrix.test.mjs:3 reaches past another workspace package's public entry into its internals with a relative path (../../../understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:third-party-deep-import] understand-anything-plugin/packages/dashboard/scripts/benchmark-layout.mjs:17 — understand-anything-plugin/packages/dashboard/scripts/benchmark-layout.mjs:17 imports elkjs/lib/elk.bundled.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] understand-anything-plugin/packages/dashboard/src/utils/elk-layout.ts:1 — understand-anything-plugin/packages/dashboard/src/utils/elk-layout.ts:1 imports elkjs/lib/elk.bundled.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.

AC6 · Visual & motion safety · Focus outline removed inline · ×4

Focus outline removed inline understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:150 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:172 — <select> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline understand-anything-plugin/packages/dashboard/src/components/SearchBar.tsx:103 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline understand-anything-plugin/packages/dashboard/src/components/TokenGate.tsx:52 — <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).

D30 · Dependency Vulnerabilities · Medium CVE · ×4

REDACTED
REDACTED
REDACTED
REDACTED

R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×4

Duplicated block (29 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts:147 — understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts:147 · understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:165 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (29 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:122 — understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:122 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:139 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (29 lines × 2 locations) understand-anything-plugin/packages/dashboard/vite.config.demo.ts:18 — understand-anything-plugin/packages/dashboard/vite.config.demo.ts:18 · REDACTED:311 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (29 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs:2140 — understand-anything-plugin/skills/understand/extract-import-map.mjs:2140 · understand-anything-plugin/skills/understand/scan-project.mjs:867 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×4

Duplicated block (20 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:169 — understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:169 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:169 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:13 — understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:13 · understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:143 — understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:143 · understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:165 — 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 (20 lines × 2 locations) REDACTED:45 — REDACTED:45 · understand-anything-plugin/packages/viewer/bin/viewer.mjs:96 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

R10 · Code Duplication · Duplicated block (21 lines × 2 locations) · ×3

Duplicated block (21 lines × 2 locations) understand-anything-plugin/packages/core/src/analyzer/graph-builder.ts:131 — understand-anything-plugin/packages/core/src/analyzer/graph-builder.ts:131 · understand-anything-plugin/packages/core/src/analyzer/graph-builder.ts:155 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2 locations) understand-anything-plugin/packages/core/src/persistence/index.ts:100 — understand-anything-plugin/packages/core/src/persistence/index.ts:100 · understand-anything-plugin/packages/core/src/persistence/index.ts:177 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:132 — understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:132 · understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:154 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

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

Duplicated block (17 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:247 — understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:247 · understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:337 — 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 (17 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:171 — understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:171 · understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:190 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs:353 — understand-anything-plugin/skills/understand/extract-import-map.mjs:353 · understand-anything-plugin/skills/understand/extract-import-map.mjs:1629 — 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.

AC3 · Page structure · Page without a main landmark · ×2

Page without a main landmark homepage/src/layouts/Layout.astro:10 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark understand-anything-plugin/packages/dashboard/index.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="root">, so there is no content here to wrap — render the <main> from the component mounted into it.

AC4 · Keyboard semantics · Modal dialog does not manage focus · ×2

Modal dialog does not manage focus understand-anything-plugin/packages/dashboard/src/components/MobileDrawer.tsx:101 — This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus understand-anything-plugin/packages/dashboard/src/components/OnboardingOverlay.tsx:51 — This <div role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.

AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×2

Animation without a prefers-reduced-motion guard understand-anything-plugin/packages/dashboard/src/index.css:182 — `.animate-fade-slide-in` moves (`animation: fadeSlideIn 0.3s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard understand-anything-plugin/packages/dashboard/src/index.css:186 — `.animate-slide-up` moves (`animation: slideUp 0.3s ease-out forwards`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.

D17 · Explicit Debt · TodoComment · ×2

TodoComment understand-anything-plugin/packages/core/src/languages/configs/json-schema.ts:3 — // TODO: JSON Schema files have no unique extension — *.schema.json files will match — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment understand-anything-plugin/packages/core/src/languages/configs/kubernetes.ts:3 — // TODO: Kubernetes manifests are YAML files with no unique extension or filename. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

IC1 · Incompleteness & stubs · Guard cannot change the result · ×2

Guard cannot change the result — returns what the code already falls through to understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:497 — The guard above `return funcNode.text;` also returns `funcNode.text`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Guard cannot change the result — returns what the code already falls through to understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:218 — The guard above `return funcNode.text;` also returns `funcNode.text`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.

R10 · Code Duplication · Duplicated block (37 lines × 2 locations) · ×2

Duplicated block (37 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:222 — understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:222 · understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:175 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (37 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:258 — understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:258 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:296 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×2

Duplicated block (22 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:215 — understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:215 · understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:248 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (22 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:107 — understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:107 · understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:129 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×2

Duplicated block (19 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:104 — understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:104 · understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:123 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (19 lines × 2 locations) understand-anything-plugin/skills/understand/finalize-incremental.mjs:484 — understand-anything-plugin/skills/understand/finalize-incremental.mjs:484 · understand-anything-plugin/skills/understand/prepare-incremental.mjs:723 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×2

Duplicated block (16 lines × 2 locations) understand-anything-plugin/packages/core/src/fingerprint.ts:181 — understand-anything-plugin/packages/core/src/fingerprint.ts:181 · understand-anything-plugin/packages/core/src/fingerprint.ts:219 — 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 (16 lines × 2 locations) understand-anything-plugin/packages/core/src/schema.ts:672 — understand-anything-plugin/packages/core/src/schema.ts:672 · understand-anything-plugin/packages/core/src/schema.ts:693 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

AC3 · Page structure · Heading level jumps from h2 to h4 · ×1

Heading level jumps from h2 to h4 understand-anything-plugin/packages/dashboard/src/components/LearnPanel.tsx:160 — Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-jsx-a11y) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 48 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D1 · Cyclomatic Complexity · symbol-evidence.collectSymbolEvidence · ×1

symbol-evidence.collectSymbolEvidence::visit (cyclomatic 142) understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:98 — symbol-evidence.collectSymbolEvidence::visit has cyclomatic complexity 142 (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 · symbol-scopes.buildSymbolScopes.scan (cyclomatic 78) · ×1

symbol-scopes.buildSymbolScopes.scan (cyclomatic 78) understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts:88 — symbol-scopes.buildSymbolScopes.scan has cyclomatic complexity 78 (threshold 15). Of this number, 77 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · merge-knowledge-graph.merge (cyclomatic 64) · ×1

merge-knowledge-graph.merge (cyclomatic 64) understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:120 — merge-knowledge-graph.merge has cyclomatic complexity 64 (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 · GraphView.useLayerDetailTopology (cyclomatic 59) · ×1

GraphView.useLayerDetailTopology (cyclomatic 59) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:393 — GraphView.useLayerDetailTopology has cyclomatic complexity 59 (threshold 15). Most of this is not in the body itself: 1 of the 59 points is its own statement and the rest belongs to 15 function literals inside it that branch (lines 428, 824, 895, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · validateIncrementalSymbols (cyclomatic 56) · ×1

validateIncrementalSymbols (cyclomatic 56) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:314 — validateIncrementalSymbols has cyclomatic complexity 56 (threshold 15). Of this number, 40 points are the body's own statements and 16 belong to 27 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · merge-batch-graphs.production_candidates (cyclomatic 54) · ×1

merge-batch-graphs.production_candidates (cyclomatic 54) understand-anything-plugin/skills/understand/merge-batch-graphs.py:405 — merge-batch-graphs.production_candidates has cyclomatic complexity 54 (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 · App.DashboardContent (cyclomatic 52) · ×1

App.DashboardContent (cyclomatic 52) understand-anything-plugin/packages/dashboard/src/App.tsx:274 — App.DashboardContent has cyclomatic complexity 52 (threshold 15). Of this number, 34 points are the body's own statements and 18 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · merge-subdomain-graphs.merge_graphs (cyclomatic 50) · ×1

merge-subdomain-graphs.merge_graphs (cyclomatic 50) understand-anything-plugin/skills/understand/merge-subdomain-graphs.py:66 — merge-subdomain-graphs.merge_graphs has cyclomatic complexity 50 (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 · store.useDashboardStore (cyclomatic 47) · ×1

store.useDashboardStore (cyclomatic 47) understand-anything-plugin/packages/dashboard/src/store.ts:290 — store.useDashboardStore has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 1 of the 47 points is its own statement and the rest belongs to 16 function literals inside it that branch (lines 639, 366, 414, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · parse-knowledge-base.parse_wiki (cyclomatic 46) · ×1

parse-knowledge-base.parse_wiki (cyclomatic 46) understand-anything-plugin/skills/understand-knowledge/parse-knowledge-base.py:323 — parse-knowledge-base.parse_wiki has cyclomatic complexity 46 (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 · main (cyclomatic 45) · ×1

main (cyclomatic 45) understand-anything-plugin/skills/understand/compute-batches.mjs:395 — main has cyclomatic complexity 45 (threshold 15). Of this number, 32 points are the body's own statements and 13 belong to 16 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · large-repo-benchmark.summarizeStructureOutput (cyclomatic 44) · ×1

large-repo-benchmark.summarizeStructureOutput (cyclomatic 44) scripts/lib/large-repo-benchmark.mjs:1257 — large-repo-benchmark.summarizeStructureOutput has cyclomatic complexity 44 (threshold 15). Of this number, 43 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · merge-batch-graphs.merge_and_normalize (cyclomatic 44) · ×1

merge-batch-graphs.merge_and_normalize (cyclomatic 44) understand-anything-plugin/skills/understand/merge-batch-graphs.py:808 — merge-batch-graphs.merge_and_normalize has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · main (cyclomatic 44) · ×1

main (cyclomatic 44) understand-anything-plugin/skills/understand/prepare-incremental.mjs:476 — main has cyclomatic complexity 44 (threshold 15). Of this number, 37 points are the body's own statements and 7 belong to 14 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · buildResult (cyclomatic 41) · ×1

buildResult (cyclomatic 41) understand-anything-plugin/skills/understand/extract-structure-result.mjs:216 — buildResult has cyclomatic complexity 41 (threshold 15). Of this number, 34 points are the body's own statements and 7 belong to 10 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · GraphView.GraphViewInner (cyclomatic 39) · ×1

GraphView.GraphViewInner (cyclomatic 39) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1321 — GraphView.GraphViewInner has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 10 of the 39 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 1431, 1472, 1418, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · validate-incremental-symbols.compareFileSymbols (cyclomatic 39) · ×1

validate-incremental-symbols.compareFileSymbols (cyclomatic 39) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:200 — validate-incremental-symbols.compareFileSymbols has cyclomatic complexity 39 (threshold 15). Of this number, 32 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · main (cyclomatic 39) · ×1

main (cyclomatic 39) understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs:17 — main has cyclomatic complexity 39 (threshold 15). Of this number, 26 points are the body's own statements and 13 belong to 31 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · KnowledgeGraphView.KnowledgeGraphViewInner (cyclomatic 38) · ×1

KnowledgeGraphView.KnowledgeGraphViewInner (cyclomatic 38) understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx:119 — KnowledgeGraphView.KnowledgeGraphViewInner has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 8 of the 38 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 307, 254, 266, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · NodeInfo.NodeInfo (cyclomatic 38) · ×1

NodeInfo.NodeInfo (cyclomatic 38) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:278 — NodeInfo.NodeInfo has cyclomatic complexity 38 (threshold 15). Of this number, 31 points are the body's own statements and 7 belong to 6 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · merge-batch-graphs.main (cyclomatic 35) · ×1

merge-batch-graphs.main (cyclomatic 35) understand-anything-plugin/skills/understand/merge-batch-graphs.py:1154 — merge-batch-graphs.main has cyclomatic complexity 35 (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 · main (cyclomatic 32) · ×1

main (cyclomatic 32) understand-anything-plugin/skills/understand/finalize-incremental.mjs:379 — main 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 · schema.autoFixGraph (cyclomatic 31) · ×1

schema.autoFixGraph (cyclomatic 31) understand-anything-plugin/packages/core/src/schema.ts:236 — schema.autoFixGraph has cyclomatic complexity 31 (threshold 15). Of this number, 16 points are the body's own statements and 15 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · fingerprint.compareFingerprints (cyclomatic 30) · ×1

fingerprint.compareFingerprints (cyclomatic 30) understand-anything-plugin/packages/core/src/fingerprint.ts:142 — fingerprint.compareFingerprints 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 · CodeViewer.CodeViewer (cyclomatic 30) · ×1

CodeViewer.CodeViewer (cyclomatic 30) understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx:121 — CodeViewer.CodeViewer has cyclomatic complexity 30 (threshold 15). Of this number, 17 points are the body's own statements and 13 belong to 7 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · App.Dashboard (cyclomatic 30) · ×1

App.Dashboard (cyclomatic 30) understand-anything-plugin/packages/dashboard/src/App.tsx:118 — App.Dashboard has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 12 function literals inside it that branch (lines 166, 224, 248, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · scan-project.main (cyclomatic 30) · ×1

scan-project.main (cyclomatic 30) understand-anything-plugin/skills/understand/scan-project.mjs:695 — scan-project.main has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · buildNonCodeBatches (cyclomatic 30) · ×1

buildNonCodeBatches (cyclomatic 30) understand-anything-plugin/skills/understand/compute-batches.mjs:145 — buildNonCodeBatches has cyclomatic complexity 30 (threshold 15). Of this number, 21 points are the body's own statements and 9 belong to 17 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · large-repo-benchmark.parseArgs (cyclomatic 29) · ×1

large-repo-benchmark.parseArgs (cyclomatic 29) scripts/lib/large-repo-benchmark.mjs:182 — large-repo-benchmark.parseArgs has cyclomatic complexity 29 (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 · TypeScriptExtractor.processExportStatement (cyclomatic 29) · ×1

TypeScriptExtractor.processExportStatement (cyclomatic 29) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:385 — TypeScriptExtractor.processExportStatement has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · normalizeJsonc (cyclomatic 29) · ×1

normalizeJsonc (cyclomatic 29) understand-anything-plugin/skills/understand/extract-import-map.mjs:210 — normalizeJsonc has cyclomatic complexity 29 (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 · main (cyclomatic 29) · ×1

main (cyclomatic 29) understand-anything-plugin/skills/understand/extract-import-map.mjs:1970 — main has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · large-repo-benchmark.runBenchmark (cyclomatic 28) · ×1

large-repo-benchmark.runBenchmark (cyclomatic 28) scripts/lib/large-repo-benchmark.mjs:1671 — large-repo-benchmark.runBenchmark has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · WarningBanner.WarningBanner (cyclomatic 28) · ×1

WarningBanner.WarningBanner (cyclomatic 28) understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:45 — WarningBanner.WarningBanner has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · extract-import-map.resolvePythonImport (cyclomatic 28) · ×1

extract-import-map.resolvePythonImport (cyclomatic 28) understand-anything-plugin/skills/understand/extract-import-map.mjs:948 — extract-import-map.resolvePythonImport has cyclomatic complexity 28 (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 · tour-generator.generateHeuristicTour (cyclomatic 26) · ×1

tour-generator.generateHeuristicTour (cyclomatic 26) understand-anything-plugin/packages/core/src/analyzer/tour-generator.ts:135 — tour-generator.generateHeuristicTour has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · schema.validateGraph (cyclomatic 26) · ×1

schema.validateGraph (cyclomatic 26) understand-anything-plugin/packages/core/src/schema.ts:563 — schema.validateGraph has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · merge.mergeDesignGraph (cyclomatic 26) · ×1

merge.mergeDesignGraph (cyclomatic 26) understand-anything-plugin/packages/core/src/figma/merge.ts:11 — merge.mergeDesignGraph has cyclomatic complexity 26 (threshold 15). Of this number, 23 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · elk-layout.repairElkInput (cyclomatic 26) · ×1

elk-layout.repairElkInput (cyclomatic 26) understand-anything-plugin/packages/dashboard/src/utils/elk-layout.ts:56 — elk-layout.repairElkInput has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 9 function items inside it that branch (a function literal at line 66, dedupe, fillParents, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · PathFinderModal.PathFinderModal (cyclomatic 26) · ×1

PathFinderModal.PathFinderModal (cyclomatic 26) understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:9 — PathFinderModal.PathFinderModal has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 10 of the 26 points are its own statements and the rest belongs to 6 function items inside it that branch (findPath, a function literal at line 22, a function literal at line 19, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · sourceSymbols (cyclomatic 26) · ×1

sourceSymbols (cyclomatic 26) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:98 — sourceSymbols has cyclomatic complexity 26 (threshold 15). Of this number, 20 points are the body's own statements and 6 belong to 6 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · SwiftExtractor.extractCallGraph · ×1

SwiftExtractor.extractCallGraph::walk (cyclomatic 25) understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:314 — SwiftExtractor.extractCallGraph::walk 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 · ExportMenu.ExportMenu (cyclomatic 25) · ×1

ExportMenu.ExportMenu (cyclomatic 25) understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx:22 — ExportMenu.ExportMenu has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 10 function items inside it that branch (exportPNG, exportSVG, exportJSON, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · large-repo-benchmark.deliverBenchmarkReports (cyclomatic 24) · ×1

large-repo-benchmark.deliverBenchmarkReports (cyclomatic 24) scripts/lib/large-repo-benchmark.mjs:882 — large-repo-benchmark.deliverBenchmarkReports has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · normalize-graph.normalizeBatchOutput (cyclomatic 24) · ×1

normalize-graph.normalizeBatchOutput (cyclomatic 24) understand-anything-plugin/packages/core/src/analyzer/normalize-graph.ts:202 — normalize-graph.normalizeBatchOutput has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · dart-extractor.collectClassBody (cyclomatic 24) · ×1

dart-extractor.collectClassBody (cyclomatic 24) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:204 — dart-extractor.collectClassBody has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · freshness.isGraphFreshnessResult (cyclomatic 24) · ×1

freshness.isGraphFreshnessResult (cyclomatic 24) understand-anything-plugin/packages/dashboard/src/freshness.ts:95 — freshness.isGraphFreshnessResult has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · MobileLayout.MobileLayout (cyclomatic 24) · ×1

MobileLayout.MobileLayout (cyclomatic 24) understand-anything-plugin/packages/dashboard/src/components/MobileLayout.tsx:34 — MobileLayout.MobileLayout has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · schema.sanitizeGraph (cyclomatic 23) · ×1

schema.sanitizeGraph (cyclomatic 23) understand-anything-plugin/packages/core/src/schema.ts:188 — schema.sanitizeGraph has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 197, 213, 225). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · python-extractor.extractParams (cyclomatic 23) · ×1

python-extractor.extractParams (cyclomatic 23) understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:12 — python-extractor.extractParams has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · GraphView.useLayerDetailGraph.nodes (cyclomatic 23) · ×1

GraphView.useLayerDetailGraph.nodes (cyclomatic 23) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1114 — GraphView.useLayerDetailGraph.nodes has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 5 of the 23 points are its own statements and the rest belongs to one function literal inside it that branches (line 1130). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · extract-structure-result.analyzeFileWithOutcomes (cyclomatic 22) · ×1

extract-structure-result.analyzeFileWithOutcomes (cyclomatic 22) understand-anything-plugin/skills/understand/extract-structure-result.mjs:132 — extract-structure-result.analyzeFileWithOutcomes has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CppExtractor.extractClassOrStruct (cyclomatic 21) · ×1

CppExtractor.extractClassOrStruct (cyclomatic 21) understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:317 — CppExtractor.extractClassOrStruct has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · YAMLConfigParser.extractSections (cyclomatic 21) · ×1

YAMLConfigParser.extractSections (cyclomatic 21) REDACTED:35 — YAMLConfigParser.extractSections has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · merge-batch-graphs.link_tests (cyclomatic 21) · ×1

merge-batch-graphs.link_tests (cyclomatic 21) understand-anything-plugin/skills/understand/merge-batch-graphs.py:640 — merge-batch-graphs.link_tests has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · validSupplement (cyclomatic 21) · ×1

validSupplement (cyclomatic 21) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:67 — validSupplement has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (validEntry, validDeclaration). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · diff-analyzer.formatDiffAnalysis (cyclomatic 20) · ×1

diff-analyzer.formatDiffAnalysis (cyclomatic 20) understand-anything-plugin/src/diff-analyzer.ts:93 — diff-analyzer.formatDiffAnalysis has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · assignLayers (cyclomatic 20) · ×1

assignLayers (cyclomatic 20) understand-anything-plugin/skills/understand/finalize-incremental.mjs:166 — assignLayers has cyclomatic complexity 20 (threshold 15). Of this number, 18 points are the body's own statements and 2 belong to 7 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · tour-generator.parseTourGenerationResponse (cyclomatic 19) · ×1

tour-generator.parseTourGenerationResponse (cyclomatic 19) understand-anything-plugin/packages/core/src/analyzer/tour-generator.ts:70 — tour-generator.parseTourGenerationResponse has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · parse-document.parseDocument (cyclomatic 19) · ×1

parse-document.parseDocument (cyclomatic 19) understand-anything-plugin/packages/core/src/figma/parse/parse-document.ts:21 — parse-document.parseDocument has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (handlePageChild, collectInstances, add). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · useKeyboardShortcuts.useKeyboardShortcuts (cyclomatic 19) · ×1

useKeyboardShortcuts.useKeyboardShortcuts (cyclomatic 19) understand-anything-plugin/packages/dashboard/src/hooks/useKeyboardShortcuts.ts:14 — useKeyboardShortcuts.useKeyboardShortcuts has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 21, 18). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D1 · Cyclomatic Complexity · extract-import-map.resolvePhpImport (cyclomatic 19) · ×1

extract-import-map.resolvePhpImport (cyclomatic 19) understand-anything-plugin/skills/understand/extract-import-map.mjs:1657 — extract-import-map.resolvePhpImport has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · TypeScriptExtractor.extractCallGraph · ×1

TypeScriptExtractor.extractCallGraph::walkForCalls (cyclomatic 18) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:136 — TypeScriptExtractor.extractCallGraph::walkForCalls has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PhpExtractor.extractCallGraph · ×1

PhpExtractor.extractCallGraph::walkForCalls (cyclomatic 18) understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:195 — PhpExtractor.extractCallGraph::walkForCalls has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · DartExtractor.extractCallGraph (cyclomatic 18) · ×1

DartExtractor.extractCallGraph (cyclomatic 18) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:557 — DartExtractor.extractCallGraph has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 2 function items inside it that branch (walkSiblings, walkNode). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · ScalaExtractor.collectTemplateBody (cyclomatic 18) · ×1

ScalaExtractor.collectTemplateBody (cyclomatic 18) understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:339 — ScalaExtractor.collectTemplateBody has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · viewer.readSourceFile (cyclomatic 18) · ×1

viewer.readSourceFile (cyclomatic 18) understand-anything-plugin/packages/viewer/bin/viewer.mjs:144 — viewer.readSourceFile has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · extract-import-map.resolveTsJsImport (cyclomatic 18) · ×1

extract-import-map.resolveTsJsImport (cyclomatic 18) understand-anything-plugin/skills/understand/extract-import-map.mjs:755 — extract-import-map.resolveTsJsImport has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · merge-batch-graphs.recover_imports_from_scan (cyclomatic 18) · ×1

merge-batch-graphs.recover_imports_from_scan (cyclomatic 18) understand-anything-plugin/skills/understand/merge-batch-graphs.py:1066 — merge-batch-graphs.recover_imports_from_scan has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · RubyExtractor.extractCallGraph · ×1

RubyExtractor.extractCallGraph::walkForCalls (cyclomatic 17) understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:170 — RubyExtractor.extractCallGraph::walkForCalls 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 · index.resolveLocaleKey (cyclomatic 17) · ×1

index.resolveLocaleKey (cyclomatic 17) understand-anything-plugin/packages/dashboard/src/locales/index.ts:26 — index.resolveLocaleKey has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · NodeInfo.DomainNodeDetails (cyclomatic 17) · ×1

NodeInfo.DomainNodeDetails (cyclomatic 17) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:157 — NodeInfo.DomainNodeDetails has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MobileDrawer.MobileDrawer (cyclomatic 17) · ×1

MobileDrawer.MobileDrawer (cyclomatic 17) understand-anything-plugin/packages/dashboard/src/components/MobileDrawer.tsx:34 — MobileDrawer.MobileDrawer has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · extract-import-map.resolveScalaImport (cyclomatic 17) · ×1

extract-import-map.resolveScalaImport (cyclomatic 17) understand-anything-plugin/skills/understand/extract-import-map.mjs:1361 — extract-import-map.resolveScalaImport has cyclomatic complexity 17 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D1 · Cyclomatic Complexity · onboard-builder.buildOnboardingGuide (cyclomatic 17) · ×1

onboard-builder.buildOnboardingGuide (cyclomatic 17) understand-anything-plugin/src/onboard-builder.ts:7 — onboard-builder.buildOnboardingGuide has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · normalize-graph.normalizeNodeId (cyclomatic 16) · ×1

normalize-graph.normalizeNodeId (cyclomatic 16) understand-anything-plugin/packages/core/src/analyzer/normalize-graph.ts:64 — normalize-graph.normalizeNodeId 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 · schema.normalizeGraph (cyclomatic 16) · ×1

schema.normalizeGraph (cyclomatic 16) understand-anything-plugin/packages/core/src/schema.ts:516 — schema.normalizeGraph has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D1 · Cyclomatic Complexity · ScalaExtractor.walkTopLevel (cyclomatic 16) · ×1

ScalaExtractor.walkTopLevel (cyclomatic 16) understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:219 — ScalaExtractor.walkTopLevel 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 · json-parser.stripJsoncSyntax (cyclomatic 16) · ×1

json-parser.stripJsoncSyntax (cyclomatic 16) understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts:11 — json-parser.stripJsoncSyntax 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 · ContainerNode.ContainerNodeComponent (cyclomatic 16) · ×1

ContainerNode.ContainerNodeComponent (cyclomatic 16) understand-anything-plugin/packages/dashboard/src/components/ContainerNode.tsx:21 — ContainerNode.ContainerNodeComponent has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · extract-import-map.resolveRustImport (cyclomatic 16) · ×1

extract-import-map.resolveRustImport (cyclomatic 16) understand-anything-plugin/skills/understand/extract-import-map.mjs:1763 — extract-import-map.resolveRustImport 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 · scan-project.detectCategory (cyclomatic 16) · ×1

scan-project.detectCategory (cyclomatic 16) understand-anything-plugin/skills/understand/scan-project.mjs:388 — scan-project.detectCategory has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · merge-subdomain-graphs.main (cyclomatic 16) · ×1

merge-subdomain-graphs.main (cyclomatic 16) understand-anything-plugin/skills/understand/merge-subdomain-graphs.py:312 — merge-subdomain-graphs.main 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.

D12 · Dependency Hygiene · Deprecated · ×1

Deprecated: eslint REDACTED:40 — eslint 9.39.4, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.

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

Repeated repair: understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts:62 — understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts changed 11 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is TreeSitterPlugin.constructor at line 62), 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(incremental): replace static accessor leaves with exact installed names”; “fix(incremental): scope Ruby accessor evidence to installed names”; “fix(incremental): recognize Ruby attr as a runtime method installer”; “fix(incremental): detect Ruby and Python runtime method installers”. 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-07-28..2026-10-26, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-28 15:05:22 +08:00' --until='2026-10-26 15:05:22 +08:00' --full-history --no-merges -- understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts`: 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 · symbol-evidence.collectSymbolEvidence · ×1

symbol-evidence.collectSymbolEvidence::visit (cognitive 177) understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:98 — symbol-evidence.collectSymbolEvidence::visit has cognitive complexity 177 (threshold 15). Drivers by points: if/else 41 (70 pts), boolean chains 54, ternaries 14 (41 pts), loops 4 (12 pts) (nesting depth added 64). 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. This shape REPEATS in the file: one other method here (symbol-evidence.collectSymbolEvidence) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · merge-batch-graphs.production_candidates (cognitive 130) · ×1

merge-batch-graphs.production_candidates (cognitive 130) understand-anything-plugin/skills/understand/merge-batch-graphs.py:405 — merge-batch-graphs.production_candidates has cognitive complexity 130 (threshold 15). Drivers by points: if/else 25 (79 pts), loops 11 (35 pts), boolean chains 10, ternaries 1 (6 pts) (nesting depth added 83). 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 · merge-knowledge-graph.merge (cognitive 128) · ×1

merge-knowledge-graph.merge (cognitive 128) understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:120 — merge-knowledge-graph.merge has cognitive complexity 128 (threshold 15). Drivers by points: if/else 31 (81 pts), loops 15 (25 pts), boolean chains 13, ternaries 2 (6 pts), error handling 2 (3 pts) (nesting depth added 65). 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 · symbol-scopes.buildSymbolScopes.scan (cognitive 116) · ×1

symbol-scopes.buildSymbolScopes.scan (cognitive 116) understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts:88 — symbol-scopes.buildSymbolScopes.scan has cognitive complexity 116 (threshold 15). Drivers by points: if/else 27 (40 pts), ternaries 9 (30 pts), boolean chains 24, loops 11 (22 pts) (nesting depth added 45). 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 · validateIncrementalSymbols (cognitive 107) · ×1

validateIncrementalSymbols (cognitive 107) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:314 — validateIncrementalSymbols has cognitive complexity 107 (threshold 15). Drivers by points: if/else 18 (38 pts), ternaries 10 (35 pts), boolean chains 16, loops 4 (11 pts), error handling 2 (4 pts), other 3 (nesting depth added 54). Of this number, 82 points are the body's own statements and 25 belong to 27 function items inside it that branch. 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 · merge-subdomain-graphs.merge_graphs (cognitive 102) · ×1

merge-subdomain-graphs.merge_graphs (cognitive 102) understand-anything-plugin/skills/understand/merge-subdomain-graphs.py:66 — merge-subdomain-graphs.merge_graphs has cognitive complexity 102 (threshold 15). Drivers by points: if/else 32 (69 pts), loops 17 (28 pts), boolean chains 3, ternaries 2 (nesting depth added 48). 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 · GraphView.useLayerDetailTopology (cognitive 79) · ×1

GraphView.useLayerDetailTopology (cognitive 79) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:393 — GraphView.useLayerDetailTopology has cognitive complexity 79 (threshold 15). Drivers by points: if/else 31 (51 pts), loops 9 (13 pts), boolean chains 12, ternaries 2, error handling 1 (nesting depth added 24). None of this is in the body itself: all 79 points belong to 15 function literals inside it that branch (lines 428, 824, 895, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · dart-extractor.collectClassBody (cognitive 71) · ×1

dart-extractor.collectClassBody (cognitive 71) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:204 — dart-extractor.collectClassBody has cognitive complexity 71 (threshold 15). Drivers by points: if/else 21 (67 pts), loops 2 (4 pts) (nesting depth added 48). 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 · parse-knowledge-base.parse_wiki (cognitive 69) · ×1

parse-knowledge-base.parse_wiki (cognitive 69) understand-anything-plugin/skills/understand-knowledge/parse-knowledge-base.py:323 — parse-knowledge-base.parse_wiki has cognitive complexity 69 (threshold 15). Drivers by points: if/else 20 (40 pts), loops 11 (15 pts), boolean chains 11, ternaries 2 (3 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · merge-batch-graphs.merge_and_normalize (cognitive 68) · ×1

merge-batch-graphs.merge_and_normalize (cognitive 68) understand-anything-plugin/skills/understand/merge-batch-graphs.py:808 — merge-batch-graphs.merge_and_normalize has cognitive complexity 68 (threshold 15). Drivers by points: if/else 22 (39 pts), loops 11 (16 pts), boolean chains 7, ternaries 2 (6 pts) (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 · main (cognitive 63) · ×1

main (cognitive 63) understand-anything-plugin/skills/understand/extract-import-map.mjs:1970 — main has cognitive complexity 63 (threshold 15). Drivers by points: if/else 12 (28 pts), loops 7 (22 pts), boolean chains 5, error handling 3 (5 pts), ternaries 1 (2 pts), other 1 (nesting depth added 34). Of this number, 61 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CppExtractor.extractClassOrStruct (cognitive 61) · ×1

CppExtractor.extractClassOrStruct (cognitive 61) understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:317 — CppExtractor.extractClassOrStruct has cognitive complexity 61 (threshold 15). Drivers by points: if/else 15 (54 pts), boolean chains 3, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 41). 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 · main (cognitive 60) · ×1

main (cognitive 60) understand-anything-plugin/skills/understand/compute-batches.mjs:395 — main has cognitive complexity 60 (threshold 15). Drivers by points: if/else 15 (25 pts), loops 9 (14 pts), boolean chains 10, error handling 3 (5 pts), ternaries 4, other 2 (nesting depth added 17). Of this number, 46 points are the body's own statements and 14 belong to 16 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TypeScriptExtractor.processExportStatement (cognitive 58) · ×1

TypeScriptExtractor.processExportStatement (cognitive 58) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:385 — TypeScriptExtractor.processExportStatement has cognitive complexity 58 (threshold 15). Drivers by points: if/else 8 (27 pts), ternaries 3 (15 pts), boolean chains 7, loops 3 (7 pts), match/switch 1 (2 pts) (nesting depth added 36). Of this number, 57 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · extract-import-map.resolvePythonImport (cognitive 55) · ×1

extract-import-map.resolvePythonImport (cognitive 55) understand-anything-plugin/skills/understand/extract-import-map.mjs:948 — extract-import-map.resolvePythonImport has cognitive complexity 55 (threshold 15). Drivers by points: if/else 13 (31 pts), ternaries 6 (15 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 29). 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 · merge-batch-graphs.main (cognitive 52) · ×1

merge-batch-graphs.main (cognitive 52) understand-anything-plugin/skills/understand/merge-batch-graphs.py:1154 — merge-batch-graphs.main has cognitive complexity 52 (threshold 15). Drivers by points: if/else 22 (35 pts), loops 6 (8 pts), ternaries 5 (7 pts), boolean chains 2 (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 · extract-import-map.normalizeJsonc (cognitive 51) · ×1

extract-import-map.normalizeJsonc (cognitive 51) understand-anything-plugin/skills/understand/extract-import-map.mjs:210 — extract-import-map.normalizeJsonc has cognitive complexity 51 (threshold 15). Drivers by points: if/else 16 (34 pts), loops 5 (11 pts), boolean chains 6 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · compareFileSymbols (cognitive 49) · ×1

compareFileSymbols (cognitive 49) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:200 — compareFileSymbols has cognitive complexity 49 (threshold 15). Drivers by points: if/else 19 (33 pts), boolean chains 15, loops 1 (nesting depth added 14). Of this number, 43 points are the body's own statements and 6 belong to 12 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · tour-generator.generateHeuristicTour (cognitive 48) · ×1

tour-generator.generateHeuristicTour (cognitive 48) understand-anything-plugin/packages/core/src/analyzer/tour-generator.ts:135 — tour-generator.generateHeuristicTour has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (24 pts), loops 12 (19 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 22). Of this number, 45 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · extract-import-map.resolveTsJsImport (cognitive 46) · ×1

extract-import-map.resolveTsJsImport (cognitive 46) understand-anything-plugin/skills/understand/extract-import-map.mjs:755 — extract-import-map.resolveTsJsImport has cognitive complexity 46 (threshold 15). Drivers by points: if/else 8 (20 pts), ternaries 3 (15 pts), loops 2 (7 pts), boolean chains 4 (nesting depth added 29). 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 · fingerprint.compareFingerprints (cognitive 44) · ×1

fingerprint.compareFingerprints (cognitive 44) understand-anything-plugin/packages/core/src/fingerprint.ts:142 — fingerprint.compareFingerprints has cognitive complexity 44 (threshold 15). Drivers by points: if/else 21 (36 pts), loops 6, boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · schema.validateGraph (cognitive 43) · ×1

schema.validateGraph (cognitive 43) understand-anything-plugin/packages/core/src/schema.ts:563 — schema.validateGraph has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (30 pts), loops 5 (9 pts), boolean chains 3, ternaries 1 (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 · merge-batch-graphs.link_tests (cognitive 43) · ×1

merge-batch-graphs.link_tests (cognitive 43) understand-anything-plugin/skills/understand/merge-batch-graphs.py:640 — merge-batch-graphs.link_tests has cognitive complexity 43 (threshold 15). Drivers by points: if/else 17 (37 pts), loops 5 (6 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · main (cognitive 43) · ×1

main (cognitive 43) understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs:17 — main has cognitive complexity 43 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 11, loops 5 (6 pts), ternaries 3 (5 pts), other 2 (nesting depth added 9). Of this number, 30 points are the body's own statements and 13 belong to 31 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · store.useDashboardStore (cognitive 42) · ×1

store.useDashboardStore (cognitive 42) understand-anything-plugin/packages/dashboard/src/store.ts:290 — store.useDashboardStore has cognitive complexity 42 (threshold 15). Drivers by points: if/else 23, boolean chains 12, ternaries 7. None of this is in the body itself: all 42 points belong to 16 function literals inside it that branch (lines 414, 366, 462, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · scan-project.main (cognitive 42) · ×1

scan-project.main (cognitive 42) understand-anything-plugin/skills/understand/scan-project.mjs:695 — scan-project.main has cognitive complexity 42 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 8, loops 4, error handling 1 (2 pts), ternaries 1 (nesting depth added 13). Of this number, 40 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · main (cognitive 42) · ×1

main (cognitive 42) understand-anything-plugin/skills/understand/prepare-incremental.mjs:476 — main has cognitive complexity 42 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 13, ternaries 6 (8 pts), other 2 (nesting depth added 4). Of this number, 37 points are the body's own statements and 5 belong to 14 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · KnowledgeGraphView.KnowledgeGraphViewInner (cognitive 41) · ×1

KnowledgeGraphView.KnowledgeGraphViewInner (cognitive 41) understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx:119 — KnowledgeGraphView.KnowledgeGraphViewInner has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 14, ternaries 3, loops 1 (2 pts) (nesting depth added 6). Most of this is not in the body itself: 6 of the 41 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 254, 307, 179, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · App.DashboardContent (cognitive 41) · ×1

App.DashboardContent (cognitive 41) understand-anything-plugin/packages/dashboard/src/App.tsx:274 — App.DashboardContent has cognitive complexity 41 (threshold 15). Drivers by points: boolean chains 17, if/else 14, ternaries 9 (10 pts) (nesting depth added 1). Of this number, 22 points are the body's own statements and 19 belong to 7 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · buildResult (cognitive 41) · ×1

buildResult (cognitive 41) understand-anything-plugin/skills/understand/extract-structure-result.mjs:216 — buildResult has cognitive complexity 41 (threshold 15). Drivers by points: if/else 22, boolean chains 16, ternaries 1 (2 pts), other 1 (nesting depth added 1). Of this number, 33 points are the body's own statements and 8 belong to 10 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · merge.mergeDesignGraph (cognitive 40) · ×1

merge.mergeDesignGraph (cognitive 40) understand-anything-plugin/packages/core/src/figma/merge.ts:11 — merge.mergeDesignGraph has cognitive complexity 40 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 9 (11 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 15). Of this number, 36 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · large-repo-benchmark.parseArgs (cognitive 39) · ×1

large-repo-benchmark.parseArgs (cognitive 39) scripts/lib/large-repo-benchmark.mjs:182 — large-repo-benchmark.parseArgs has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (32 pts), boolean chains 5, loops 1, ternaries 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · normalize-graph.normalizeBatchOutput (cognitive 39) · ×1

normalize-graph.normalizeBatchOutput (cognitive 39) understand-anything-plugin/packages/core/src/analyzer/normalize-graph.ts:202 — normalize-graph.normalizeBatchOutput has cognitive complexity 39 (threshold 15). Drivers by points: if/else 10 (23 pts), ternaries 2 (7 pts), boolean chains 5, loops 4 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · buildNonCodeBatches (cognitive 38) · ×1

buildNonCodeBatches (cognitive 38) understand-anything-plugin/skills/understand/compute-batches.mjs:145 — buildNonCodeBatches has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (19 pts), loops 8 (9 pts), boolean chains 6, other 2, ternaries 2 (nesting depth added 10). Of this number, 30 points are the body's own statements and 8 belong to 17 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · large-repo-benchmark.runBenchmark (cognitive 37) · ×1

large-repo-benchmark.runBenchmark (cognitive 37) scripts/lib/large-repo-benchmark.mjs:1671 — large-repo-benchmark.runBenchmark has cognitive complexity 37 (threshold 15). Drivers by points: error handling 7 (12 pts), if/else 11, ternaries 6 (11 pts), boolean chains 3 (nesting depth added 10). Of this number, 33 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · GraphView.GraphViewInner (cognitive 37) · ×1

GraphView.GraphViewInner (cognitive 37) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1321 — GraphView.GraphViewInner has cognitive complexity 37 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 8, loops 3, ternaries 3 (nesting depth added 3). Most of this is not in the body itself: 7 of the 37 points are its own statements and the rest belongs to 9 function literals inside it that branch (lines 1431, 1472, 1418, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · main (cognitive 37) · ×1

main (cognitive 37) understand-anything-plugin/skills/understand/finalize-incremental.mjs:379 — main has cognitive complexity 37 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 8, other 5, ternaries 3 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ScalaExtractor.collectTemplateBody (cognitive 35) · ×1

ScalaExtractor.collectTemplateBody (cognitive 35) understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:339 — ScalaExtractor.collectTemplateBody has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (28 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · assignLayers (cognitive 35) · ×1

assignLayers (cognitive 35) understand-anything-plugin/skills/understand/finalize-incremental.mjs:166 — assignLayers has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 5 (8 pts), boolean chains 4, ternaries 1 (3 pts), other 1 (nesting depth added 16). Of this number, 30 points are the body's own statements and 5 belong to 7 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · onboard-builder.buildOnboardingGuide (cognitive 34) · ×1

onboard-builder.buildOnboardingGuide (cognitive 34) understand-anything-plugin/src/onboard-builder.ts:7 — onboard-builder.buildOnboardingGuide has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 6 (14 pts), boolean chains 1 (nesting depth added 18). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · App.Dashboard (cognitive 33) · ×1

App.Dashboard (cognitive 33) understand-anything-plugin/packages/dashboard/src/App.tsx:118 — App.Dashboard has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (23 pts), boolean chains 3, ternaries 3, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 7). None of this is in the body itself: all 33 points belong to 12 function literals inside it that branch (lines 166, 146, 224, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · YAMLConfigParser.extractSections (cognitive 32) · ×1

YAMLConfigParser.extractSections (cognitive 32) REDACTED:35 — YAMLConfigParser.extractSections has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 5 (10 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · extract-structure-result.analyzeFileWithOutcomes (cognitive 32) · ×1

extract-structure-result.analyzeFileWithOutcomes (cognitive 32) understand-anything-plugin/skills/understand/extract-structure-result.mjs:132 — extract-structure-result.analyzeFileWithOutcomes has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 5 (6 pts), boolean chains 5, error handling 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 · large-repo-benchmark.deliverBenchmarkReports (cognitive 31) · ×1

large-repo-benchmark.deliverBenchmarkReports (cognitive 31) scripts/lib/large-repo-benchmark.mjs:882 — large-repo-benchmark.deliverBenchmarkReports has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 7 (8 pts), boolean chains 3, error handling 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PhpExtractor.extractCallGraph · ×1

PhpExtractor.extractCallGraph::walkForCalls (cognitive 31) understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:195 — PhpExtractor.extractCallGraph::walkForCalls has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 2 (8 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · elk-layout.repairElkInput (cognitive 31) · ×1

elk-layout.repairElkInput (cognitive 31) understand-anything-plugin/packages/dashboard/src/utils/elk-layout.ts:56 — elk-layout.repairElkInput has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 4, loops 4, ternaries 2 (3 pts) (nesting depth added 6). Most of this is not in the body itself: 5 of the 31 points are its own statements and the rest belongs to 9 function items inside it that branch (dedupe, fillParents, isCyclic, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · extract-import-map.parseSwiftPackageTargets (cognitive 31) · ×1

extract-import-map.parseSwiftPackageTargets (cognitive 31) understand-anything-plugin/skills/understand/extract-import-map.mjs:458 — extract-import-map.parseSwiftPackageTargets has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (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 · merge-batch-graphs.recover_imports_from_scan (cognitive 31) · ×1

merge-batch-graphs.recover_imports_from_scan (cognitive 31) understand-anything-plugin/skills/understand/merge-batch-graphs.py:1066 — merge-batch-graphs.recover_imports_from_scan has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 3 (4 pts), boolean chains 1, error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · sourceSymbols (cognitive 31) · ×1

sourceSymbols (cognitive 31) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:98 — sourceSymbols has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 7, loops 5 (6 pts), ternaries 2 (5 pts), other 1 (nesting depth added 10). Of this number, 27 points are the body's own statements and 4 belong to 6 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · parse-document.parseDocument (cognitive 30) · ×1

parse-document.parseDocument (cognitive 30) understand-anything-plugin/packages/core/src/figma/parse/parse-document.ts:21 — parse-document.parseDocument has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 5 (8 pts), ternaries 3 (8 pts), match/switch 1 (nesting depth added 15). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 3 function items inside it that branch (collectInstances, handlePageChild, add). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · json-parser.stripJsoncSyntax (cognitive 30) · ×1

json-parser.stripJsoncSyntax (cognitive 30) understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts:11 — json-parser.stripJsoncSyntax has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 4 (10 pts), boolean chains 6 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · large-repo-benchmark.summarizeStructureOutput (cognitive 29) · ×1

large-repo-benchmark.summarizeStructureOutput (cognitive 29) scripts/lib/large-repo-benchmark.mjs:1257 — large-repo-benchmark.summarizeStructureOutput has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 12, if/else 4 (7 pts), boolean chains 6, loops 3 (4 pts) (nesting depth added 4). Of this number, 28 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · typescript-extractor.extractImportSpecifiers (cognitive 29) · ×1

typescript-extractor.extractImportSpecifiers (cognitive 29) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:66 — typescript-extractor.extractImportSpecifiers has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 2 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 18). 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 · ShellParser.extractFunctions (cognitive 29) · ×1

ShellParser.extractFunctions (cognitive 29) understand-anything-plugin/packages/core/src/plugins/parsers/shell-parser.ts:42 — ShellParser.extractFunctions has cognitive complexity 29 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 4 (8 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · python-extractor.extractParams (cognitive 28) · ×1

python-extractor.extractParams (cognitive 28) understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:12 — python-extractor.extractParams has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SwiftExtractor.extractCallGraph · ×1

SwiftExtractor.extractCallGraph::walk (cognitive 28) understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:314 — SwiftExtractor.extractCallGraph::walk has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 5, loops 1, match/switch 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 · typescript-extractor.extractParams (cognitive 27) · ×1

typescript-extractor.extractParams (cognitive 27) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:8 — typescript-extractor.extractParams has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 2 (5 pts), boolean chains 3 (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 · PythonExtractor.extractClass (cognitive 27) · ×1

PythonExtractor.extractClass (cognitive 27) understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:215 — PythonExtractor.extractClass has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 17). 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 · WarningBanner.WarningBanner (cognitive 27) · ×1

WarningBanner.WarningBanner (cognitive 27) understand-anything-plugin/packages/dashboard/src/components/WarningBanner.tsx:45 — WarningBanner.WarningBanner has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 14 (17 pts), boolean chains 5, if/else 4, error handling 1 (nesting depth added 3). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · diff-analyzer.formatDiffAnalysis (cognitive 27) · ×1

diff-analyzer.formatDiffAnalysis (cognitive 27) understand-anything-plugin/src/diff-analyzer.ts:93 — diff-analyzer.formatDiffAnalysis has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (16 pts), loops 5 (10 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · ExportMenu.ExportMenu (cognitive 26) · ×1

ExportMenu.ExportMenu (cognitive 26) understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx:22 — ExportMenu.ExportMenu has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (12 pts), ternaries 4 (7 pts), boolean chains 4, error handling 3 (nesting depth added 4). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 10 function items inside it that branch (exportPNG, exportSVG, exportJSON, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · PathFinderModal.PathFinderModal (cognitive 26) · ×1

PathFinderModal.PathFinderModal (cognitive 26) understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx:9 — PathFinderModal.PathFinderModal has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 6, loops 3 (4 pts), ternaries 1 (nesting depth added 6). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 6 function items inside it that branch (findPath, a function literal at line 22, a function literal at line 19, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · normalize-graph.normalizeNodeId (cognitive 25) · ×1

normalize-graph.normalizeNodeId (cognitive 25) understand-anything-plugin/packages/core/src/analyzer/normalize-graph.ts:64 — normalize-graph.normalizeNodeId has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (9 pts), boolean chains 4 (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 · NodeInfo.NodeInfo (cognitive 25) · ×1

NodeInfo.NodeInfo (cognitive 25) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:278 — NodeInfo.NodeInfo has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 19, ternaries 4, if/else 2. Of this number, 21 points are the body's own statements and 4 belong to 6 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · CodeViewer.CodeViewer (cognitive 25) · ×1

CodeViewer.CodeViewer (cognitive 25) understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx:121 — CodeViewer.CodeViewer has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, ternaries 6 (7 pts), if/else 6 (nesting depth added 1). Of this number, 16 points are the body's own statements and 9 belong to 7 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · layer-detector.applyLLMLayers (cognitive 24) · ×1

layer-detector.applyLLMLayers (cognitive 24) understand-anything-plugin/packages/core/src/analyzer/layer-detector.ts:231 — layer-detector.applyLLMLayers has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 5 (8 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · tour-generator.parseTourGenerationResponse (cognitive 24) · ×1

tour-generator.parseTourGenerationResponse (cognitive 24) understand-anything-plugin/packages/core/src/analyzer/tour-generator.ts:70 — tour-generator.parseTourGenerationResponse has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 6, error handling 1, loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RubyExtractor.extractCallGraph · ×1

RubyExtractor.extractCallGraph::walkForCalls (cognitive 24) understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:170 — RubyExtractor.extractCallGraph::walkForCalls has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 1 (4 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · extract-import-map.resolvePhpImport (cognitive 24) · ×1

extract-import-map.resolvePhpImport (cognitive 24) understand-anything-plugin/skills/understand/extract-import-map.mjs:1657 — extract-import-map.resolvePhpImport has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 4 (8 pts), boolean chains 4, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · diff-analyzer.buildDiffContext (cognitive 24) · ×1

diff-analyzer.buildDiffContext (cognitive 24) understand-anything-plugin/src/diff-analyzer.ts:22 — diff-analyzer.buildDiffContext has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 4 (5 pts), boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · kotlin-extractor.collectClassBody (cognitive 23) · ×1

kotlin-extractor.collectClassBody (cognitive 23) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:97 — kotlin-extractor.collectClassBody has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · scala-extractor.collectClassParameterProperties (cognitive 23) · ×1

scala-extractor.collectClassParameterProperties (cognitive 23) understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:122 — scala-extractor.collectClassParameterProperties has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GraphView.useLayerDetailGraph.expandedEdges (cognitive 23) · ×1

GraphView.useLayerDetailGraph.expandedEdges (cognitive 23) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1222 — GraphView.useLayerDetailGraph.expandedEdges has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (6 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 10). Of this number, 22 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · extract-import-map.resolveScalaImport (cognitive 23) · ×1

extract-import-map.resolveScalaImport (cognitive 23) understand-anything-plugin/skills/understand/extract-import-map.mjs:1361 — extract-import-map.resolveScalaImport has cognitive complexity 23 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 6 (9 pts), boolean chains 1, ternaries 1 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · symbol-evidence.collectSymbolEvidence (cognitive 22) · ×1

symbol-evidence.collectSymbolEvidence (cognitive 22) understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:49 — symbol-evidence.collectSymbolEvidence has cognitive complexity 22 (threshold 15). Drivers by points: if/else 56 (91 pts), boolean chains 66, ternaries 19 (54 pts), loops 11 (24 pts) (nesting depth added 83). 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. This shape REPEATS in the file: one other method here (symbol-evidence.collectSymbolEvidence::visit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · TypeScriptExtractor.extractClass (cognitive 22) · ×1

TypeScriptExtractor.extractClass (cognitive 22) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:267 — TypeScriptExtractor.extractClass has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 11). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PhpExtractor.extractDeclarationList (cognitive 22) · ×1

PhpExtractor.extractDeclarationList (cognitive 22) understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:363 — PhpExtractor.extractDeclarationList has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (21 pts), loops 1 (nesting depth added 13). 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 · DartExtractor.extractCallGraph · ×1

DartExtractor.extractCallGraph::walkSiblings (cognitive 22) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:620 — DartExtractor.extractCallGraph::walkSiblings has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (21 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 · DockerfileParser.extractStages (cognitive 22) · ×1

DockerfileParser.extractStages (cognitive 22) understand-anything-plugin/packages/core/src/plugins/parsers/dockerfile-parser.ts:25 — DockerfileParser.extractStages has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 4 (8 pts), ternaries 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MobileLayout.MobileLayout (cognitive 22) · ×1

MobileLayout.MobileLayout (cognitive 22) understand-anything-plugin/packages/dashboard/src/components/MobileLayout.tsx:34 — MobileLayout.MobileLayout has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, ternaries 7 (8 pts), if/else 2 (nesting depth added 1). Of this number, 20 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · parse-knowledge-base.resolve_wikilink (cognitive 22) · ×1

parse-knowledge-base.resolve_wikilink (cognitive 22) understand-anything-plugin/skills/understand-knowledge/parse-knowledge-base.py:283 — parse-knowledge-base.resolve_wikilink has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TypeScriptExtractor.extractCallGraph · ×1

TypeScriptExtractor.extractCallGraph::walkForCalls (cognitive 21) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:136 — TypeScriptExtractor.extractCallGraph::walkForCalls has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 4, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RustExtractor.extractUseDeclaration (cognitive 21) · ×1

RustExtractor.extractUseDeclaration (cognitive 21) understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:433 — RustExtractor.extractUseDeclaration has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 2 (4 pts), loops 1 (3 pts), boolean chains 1, match/switch 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 · ScalaExtractor.walkTopLevel (cognitive 21) · ×1

ScalaExtractor.walkTopLevel (cognitive 21) understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:219 — ScalaExtractor.walkTopLevel has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GraphView.useLayerDetailGraph.nodes (cognitive 21) · ×1

GraphView.useLayerDetailGraph.nodes (cognitive 21) understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1114 — GraphView.useLayerDetailGraph.nodes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5, loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 7). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 1130). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · NodeInfo.DomainNodeDetails (cognitive 21) · ×1

NodeInfo.DomainNodeDetails (cognitive 21) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:157 — NodeInfo.DomainNodeDetails has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (8 pts), if/else 4 (5 pts) (nesting depth added 5). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · useKeyboardShortcuts.useKeyboardShortcuts (cognitive 21) · ×1

useKeyboardShortcuts.useKeyboardShortcuts (cognitive 21) understand-anything-plugin/packages/dashboard/src/hooks/useKeyboardShortcuts.ts:14 — useKeyboardShortcuts.useKeyboardShortcuts has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 4 (8 pts), boolean chains 3, loops 1 (nesting depth added 8). None of this is in the body itself: all 21 points belong to 2 function literals inside it that branch (lines 21, 18). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · extract-import-map.resolveRustImport (cognitive 21) · ×1

extract-import-map.resolveRustImport (cognitive 21) understand-anything-plugin/skills/understand/extract-import-map.mjs:1763 — extract-import-map.resolveRustImport has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · context-builder.formatContextForPrompt (cognitive 21) · ×1

context-builder.formatContextForPrompt (cognitive 21) understand-anything-plugin/src/context-builder.ts:85 — context-builder.formatContextForPrompt has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (6 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 · tokens.extractTokens (cognitive 20) · ×1

tokens.extractTokens (cognitive 20) understand-anything-plugin/packages/core/src/figma/parse/tokens.ts:12 — tokens.extractTokens has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 9). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to one function item inside it that branches (walk). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · JavaExtractor.extractCallGraph · ×1

JavaExtractor.extractCallGraph::walkForCalls (cognitive 20) understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:133 — JavaExtractor.extractCallGraph::walkForCalls has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CSharpExtractor.extractCallGraph · ×1

CSharpExtractor.extractCallGraph::walkForCalls (cognitive 20) understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:144 — CSharpExtractor.extractCallGraph::walkForCalls has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · explain-builder.formatExplainPrompt (cognitive 20) · ×1

explain-builder.formatExplainPrompt (cognitive 20) understand-anything-plugin/src/explain-builder.ts:108 — explain-builder.formatExplainPrompt has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 3 (6 pts), ternaries 1 (3 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · selectAnalysisFiles (cognitive 20) · ×1

selectAnalysisFiles (cognitive 20) understand-anything-plugin/skills/understand/extract-import-map.mjs:111 — selectAnalysisFiles has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DartExtractor.extractCalleeName (cognitive 19) · ×1

DartExtractor.extractCalleeName (cognitive 19) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:699 — DartExtractor.extractCalleeName has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · extract-import-map.buildSwiftModuleIndex (cognitive 19) · ×1

extract-import-map.buildSwiftModuleIndex (cognitive 19) understand-anything-plugin/skills/understand/extract-import-map.mjs:1269 — extract-import-map.buildSwiftModuleIndex has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 3 (8 pts), boolean chains 2 (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.

D2 · Cognitive Complexity · extract-domain-context.detect_entry_points (cognitive 19) · ×1

extract-domain-context.detect_entry_points (cognitive 19) understand-anything-plugin/skills/understand-domain/extract-domain-context.py:204 — extract-domain-context.detect_entry_points has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 pts), error handling 1 (2 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 · merge-subdomain-graphs.main (cognitive 19) · ×1

merge-subdomain-graphs.main (cognitive 19) understand-anything-plugin/skills/understand/merge-subdomain-graphs.py:312 — merge-subdomain-graphs.main has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 3 (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 · main (cognitive 19) · ×1

main (cognitive 19) understand-anything-plugin/skills/understand/extract-structure.mjs:63 — main has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 2 (5 pts), boolean chains 3, error handling 1 (2 pts), loops 1, other 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · layer-detector.parseLayerDetectionResponse (cognitive 18) · ×1

layer-detector.parseLayerDetectionResponse (cognitive 18) understand-anything-plugin/packages/core/src/analyzer/layer-detector.ts:181 — layer-detector.parseLayerDetectionResponse has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 4 (6 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ruby-extractor.extractParams (cognitive 18) · ×1

ruby-extractor.extractParams (cognitive 18) understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:24 — ruby-extractor.extractParams has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · dart-extractor.extractParamName (cognitive 18) · ×1

dart-extractor.extractParamName (cognitive 18) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:44 — dart-extractor.extractParamName has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TreeSitterPlugin.init (cognitive 18) · ×1

TreeSitterPlugin.init (cognitive 18) understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts:130 — TreeSitterPlugin.init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), error handling 2 (7 pts), loops 1 (2 pts) (nesting depth added 10). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (loadGrammar). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · extract-import-map.loadSwiftPackageTargets (cognitive 18) · ×1

extract-import-map.loadSwiftPackageTargets (cognitive 18) understand-anything-plugin/skills/understand/extract-import-map.mjs:513 — extract-import-map.loadSwiftPackageTargets has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · extract-import-map.resolvePythonProbe (cognitive 18) · ×1

extract-import-map.resolvePythonProbe (cognitive 18) understand-anything-plugin/skills/understand/extract-import-map.mjs:1043 — extract-import-map.resolvePythonProbe has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · symbol-scopes.buildSymbolScopes (cognitive 17) · ×1

symbol-scopes.buildSymbolScopes (cognitive 17) understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts:39 — symbol-scopes.buildSymbolScopes has cognitive complexity 17 (threshold 15). Drivers by points: loops 3 (7 pts), if/else 2 (6 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · JavaExtractor.extractInterface (cognitive 17) · ×1

JavaExtractor.extractInterface (cognitive 17) understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:282 — JavaExtractor.extractInterface has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3 (7 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · RubyExtractor.extractClassBody (cognitive 17) · ×1

RubyExtractor.extractClassBody (cognitive 17) understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:362 — RubyExtractor.extractClassBody has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · dart-extractor.extractParams (cognitive 17) · ×1

dart-extractor.extractParams (cognitive 17) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:77 — dart-extractor.extractParams has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MakefileParser.extractTargets (cognitive 17) · ×1

MakefileParser.extractTargets (cognitive 17) understand-anything-plugin/packages/core/src/plugins/parsers/makefile-parser.ts:23 — MakefileParser.extractTargets has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · louvain.detectCommunities (cognitive 17) · ×1

louvain.detectCommunities (cognitive 17) understand-anything-plugin/packages/dashboard/src/utils/louvain.ts:17 — louvain.detectCommunities has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 5, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · FileExplorer.buildFileTree (cognitive 17) · ×1

FileExplorer.buildFileTree (cognitive 17) understand-anything-plugin/packages/dashboard/src/components/FileExplorer.tsx:27 — FileExplorer.buildFileTree has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 8). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · extract-import-map.loadGoModules (cognitive 17) · ×1

extract-import-map.loadGoModules (cognitive 17) understand-anything-plugin/skills/understand/extract-import-map.mjs:395 — extract-import-map.loadGoModules has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (4 pts), ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · scan-project.detectCategory (cognitive 17) · ×1

scan-project.detectCategory (cognitive 17) understand-anything-plugin/skills/understand/scan-project.mjs:388 — scan-project.detectCategory has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.

D2 · Cognitive Complexity · explain-builder.buildExplainContext (cognitive 17) · ×1

explain-builder.buildExplainContext (cognitive 17) understand-anything-plugin/src/explain-builder.ts:22 — explain-builder.buildExplainContext has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 5, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · change-classifier.classifyUpdate (cognitive 16) · ×1

change-classifier.classifyUpdate (cognitive 16) understand-anything-plugin/packages/core/src/change-classifier.ts:21 — change-classifier.classifyUpdate has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), boolean chains 4, if/else 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · kotlin-extractor.extractReturnType (cognitive 16) · ×1

kotlin-extractor.extractReturnType (cognitive 16) understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:70 — kotlin-extractor.extractReturnType has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SwiftExtractor.extractCalleeName (cognitive 16) · ×1

SwiftExtractor.extractCalleeName (cognitive 16) understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:673 — SwiftExtractor.extractCalleeName has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TreeSitterPlugin.constructor (cognitive 16) · ×1

TreeSitterPlugin.constructor (cognitive 16) understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts:62 — TreeSitterPlugin.constructor has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (7 pts), if/else 5, ternaries 1 (3 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GraphQLParser.extractEndpoints (cognitive 16) · ×1

GraphQLParser.extractEndpoints (cognitive 16) understand-anything-plugin/packages/core/src/plugins/parsers/graphql-parser.ts:58 — GraphQLParser.extractEndpoints has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (5 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CustomNode.CustomNodeComponent (cognitive 16) · ×1

CustomNode.CustomNodeComponent (cognitive 16) understand-anything-plugin/packages/dashboard/src/components/CustomNode.tsx:96 — CustomNode.CustomNodeComponent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 2, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · FilterPanel.FilterPanel (cognitive 16) · ×1

FilterPanel.FilterPanel (cognitive 16) understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:6 — FilterPanel.FilterPanel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 4, ternaries 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 25, toggleNodeType, toggleComplexity, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · prepare-incremental.parseNameStatusZ (cognitive 16) · ×1

prepare-incremental.parseNameStatusZ (cognitive 16) understand-anything-plugin/skills/understand/prepare-incremental.mjs:158 — prepare-incremental.parseNameStatusZ has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · merge-batch-graphs.normalize_node_id (cognitive 16) · ×1

merge-batch-graphs.normalize_node_id (cognitive 16) understand-anything-plugin/skills/understand/merge-batch-graphs.py:233 — merge-batch-graphs.normalize_node_id has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

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

REDACTED

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

REDACTED

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

REDACTED

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

Duplicated block (16–18 lines × 2) understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:35 — understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:35-50 | understand-anything-plugin/skills/understand-knowledge/parse-knowledge-base.py:44-61 — 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 `understand-anything-plugin/skills/understand-knowledge/parse-knowledge-base.py:44` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

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

Duplicated block (15–17 lines × 2) understand-anything-plugin/skills/understand/merge-batch-graphs.py:482 — understand-anything-plugin/skills/understand/merge-batch-graphs.py:482-498 | understand-anything-plugin/skills/understand/merge-batch-graphs.py:500-514 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

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

Duplicated block (8 lines × 3) understand-anything-plugin/skills/understand-domain/extract-domain-context.py:384 — understand-anything-plugin/skills/understand-domain/extract-domain-context.py:384-391 | understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:413-420 | understand-anything-plugin/skills/understand-knowledge/parse-knowledge-base.py:537-544 — 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.

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

Duplicated block (7 lines × 2) understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:206 — understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:206-212 | understand-anything-plugin/skills/understand-knowledge/parse-knowledge-base.py:517-523 — 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 (6 lines × 2) · ×1

Duplicated block (6 lines × 2) understand-anything-plugin/skills/understand/merge-batch-graphs.py:190 — understand-anything-plugin/skills/understand/merge-batch-graphs.py:190-195 | understand-anything-plugin/skills/understand/merge-subdomain-graphs.py:51-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `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.

IC1 · Incompleteness & stubs · Fake-async · ×1

Fake-async — async method never awaits understand-anything-plugin/skills/understand/scan-project.mjs:695 — `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

P2 · Observability · No structured logging · ×1

No structured logging — No logging call was found in the 210 Python, JavaScript/TypeScript production file(s) this check read across 5 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru; JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

R10 · Code Duplication · Duplication concentrated across 3 sibling directories (8 clone groups) · ×1

Duplication concentrated across 3 sibling directories (8 clone groups) understand-anything-plugin/packages/core/src/staleness.ts:9 — 8 duplicated blocks under understand-anything-plugin/packages/ have copies in at least two of the sibling directories core, dashboard, viewer — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplicated block with local edits (241 matched lines × 2 locations) · ×1

Duplicated block with local edits (241 matched lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:14 — understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:14 · understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:23 — the two spans are one implementation copied and then locally edited — 1397 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (144 matched lines × 2 locations) · ×1

Duplicated block with local edits (144 matched lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:144 — understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:144 · understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:120 — the two spans are one implementation copied and then locally edited — 851 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (116 matched lines × 2 locations) · ×1

Duplicated block with local edits (116 matched lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts:85 — understand-anything-plugin/packages/core/src/plugins/extractors/go-extractor.ts:85 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:93 — the two spans are one implementation copied and then locally edited — 694 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (77 matched lines × 2 locations) · ×1

Duplicated block with local edits (77 matched lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:81 — understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:81 · understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:104 — the two spans are one implementation copied and then locally edited — 497 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (72 matched lines × 2 locations) · ×1

Duplicated block with local edits (72 matched lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:79 — understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:79 · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:23 — the two spans are one implementation copied and then locally edited — 431 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (51 matched lines × 2 locations) · ×1

Duplicated block with local edits (51 matched lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:201 — understand-anything-plugin/packages/core/src/plugins/extractors/python-extractor.ts:201 · understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:253 — the two spans are one implementation copied and then locally edited — 258 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (47 lines × 2 locations) · ×1

Duplicated block (47 lines × 2 locations) understand-anything-plugin/packages/core/src/staleness.ts:9 — understand-anything-plugin/packages/core/src/staleness.ts:9 · understand-anything-plugin/packages/dashboard/src/freshness.ts:1 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.

R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1

Duplicated block (27 lines × 2 locations) understand-anything-plugin/packages/dashboard/src/App.tsx:733 — understand-anything-plugin/packages/dashboard/src/App.tsx:733 · understand-anything-plugin/packages/dashboard/src/components/MobileLayout.tsx:209 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×1

Duplicated block (26 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:304 — understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:304 · understand-anything-plugin/packages/core/src/plugins/extractors/ruby-extractor.ts:331 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1

Duplicated block (25 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:431 — understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:431 · understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:474 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

R10 · Code Duplication · Duplicated block (23 lines × 2 locations) · ×1

Duplicated block (23 lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts:74 — understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts:74 · understand-anything-plugin/packages/core/src/plugins/parsers/markdown-parser.ts:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.

R10 · Code Duplication · Duplicated block (22 lines × 4 locations) · ×1

Duplicated block (22 lines × 4 locations) understand-anything-plugin/skills/understand/extract-import-map.mjs:295 — understand-anything-plugin/skills/understand/extract-import-map.mjs:295 · understand-anything-plugin/skills/understand/extract-import-map.mjs:368 · understand-anything-plugin/skills/understand/extract-import-map.mjs:510 · understand-anything-plugin/skills/understand/extract-import-map.mjs:1584 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) · ×1

Duplicated block with local edits (21 matched lines × 2 locations) understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:497 — understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:497 · understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:437 — the two spans are one implementation copied and then locally edited — 102 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (21 lines × 3 locations) · ×1

Duplicated block (21 lines × 3 locations) understand-anything-plugin/skills/understand/compute-batches.mjs:655 — understand-anything-plugin/skills/understand/compute-batches.mjs:655 · understand-anything-plugin/skills/understand/extract-import-map.mjs:2151 · understand-anything-plugin/skills/understand/scan-project.mjs:879 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (17 lines × 3 locations) · ×1

Duplicated block (17 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:392 — understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:392 · understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:297 · understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:326 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.

R10 · Code Duplication · Duplicated block with local edits (17 matched lines × 2 locations) · ×1

Duplicated block with local edits (17 matched lines × 2 locations) understand-anything-plugin/packages/dashboard/src/utils/layout.ts:27 — understand-anything-plugin/packages/dashboard/src/utils/layout.ts:27 · understand-anything-plugin/packages/dashboard/src/utils/layout.worker.ts:18 — the two spans are one implementation copied and then locally edited — 95 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (16 lines × 3 locations) · ×1

Duplicated block (16 lines × 3 locations) understand-anything-plugin/packages/core/src/plugins/parsers/env-parser.ts:10 — understand-anything-plugin/packages/core/src/plugins/parsers/env-parser.ts:10 · understand-anything-plugin/packages/core/src/plugins/parsers/makefile-parser.ts:10 · understand-anything-plugin/packages/core/src/plugins/parsers/toml-parser.ts:10 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.

R2 · Cyclomatic Complexity · Complex function visit (cyclomatic 149, cognitive 193) · ×1

Complex function visit (cyclomatic 149, cognitive 193) understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:98 — visit has cyclomatic complexity 149 and cognitive complexity 193; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function scan (cyclomatic 81, cognitive 116) · ×1

Complex function scan (cyclomatic 81, cognitive 116) understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts:88 — scan has cyclomatic complexity 81 and cognitive complexity 116; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function validateIncrementalSymbols (cyclomatic 40, cognitive 82) · ×1

Complex function validateIncrementalSymbols (cyclomatic 40, cognitive 82) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:314 — validateIncrementalSymbols has cyclomatic complexity 40 and cognitive complexity 82; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function main (cyclomatic 37, cognitive 37) · ×1

Complex function main (cyclomatic 37, cognitive 37) understand-anything-plugin/skills/understand/prepare-incremental.mjs:476 — main has cyclomatic complexity 37 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function DashboardContent (cyclomatic 35, cognitive 27) · ×1

Complex function DashboardContent (cyclomatic 35, cognitive 27) understand-anything-plugin/packages/dashboard/src/App.tsx:274 — DashboardContent has cyclomatic complexity 35 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function buildResult (cyclomatic 34, cognitive 33) · ×1

Complex function buildResult (cyclomatic 34, cognitive 33) understand-anything-plugin/skills/understand/extract-structure-result.mjs:216 — buildResult has cyclomatic complexity 34 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function NodeInfo (cyclomatic 33, cognitive 26) · ×1

Complex function NodeInfo (cyclomatic 33, cognitive 26) understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:278 — NodeInfo has cyclomatic complexity 33 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function ProjectOverview (cyclomatic 33, cognitive 23) · ×1

Complex function ProjectOverview (cyclomatic 33, cognitive 23) understand-anything-plugin/packages/dashboard/src/components/ProjectOverview.tsx:4 — ProjectOverview has cyclomatic complexity 33 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function normalizeBatchOutput (cyclomatic 32, cognitive 46) · ×1

Complex function normalizeBatchOutput (cyclomatic 32, cognitive 46) understand-anything-plugin/packages/core/src/analyzer/normalize-graph.ts:202 — normalizeBatchOutput has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function main (cyclomatic 32, cognitive 46) · ×1

Complex function main (cyclomatic 32, cognitive 46) understand-anything-plugin/skills/understand/compute-batches.mjs:395 — main has cyclomatic complexity 32 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function main (cyclomatic 32, cognitive 37) · ×1

Complex function main (cyclomatic 32, cognitive 37) understand-anything-plugin/skills/understand/finalize-incremental.mjs:379 — main has cyclomatic complexity 32 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function validateGraph (cyclomatic 30, cognitive 47) · ×1

Complex function validateGraph (cyclomatic 30, cognitive 47) understand-anything-plugin/packages/core/src/schema.ts:563 — validateGraph has cyclomatic complexity 30 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function compareFingerprints (cyclomatic 30, cognitive 44) · ×1

Complex function compareFingerprints (cyclomatic 30, cognitive 44) understand-anything-plugin/packages/core/src/fingerprint.ts:142 — compareFingerprints has cyclomatic complexity 30 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function processExportStatement (cyclomatic 29, cognitive 57) · ×1

Complex function processExportStatement (cyclomatic 29, cognitive 57) understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:385 — processExportStatement has cyclomatic complexity 29 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function normalizeJsonc (cyclomatic 29, cognitive 51) · ×1

Complex function normalizeJsonc (cyclomatic 29, cognitive 51) understand-anything-plugin/skills/understand/extract-import-map.mjs:210 — normalizeJsonc has cyclomatic complexity 29 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function generateHeuristicTour (cyclomatic 29, cognitive 49) · ×1

Complex function generateHeuristicTour (cyclomatic 29, cognitive 49) understand-anything-plugin/packages/core/src/analyzer/tour-generator.ts:135 — generateHeuristicTour has cyclomatic complexity 29 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function compareFileSymbols (cyclomatic 29, cognitive 43) · ×1

Complex function compareFileSymbols (cyclomatic 29, cognitive 43) understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:200 — compareFileSymbols has cyclomatic complexity 29 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function main (cyclomatic 28, cognitive 61) · ×1

Complex function main (cyclomatic 28, cognitive 61) understand-anything-plugin/skills/understand/extract-import-map.mjs:1970 — main has cyclomatic complexity 28 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function resolvePythonImport (cyclomatic 28, cognitive 55) · ×1

Complex function resolvePythonImport (cyclomatic 28, cognitive 55) understand-anything-plugin/skills/understand/extract-import-map.mjs:948 — resolvePythonImport has cyclomatic complexity 28 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function main (cyclomatic 28, cognitive 40) · ×1

Complex function main (cyclomatic 28, cognitive 40) understand-anything-plugin/skills/understand/scan-project.mjs:695 — main has cyclomatic complexity 28 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R3 · Large Files · understand-anything-plugin/skills/understand/extract-import-map.mjs · ×1

understand-anything-plugin/skills/understand/extract-import-map.mjs: 2022 lines of code understand-anything-plugin/skills/understand/extract-import-map.mjs:1 — understand-anything-plugin/skills/understand/extract-import-map.mjs has 2022 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx · ×1

understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx: 1485 lines of code understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx:1 — understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx has 1485 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/skills/understand/scan-project.mjs · ×1

understand-anything-plugin/skills/understand/scan-project.mjs: 855 lines of code understand-anything-plugin/skills/understand/scan-project.mjs:1 — understand-anything-plugin/skills/understand/scan-project.mjs has 855 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/dashboard/src/App.tsx · ×1

understand-anything-plugin/packages/dashboard/src/App.tsx: 733 lines of code understand-anything-plugin/packages/dashboard/src/App.tsx:1 — understand-anything-plugin/packages/dashboard/src/App.tsx has 733 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/dashboard/src/store.ts · ×1

understand-anything-plugin/packages/dashboard/src/store.ts: 714 lines of code understand-anything-plugin/packages/dashboard/src/store.ts:1 — understand-anything-plugin/packages/dashboard/src/store.ts has 714 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/skills/understand/prepare-incremental.mjs · ×1

understand-anything-plugin/skills/understand/prepare-incremental.mjs: 701 lines of code understand-anything-plugin/skills/understand/prepare-incremental.mjs:1 — understand-anything-plugin/skills/understand/prepare-incremental.mjs has 701 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts: 685 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts has 685 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/schema.ts · ×1

understand-anything-plugin/packages/core/src/schema.ts: 665 lines of code understand-anything-plugin/packages/core/src/schema.ts:1 — understand-anything-plugin/packages/core/src/schema.ts has 665 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts: 629 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/swift-extractor.ts has 629 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/skills/understand/compute-batches.mjs · ×1

understand-anything-plugin/skills/understand/compute-batches.mjs: 627 lines of code understand-anything-plugin/skills/understand/compute-batches.mjs:1 — understand-anything-plugin/skills/understand/compute-batches.mjs has 627 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts: 547 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx · ×1

understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx: 521 lines of code understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx:1 — understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx has 521 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs · ×1

understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs: 476 lines of code understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs:1 — understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/skills/understand/finalize-incremental.mjs · ×1

understand-anything-plugin/skills/understand/finalize-incremental.mjs: 472 lines of code understand-anything-plugin/skills/understand/finalize-incremental.mjs:1 — understand-anything-plugin/skills/understand/finalize-incremental.mjs has 472 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/staleness.ts · ×1

understand-anything-plugin/packages/core/src/staleness.ts: 466 lines of code understand-anything-plugin/packages/core/src/staleness.ts:1 — understand-anything-plugin/packages/core/src/staleness.ts has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts: 458 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts has 458 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts: 454 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/typescript-extractor.ts has 454 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts: 449 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts has 449 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts: 444 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts has 444 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts: 408 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/php-extractor.ts has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts · ×1

understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts: 403 lines of code understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts:1 — understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R4 · Test Coverage · No test rig can mount a component in this workspace · ×1

No test rig can mount a component in this workspace REDACTED:1 — REDACTED declares environment "node", and no package here declares a DOM implementation (jsdom / happy-dom), a component testing library or a browser runner — so none of the 27 unreached component module(s) can be tested as written, however the suite is authored: understand-anything-plugin/packages/dashboard/src/App.tsx, understand-anything-plugin/packages/dashboard/src/components/NodeInfo.tsx, understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx, understand-anything-plugin/packages/dashboard/src/components/CodeViewer.tsx, understand-anything-plugin/packages/dashboard/src/components/PathFinderModal.tsx, understand-anything-plugin/packages/dashboard/src/components/DomainGraphView.tsx and 21 more. Add a DOM environment and a component testing library (for example jsdom + @testing-library, or the runner's browser mode), then test the components. Reported once because these files share one cause, not one omission each.

R7 · Dead Code · Dead file (~124 LoC) · ×1

Dead file (~124 LoC) understand-anything-plugin/packages/dashboard/src/components/NodeTooltip.tsx — no import path from any entry point (91 application, 24 tooling, 89 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~57 LoC) · ×1

Dead file (~57 LoC) understand-anything-plugin/hooks/post-tool-use-auto-update.mjs — no import path from any entry point (91 application, 24 tooling, 89 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~47 LoC) · ×1

Dead file (~47 LoC) understand-anything-plugin/packages/dashboard/src/utils/layout.worker.ts — no import path from any entry point (91 application, 24 tooling, 89 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R8 · Dependency Hygiene · Unused dependency 'devlop' · ×1

Unused dependency 'devlop' — Declared in understand-anything-plugin/packages/dashboard/REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

X2 · Cancellation propagation · Async function without AbortSignal · ×1

Async function without AbortSignal: get understand-anything-plugin/packages/core/src/figma/source/api-source.ts:25 — `get` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1

Swallowed exception (caught, then discarded) understand-anything-plugin/hooks/post-tool-use-auto-update.mjs:29 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.

Minor — 51 finding(s)

X10 · Duplicated predicate · Duplicated predicate · ×18

Duplicated predicate understand-anything-plugin/packages/core/src/analyzer/layer-detector.ts:184 — `!response || response.trim().length === 0` appears character-identically in 2 files — understand-anything-plugin/packages/core/src/analyzer/layer-detector.ts, understand-anything-plugin/packages/core/src/analyzer/tour-generator.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts:332 — `body && body.type === "field_declaration_list"` appears character-identically in 2 files — understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts, understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:167 — `child && (child.type === "val" || child.type === "var")` appears character-identically in 2 files — understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts, understand-anything-plugin/packages/core/src/plugins/extractors/scala-extractor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx:37 — `containerRef.current && !containerRef.current.contains(e.target as Node)` appears character-identically in 3 files — understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx, understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx, understand-anything-plugin/packages/dashboard/src/components/SearchBar.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts:110 — `doc && typeof doc === "object" && !Array.isArray(doc)` appears character-identically in 2 files — understand-anything-plugin/packages/core/src/plugins/parsers/json-parser.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs:58 — `edge.type === 'contains' && edge.target === node.id` appears character-identically in 2 files — understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs, understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx:197 — `filteredNodeIds.has(e.source) && filteredNodeIds.has(e.target)` appears character-identically in 3 files — understand-anything-plugin/packages/dashboard/src/components/ExportMenu.tsx, understand-anything-plugin/packages/dashboard/src/components/GraphView.tsx, understand-anything-plugin/packages/dashboard/src/components/KnowledgeGraphView.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/dashboard/vite.config.demo.ts:31 — `id.includes("node_modules/@dagrejs/") || id.includes("node_modules/d3-force/")` appears character-identically in 2 files — understand-anything-plugin/packages/dashboard/vite.config.demo.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/dashboard/vite.config.demo.ts:37 — `id.includes("node_modules/react-markdown/") || id.includes("node_modules/hast-util-to-jsx-runtime/") || /[\\/]node_modules[\\/](remark|rehyp…` appears character-identically in 2 files — understand-anything-plugin/packages/dashboard/vite.config.demo.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/skills/understand/prepare-incremental.mjs:682 — `ids.has(edge.source) && ids.has(edge.target)` appears character-identically in 2 files — understand-anything-plugin/skills/understand/prepare-incremental.mjs, understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts:106 — `node !== root && CLASS_NODES.has(node.type)` appears character-identically in 2 files — understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts, understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts:149 — `node.type === "method_declaration" || node.type === "constructor_declaration"` appears character-identically in 2 files — understand-anything-plugin/packages/core/src/plugins/extractors/csharp-extractor.ts, understand-anything-plugin/packages/core/src/plugins/extractors/java-extractor.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs:60 — `parent.type === 'class' && parents.has(parent.id)` appears character-identically in 2 files — understand-anything-plugin/skills/understand/prepare-symbol-retry.mjs, understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/skills/understand/finalize-incremental.mjs:318 — `raw && raw.files && typeof raw.files === 'object' && !Array.isArray(raw.files)` appears character-identically in 2 files — understand-anything-plugin/skills/understand/finalize-incremental.mjs, understand-anything-plugin/skills/understand/prepare-incremental.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/skills/understand/finalize-incremental.mjs:325 — `raw && typeof raw === 'object' && !Array.isArray(raw)` appears character-identically in 2 files — understand-anything-plugin/skills/understand/finalize-incremental.mjs, understand-anything-plugin/skills/understand/prepare-incremental.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/packages/core/src/analyzer/layer-detector.ts:208 — `typeof item !== "object" || item === null` appears character-identically in 2 files — understand-anything-plugin/packages/core/src/analyzer/layer-detector.ts, understand-anything-plugin/packages/core/src/analyzer/tour-generator.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/skills/understand/finalize-incremental.mjs:74 — `typeof value !== 'string' || !value || isAbsolute(value)` appears character-identically in 2 files — understand-anything-plugin/skills/understand/finalize-incremental.mjs, understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py:48 — `child.is_file() and child.name.lower() == wanted` appears character-identically in 2 files — understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py, understand-anything-plugin/skills/understand-knowledge/parse-knowledge-base.py. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

D34 · Knowledge Freshness · Orphaned file · ×6

Orphaned file understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file understand-anything-plugin/packages/dashboard/src/freshness.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file understand-anything-plugin/packages/dashboard/src/components/NodeTooltip.tsx:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file understand-anything-plugin/packages/dashboard/src/utils/force-layout-client.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file understand-anything-plugin/packages/core/src/languages/framework-registry.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.

D12 · Dependency Hygiene · Deprecated · ×3

Deprecated: glob REDACTED:1869 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @ungap/structured-clone REDACTED:785 — @ungap/structured-clone 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "Potential CWE-502 - Update to 1.3.1 or higher". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:1100 — glob 10.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.

D30 · Dependency Vulnerabilities · Low CVE · ×2

REDACTED
REDACTED

X7 · Silent fallback defaults · Silent fallback default on parse failure · ×2

Silent fallback default on parse failure understand-anything-plugin/skills/understand/merge-batch-graphs.py:159 — `_num` returns `0.0` when `(TypeError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure understand-anything-plugin/skills/understand/merge-subdomain-graphs.py:46 — `_num` returns `0.0` when `(TypeError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

X7 · Silent fallback defaults · Silent fallback default in catch · ×2

Silent fallback default in catch scripts/lib/large-repo-benchmark.mjs:789 — `fileSizeOrZero` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch understand-anything-plugin/packages/core/src/ignore-generator.ts:240 — `detectDirectories` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 29 significant file(s) lose their only recent owner: understand-anything-plugin/skills/understand/validate-incremental-symbols.mjs, understand-anything-plugin/skills/understand/prepare-incremental.mjs, understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts, understand-anything-plugin/skills/understand/finalize-incremental.mjs, understand-anything-plugin/skills/understand-knowledge/merge-knowledge-graph.py, understand-anything-plugin/skills/understand/merge-subdomain-graphs.py, understand-anything-plugin/packages/core/src/plugins/extractors/cpp-extractor.ts, understand-anything-plugin/packages/core/src/plugins/extractors/rust-extractor.ts (+21 more). Pair on, review, or document these before any departure.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (35 single-owned of 117 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 117 of the 215 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: understand-anything-plugin/packages/core/src/plugins/extractors/dart-extractor.ts, understand-anything-plugin/packages/core/src/ignore-generator.ts, understand-anything-plugin/skills/understand-figma/figma-scan.mjs, understand-anything-plugin/packages/core/src/figma/merge.ts, understand-anything-plugin/packages/dashboard/src/components/StalenessBanner.tsx, understand-anything-plugin/packages/dashboard/src/utils/force-layout.ts.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 1 of 5 project(s) overshoot their size bounds, lowering Project Cohesion to 6.0/10. The most over is `understand-anything-plugin/packages/core` (14000 LoC, 137 module-visible types across 10 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.

D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1

Further orphaned files (smaller) — 6 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: understand-anything-plugin/packages/core/src/plugins/extractors/kotlin-extractor.ts, understand-anything-plugin/packages/dashboard/src/components/FilterPanel.tsx, understand-anything-plugin/packages/dashboard/src/freshness.ts, understand-anything-plugin/packages/dashboard/src/components/NodeTooltip.tsx, understand-anything-plugin/packages/dashboard/src/utils/force-layout-client.ts, understand-anything-plugin/packages/core/src/languages/framework-registry.ts (8 orphaned of 117 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 117 of the 215 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D36 · Supply-chain Provenance & Signing · REDACTED · ×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.

M4 · Documentation accuracy · README/code drift · ×1

README/code drift CONTRIBUTING.md:186 — CONTRIBUTING.md names React 18, but the manifest declares `react` ^19.0.0. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

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

No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 3467 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.)

R7 · Dead Code · Unused export 'hasChildOfType' · ×1

Unused export 'hasChildOfType' understand-anything-plugin/packages/core/src/plugins/extractors/base-extractor.ts:46 — Nothing ultimately consumes this binding: its only referrer is the re-export in understand-anything-plugin/packages/core/src/plugins/extractors/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in understand-anything-plugin/packages/core/src/plugins/extractors/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export '"zh-TW"' · ×1

Unused export '"zh-TW"' understand-anything-plugin/packages/dashboard/src/locales/index.ts:38 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'applyDagreLayout' · ×1

Unused export 'applyDagreLayout' understand-anything-plugin/packages/dashboard/src/utils/layout.ts:20 — Nothing imports this binding — it is safe to review for removal.

X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1

Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.

X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1

Strict null checking is not enabled everywhere the repository type-checks — 4/5 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.

X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1

Null assertions (`!`) reduce the strict null checking score — ~1.1 `!` null assertions per 1k TypeScript source lines — 32 assertion(s) across the 29863 source line(s) of the 188 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: understand-anything-plugin/packages/core/src/plugins/symbol-scopes.ts (5), understand-anything-plugin/packages/core/src/plugins/tree-sitter-plugin.ts (5), understand-anything-plugin/packages/core/src/plugins/symbol-evidence.ts (4). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

Minor — 23 finding(s)

D12 · Dependency Hygiene · Outdated (npm) · ×13

Outdated (npm): @dagrejs/dagre — @dagrejs/dagre is pinned at 2.0.4; registry.npmjs.org publishes 3.1.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @xyflow/react — @xyflow/react is pinned at 12.10.1; registry.npmjs.org publishes 12.12.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): astro — astro is pinned at 6.3.7; registry.npmjs.org publishes 7.4.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): elkjs — elkjs is pinned at 0.9.3; registry.npmjs.org publishes 0.12.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): fuse.js — fuse.js is pinned at 7.1.0; registry.npmjs.org publishes 7.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): ignore — ignore is pinned at 7.0.5; registry.npmjs.org publishes 7.0.14 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react — react is pinned at 19.2.4; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-dom — react-dom is pinned at 19.2.4; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): tree-sitter-php — tree-sitter-php is pinned at 0.23.12; registry.npmjs.org publishes 0.24.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): web-tree-sitter — web-tree-sitter is pinned at 0.26.8; registry.npmjs.org publishes 0.27.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): yaml — yaml is pinned at 2.8.3; registry.npmjs.org publishes 2.9.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): zod — zod is pinned at 4.3.6; registry.npmjs.org publishes 4.6.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): zustand — zustand is pinned at 5.0.12; registry.npmjs.org publishes 5.0.16 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

D10 · Test Quality · Skipped (documented) · ×10

Skipped (documented): (unnamed test) understand-anything-plugin/packages/core/src/__tests__/change-classifier.test.ts:146 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) tests/skill/understand/test_compute_batches.test.mjs:798 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) tests/skill/understand/test_extract_import_map.test.mjs:170 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) tests/skill/understand/test_extract_import_map.test.mjs:190 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) tests/skill/understand/test_prepare_incremental.test.mjs:1115 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) tests/skill/understand/test_prepare_incremental.test.mjs:1134 — Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) tests/benchmark/test_large_repo_benchmark.test.mjs:958 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) tests/benchmark/test_large_repo_benchmark.test.mjs:1014 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) tests/benchmark/test_large_repo_benchmark.test.mjs:1208 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) tests/benchmark/test_large_repo_benchmark.test.mjs:1639 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs

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-6468364f9ba64d148bba724324c87161/history.json --exit-code 0 --source .	0	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-6468364f9ba64d148bba724324c87161/tree.json --exit-code 0 --source .	0	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 --exclude .arrow --exclude .avro --exclude .csv --exclude .dat --exclude .db --exclude .feather --exclude .geojson --exclude .h5 --exclude .hdf5 --exclude .jsonl --exclude .log --exclude .ndjson --exclude .npy --exclude .npz --exclude .orc --exclude .parquet --exclude .pickle --exclude .pkl --exclude .psv --exclude .sqlite --exclude .sqlite3 --exclude .tfrecord --exclude .tsv --exclude .txt .	18	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	33	artifacts/raw/trivy-fs.json
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. semgrep could not parse 57 file(s) — `understand-anything-plugin/packages/core/src/languages/configs/batch.ts`, `understand-anything-plugin/packages/core/src/languages/configs/c.ts`, `understand-anything-plugin/packages/core/src/languages/configs/cpp.ts`, `understand-anything-plugin/packages/core/src/languages/configs/csharp.ts`, `understand-anything-plugin/packages/core/src/languages/configs/css.ts`, … (+52 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	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	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a17814-1a0a-744e-9976-d7300882b2bb · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 58% · Adequate · gated by D1, D2 ·

At a glance — Architecture · 92% · Exemplary ·

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

At a glance — Readiness · 42% · Weak · gated by P2, P3 ·

At a glance — Security · 54% · Adequate · gated by D29, D30, D36 ·

At a glance — Accessibility · 49% · Weak · gated by AC4 ·

At a glance — Performance · 60% · Adequate ·

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

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts