Executive summary
felangel/bloc falls short of our standard for production, in part because it has pages that don't say their language. It scores 42 out of 100 and is rated Weak, and 42 of its 61 critical findings are security problems.
Accessibility, at 17, is the weakest lens and counts most in the score. The best first steps are structuring the pages and fixing focus, motion and contrast, each worth about 11 points. Raising Accessibility to 70 would lift the score to about 62.
Twenty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version and passing outside input through environment variables would close both risks. Updating the vulnerable packages would fix the three packages with a known security hole, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The nine pages or frames without a title need a descriptive title.
The product code is 16,297 lines, about €35,000 to rebuild.
If Accessibility rose from 17 to 70, the lowest score rated Strong, the score would rise from 42 to about 62.
New since the last survey: 2 findings
- Exception handling · Swallowed exception (empty catch) extensions/vscode/src/utils/set-show-context-menu.ts
- Exception handling · Swallowed exception (empty catch) extensions/vscode/src/utils/set-show-context-menu.ts
Fixed since the last survey: 5 findings
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Supply-chain Provenance & Signing · Unpinned build actions
- Exception handling · Swallowed exception (empty catch) extensions/vscode/src/utils/set-show-context-menu.ts
- Exception handling · Swallowed exception (empty catch) extensions/vscode/src/utils/set-show-context-menu.ts
Rebuild cost: about €35,000 · Estimate
| Cost to rebuild | €12,000 to €59,000, for 195 to 618 hours of work, about 0.2 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 42. 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 | Small: 16,297 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 bloc_zed | 2 com.bloc.intellij_generator_plugin.generator | 3 com.bloc.intellij_generator_plugin.intention_action | 4 com.bloc.intellij_generator_plugin.intention_action.WrapHelper | 5 com.bloc.intellij_generator_plugin.language_server | 6 com.bloc.intellij_generator_plugin.live_templates | 7 com.bloc.intellij_generator_plugin.util | 8 extensions.vscode.src | 9 extensions.vscode.src.code-actions.bloc-code-action-provider | 10 extensions.vscode.src.language-server | 11 extensions.vscode.src.utils.analyze-dependencies | 12 extensions.vscode.src.utils.exec | 13 extensions.vscode.src.utils.get-bloc-type | 14 extensions.vscode.src.utils.get-template-setting | 15 extensions.vscode.src.utils.install-bloc-tools | 16 repository | 17 repository.src | 18 com.bloc.intellij_generator_plugin.action | 19 com.bloc.intellij_generator_plugin.generator.components | 20 com.bloc.intellij_generator_plugin.intention_action.Common | 21 com.bloc.intellij_generator_plugin.intention_action.SnippetType | 22 com.bloc.intellij_generator_plugin.language_server.Architecture | 23 com.bloc.intellij_generator_plugin.language_server.OperatingSystem | 24 extensions.vscode.src.commands | 25 extensions.vscode.src.templates | 26 extensions.vscode.src.utils |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 bloc_zed | ||||||||||||||||||||||||||
| 2 com.bloc.intellij_generator_plugin.generator | ||||||||||||||||||||||||||
| 3 com.bloc.intellij_generator_plugin.intention_action | ||||||||||||||||||||||||||
| 4 com.bloc.intellij_generator_plugin.intention_action.WrapHelper | ||||||||||||||||||||||||||
| 5 com.bloc.intellij_generator_plugin.language_server | ||||||||||||||||||||||||||
| 6 com.bloc.intellij_generator_plugin.live_templates | ||||||||||||||||||||||||||
| 7 com.bloc.intellij_generator_plugin.util | ||||||||||||||||||||||||||
| 8 extensions.vscode.src | ||||||||||||||||||||||||||
| 9 extensions.vscode.src.code-actions.bloc-code-action-provider | ||||||||||||||||||||||||||
| 10 extensions.vscode.src.language-server | ||||||||||||||||||||||||||
| 11 extensions.vscode.src.utils.analyze-dependencies | ||||||||||||||||||||||||||
| 12 extensions.vscode.src.utils.exec | ||||||||||||||||||||||||||
| 13 extensions.vscode.src.utils.get-bloc-type | ||||||||||||||||||||||||||
| 14 extensions.vscode.src.utils.get-template-setting | ||||||||||||||||||||||||||
| 15 extensions.vscode.src.utils.install-bloc-tools | ||||||||||||||||||||||||||
| 16 repository | ||||||||||||||||||||||||||
| 17 repository.src | ||||||||||||||||||||||||||
| 18 com.bloc.intellij_generator_plugin.action | 2 | |||||||||||||||||||||||||
| 19 com.bloc.intellij_generator_plugin.generator.components | 5 | |||||||||||||||||||||||||
| 20 com.bloc.intellij_generator_plugin.intention_action.Common | 1 | |||||||||||||||||||||||||
| 21 com.bloc.intellij_generator_plugin.intention_action.SnippetType | 9 | |||||||||||||||||||||||||
| 22 com.bloc.intellij_generator_plugin.language_server.Architecture | 4 | |||||||||||||||||||||||||
| 23 com.bloc.intellij_generator_plugin.language_server.OperatingSystem | 5 | |||||||||||||||||||||||||
| 24 extensions.vscode.src.commands | 2 | |||||||||||||||||||||||||
| 25 extensions.vscode.src.templates | 5 | |||||||||||||||||||||||||
| 26 extensions.vscode.src.utils | 1 | 1 | 1 | 3 | 2 |
18→2 com.bloc.intellij_generator_plugin.action uses com.bloc.intellij_generator_plugin.generator✕
- Connections
- 2 pairs of types, where a type in com.bloc.intellij_generator_plugin.action uses a type in com.bloc.intellij_generator_plugin.generator.
- The types involved
com.bloc.intellij_generator_plugin.action.GenerateBlocAction→com.bloc.intellij_generator_plugin.generator.BlocGeneratorcom.bloc.intellij_generator_plugin.action.GenerateCubitAction→com.bloc.intellij_generator_plugin.generator.CubitGenerator
- Direction
- com.bloc.intellij_generator_plugin.action uses com.bloc.intellij_generator_plugin.generator, so a change to com.bloc.intellij_generator_plugin.generator can break com.bloc.intellij_generator_plugin.action, while a change to com.bloc.intellij_generator_plugin.action can't break com.bloc.intellij_generator_plugin.generator.
- Position
- Below the diagonal: com.bloc.intellij_generator_plugin.action uses a module listed above it, which is the healthy direction.
19→2 com.bloc.intellij_generator_plugin.generator.components uses com.bloc.intellij_generator_plugin.generator✕
- Connections
- 5 pairs of types, where a type in com.bloc.intellij_generator_plugin.generator.components uses a type in com.bloc.intellij_generator_plugin.generator.
- The types involved
com.bloc.intellij_generator_plugin.generator.components.BlocEventGenerator→com.bloc.intellij_generator_plugin.generator.BlocGeneratorcom.bloc.intellij_generator_plugin.generator.components.BlocGenerator→com.bloc.intellij_generator_plugin.generator.BlocGeneratorcom.bloc.intellij_generator_plugin.generator.components.BlocStateGenerator→com.bloc.intellij_generator_plugin.generator.BlocGeneratorcom.bloc.intellij_generator_plugin.generator.components.CubitGenerator→com.bloc.intellij_generator_plugin.generator.CubitGeneratorcom.bloc.intellij_generator_plugin.generator.components.CubitStateGenerator→com.bloc.intellij_generator_plugin.generator.CubitGenerator
- Direction
- com.bloc.intellij_generator_plugin.generator.components uses com.bloc.intellij_generator_plugin.generator, so a change to com.bloc.intellij_generator_plugin.generator can break com.bloc.intellij_generator_plugin.generator.components, while a change to com.bloc.intellij_generator_plugin.generator.components can't break com.bloc.intellij_generator_plugin.generator.
- Position
- Below the diagonal: com.bloc.intellij_generator_plugin.generator.components uses a module listed above it, which is the healthy direction.
20→3 com.bloc.intellij_generator_plugin.intention_action.Common uses com.bloc.intellij_generator_plugin.intention_action✕
- Connections
- 1 pair of types, where a type in com.bloc.intellij_generator_plugin.intention_action.Common uses a type in com.bloc.intellij_generator_plugin.intention_action.
- The types involved
com.bloc.intellij_generator_plugin.intention_action.Common.Companion→com.bloc.intellij_generator_plugin.intention_action.SnippetType
- Direction
- com.bloc.intellij_generator_plugin.intention_action.Common uses com.bloc.intellij_generator_plugin.intention_action, so a change to com.bloc.intellij_generator_plugin.intention_action can break com.bloc.intellij_generator_plugin.intention_action.Common, while a change to com.bloc.intellij_generator_plugin.intention_action.Common can't break com.bloc.intellij_generator_plugin.intention_action.
- Position
- Below the diagonal: com.bloc.intellij_generator_plugin.intention_action.Common uses a module listed above it, which is the healthy direction.
21→3 com.bloc.intellij_generator_plugin.intention_action.SnippetType uses com.bloc.intellij_generator_plugin.intention_action✕
- Connections
- 9 pairs of types, where a type in com.bloc.intellij_generator_plugin.intention_action.SnippetType uses a type in com.bloc.intellij_generator_plugin.intention_action.
- The types involved
com.bloc.intellij_generator_plugin.intention_action.SnippetType.BlocBuilder→com.bloc.intellij_generator_plugin.intention_action.SnippetTypecom.bloc.intellij_generator_plugin.intention_action.SnippetType.BlocConsumer→com.bloc.intellij_generator_plugin.intention_action.SnippetTypecom.bloc.intellij_generator_plugin.intention_action.SnippetType.BlocListener→com.bloc.intellij_generator_plugin.intention_action.SnippetTypecom.bloc.intellij_generator_plugin.intention_action.SnippetType.BlocProvider→com.bloc.intellij_generator_plugin.intention_action.SnippetTypecom.bloc.intellij_generator_plugin.intention_action.SnippetType.BlocSelector→com.bloc.intellij_generator_plugin.intention_action.SnippetTypecom.bloc.intellij_generator_plugin.intention_action.SnippetType.MultiBlocListener→com.bloc.intellij_generator_plugin.intention_action.SnippetTypecom.bloc.intellij_generator_plugin.intention_action.SnippetType.MultiBlocProvider→com.bloc.intellij_generator_plugin.intention_action.SnippetTypecom.bloc.intellij_generator_plugin.intention_action.SnippetType.MultiRepositoryProvider→com.bloc.intellij_generator_plugin.intention_action.SnippetTypecom.bloc.intellij_generator_plugin.intention_action.SnippetType.RepositoryProvider→com.bloc.intellij_generator_plugin.intention_action.SnippetType
- Direction
- com.bloc.intellij_generator_plugin.intention_action.SnippetType uses com.bloc.intellij_generator_plugin.intention_action, so a change to com.bloc.intellij_generator_plugin.intention_action can break com.bloc.intellij_generator_plugin.intention_action.SnippetType, while a change to com.bloc.intellij_generator_plugin.intention_action.SnippetType can't break com.bloc.intellij_generator_plugin.intention_action.
- Position
- Below the diagonal: com.bloc.intellij_generator_plugin.intention_action.SnippetType uses a module listed above it, which is the healthy direction.
22→5 com.bloc.intellij_generator_plugin.language_server.Architecture uses com.bloc.intellij_generator_plugin.language_server✕
- Connections
- 4 pairs of types, where a type in com.bloc.intellij_generator_plugin.language_server.Architecture uses a type in com.bloc.intellij_generator_plugin.language_server.
- The types involved
com.bloc.intellij_generator_plugin.language_server.Architecture.Arm64→com.bloc.intellij_generator_plugin.language_server.Architecturecom.bloc.intellij_generator_plugin.language_server.Architecture.Companion→com.bloc.intellij_generator_plugin.language_server.Architecturecom.bloc.intellij_generator_plugin.language_server.Architecture.Unknown→com.bloc.intellij_generator_plugin.language_server.Architecturecom.bloc.intellij_generator_plugin.language_server.Architecture.X64→com.bloc.intellij_generator_plugin.language_server.Architecture
- Direction
- com.bloc.intellij_generator_plugin.language_server.Architecture uses com.bloc.intellij_generator_plugin.language_server, so a change to com.bloc.intellij_generator_plugin.language_server can break com.bloc.intellij_generator_plugin.language_server.Architecture, while a change to com.bloc.intellij_generator_plugin.language_server.Architecture can't break com.bloc.intellij_generator_plugin.language_server.
- Position
- Below the diagonal: com.bloc.intellij_generator_plugin.language_server.Architecture uses a module listed above it, which is the healthy direction.
23→5 com.bloc.intellij_generator_plugin.language_server.OperatingSystem uses com.bloc.intellij_generator_plugin.language_server✕
- Connections
- 5 pairs of types, where a type in com.bloc.intellij_generator_plugin.language_server.OperatingSystem uses a type in com.bloc.intellij_generator_plugin.language_server.
- The types involved
com.bloc.intellij_generator_plugin.language_server.OperatingSystem.Companion→com.bloc.intellij_generator_plugin.language_server.OperatingSystemcom.bloc.intellij_generator_plugin.language_server.OperatingSystem.Linux→com.bloc.intellij_generator_plugin.language_server.OperatingSystemcom.bloc.intellij_generator_plugin.language_server.OperatingSystem.MacOS→com.bloc.intellij_generator_plugin.language_server.OperatingSystemcom.bloc.intellij_generator_plugin.language_server.OperatingSystem.Unknown→com.bloc.intellij_generator_plugin.language_server.OperatingSystemcom.bloc.intellij_generator_plugin.language_server.OperatingSystem.Windows→com.bloc.intellij_generator_plugin.language_server.OperatingSystem
- Direction
- com.bloc.intellij_generator_plugin.language_server.OperatingSystem uses com.bloc.intellij_generator_plugin.language_server, so a change to com.bloc.intellij_generator_plugin.language_server can break com.bloc.intellij_generator_plugin.language_server.OperatingSystem, while a change to com.bloc.intellij_generator_plugin.language_server.OperatingSystem can't break com.bloc.intellij_generator_plugin.language_server.
- Position
- Below the diagonal: com.bloc.intellij_generator_plugin.language_server.OperatingSystem uses a module listed above it, which is the healthy direction.
24→13 extensions.vscode.src.commands uses extensions.vscode.src.utils.get-bloc-type✕
- Connections
- 2 pairs of types, where a type in extensions.vscode.src.commands uses a type in extensions.vscode.src.utils.get-bloc-type.
- The types involved
extensions.vscode.src.commands.new-bloc.command→extensions.vscode.src.utils.get-bloc-type.BlocTypeextensions.vscode.src.commands.new-cubit.command→extensions.vscode.src.utils.get-bloc-type.BlocType
- Direction
- extensions.vscode.src.commands uses extensions.vscode.src.utils.get-bloc-type, so a change to extensions.vscode.src.utils.get-bloc-type can break extensions.vscode.src.commands, while a change to extensions.vscode.src.commands can't break extensions.vscode.src.utils.get-bloc-type.
- Position
- Below the diagonal: extensions.vscode.src.commands uses a module listed above it, which is the healthy direction.
25→13 extensions.vscode.src.templates uses extensions.vscode.src.utils.get-bloc-type✕
- Connections
- 5 pairs of types, where a type in extensions.vscode.src.templates uses a type in extensions.vscode.src.utils.get-bloc-type.
- The types involved
extensions.vscode.src.templates.bloc-event.template→extensions.vscode.src.utils.get-bloc-type.BlocTypeextensions.vscode.src.templates.bloc-state.template→extensions.vscode.src.utils.get-bloc-type.BlocTypeextensions.vscode.src.templates.bloc.template→extensions.vscode.src.utils.get-bloc-type.BlocTypeextensions.vscode.src.templates.cubit-state.template→extensions.vscode.src.utils.get-bloc-type.BlocTypeextensions.vscode.src.templates.cubit.template→extensions.vscode.src.utils.get-bloc-type.BlocType
- Direction
- extensions.vscode.src.templates uses extensions.vscode.src.utils.get-bloc-type, so a change to extensions.vscode.src.utils.get-bloc-type can break extensions.vscode.src.templates, while a change to extensions.vscode.src.templates can't break extensions.vscode.src.utils.get-bloc-type.
- Position
- Below the diagonal: extensions.vscode.src.templates uses a module listed above it, which is the healthy direction.
26→11 extensions.vscode.src.utils uses extensions.vscode.src.utils.analyze-dependencies✕
- Connections
- 1 pair of types, where a type in extensions.vscode.src.utils uses a type in extensions.vscode.src.utils.analyze-dependencies.
- The types involved
extensions.vscode.src.utils.analyze-dependencies→extensions.vscode.src.utils.analyze-dependencies.Dependency
- Direction
- extensions.vscode.src.utils uses extensions.vscode.src.utils.analyze-dependencies, so a change to extensions.vscode.src.utils.analyze-dependencies can break extensions.vscode.src.utils, while a change to extensions.vscode.src.utils can't break extensions.vscode.src.utils.analyze-dependencies.
- Position
- Below the diagonal: extensions.vscode.src.utils uses a module listed above it, which is the healthy direction.
26→12 extensions.vscode.src.utils uses extensions.vscode.src.utils.exec✕
- Connections
- 1 pair of types, where a type in extensions.vscode.src.utils uses a type in extensions.vscode.src.utils.exec.
- The types involved
extensions.vscode.src.utils.exec→extensions.vscode.src.utils.exec.ExecOptions
- Direction
- extensions.vscode.src.utils uses extensions.vscode.src.utils.exec, so a change to extensions.vscode.src.utils.exec can break extensions.vscode.src.utils, while a change to extensions.vscode.src.utils can't break extensions.vscode.src.utils.exec.
- Position
- Below the diagonal: extensions.vscode.src.utils uses a module listed above it, which is the healthy direction.
26→13 extensions.vscode.src.utils uses extensions.vscode.src.utils.get-bloc-type✕
- Connections
- 1 pair of types, where a type in extensions.vscode.src.utils uses a type in extensions.vscode.src.utils.get-bloc-type.
- The types involved
extensions.vscode.src.utils.get-bloc-type→extensions.vscode.src.utils.get-bloc-type.BlocType
- Direction
- extensions.vscode.src.utils uses extensions.vscode.src.utils.get-bloc-type, so a change to extensions.vscode.src.utils.get-bloc-type can break extensions.vscode.src.utils, while a change to extensions.vscode.src.utils can't break extensions.vscode.src.utils.get-bloc-type.
- Position
- Below the diagonal: extensions.vscode.src.utils uses a module listed above it, which is the healthy direction.
26→14 extensions.vscode.src.utils uses extensions.vscode.src.utils.get-template-setting✕
- Connections
- 3 pairs of types, where a type in extensions.vscode.src.utils uses a type in extensions.vscode.src.utils.get-template-setting.
- The types involved
extensions.vscode.src.utils.get-bloc-type→extensions.vscode.src.utils.get-template-setting.TemplateTypeextensions.vscode.src.utils.get-template-setting→extensions.vscode.src.utils.get-template-setting.TemplateSettingextensions.vscode.src.utils.get-template-setting→extensions.vscode.src.utils.get-template-setting.TemplateType
- Direction
- extensions.vscode.src.utils uses extensions.vscode.src.utils.get-template-setting, so a change to extensions.vscode.src.utils.get-template-setting can break extensions.vscode.src.utils, while a change to extensions.vscode.src.utils can't break extensions.vscode.src.utils.get-template-setting.
- Position
- Below the diagonal: extensions.vscode.src.utils uses a module listed above it, which is the healthy direction.
26→15 extensions.vscode.src.utils uses extensions.vscode.src.utils.install-bloc-tools✕
- Connections
- 2 pairs of types, where a type in extensions.vscode.src.utils uses a type in extensions.vscode.src.utils.install-bloc-tools.
- The types involved
extensions.vscode.src.utils.install-bloc-tools→extensions.vscode.src.utils.install-bloc-tools.Architectureextensions.vscode.src.utils.install-bloc-tools→extensions.vscode.src.utils.install-bloc-tools.OperatingSystem
- Direction
- extensions.vscode.src.utils uses extensions.vscode.src.utils.install-bloc-tools, so a change to extensions.vscode.src.utils.install-bloc-tools can break extensions.vscode.src.utils, while a change to extensions.vscode.src.utils can't break extensions.vscode.src.utils.install-bloc-tools.
- Position
- Below the diagonal: extensions.vscode.src.utils uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 40 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | High / Critical |
Roadmap
Top priorities: Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; 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; Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +11.0 pts | Medium | Page structure |
| 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. | +11.0 pts | Medium | Visual & motion safety |
| Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge. | +6.6 pts | Medium | A11y enforcement |
| 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. | +1.8 pts | Medium | Async & latency hygiene |
| Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing. | +1.6 pts | Medium | Security & performance tooling |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +0.6 pts | Low | ADR Quality |
| Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production. | +1.1 pts | Medium | Observability |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +0.5 pts | Low | Documentation Quality |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| extensions/vscode/src/templates/bloc.template.ts | 6.9 | Mixed | Explicit Debt: TodoComment |
| examples/flutter_weather/lib/weather/cubit/weather_cubit.dart | 7.0 | Mixed | Code Duplication: Duplicated block (14 lines × 2) |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| extensions/vscode/src/commands/wrap-with.command.ts | 7.3 | Mixed | Explicit Debt: TodoComment |
| packages/flutter_bloc/example/lib/main.dart | 7.4 | Mixed | Code Duplication: Duplicated block (16 lines × 2) |
| examples/flutter_shopping_cart/lib/simple_bloc_observer.dart | 7.4 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
| extensions/vscode/src/utils/get-selected-text.ts | 7.8 | Mixed | Cyclomatic Complexity: get-selected-text.getSelectedText (cyclomatic 17) |
| packages/bloc_lint/lib/src/rules/prefer_bloc.dart | 7.8 | Mixed | Code Duplication: Edited copy of a member (28 corresponding lines) |
| packages/bloc_lint/lib/src/text_document.dart | 7.8 | Mixed | Code Duplication: Duplicated block (12 lines × 2) |
| extensions/intellij/intellij_generator_plugin/src/main/java/com/bloc/intellij_generator_plugin/action/GenerateBlocAction.kt | 7.8 | Mixed | Code Duplication: Duplicated block (11 lines × 2) |
| examples/flutter_weather/lib/weather/widgets/weather_empty.dart | 7.8 | Mixed | Code Duplication: Duplicated block (13 lines × 2) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 63 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 63 dimensions across the health lenses
- 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, 164 of 172 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, 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.
Tools & methods
| 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 |
| Canine Code Analyzer 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 |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.dart) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.dart) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (260 contributor(s) across 2838 commit(s) sampled, automation and bot accounts excluded). One of them holds 82% of the history; the other 259 hold 0.1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `extensions/vscode/src/utils/install-bloc-tools.ts` 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.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_ce' is imported (packages/hydrated_bloc/lib/src/hydrated_cipher.dart:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_ce' is imported (packages/hydrated_bloc/lib/src/hydrated_cipher.dart:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_ce' is imported (packages/hydrated_bloc/lib/src/hydrated_cipher.dart:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'package:hive_ce' is imported (packages/hydrated_bloc/lib/src/hydrated_cipher.dart:3), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- 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.
- 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.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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 Complexity
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was get-selected-text.getSelectedText at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with get-selected-text.getSelectedText (cyclomatic 17). — Refactoring it lifts Cyclomatic Complexity from 9.8 to about 10.0/10.
D2 · Cognitive Complexity
3 method(s) exceeded the cognitive complexity threshold of 15; the worst was get-selected-text.getSelectedText at 27.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cognitive Complexity — start with get-selected-text.getSelectedText (cognitive 27), BlocExtension::language_server_binary_path (cognitive 21), TextDocument.update (cognitive 19). — 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 Cognitive Complexity from 9.1 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
21 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted. 15 of the 22 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
What to do
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with simple_bloc_observer.dart (2), counter_observer.dart, main.dart. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with text_document.dart, simple_bloc_observer.dart. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (15 lines × 3) finding(s) in Code Duplication — start with new_car_page.dart, main.dart. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
11 production modules (Gradle+Cargo+npm+pub), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
3 of 78 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with language_server_command.dart, lint_command.dart, weather_cubit.dart. — One of this dimension's main actionable groups (3 warning-level).
D9 · Test Distribution
1 test methods: 1 unit, 0 integration, 0 BDD, 0 e2e.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 87 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
6 deducted task-comment markers across 16297 LoC (0.0/KLoC) → score 9.9. 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.
What to do
- Resolve the 6 TodoComment finding(s) in Explicit Debt — start with bloc.template.ts (3), wrap-with.command.ts (2), convert-to.command.ts. — One of this dimension's main actionable groups (6 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 322 document(s) read across 3 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 18 build units (Cargo, Gradle, npm, pub) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
40 finding(s): 0 critical, 39 high, 1 medium, 0 low. 18 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 2 file(s) — `extensions/intellij/intellij_generator_plugin/gradlew` (lines 144–145, line 146, line 147, …), `extensions/vscode/src/utils/install-bloc-tools.ts` (line 1) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 11 REDACTED finding(s) charged to Static Analysis (SAST) — the other 17 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (28 issue-level, 11 of them charged here).
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
4 finding(s): 0 critical, 3 high, 1 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
7 of 43 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is extensions/intellij/intellij_generator_plugin/src/main/java/com/bloc/intellij_generator_plugin/action/GenerateEquatablePropsAction.kt. Counted over 43 of the 164 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 7 Orphaned file finding(s) in Knowledge Freshness — start with GenerateEquatablePropsAction.kt, Snippets.kt, Common.kt. — One of this dimension's main actionable groups (7 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: bloc_provider.dart↔repository_provider.dart 60%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with bloc_provider.dart. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 5 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC3 · Page structure
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×9) — extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocListenerIntentionAction/description.html:1, extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocProviderIntentionAction/description.html:1, extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiRepositoryProviderIntentionAction/description.html:1, …
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×9) — extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocListenerIntentionAction/description.html:1, extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocProviderIntentionAction/description.html:1, extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiRepositoryProviderIntentionAction/description.html:1, …
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×9) — extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocListenerIntentionAction/description.html:1, extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocProviderIntentionAction/description.html:1, extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiRepositoryProviderIntentionAction/description.html:1, …
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.
AC6 · Visual & motion safety
- `.outline-0` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/github_search/angular_github_search/web/styles.css:562
- `.outline-0-ns` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/github_search/angular_github_search/web/styles.css:4313
- `.outline-0-m` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/github_search/angular_github_search/web/styles.css:5658
- `.outline-0-l` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — examples/github_search/angular_github_search/web/styles.css:7003
- `.sk-chase` moves (`animation: sk-chase 2.5s infinite linear both`) 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. — examples/github_search/angular_github_search/web/styles.css:7
- `.sk-chase-dot` moves (`animation: sk-chase-dot 2.0s infinite ease-in-out both`) 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. — examples/github_search/angular_github_search/web/styles.css:16
- `.sk-chase-dot:before` moves (`animation: sk-chase-dot-before 2.0s infinite ease-in-out both`) 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. — examples/github_search/angular_github_search/web/styles.css:26
- `.grow` moves (`transition: transform 0.25s ease-out`) 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. — examples/github_search/angular_github_search/web/styles.css:3938
- `.grow` moves (`transition: transform 0.25s ease-out, -webkit-transform 0.25s ease-out`) 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. — examples/github_search/angular_github_search/web/styles.css:3939
- `.grow-large` moves (`transition: transform 0.25s ease-in-out`) 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. — examples/github_search/angular_github_search/web/styles.css:3957
- `.grow-large` moves (`transition: transform 0.25s ease-in-out, -webkit-transform 0.25s ease-in-out`) 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. — examples/github_search/angular_github_search/web/styles.css:3958
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.
AC7 · A11y enforcement
- No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 9 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 your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies
AX10 · Code composition
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.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
AX9 · CQS / query purity
DM5 · Encapsulated state
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Describe the projects a newcomer cannot place from the root README: 2 of 6 have no README of their own, in their folder or in their family's project (`docs`, `examples/flutter_firebase_login/android/app`).
M2 · Architecture documentation
- 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.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 2/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/bloc`, `packages/bloc_concurrency`, `packages/bloc_lint`, `packages/bloc_test`, `packages/flutter_bloc/example` and 2 more.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:8
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `npm`, `cargo`, `gradle`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `npm`, `cargo`, `gradle` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
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 we 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.
P6 · Release Hygiene
What to do
- Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
PF3 · Async & latency hygiene
- `lstatSync` in `newBloc` 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. — extensions/vscode/src/commands/new-bloc.command.ts:28
- `existsSync` in `generateBlocCode` 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. — extensions/vscode/src/commands/new-bloc.command.ts:87
- `lstatSync` in `newCubit` 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. — extensions/vscode/src/commands/new-cubit.command.ts:24
- `existsSync` in `generateCubitCode` 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. — extensions/vscode/src/commands/new-cubit.command.ts:83
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.
R1 · Type Safety
R10 · Code Duplication
- extensions/vscode/src/commands/new-bloc.command.ts:20 · extensions/vscode/src/commands/new-cubit.command.ts:16 — the two spans are one implementation copied and then locally edited — 681 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. — extensions/vscode/src/commands/new-bloc.command.ts:20
- extensions/vscode/src/templates/bloc-state.template.ts:4 · extensions/vscode/src/templates/cubit-state.template.ts:4 — 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. — extensions/vscode/src/templates/bloc-state.template.ts:4
- extensions/vscode/src/language-server/language-server.ts:46 · extensions/vscode/src/language-server/language-server.ts:68 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — extensions/vscode/src/language-server/language-server.ts:46
- extensions/vscode/src/templates/bloc-event.template.ts:4 · extensions/vscode/src/templates/bloc-state.template.ts:4 · extensions/vscode/src/templates/cubit-state.template.ts:4 — 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. — extensions/vscode/src/templates/bloc-event.template.ts:4
- extensions/vscode/src/templates/bloc.template.ts:4 · extensions/vscode/src/templates/cubit.template.ts:4 — 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. — extensions/vscode/src/templates/bloc.template.ts:4
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.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 17 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 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. — extensions/vscode/src/utils/get-selected-text.ts:6
R3 · Large Files
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Nothing ultimately consumes this binding: its only referrer is the re-export in extensions/vscode/src/utils/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 extensions/vscode/src/utils/index.ts in the same commit, or the barrel will import a name that no longer exists. — extensions/vscode/src/utils/get-dart-version.ts:4
R8 · Dependency Hygiene
- Declared in extensions/vscode/package.json 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.
R9 · Circular Imports
- extensions/vscode/src/utils/analyze-dependencies.ts → extensions/vscode/src/utils/index.ts → extensions/vscode/src/utils/analyze-dependencies.ts (one verified cycle inside a mutually-dependent group of 8 files) — extensions/vscode/src/utils/analyze-dependencies.ts:4
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
- The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. (×5) — extensions/vscode/src/commands/new-bloc.command.ts:132, extensions/vscode/src/commands/new-bloc.command.ts:159, extensions/vscode/src/commands/new-bloc.command.ts:185, …
What to do
- `async` Promise executor
X12 · Unreachable branch
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X2 · Cancellation propagation
- Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) 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.
- `getAsStream` awaits `axios.get(…)` 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: `axios.get(url, { signal })`. — extensions/vscode/src/utils/downloader.ts:140
- `getLatestPackageVersion` 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 })`. — extensions/vscode/src/utils/get-latest-package-version.ts:4
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X25 · Inert configuration knob
X27 · Collection changed while being enumerated
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×7) — packages/hydrated_bloc/lib/src/_migration/_migration_io.dart:18, packages/hydrated_bloc/lib/src/_migration/_migration_io.dart:20, packages/bloc_tools/lib/src/command_runner.dart:110, …
- `on Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×3) — packages/bloc_lint/lib/src/analysis_options.dart:71, packages/bloc_lint/lib/src/analysis_options.dart:80, packages/bloc_lint/lib/src/env.dart:70
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 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) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 67% | Adequate | Acceptable, with room to improve. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 73% | Strong | Solid. |
| Readiness | 58% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 68% | Checked 3 of 8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 17% | Critical — gated by AC3, AC6 | 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
- X10 Duplicated predicate — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'package:hive_ce' (packages/hydrated_bloc/lib/src/hydrated_cipher.dart:3) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'package:hive_ce' (packages/hydrated_bloc/lib/src/hydrated_cipher.dart:3) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'package:hive_ce' (packages/hydrated_bloc/lib/src/hydrated_cipher.dart:3) but declares no persisted model this check reads (Drift tables, ObjectBox/Floor @Entity, Isar @collection and Hive @HiveType classes, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: this repository stores data through 'package:hive_ce' (packages/hydrated_bloc/lib/src/hydrated_cipher.dart:3) but declares no persisted model this check reads (Drift tables, Isar/ObjectBox/Floor/Hive entities, Serverpod table models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server another machine can reach (no HttpServer or shelf server bound beyond loopback, no dart_frog route, no Serverpod endpoint, no Conduit, Alfred or Angel application) and keeps no data in a hosted backend. Access control is therefore N/A here — a Flutter app or pub package is authorized by the server it calls, not by itself; hiding a screen authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D10 Test Quality — ~24782 lines of test source are present (.dart) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .dart test runner
- D12 Dependency Hygiene — Not scored — 3 Maven/Gradle manifest(s) were read, stating a version for 4 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Dart, Java, Kotlin, Rust, Swift not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .dart, .java, .kt, .rs, .swift source were not judged.
- 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 (.dart), 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Aggregate boundaries — not scored for Dart: aggregate-vs-value-object classification cannot be told apart in source (every class-holding-class reads alike), and a child COLLECTION (legitimate membership) vs a single embedded aggregate is indistinguishable — reported as guidance rather than measured
- DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
- DM3 Integration-event coupling — not scored for Dart: a cross-package domain leak cannot be told apart in source from a legitimate shared-kernel package, and most repositories ship a single package — reported as guidance rather than measured
- DM4 Rich vs anemic domain model — this Dart repository declares no domain-layer entity carrying stored data (every type is a typed-id wrapper, DTO/config, ORM row or presentation container), so DM4's rich-vs-anemic read has no population to be taken over
- DM6 Domain ↔ infrastructure boundary — this Dart repository maps no type to a persistence framework (drift/floor/isar/objectbox/hive), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — not scored for Dart: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 200 current-state document(s) make no claim of a kind M4 checks. 40 claim(s) of kinds M4 does not check were not checked (path 40); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, JVM, JavaScript/TypeScript, Rust 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (31 production file(s)) has no JavaScript/TypeScript test, but it is 10.14% of this repository's production source and the other 89.86% carries 24,782 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 61 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocListenerIntentionAction/description.html:1
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocProviderIntentionAction/description.html:1
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiRepositoryProviderIntentionAction/description.html:1
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocBuilderIntentionAction/description.html:1
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocConsumerIntentionAction/description.html:1
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocListenerIntentionAction/description.html:1
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocProviderIntentionAction/description.html:1
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocSelectorIntentionAction/description.html:1
- <html> without a lang extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithRepositoryProviderIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocListenerIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocProviderIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiRepositoryProviderIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocBuilderIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocConsumerIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocListenerIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocProviderIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocSelectorIntentionAction/description.html:1
- Document without a <title> extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithRepositoryProviderIntentionAction/description.html:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) extensions/vscode/src/utils/analyze-dependencies.ts:4
Serious — 88 finding(s)
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocListenerIntentionAction/description.html:1
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiBlocProviderIntentionAction/description.html:1
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocConvertToMultiRepositoryProviderIntentionAction/description.html:1
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocBuilderIntentionAction/description.html:1
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocConsumerIntentionAction/description.html:1
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocListenerIntentionAction/description.html:1
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocProviderIntentionAction/description.html:1
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithBlocSelectorIntentionAction/description.html:1
- Page without a main landmark extensions/intellij/intellij_generator_plugin/src/main/resources/intentionDescriptions/BlocWrapWithRepositoryProviderIntentionAction/description.html:1
- Animation without a prefers-reduced-motion guard examples/github_search/angular_github_search/web/styles.css:7
- Animation without a prefers-reduced-motion guard examples/github_search/angular_github_search/web/styles.css:16
- Animation without a prefers-reduced-motion guard examples/github_search/angular_github_search/web/styles.css:26
- Animation without a prefers-reduced-motion guard examples/github_search/angular_github_search/web/styles.css:3938
- Animation without a prefers-reduced-motion guard examples/github_search/angular_github_search/web/styles.css:3939
- Animation without a prefers-reduced-motion guard examples/github_search/angular_github_search/web/styles.css:3957
- Animation without a prefers-reduced-motion guard examples/github_search/angular_github_search/web/styles.css:3958
- Swallowed exception (empty catch) packages/hydrated_bloc/lib/src/_migration/_migration_io.dart:18
- Swallowed exception (empty catch) packages/hydrated_bloc/lib/src/_migration/_migration_io.dart:20
- Swallowed exception (empty catch) packages/bloc_tools/lib/src/command_runner.dart:110
- Swallowed exception (empty catch) extensions/vscode/src/utils/get-pubspec.ts:20
- Swallowed exception (empty catch) extensions/vscode/src/utils/set-show-context-menu.ts:21
- Swallowed exception (empty catch) extensions/vscode/src/utils/set-show-context-menu.ts:33
- Swallowed exception (empty catch) extensions/vscode/src/utils/update-pubspec-dependency.ts:24
- TodoComment extensions/vscode/src/templates/bloc.template.ts:29
- TodoComment extensions/vscode/src/templates/bloc.template.ts:50
- TodoComment extensions/vscode/src/templates/bloc.template.ts:72
- TodoComment extensions/vscode/src/commands/convert-to.command.ts:21
- TodoComment extensions/vscode/src/commands/wrap-with.command.ts:25
- TodoComment extensions/vscode/src/commands/wrap-with.command.ts:41
- `async` Promise executor extensions/vscode/src/commands/new-bloc.command.ts:132
- `async` Promise executor extensions/vscode/src/commands/new-bloc.command.ts:159
- `async` Promise executor extensions/vscode/src/commands/new-bloc.command.ts:185
- `async` Promise executor extensions/vscode/src/commands/new-cubit.command.ts:118
- `async` Promise executor extensions/vscode/src/commands/new-cubit.command.ts:144
- Focus outline removed in CSS without a :focus replacement examples/github_search/angular_github_search/web/styles.css:562
- Focus outline removed in CSS without a :focus replacement examples/github_search/angular_github_search/web/styles.css:4313
- Focus outline removed in CSS without a :focus replacement examples/github_search/angular_github_search/web/styles.css:5658
- Focus outline removed in CSS without a :focus replacement examples/github_search/angular_github_search/web/styles.css:7003
- Duplicated block (5 lines × 2) examples/flutter_counter/lib/counter_observer.dart:11
- Duplicated block (5 lines × 2) packages/flutter_bloc/example/lib/main.dart:18
- Duplicated block (5 lines × 2) examples/flutter_shopping_cart/lib/simple_bloc_observer.dart:8
- Duplicated block (5 lines × 2) examples/flutter_shopping_cart/lib/simple_bloc_observer.dart:14
- Sync-over-async blocking extensions/vscode/src/commands/new-bloc.command.ts:28
- Sync-over-async blocking extensions/vscode/src/commands/new-bloc.command.ts:87
- Sync-over-async blocking extensions/vscode/src/commands/new-cubit.command.ts:24
- Sync-over-async blocking extensions/vscode/src/commands/new-cubit.command.ts:83
- Low cohesion: LanguageServerCommand (LCOM4 5) packages/bloc_tools/lib/src/commands/language_server/language_server_command.dart:7
- Low cohesion: LintCommand (LCOM4 4) packages/bloc_tools/lib/src/commands/lint/lint_command.dart:8
- Low cohesion: WeatherCubit (LCOM4 4) examples/flutter_weather/lib/weather/cubit/weather_cubit.dart:11
- Swallowed exception (caught, then discarded) packages/bloc_lint/lib/src/analysis_options.dart:71
- Swallowed exception (caught, then discarded) packages/bloc_lint/lib/src/analysis_options.dart:80
- Swallowed exception (caught, then discarded) packages/bloc_lint/lib/src/env.dart:70
- Duplicated block (8 lines × 2) packages/bloc_lint/lib/src/text_document.dart:191
- Duplicated block (8 lines × 2) examples/flutter_shopping_cart/lib/simple_bloc_observer.dart:20
- Duplicated block (15 lines × 3) examples/flutter_dynamic_form/lib/new_car/view/new_car_page.dart:49
- Duplicated block (15 lines × 3) packages/flutter_bloc/example/lib/main.dart:119
- Duplicated block (14 lines × 2) examples/flutter_weather/lib/weather/cubit/weather_cubit.dart:24
- Duplicated block (14 lines × 2) examples/flutter_firebase_login/lib/app/bloc_observer.dart:7
- Duplicated block (14 lines × 2 locations) extensions/vscode/src/language-server/language-server.ts:46
- Duplicated block (14 lines × 2 locations) extensions/vscode/src/templates/bloc.template.ts:4
- Async function without AbortSignal: getAsStream extensions/vscode/src/utils/downloader.ts:140
- Async function without AbortSignal: getLatestPackageVersion extensions/vscode/src/utils/get-latest-package-version.ts:4
- Accessibility enforcement below the top rung
- get-selected-text.getSelectedText (cyclomatic 17) extensions/vscode/src/utils/get-selected-text.ts:6
- get-selected-text.getSelectedText (cognitive 27) extensions/vscode/src/utils/get-selected-text.ts:6
- BlocExtension::language_server_binary_path (cognitive 21) extensions/zed/src/lib.rs:12
- TextDocument.update (cognitive 19) packages/bloc_tools/lib/src/lsp/text_document.dart:101
- REDACTED
- REDACTED
- Change coupling: bloc_provider.dart ↔ repository_provider.dart packages/flutter_bloc/lib/src/bloc_provider.dart:1
- Edited copy of a member (28 corresponding lines) packages/bloc_lint/lib/src/rules/prefer_bloc.dart:23
- Duplicated block (20 lines × 2) packages/bloc_lint/lib/src/rules/avoid_public_bloc_methods.dart:45
- Duplicated block (18 lines × 3) packages/bloc_lint/lib/src/rules/prefer_bloc.dart:23
- Duplicated block (12 lines × 2) packages/bloc_lint/lib/src/text_document.dart:165
- Duplicated block (11 lines × 2) extensions/intellij/intellij_generator_plugin/src/main/java/com/bloc/intellij_generator_plugin/action/GenerateBlocAction.kt:54
- Duplicated block (7 lines × 2) extensions/intellij/intellij_generator_plugin/src/main/java/com/bloc/intellij_generator_plugin/action/GenerateBlocAction.kt:41
- Duplicated block (16 lines × 2) packages/flutter_bloc/example/lib/main.dart:112
- Duplicated block (13 lines × 2) examples/flutter_weather/lib/weather/widgets/weather_empty.dart:7
- Duplicated block (12–13 lines × 2) packages/hydrated_bloc/example/lib/main.dart:66
- Duplicated block (11 lines × 3) examples/flutter_weather/lib/weather/widgets/weather_empty.dart:6
- Duplicated block (10 lines × 2) examples/flutter_wizard/lib/main.dart:104
- Duplicated block (7 lines × 5) examples/flutter_counter/lib/counter/view/counter_page.dart:13
- Off the main sequence: bloc_lint
- Duplicated block with local edits (133 matched lines × 2 locations) extensions/vscode/src/commands/new-bloc.command.ts:20
- Duplicated block (43 lines × 2 locations) extensions/vscode/src/templates/bloc-state.template.ts:4
- Duplicated block (14 lines × 3 locations) extensions/vscode/src/templates/bloc-event.template.ts:4
- Complex function (anonymous) (cyclomatic 17, cognitive 26) extensions/vscode/src/utils/get-selected-text.ts:6
- Unused dependency 'tslint'
Minor — 23 finding(s)
- Orphaned file extensions/intellij/intellij_generator_plugin/src/main/java/com/bloc/intellij_generator_plugin/action/GenerateEquatablePropsAction.kt:1
- Orphaned file extensions/intellij/intellij_generator_plugin/src/main/java/com/bloc/intellij_generator_plugin/intention_action/Snippets.kt:1
- Orphaned file extensions/intellij/intellij_generator_plugin/src/main/java/com/bloc/intellij_generator_plugin/intention_action/Common.kt:1
- Orphaned file extensions/zed/src/lib.rs:1
- Orphaned file extensions/intellij/intellij_generator_plugin/src/main/java/com/bloc/intellij_generator_plugin/intention_action/BlocWrapWithIntentionAction.kt:1
- Orphaned file packages/bloc_lint/lib/src/rules/avoid_build_context_extensions.dart:1
- Orphaned file packages/bloc_lint/lib/src/rules/prefer_build_context_extensions.dart:1
- Duplicated predicate packages/bloc_lint/lib/src/rules/avoid_public_fields.dart:41
- Duplicated predicate packages/bloc_lint/lib/src/text_document.dart:192
- Duplicated predicate packages/bloc_lint/lib/src/rules/avoid_public_fields.dart:46
- Duplicated predicate extensions/vscode/src/commands/new-bloc.command.ts:28
- Duplicated predicate extensions/vscode/src/utils/get-pubspec-path.ts:16
- Silent fallback default in catch extensions/vscode/src/utils/downloader.ts:97
- Silent fallback default in catch extensions/vscode/src/utils/get-latest-package-version.ts:10
- Documentation: no build, run or usage example extensions/vscode/README.md:1
- No ADRs found
- Orphaned files with no living knowledge
- No ADRs
- Logging is not universal
- No SAST REDACTED:8
- Dependabot does not watch npm/cargo/gradle REDACTED:2
- Unused export 'getDartVersion' extensions/vscode/src/utils/get-dart-version.ts:4
- Not all async functions that make a request accept an AbortSignal
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f46b51daf8e343d7af5a131e53d8fcf2/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-f46b51daf8e343d7af5a131e53d8fcf2/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude examples/flutter_infinite_list/macos/Flutter --exclude examples/flutter_shopping_cart/macos/Flutter --exclude examples/flutter_timer/macos/Flutter --exclude examples/flutter_weather/linux/flutter --exclude examples/flutter_weather/macos/Flutter --exclude packages/bloc_tools/lib/src/commands/new/bundles . | 40 | 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/** . | 4 | 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 1 file(s) — `extensions/vscode/src/utils/install-bloc-tools.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |