Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
wuba/Fair carries serious gaps (43%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Domain Modelling (100%) — the domain model is expressive and well-guarded. Architecture (100%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (32%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Maturity (41%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: SAST step to CI running what this repository's stack ships (Security & performance tooling); test runner (vitest / jest / playwright) and eslint and type… (Tooling); tests that import the unreached modules (directly or through… (Test Coverage).
For scale: Large (~326,700 production lines); rebuilding it from scratch would take roughly ~2.0 person-years (~1–4 engineers). Approximate, ±~30%.
It builds on a genuinely strong Domain Modelling foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
Code Health
56%
Adequate · gated by R1
Architecture
100% ★
Exemplary
Maturity
41%
Weak · gated by D34, M2
Readiness
32%
Weak · gated by R4, R6, P3
Security
56%
Adequate · gated by D29, D36, D38
Domain Modelling
100% ★
Exemplary
Accessibility
60%
Adequate
How the score is built — each lens's share of the headline
Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
Readiness 32% · 46% weightMaturity 41% · 25% weightCode Health 56% · 14% weightSecurity 56% · 8% weightAccessibility 60% · 4% weightArchitecture 100% · 2% weightDomain Modelling 100% · 1% weight
Raise Readiness 32 → 70 (the Healthy floor) ⇒ headline 43 → ~52.
Code composition — where the lines go
Tests 100%
Rebuild cost & value ~ Modeled — €95,000–€480,000
| Cost to rebuild | €95,000–€480,000 |
| Domain complexity | Standard |
| Quality factor | 0.7× (at 43% quality) |
| Size & shape | Large · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk) |
| Dead frontend code | ~28 LoC unreachable (2 file(s)) |
This codebase represents roughly ~2.0 person-years of build effort (about ~€290,000 to rebuild). Its weakest lens is Readiness at 32% — the part of that asset most exposed by the findings below.
Top priorities
1
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with $$m.dart (2), fair_google_fonts.dart.
2
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.
3
Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Diagnosis — what's actually going on
Value concentrated against a weak lens
This is a Large asset (~2.0 person-years to rebuild), and its weakest lens is Readiness at 32%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
Highest-leverage move
Of everything flagged, the best return on effort is: 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. The rest can wait behind it.
Architecture — module dependency matrix
At a glance — Code Health
The Good
The Bad
The Ugly
At a glance — Architecture
The Good
At a glance — Maturity
The Good
At a glance — Readiness
The Good
The Ugly
At a glance — Security
The Good
The Ugly
At a glance — Domain Modelling
The Good
At a glance — Accessibility
The Good
The Ugly
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A06:2021 — Vulnerable & Outdated Components | 50 | High / Critical |
| A03:2021 — Injection | 12 | High / Critical |
| A05:2021 — Security Misconfiguration | 3 | High / Critical |
Roadmap
First, enforce security and performance standards by integrating static analysis and benchmarking into the CI pipeline to fail the build on regressions. Next, establish a robust testing and linting foundation by adding a test runner, linter, and type checking to the project scripts and CI. Then, increase test coverage by writing tests for currently unreached modules. Finally, improve release safety by gating deployments behind manual approval or draft states, and ensure every release is traceable by stamping a version number.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with $$m.dart (2), fair_google_fonts.dart. | +5.6 pts | Low | Knowledge Freshness |
| 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. | +9.9 pts | Medium | Security & performance tooling |
| Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI. | +9.9 pts | Medium | Tooling |
| Add tests that import the unreached modules (directly or through their public entry). | +9.8 pts | Medium | Test Coverage |
| Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it. | +9.2 pts | Medium | Deployment & Rollback |
| 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. | +9.2 pts | Medium | Release Hygiene |
| Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. | +4.2 pts | Low | Knowledge Freshness |
| Run the test suite in CI via an explicit runner step (`flutter test` for the toolchain this pipeline already uses) and gate merges on it. | +5.7 pts | Medium | CI/CD gates |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| package-lock.json | 0.7 | Slop | OSV Dependency Vulnerabilities: Critical CVE: [GHSA redacted] |
| fair_online/fair_online_service/Dockerfile | 4.4 | Mixed | IaC & Container Security: High IaC: DS-0002 |
| .github/workflows/flutter_1_12_13.yml | 5.8 | Mixed | Static Analysis (SAST): High: github-actions-mutable-action-tag |
| .github/workflows/flutter_1_17_3.yml | 5.8 | Mixed | Static Analysis (SAST): High: github-actions-mutable-action-tag |
| .github/workflows/flutter_1_20_4.yml | 5.8 | Mixed | Static Analysis (SAST): High: github-actions-mutable-action-tag |
| .github/workflows/flutter_1_22_4.yml | 5.8 | Mixed | Static Analysis (SAST): High: github-actions-mutable-action-tag |
| .github/workflows/main.yml | 5.8 | Mixed | Static Analysis (SAST): High: github-actions-mutable-action-tag |
| fair/android/src/main/v8/com/eclipsesource/v8/debug/V8DebugServer.java | 7.9 | Mixed | Static Analysis (SAST): Medium: unencrypted-socket |
| fair_online/fair_online/web/scripts/frame.js | 7.9 | Mixed | Static Analysis (SAST): Medium: wildcard-postmessage-configuration |
| fair/android/src/main/java/com/wuba/fair/channel/FairFfi.java | 8.5 | Near-clean | Change Coupling: Change coupling: FairFfi.java ↔ FairV8JsLoader.java |
| dart2dsl/lib/fairdsl/fair_ast_gen.dart | 8.5 | Near-clean | Change Coupling: Change coupling: fair_ast_gen.dart ↔ fair_dsl_gen.dart |
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 36 of 38 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 38 dimensions across the health lenses
D4D13D19D21D28D29D31D33D34D35D36D38AC2AC6AC7AX9DM2DM4DM5DM6M1M2M3M4P1P3P4P6R1R10R2R3R4R5R6R7R8R9
How to trust any code-health report — three questions
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 70 of 81 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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 |
| jscpd | Code duplication | — | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.302 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.302 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | Local LLM | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
- D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
Dimensions
D4 · Code Duplication
0 duplicated block group(s) detected.
Do you agree with this assessment?
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
Do you agree with this assessment?
D19 · Documentation Quality
Fair's documentation is comprehensive and well-structured across READMEs, architecture markdown, fair_provider, fair_online, fair_extension, fair_compiler, and test-case directories. It covers the core Fair dynamic update model (what it does, a lossless UI rendering demo), fair_provider state-management integration with adapter usage, platform-specific features like offline compilation, an online development platform walkthrough, fair_extension plugin support for built-in logic, and a compiler companion for Dart->JS/DSL conversion. The fair_compiler README is the longest at 377 words and covers running, dependencies, SDK versioning, and the full architecture outline (add Fair dependency; add build_runner and compiler dependency; switch 'fair_version' per Flutter SDK). It is clear and complete but lacks a dedicated Getting Started section for the Dart2JS compiler companion that appears in the test-case directories. The fair_template, fair_provider, fair_mobx, fair_list_demo, fair_bloc projects all have identical READMEs: one line 'A new Flutter project.' followed by a 'Getting Started' section listing the same two resources (Flutter codelab and cookbook links) plus an online docs link. The repeated boilerplate is unavoidable for starter projects but shows no architecture or feature documentation; each README only names the project without describing what it does, its features, or how to use the code beyond the 'Getting Started' snippet.
What to do
- Improve Documentation Quality — currently 7.0/10. — Fair's documentation is comprehensive and well-structured across READMEs, architecture markdown, fair_provider, fair_online, fair_extension, fair_compiler, and test-case directories. It covers the core Fair dynamic update model (what it does, a lossless UI rendering demo), fair_provider state-management integration with adapter usage, platform-specific features like offline compilation, an online development platform walkthrough, fair_extension plugin support for built-in logic, and a compiler companion for Dart->JS/DSL conversion. The fair_compiler README is the longest at 377 words and covers running, dependencies, SDK versioning, and the full architecture outline (add Fair dependency; add build_runner and compiler dependency; switch 'fair_version' per Flutter SDK). It is clear and complete but lacks a dedicated Getting Started section for the Dart2JS compiler companion that appears in the test-case directories. The fair_template, fair_provider, fair_mobx, fair_list_demo, fair_bloc projects all have identical READMEs: one line 'A new Flutter project.' followed by a 'Getting Started' section listing the same two resources (Flutter codelab and cookbook links) plus an online docs link. The repeated boilerplate is unavoidable for starter projects but shows no architecture or feature documentation; each README only names the project without describing what it does, its features, or how to use the code beyond the 'Getting Started' snippet.
Do you agree with this assessment?
D21 · Naming Consistency
0 naming inconsistencies across 0 sampled symbols.
Do you agree with this assessment?
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
Do you agree with this assessment?
D29 · Static Analysis (SAST)
12 finding(s): 0 critical, 10 high, 2 medium, 0 low.
High: github-actions-mutable-action-tag .github/workflows/flutter_1_12_13.yml:16
Medium: unencrypted-socket fair/android/src/main/v8/com/eclipsesource/v8/debug/V8DebugServer.java:161
What to do
- Resolve the 10 High finding(s) in Static Analysis (SAST) — start with flutter_1_12_13.yml (2), flutter_1_17_3.yml (2), flutter_1_20_4.yml (2). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 2 Medium finding(s) in Static Analysis (SAST) — start with V8DebugServer.java, frame.js. — One of this dimension's main actionable groups (2 warning-level).
Do you agree with this assessment?
D31 · IaC & Container Security
3 finding(s): 0 critical, 1 high, 1 medium, 1 low.
High IaC: DS-0002fair_online/fair_online_service/Dockerfile
Medium IaC: CKV_DOCKER_3fair_online/fair_online_service/Dockerfile:1
Low IaC: DS-0026fair_online/fair_online_service/Dockerfile
Do you agree with this assessment?
D33 · JS/npm Dependency Vulnerabilities
No known-vulnerable JS/npm dependencies.
Do you agree with this assessment?
D34 · Knowledge Freshness
328 of 328 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is test_case/flutter_libs_app/lib/google_fonts/fair_google_fonts.dart.
Largest orphaned file test_case/flutter_libs_app/lib/google_fonts/fair_google_fonts.dart
Dormant codebase
What to do
- Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with $$m.dart (2), fair_google_fonts.dart. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D35 · Change Coupling
Strongest change-coupling: FairFfi.java↔FairV8JsLoader.java 57%; fair_ast_gen.dart↔fair_dsl_gen.dart 50%
Change coupling: FairFfi.java ↔ FairV8JsLoader.java fair/android/src/main/java/com/wuba/fair/channel/FairFfi.java
Do you agree with this assessment?
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
Unpinned build actions
Workflow token permissions not restricted
No build provenance
No SBOM
What to do
- Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Workflow token permissions not restricted finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Do you agree with this assessment?
D38 · OSV Dependency Vulnerabilities
76 finding(s): 11 critical, 36 high, 22 medium, 7 low.
High CVE: [GHSA redacted] package-lock.json
Critical CVE: [GHSA redacted] package-lock.json
High vulnerability: [GHSA redacted] package-lock.json
Critical vulnerability: [GHSA redacted]package-lock.json
Medium CVE: [GHSA redacted] package-lock.json
What to do
- Resolve the 33 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (33). — One of this dimension's main actionable groups (33 issue-level).
- Resolve the 10 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (10). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 3 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (3). — One of this dimension's main actionable groups (3 issue-level).
Do you agree with this assessment?
Frontend & cross-cutting dimensions
AC2 · Forms & labels
Do you agree with this assessment?
AC6 · Visual & motion safety
- The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. — Layout.vue:3
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have) and no axe/pa11y/Lighthouse in tests or CI. Start by running that check over your rendered pages in CI.
What to do
- Enforce accessibility in the toolchain: add an accessibility check that can read your UI — no component framework was detected and your pages are rendered by server-side templates, which neither the JSX/Vue ESLint plugins nor the HTML-template linters can parse; run axe/pa11y over the rendered pages, or assert the accessibility invariants over that rendered HTML in the test suite you already have, then assert with your test runner's axe binding (jest-axe, vitest-axe, cypress-axe or @axe-core/playwright) in tests, then gate axe/pa11y/Lighthouse in CI.
Do you agree with this assessment?
AX9 · CQS / query purity
Do you agree with this assessment?
DM2 · Strongly-typed ids
Do you agree with this assessment?
DM4 · Rich vs anemic domain model
Do you agree with this assessment?
DM5 · Encapsulated state
Do you agree with this assessment?
DM6 · Domain ↔ infrastructure boundary
Do you agree with this assessment?
M1 · Documentation (README)
What to do
- Add a 'Testing' section to the root README — how to run the test suite.
- Add a README to the 50 of 51 project(s) that lack one — worth up to 2 pts.
Do you agree with this assessment?
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Do you agree with this assessment?
M3 · Folder & project structure
Do you agree with this assessment?
M4 · Documentation accuracy
Do you agree with this assessment?
P1 · CI/CD gates
- A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Check the coverage dimensions first: if this repo has no test suite yet, that is the finding and this row follows from it. If a suite does exist, make the runner step explicit so the gate is unambiguous.
What to do
- Run the test suite in CI via an explicit runner step (`flutter test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
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 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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Do you agree with this assessment?
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Do you agree with this assessment?
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.
Do you agree with this assessment?
R1 · Type Safety
- 0 typed · 78 plain JS — the untyped files are dart2dsl/lib/dartjs/core-types/bigInt.js, dart2dsl/lib/dartjs/core-types/bigInt.test.js, dart2dsl/lib/dartjs/core-types/core.js, dart2dsl/lib/dartjs/core-types/date.js, dart2dsl/lib/dartjs/core-types/date.test.js, dart2dsl/lib/dartjs/core-types/duration.js (+72 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Do you agree with this assessment?
R10 · Code Duplication
- dart2js/core-types/core.js:743 · dart2js/core-types/date.js:342 · fair/assets/fair_core/fair_jsbase.js:737 · fair_online/fair_online_service/fairDir/empty/project/empty_project/web/fair_core/fair_jsbase.js:734 · +2 more site(s) not listed — the 6 copies are spread across 5 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — core.js:743
- dart2dsl/lib/dartjs/core-types/core.js:1548 · dart2dsl/lib/dartjs/core-types/string.js:8 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — core.js:1548
- dart2dsl/lib/dartjs/core-types/core.js:256 · dart2dsl/lib/dartjs/core-types/iterable.js:113 — 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. — core.js:256
- dart2js/core-types/core.js:384 · dart2js/core-types/iterable.js:122 · fair/assets/fair_core/fair_jsbase.js:378 · fair_online/fair_online_service/fairDir/empty/project/empty_project/web/fair_core/fair_jsbase.js:375 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core.js:384
- dart2js/core-types/core.js:1764 · fair_online/fair_online_service/fairDir/empty/project/empty_project/web/fair_core/fair_jsbase.js:1758 · fair_online/fair_online_service/fairDir/template/project/fair_samples/web/fair_core/fair_jsbase.js:1758 · fair_online/fair_online_service/fairDir/template/project/fair_samples/web/web/fair_core/fair_jsbase.js:1758 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — core.js:1764
- dart2dsl/lib/dartjs/core-types/core.js:1217 · dart2dsl/lib/dartjs/core-types/number.js:20 — 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. — core.js:1217
- dart2js/core-types/core.js:135 · dart2js/core-types/duration.js:52 · fair/assets/fair_core/fair_jsbase.js:129 · fair_online/fair_online_service/fairDir/empty/project/empty_project/web/fair_core/fair_jsbase.js:126 · +2 more site(s) not listed — the 6 copies are spread across 6 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core.js:135
- dart2js/core-types/core.js:1573 · dart2js/core-types/regex.js:46 · fair/assets/fair_core/fair_jsbase.js:1567 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — core.js:1573
What to do
- Extract the duplicated blocks into shared functions/components.
Do you agree with this assessment?
R2 · Cyclomatic Complexity
- Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×8) — jsbeautify.js:2, jsbeautify.js:77, javascript.js:66, …
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files
- 6 file(s) over 400 lines (counted as significant lines — blank lines excluded — over production source only, tests excluded), largest first: fair_online/fair_online_service/fairDir/empty/project/empty_project/web/fair_core/fair_jsbase.js (1820), fair_online/fair_online_service/fairDir/template/project/fair_samples/web/fair_core/fair_jsbase.js (1820), fair_online/fair_online_service/fairDir/template/project/fair_samples/web/web/fair_core/fair_jsbase.js (1820), dart2js/core-types/core.js (1813), fair/assets/fair_core/fair_jsbase.js (1806), dart2dsl/lib/dartjs/core-types/core.js (1592).
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×8) — core.js, fair_jsbase.js, fair_jsbase.js, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R5 · Dependency Freshness
Do you agree with this assessment?
R6 · Tooling
- test ✗ · lint ✗ · typecheck ✗
What to do
- Add a test runner (vitest / jest / playwright) and eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code
- Unreachable from the 76 application, 0 tooling and 22 test entry point(s) detected in this repo. Gate removals on your build/type-check — an undetected custom entry would make these reachable.
- no import path from any entry point (76 application, 0 tooling, 22 test roots considered) (×2) — check_localstorage.js, ga.js
Do you agree with this assessment?
R8 · Dependency Hygiene
Do you agree with this assessment?
R9 · Circular Imports
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 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 | 56% | Adequate — gated by R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 41% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 32% | Weak — gated by R4, R6, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 56% | Adequate — gated by D29, D36, D38 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 60% | Adequate | Acceptable, with room to improve. |
Not included — 75 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC3 Page structure — No structural check found in the parsed markup — AC3 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.
- AX1 Captive dependencies — no DI registrations detected
- AX10 Code composition — not assessed — code composition is computed by ROLE over a document set that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — no singleton implementations detected
- AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D1 Cyclomatic Complexity — Most of this repository's production source (.dart, .java) had no cyclomatic complexity computed for it, so cyclomatic complexity was not measured — whatever else this pass did read is not this repository's complexity. Not scored: no method bodies were exposed for those file kinds by any language model this pass could load. This is a gap in the analysis run, not a finding about this repository.
- D10 Test Quality — ~2872 lines of test source are present (.dart, .js) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included
- D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (package.json and a Dart pubspec.yaml), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
- D15 Churn × Complexity Hotspots — complexity unreadable for .dart, .java — churn × complexity hotspots could not be measured
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D2 Cognitive Complexity — Most of this repository's production source (.dart, .java) had no cognitive complexity computed for it, so cognitive complexity was not measured — whatever else this pass did read is not this repository's complexity. Not scored: no method bodies were exposed for those file kinds by any language model this pass could load. This is a gap in the analysis run, not a finding about this repository.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D22 Internal API Consistency — No exposed public API
- D23 Boundary Type-Coupling — Production source is present (.dart, .java, .kt, .swift) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — No inline comments to assess — comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D3 God Classes — Most of this repository's production source (.dart, .java) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (package.json and a Dart pubspec.yaml — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
- D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .dart, .java, .kt, .swift, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- D9 Test Distribution — Test source is present (.dart, .js) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- DM1 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
- 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
- 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
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
- GD1 Unfinished & placeholder code — no source files
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
- P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
- PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
- PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
Issue — 58 finding(s)
D38 · OSV Dependency Vulnerabilities
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
- High CVE: [GHSA redacted] package-lock.json
D29 · Static Analysis (SAST)
- High: github-actions-mutable-action-tag .github/workflows/flutter_1_12_13.yml:16
- High: github-actions-mutable-action-tag .github/workflows/flutter_1_12_13.yml:17
- High: github-actions-mutable-action-tag .github/workflows/flutter_1_17_3.yml:16
- High: github-actions-mutable-action-tag .github/workflows/flutter_1_17_3.yml:17
- High: github-actions-mutable-action-tag .github/workflows/flutter_1_20_4.yml:16
- High: github-actions-mutable-action-tag .github/workflows/flutter_1_20_4.yml:17
- High: github-actions-mutable-action-tag .github/workflows/flutter_1_22_4.yml:16
- High: github-actions-mutable-action-tag .github/workflows/flutter_1_22_4.yml:17
- High: github-actions-mutable-action-tag .github/workflows/main.yml:18
- High: github-actions-mutable-action-tag .github/workflows/main.yml:19
D38 · OSV Dependency Vulnerabilities
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
- Critical CVE: [GHSA redacted] package-lock.json
D38 · OSV Dependency Vulnerabilities
- High vulnerability: [GHSA redacted] package-lock.json
- High vulnerability: [GHSA redacted] package-lock.json
- High vulnerability: [GHSA redacted] package-lock.json
D31 · IaC & Container Security
- High IaC: DS-0002 fair_online/fair_online_service/Dockerfile
D38 · OSV Dependency Vulnerabilities
- Critical vulnerability: [GHSA redacted] package-lock.json
Warning — 11 finding(s)
D38 · OSV Dependency Vulnerabilities
- Medium CVE: [GHSA redacted] package-lock.json
- Medium CVE: [GHSA redacted] package-lock.json
- Medium CVE: [GHSA redacted] package-lock.json
D29 · Static Analysis (SAST)
- Medium: unencrypted-socket fair/android/src/main/v8/com/eclipsesource/v8/debug/V8DebugServer.java:161
- Medium: wildcard-postmessage-configuration fair_online/fair_online/web/scripts/frame.js:87
D35 · Change Coupling
- Change coupling: FairFfi.java ↔ FairV8JsLoader.java fair/android/src/main/java/com/wuba/fair/channel/FairFfi.java
- Change coupling: fair_ast_gen.dart ↔ fair_dsl_gen.dart dart2dsl/lib/fairdsl/fair_ast_gen.dart
D16 · Bus Factor
- dormant codebase — no living knowledge left to concentrate
D31 · IaC & Container Security
- Medium IaC: CKV_DOCKER_3 fair_online/fair_online_service/Dockerfile:1
D36 · Supply-chain Provenance & Signing
- Unpinned build actions
D36 · Supply-chain Provenance & Signing
- Workflow token permissions not restricted
Recommendation — 10 finding(s)
D34 · Knowledge Freshness
- Largest orphaned file test_case/flutter_libs_app/lib/google_fonts/fair_google_fonts.dart
- Largest orphaned file flutter_version/flutter_1_22_4/lib/src/widgets/$$m.dart
- Largest orphaned file flutter_version/flutter_1_22_6/lib/src/widgets/$$m.dart
D11 · Test Reliability
- Test reliability not included
D15 · Churn × Complexity Hotspots
- complexity unreadable for .dart, .java — churn × complexity hotspots could not be measured
D31 · IaC & Container Security
- Low IaC: DS-0026 fair_online/fair_online_service/Dockerfile
D34 · Knowledge Freshness
- Dormant codebase
D36 · Supply-chain Provenance & Signing
- No build provenance
D36 · Supply-chain Provenance & Signing
- No SBOM
D8 · Code Coverage
- Coverage not included — suite not readable by the collector
Info — 2 finding(s)
D12 · Dependency Hygiene
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D22 · Internal API Consistency
- No exposed public API
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off . | 12 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (no readable dependency manifest) | — | none (no readable dependency manifest): not present in this environment | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess. | 0 | — |
| D33 · JS/npm Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 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 | — |
| D38 · OSV Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive . | 76 | artifacts/raw/osv-scanner.json |
| 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 | — |