Public report — Everdue, published 6 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
Medium · 86,489 LoC · 352 projects · rebuild ~2.7 person-years · weakest lens: Domain Modelling (40%)
Degraded — solution could not be loaded
The C# solution could not be loaded in the analyzer (the workspace returned 0 projects), so every compiler-dependent dimension ran on nothing and the size/effort figures were estimated directly from source text. This run is Degraded — treat the grade as indicative only. See diagnostics.md for the exact cause (which solution project references resolved vs were missing, a structure map of the analyzed tree, and the solution/project files), then re-run for a reliable result.
Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸
780findings with an exact file:lineof 838 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
88/115dimensions across the health lenses86489 LoC · 352 projects — wide & deep
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.
Everdue/cms is in a workable but fragile state (54%). It is not in crisis, but it carries material risk that makes change slower and incidents harder to contain if left unaddressed.
It is strongest in Maturity (87%) — it's well-documented and easy to pick up. Readiness (85%) is solid too.
The area that most needs attention is Domain Modelling (40%) — the domain model leaks and drifts, so business rules are harder to trust and change. Performance (60%) is the next concern — it raises ongoing delivery and operational cost.
Leadership focus, highest impact first: Reference other aggregates by their strongly-typed id (Aggregate boundaries); strongly-typed ids across the domain (Strongly-typed ids); Move business rules onto the aggregates/entities they govern… (Rich vs anemic model).
For scale: Medium (~86,489 production lines); rebuilding it from scratch would take roughly ~2.7 person-years (~1–6 engineers). Approximate, ±~30%.
It builds on a genuinely strong Maturity foundation (87%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
~367 LoC unreachable (2 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~2.7 person-years of build effort (about ~€390,000 to rebuild). Its weakest lens is Domain Modelling at 40% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.5) — service/app, CQRS, domain model, high decision density × a 0.8× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source (the solution did not build in-analyzer). Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~2.7 person-years to rebuild), and its weakest lens is Domain Modelling at 40%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Domain Modelling first — highest risk-reduction per euro on an asset this size.
Root cause: an un-encapsulated domain · Medium · Root cause
123 findings across public setters, anemic types and primitive ids share one root cause — the domain layer doesn't protect its own invariants. Fixing the encapsulation pattern resolves them together, rather than chasing each finding.
→ Address encapsulation as one pattern (private setters + behaviour + strongly-typed ids), not 100 separate findings.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
Architecture — bounded-context dependency graph
Each box is a bounded context (its layer projects grouped, or a project count when large); arrows show dependencies between contexts. A shared kernel is where many arrows converge.
Architecture — module dependency matrix
849 modules, 3493 dependencies — 13 dependency cycles, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
48
High / Critical
A05:2021 — Security Misconfiguration
9
Medium
A06:2021 — Vulnerable & Outdated Components
7
High / Critical
A02:2021 — Cryptographic Failures
3
High / Critical
Roadmap
First, ensure each aggregate references others only by strongly-typed IDs to maintain independent consistency boundaries. Next, complete the migration to strongly-typed IDs across the domain to prevent transposed-argument bugs. Then, move business rules onto the aggregates and entities they govern to enforce invariants at the source. Additionally, make entity setters private or init-only to ensure state changes only through invariant-enforcing methods. Finally, add a benchmarking harness for hot paths and run it in CI to catch performance regressions.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
Make entity setters private/init-only; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Raise allocation-aware density on the hot paths — currently 136 use(s) across 621,139 production line(s) (~0.2/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
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. 82 of 88 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 88 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 780 of 838 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
Solution could not be loaded — run is Degraded — The C# workspace did not read this repository's production source, so every compiler-dependent dimension ran on estimated input. Treat the grade as indicative only; diagnostics.md records the exact cause.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
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.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality 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.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value (WHY vs WHAT) is an LLM judgement over a bounded sample — it is advisory and cannot weigh a comment against the precise code change it was written to explain.
D25 ADR Conformance: ADR conformance is the LLM-scored fraction of sampled code that follows recorded decisions — it checks the decisions that were written down and the slices it sampled, not unrecorded rules or the whole tree.
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 the advisory database — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen.
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.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them.
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.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
DM4 Rich vs anemic 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.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (7): D19, D20, D21, D24, D25, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
+ 26 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.6 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
Of 7 mechanizable ADRs, 4 are prevented by analyzers, 3 by tests, 0 exist only in prose. Coverage: 100 %. Cycles found: 0.
✓ On the Gold path — maintain.
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
4092 test methods: 4092 unit, 0 integration, 0 BDD, 0 e2e.
Tests co-located / outside the solution
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
242 skipped (242 with a documented reason), 8 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4092 tests.
No assertions: ValidateUnitExists_accepts_unit_group_id_directly · ×8backend/src/Master/Features/DataContexts/CreateDataContext/Tests.cs:442
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with everdue-realm.json. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.8 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
68 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is backend/src/Enduser/Enduser.Database/Insight/DashboardDataEngine.cs.
Off-boarding risk: anonymized user #1 · ×3
What to do
Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
Everdue's documentation is strong and well-structured: a clear three-tier architecture table plus an exhaustive Quick Links section mapping every tier to its own README, a project-structure outline, and deployment scripts for each role (Master, Partner, Enduser) covering both provisioning and shipping. The README files alone exceed 2000 words with detailed architecture docs, and the XML-doc coverage is strong across most tiers (e.g. GetSyncStatus at 0% is an unshown section in a clipped file). Everdue's documentation is strong and well-organized: the front door (Documentation Index) links to a three-system architecture, domain glossary, and an onboarding guide, while the CMS backend README covers quick start, project structure, daily workflow, local development, database migrations, and a migration-addition walkthrough. The infrastructure docs describe Scaleway/Kubernetes deployment with GitHub Actions; both are solid. However, XML-doc coverage is low across most Enduser features (e.g. CreateDataContext, DeleteDataContext) at 0%, leaving many API endpoints undocumented despite the README's strong structure. The documentation is comprehensive and well-structured for the main application families, covering API surface, database/tables, domain models, and XML coverage. The CMS telemetry stack README gives a clear overview of distributed tracing (Jaeger), metrics (Prometheus), visualization (Grafana), and production configuration examples for Datadog/AWS X-Ray/New Relic/Grafana Cloud; it also documents the OpenTelemetry Collector as the centralized pipeline. The E2E tests README is excellent: three-layer architecture with a directory layout, domain-action contracts, POM conventions, and a fixture pattern guide. However, the telemetry coverage for the Master/Partner APIs (e.g., GetSyncStatus, TriggerSync) is zero in XML docs despite being present in the master API coverage list, indicating gaps between the documentation and the codebase. Customer Onboarding & Invitation/Licensing is a well-structured reference for the federated three-tier model: it states status ('Code-grounded'), lists related docs, and maps each tier's onboarding flow (Master→Partner→Enduser) with an index table plus a diagram of the invitation-to-license-to-connection sync. The document is complete per its own outline and clearly explains ownership/relationship invariants for each system. Domain model documentation is well written and fully referenced (27 READMEs plus architecture docs), covering the Master template layer, Partner applications on read-only templates, and EndUser runtime instances with a glossary, template-to-reality mapping, and taxonomy primitives. The deployment docs are also solid: a three-role router map, an interactive quick-start wizard, and platform-specific deployment options (Scaleway Kapsule, Docker Compose). However the XML-doc coverage is extremely low across most domain layers — only 25/83 Enduser.Api/XML covers GetSyncStatus, TriggerSync, CreateDataContext, DeleteDataContext, GetDataContextsByType, UpdateDataContext, CreateElement, DeleteElement, GetElementsForSidebar, ReorderTopics, and AcceptClientInvitation (0% coverage) — leaving most domain features undocumented despite the thorough model docs. The architecture and ADR docs are comprehensive (74 markdown files plus XML coverage) covering four tiers (Master/Partner/Enduser/Shared), runtime models (SSO live updates, in-process messaging with outbox, data-catalog sync), security (tenancy, EF Core query filter), and a decision-records log. The C4 overview, three-systems framing, and cross-tier sync are well illustrated; the ADR template is practical for new decisions. However, the quality score sits below 7 because many visible documents cover only one topic (e.g., SSO live updates vs. SSE live updates), leaving readers to refer back to the index or a dedicated docs page to find full coverage of each tier and its interdependencies. Everdue on canine-wrx1 is self-hosted and deployed as a blue/green multihost system with a detailed topology diagram showing the network layout (client → nginx → everdue-master → everdue-partner → everude-enduser) plus six ext/blue/green tiers. The document is excellent at conveying deployment, host roles, and cross-service relationships but lacks any architecture or API documentation for the application's core features. The project's documentation is strong and well-organized: the READMEs for each major package (Enduser.Api/Database/Domains, Master.Api/Database/Domains) cover their own coverage with detailed architecture, migration, and usage sections. The deployment README provides a clear quick-start docker-compose flow plus environment-variable guidance, and there are dedicated files documenting how migrations work across both master and partner stacks. However the XML-doc coverage is weak: only 30% of Enduser.Api methods (25/83) and no coverage for CreateDataContext/DeleteDataContext exists among the listed packages, leaving many API endpoints undocumented despite being covered by a README. Documentation is strong and well-structured for an API surface plus a design/contract layer: 27 README files (mostly Enduser.Api/Enduser.Database/Enduser.Domains) cover the exposed types with XML-doc coverage of ~30% per module, while the POM/FOM contract doc (the two main 'north-star' paths) is complete and clear. The i18n-check analyser README is a focused utility with excellent run-and-configure guidance. The READMEs are strong but the XML-doc coverage is weak: only 25/83 (Enduser.Api) to 0/49 (GetSyncStatus) across 17 features is non-zero for a feature set that is itself documented. The spike COMs document coverage as a HARD REQUIREMENT, and the database/migrations README enforces backwards compatibility with a concrete table; the master features README shows structure and guidelines but no XML docs. The documentation is strong for the shared-components and features/README structures (27 READMEs plus architecture docs), but XML-doc coverage across Enduser and Master APIs is thin: only GetSyncStatus/TriggerSync and CreateDataContext are at zero coverage. The master store README covers createStore/createSignal usage with feature-store examples, while the enduser features README outlines a self-contained module pattern.
The three-tier table lists Master, Partner, Enduser but does not explain how the Partner connects to Master or what happens after invitation sync.docs/architecture/three-systems.md
The three-tier table does not mention the data-modeling layer (Master's Data Collection & Taxonomy) or how it is consumed by Partner and Enduser.docs/architecture/three-systems.md
The body of this README is a deployment diagram with no description of the Everdue application itself (features, data models, endpoints).README.md
No architecture or API documentation for the core Everdue application.README.md
The feature-store example uses interface MyFeatureState with an initial value, but no guidance on deriving the default from the type.apps/master/src/shared/store/README.md
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 The three-tier table lists Master, Partner, Enduser but does not explain… finding(s) in Documentation Quality — start with three-systems.md. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 The three-tier table does not mention the data-modeling layer (Master's… finding(s) in Documentation Quality — start with three-systems.md. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 The body of this README is a deployment diagram with no description of… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
39 domain type(s) cross context boundaries across 6 contexts.
Cross-context type ImportRowResult (Enduser → Shared) · ×3
Cross-context type ImportMapping (Enduser → Shared) · ×2
Cross-context type DataContextMessage (Master → Partner)
Cross-context type ElementMessage (Master → Partner)
Cross-context type TagMessage (Master → Partner)
+ 17 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D24 · Comment Value / 10Exemplary◐ Sampled · advisory
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Judged by language model at low temperature (0.0-0.1) on deterministically sampled inline comments with surrounding code; findings verified back to sampled comments by substring match. Advisory, sampled.
What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.
Method: Judged by language model at low temperature against ADRs plus a deterministic structural code summary; findings linked to repo-rooted ADR paths for traceability. Advisory.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
Secret: generic-api-keybackend/src/Master/Master.Database/Extensions/SeedDataExtensions.cs:71detected by gitleaks finding
Rotate the exposed credentials — git history can't be un-committed
What to do
Resolve the 1 Secret finding(s) in Secrets (history) — start with SeedDataExtensions.cs. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
High: dependabot-missing-cooldown · ×14.github/dependabot.yml:4detected by semgrep finding
Medium: wildcard-postmessage-configuration · ×3frontend/apps/translator/src/components/PreviewPane.tsx:21detected by semgrep finding
Low: request-host-used · ×31deployment/wrx1/edge/install-edge-vhosts.sh:65detected by semgrep finding
What to do
Resolve the 31 Low finding(s) in Static Analysis (SAST) — start with install-edge-vhosts.sh (31). — One of this dimension's main actionable groups (31 recommendation-level).
Resolve the 14 High finding(s) in Static Analysis (SAST) — start with promote-prod-wrx1.yml (4), build-images.yml (3), ci.yml (3). — One of this dimension's main actionable groups (14 issue-level).
Resolve the 3 Medium finding(s) in Static Analysis (SAST) — start with PreviewPane.tsx (2), i18n-bridge.ts. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependencies have known published vulnerabilities (CVEs), direct or transitive.
Method: NuGet CVE scan via dotnet list package --vulnerable including transitive; severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer. Exhaustive, deterministic; degrades when absent.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
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 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Resolve the 1 No artifact signing finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
High CVE: [GHSA redacted] · ×3frontend/bun.lockdetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×2frontend/bun.lockdetected by osv-scanner finding
Medium vulnerability: [GHSA redacted]bun.lockdetected by osv-scanner finding
Low CVE: [GHSA redacted]bun.lockdetected by osv-scanner finding
What to do
Resolve the 3 High CVE finding(s) in OSV Dependency Vulnerabilities — start with bun.lock (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 Medium CVE finding(s) in OSV Dependency Vulnerabilities — start with bun.lock (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Medium vulnerability finding(s) in OSV Dependency Vulnerabilities — start with bun.lock. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
Resolve the 1 No AppArmor/SELinux confinement finding(s) in Kernel & Syscall Confinement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Do you agree with this assessment?
AC2 · Forms & labels4.6 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×4) — AssigneePopover.tsx:262, DataContextInput.tsx:146, DataCollectionTable.tsx:84, …
This UI-library field component has no label / aria-label / aria-labelledby / id / name — and neither does anything it renders — so it likely renders an unlabelled control. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — SurveyLandingView.tsx:440
This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. (×5) — CompanyUsersView.tsx:412, InviteUserSheet.tsx:189, ComponentSettingsDrawer.tsx:1020, …
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×15) — OwnershipEditor.tsx:342, OwnershipEditor.tsx:367, ImportWizard.tsx:317, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure7.9 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — HomePage.tsx:148, SelectPage.tsx:29
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×10) — ElementItemImageEditor.tsx:81, ElementTypeDetailsView.tsx:246, OperationsTasksTab.tsx:178, …
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. — ComboBox.tsx:132
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add vitest-axe to verify at runtime, then gate it in CI.
What to do
Accessibility linting is already configured — assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code — check that business logic isn't leaking into the application/infrastructure layers (a thin domain is the anemic-domain smell).
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`SyncService` is a singleton (one shared instance) but mutates instance state outside any lock (NextSyncAt, IsSyncing, LastSyncAt, LastSyncError, LastSyncFailedAt, LastSyncRecordCount; e.g. `NextSyncAt` at line 81). — SyncService.cs:37
`SupportSyncService` is a singleton (one shared instance) but mutates instance state outside any lock (NextSyncAt, IsSyncing, LastSyncError, LastSyncFailedAt, LastSyncAt; e.g. `NextSyncAt` at line 56). (×2) — SupportSyncService.cs:21, SupportSyncService.cs:21
`SyncService` is a singleton (one shared instance) but mutates instance state outside any lock (NextSyncAt, IsSyncing, LastSyncError, LastSyncFailedAt, LastSyncAt, LastSyncRecordCount; e.g. `NextSyncAt` at line 70). — SyncService.cs:26
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface member counts; fat-interface threshold (over 15 members) flagged per type. Deterministic, type-level.
Do you agree with this assessment?
AX7 · Slice cohesion7.8 / 10Strong✓ Tool-verified
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`SyncDependencies` (slice 'Enduser') depends on `SyncFileService` from slice 'SyncFileService'. — SyncService.cs:185
`ContextBindingResult` (slice 'Auth') depends on `CachedSession` from slice 'Authentication'. — OpaqueTokenAuthHandler.cs:222
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
`CreateNextVersionApplication.Feature` is a read (query) handler but its body writes persistent state — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — Feature.cs:25
`DuplicateApplication.Feature` is a read (query) handler but its body writes persistent state — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — Feature.cs:19
`DuplicateTopic.Feature` is a read (query) handler but its body writes persistent state — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — Feature.cs:12
`DuplicateQuestion.Feature` is a read (query) handler but its body writes persistent state — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — Feature.cs:20
`SubmitSurveyAnswers.Feature` is a read (query) handler but its body writes persistent state — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — Feature.cs:12
`ListAvailableSystemRoles.Feature` is a read (query) handler but its body writes persistent state — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — Feature.cs:10
`ListRoles.Feature` is a read (query) handler but its body writes persistent state — a query must stay side-effect-free so reads are safe to retry, cache, and route to a read replica. — Feature.cs:11
What to do
Keep query handlers read-only — move the writes/event-publishes into a command handler so reads stay safe to retry, cache, and route to a read replica.
Do you agree with this assessment?
C1 · Data Protection10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
No in-app HTTPS enforcement, but ForwardedHeaders / 127.0.0.1 binding indicates a reverse-proxy topology — adding UseHttpsRedirection in the app would be wrong in this layout. Verify the reverse proxy enforces TLS. — Program.cs:368
What to do
Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Do you agree with this assessment?
C3 · Audit Trail10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
C4 · Data Retention10.0 / 10Exemplary✓ Tool-verified
Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).
Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.
Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.
Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.
Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.
`OwnershipPeriod` references the aggregate root `ElementInstance` directly (via `OwnedInstance`) — hold its `ElementInstanceId` instead. — OwnershipPeriod.cs:21
`ElementCollectionFrequency` references the aggregate root `Kpi` directly (via `Kpi`) — hold its `KpiId` instead. — ElementCollectionFrequency.cs:44
`Kpi` references the aggregate root `KpiProjectLink` directly (via `KpiProjectLinks`) — hold its `KpiProjectLinkId` instead. — Kpi.cs:141
`Kpi` references the aggregate root `DataCollectionEntry` directly (via `DataCollectionEntries`) — hold its `DataCollectionEntryId` instead. — Kpi.cs:142
`Kpi` references the aggregate root `KpiTarget` directly (via `Targets`) — hold its `KpiTargetId` instead. — Kpi.cs:145
`KpiProjectLink` references the aggregate root `Kpi` directly (via `Kpi`) — hold its `KpiId` instead. — KpiProjectLink.cs:37
`KpiProjectLink` references the aggregate root `Project` directly (via `Project`) — hold its `ProjectId` instead. — KpiProjectLink.cs:38
`KpiTarget` references the aggregate root `Kpi` directly (via `Kpi`) — hold its `KpiId` instead. — KpiTarget.cs:36
`Project` references the aggregate root `StrategicPlan` directly (via `StrategicPlan`) — hold its `StrategicPlanId` instead. — Project.cs:23
`Project` references the aggregate root `KpiProjectLink` directly (via `KpiProjectLinks`) — hold its `KpiProjectLinkId` instead. — Project.cs:26
`StrategicPlan` references the aggregate root `Project` directly (via `Projects`) — hold its `ProjectId` instead. — StrategicPlan.cs:21
`SurveyDispatch` references the aggregate root `SurveyInvitation` directly (via `Invitations`) — hold its `SurveyInvitationId` instead. — SurveyDispatch.cs:17
`SyncedApplication` references the aggregate root `SyncedTopic` directly (via `Topics`) — hold its `SyncedTopicId` instead. — SyncedApplication.cs:39
`SyncedQuestion` references the aggregate root `SyncedTopic` directly (via `Topic`) — hold its `SyncedTopicId` instead. — SyncedQuestion.cs:28
`SyncedTopic` references the aggregate root `SyncedApplication` directly (via `Application`) — hold its `SyncedApplicationId` instead. — SyncedTopic.cs:30
`SyncedTopic` references the aggregate root `SyncedQuestion` directly (via `Questions`) — hold its `SyncedQuestionId` instead. — SyncedTopic.cs:31
`DataContext` references the aggregate root `UnitGroup` directly (via `QuantitativeUnitGroup`) — hold its `UnitGroupId` instead. — DataContext.cs:34
`DataContext` references the aggregate root `UnitGroup` directly (via `DerivedUnitGroup`) — hold its `UnitGroupId` instead. — DataContext.cs:35
`DataContext` references the aggregate root `Tag` directly (via `Tags`) — hold its `TagId` instead. — DataContext.cs:39
`Element` references the aggregate root `Comment` directly (via `Comments`) — hold its `CommentId` instead. — Element.cs:21
`Element` references the aggregate root `Attachment` directly (via `Attachments`) — hold its `AttachmentId` instead. — Element.cs:22
`Element` references the aggregate root `Tag` directly (via `Tags`) — hold its `TagId` instead. — Element.cs:23
`Element` references the aggregate root `ActivityLog` directly (via `ActivityLogs`) — hold its `ActivityLogId` instead. — Element.cs:24
`UnitGroup` references the aggregate root `Comment` directly (via `Comments`) — hold its `CommentId` instead. — UnitGroup.cs:18
`UnitGroup` references the aggregate root `Attachment` directly (via `Attachments`) — hold its `AttachmentId` instead. — UnitGroup.cs:19
`UnitGroup` references the aggregate root `ActivityLog` directly (via `ActivityLogs`) — hold its `ActivityLogId` instead. — UnitGroup.cs:20
`Application` references the aggregate root `Topic` directly (via `Topics`) — hold its `TopicId` instead. — Application.cs:38
`Question` references the aggregate root `Topic` directly (via `Topic`) — hold its `TopicId` instead. — Question.cs:28
`Question` references the aggregate root `Comment` directly (via `Comments`) — hold its `CommentId` instead. — Question.cs:31
`Question` references the aggregate root `Attachment` directly (via `Attachments`) — hold its `AttachmentId` instead. — Question.cs:32
`Question` references the aggregate root `ActivityLog` directly (via `ActivityLogs`) — hold its `ActivityLogId` instead. — Question.cs:33
`SyncedDataContext` references the aggregate root `SyncedUnitGroup` directly (via `QuantitativeUnitGroup`) — hold its `SyncedUnitGroupId` instead. — SyncedDataContext.cs:33
`SyncedDataContext` references the aggregate root `SyncedUnitGroup` directly (via `DerivedUnitGroup`) — hold its `SyncedUnitGroupId` instead. — SyncedDataContext.cs:34
`Topic` references the aggregate root `Application` directly (via `Application`) — hold its `ApplicationId` instead. — Topic.cs:35
`Topic` references the aggregate root `Question` directly (via `Questions`) — hold its `QuestionId` instead. — Topic.cs:36
`Topic` references the aggregate root `Comment` directly (via `Comments`) — hold its `CommentId` instead. — Topic.cs:37
`Topic` references the aggregate root `Attachment` directly (via `Attachments`) — hold its `AttachmentId` instead. — Topic.cs:38
`Topic` references the aggregate root `ActivityLog` directly (via `ActivityLogs`) — hold its `ActivityLogId` instead. — Topic.cs:39
`OrganizationInvitation` references the aggregate root `Organization` directly (via `Organization`) — hold its `OrganizationId` instead. — OrganizationInvitation.cs:20
`Organization` references the aggregate root `Team` directly (via `Teams`) — hold its `TeamId` instead. — Organization.cs:27
12 further occurrence(s) are not listed individually; the score already reflects all 52.
What to do
Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.
Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. Deterministic, adoption percentage.
Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.
`ApplicationExecution.ApplicationId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ApplicationExecution.cs:9
`ApplicationExecution.StartedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ApplicationExecution.cs:10
`ElementInstance.TemplateId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ElementInstance.cs:15
`ElementInstance.ExternalId` is a raw `String` — give it a strongly-typed id: a dedicated single-field type wrapping the `String`, in whatever form your language spells that. — ElementInstance.cs:23
`ElementInstance.CreatedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ElementInstance.cs:26
`OwnershipPeriod.OwnedInstanceId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — OwnershipPeriod.cs:14
`ImportJob.TargetId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ImportJob.cs:22
`ImportJob.CreatedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ImportJob.cs:52
`ImportProfile.TargetId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ImportProfile.cs:16
`ImportProfile.CreatedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ImportProfile.cs:18
`ImportProfile.LastModifiedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ImportProfile.cs:19
`TagAlias.SyncedTagId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — TagAlias.cs:13
`TagAlias.CreatedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — TagAlias.cs:15
`Notification.RecipientUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Notification.cs:25
`Notification.SourceId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Notification.cs:31
`Notification.ActorUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Notification.cs:34
`DataCollectionEntry.ElementInstanceId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — DataCollectionEntry.cs:19
`DataCollectionEntry.SubmittedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — DataCollectionEntry.cs:87
`ElementCollectionFrequency.ElementInstanceId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — ElementCollectionFrequency.cs:26
`Kpi.ApplicationExecutionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Kpi.cs:15
`Kpi.SourceActionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Kpi.cs:16
`Kpi.SourceQuestionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Kpi.cs:17
`Kpi.MasterDataContextId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Kpi.cs:18
`Kpi.LogoAttachmentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Kpi.cs:19
`Kpi.CreatedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Kpi.cs:84
`Kpi.StandingSubmittedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Kpi.cs:139
`OperationalTask.SourceActionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — OperationalTask.cs:11
`OperationalTask.SourceQuestionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — OperationalTask.cs:12
`OperationalTask.OwnerEntityId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — OperationalTask.cs:13
`OperationalTask.ThumbnailAttachmentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — OperationalTask.cs:27
`Project.SourceActionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Project.cs:12
`Project.SourceQuestionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Project.cs:13
`Project.LogoAttachmentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — Project.cs:14
`StrategicPlan.ApplicationExecutionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — StrategicPlan.cs:10
`StrategicPlan.SourceActionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — StrategicPlan.cs:11
`StrategicPlan.SourceQuestionId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — StrategicPlan.cs:12
`StrategicPlan.LogoAttachmentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — StrategicPlan.cs:13
`TaskStatusTransition.TaskId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — TaskStatusTransition.cs:33
`TaskStatusTransition.PerformedByUserId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — TaskStatusTransition.cs:47
`PartnerBranding.LogoAttachmentId` is a raw `Guid` — give it a strongly-typed id: a dedicated single-field type wrapping the `Guid`, in whatever form your language spells that. — PartnerBranding.cs:14
67 further occurrence(s) are not listed individually; the score already reflects all 107.
What to do
Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.
Do you agree with this assessment?
DM4 · Rich vs anemic model3.6 / 10Weak✓ Tool-verified
Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.
Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.
Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.
`ApplicationExecution` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ApplicationExecution.cs:6
`ElementInstance` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ElementInstance.cs:10
`OwnershipPeriod` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — OwnershipPeriod.cs:11
`ImportJob` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ImportJob.cs:14
`ImportProfile` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — ImportProfile.cs:11
`TagAlias` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — TagAlias.cs:10
`Notification` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Notification.cs:20
`KpiProjectLink` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — KpiProjectLink.cs:12
`KpiTarget` is an aggregate/entity with 12 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — KpiTarget.cs:15
`OperationalTask` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — OperationalTask.cs:8
`Project` is an aggregate/entity with 19 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Project.cs:7
`StrategicPlan` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — StrategicPlan.cs:7
`TaskStatusTransition` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — TaskStatusTransition.cs:21
`PartnerBranding` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — PartnerBranding.cs:10
`PersonalTask` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — PersonalTask.cs:10
`SubmittedAnswer` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SubmittedAnswer.cs:6
`SurveyDispatch` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SurveyDispatch.cs:5
`SurveyInvitation` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SurveyInvitation.cs:5
`SyncedApplication` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SyncedApplication.cs:10
`SyncedDashboard` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SyncedDashboard.cs:7
`SyncedDataContext` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×2) — SyncedDataContext.cs:20, SyncedDataContext.cs:14
`SyncedElement` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×2) — SyncedElement.cs:14, SyncedElement.cs:13
`SyncedQuestion` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SyncedQuestion.cs:10
`SyncedTag` is an aggregate/entity with 18 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SyncedTag.cs:11
`SyncedTopic` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SyncedTopic.cs:12
`SyncedUnitGroup` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×2) — SyncedUnitGroup.cs:6, SyncedUnitGroup.cs:12
`DataContext` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — DataContext.cs:11
`Element` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Element.cs:12
`Partner` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Partner.cs:6
`Tag` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Tag.cs:8
`UnitGroup` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — UnitGroup.cs:11
`Application` is an aggregate/entity with 14 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Application.cs:10
`Client` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Client.cs:6
`InsightDashboard` is an aggregate/entity with 12 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — InsightDashboard.cs:7
`PartnerBranding` is an aggregate/entity with 5 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — PartnerBranding.cs:10
`Question` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — Question.cs:12
`SyncedTag` is an aggregate/entity with 17 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — SyncedTag.cs:12
16 further occurrence(s) are not listed individually; the score already reflects all 56.
What to do
Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
Other · Domain Modelling — Whether entities protect their state (private/init-only setters) instead of exposing public setters that bypass invariants. Softened when a rehydration framework (Marten/EF) is present.
Method: Roslyn (DDD-gated): public setters on entities detected; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
14 further occurrence(s) are not listed individually; the score already reflects all 54.
What to do
Make entity setters private/init-only; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.
Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.
Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.
Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.
Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.
`CreateDataContext.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:24
`CreateElement.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:20
`CreatePartner.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:19
`InvitePartner.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:23
`CreateUnitGroup.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:19
`CreateApplication.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:21
`CreateTopic.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:22
`CreateClient.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:18
`InviteClient.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:23
`CreateInsightDashboard.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:18
`CreateQuestion.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:23
`UpdateQuestion.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:26
`AcceptParentInvitation.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:19
`CreateApiKey.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:17
`AssignApplication.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:26
`AssignQuestion.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:16
`AssignTopic.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:16
`StartSurveyDispatch.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:33
`GrantAssignment.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:25
`AddComment.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:25
`CreateTeam.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:17
`InviteToOrganization.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:23
`InviteToTeam.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:22
`ToggleUserActive.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:16
`CreateEnduserElementItem.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:18
`CreatePersonalTask.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:18
`ApproveSupportTicket.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:22
`CreateSupportTicket.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:26
`RejectSupportTicket.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:22
`ReviewSupportTicket.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:22
`CreateOperationalTask.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:26
`CreateProjectTask.Feature.Execute` mutates persistent state (a database save) with no visible idempotency guard. Under a client retry or at-least-once redelivery a re-run could double-apply it — confirm it's safe to re-run, or add an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write. — Feature.cs:19
What to do
Make retry-prone mutations idempotent — guard each write with an exists/dedup check, an upsert, an idempotency-key/inbox, or a versioned write, so a re-run doesn't double-apply.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A placeholder string ("acme@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. (×8) — Tests.cs:104, Tests.cs:88, Tests.cs:97, …
A placeholder string ("MixedCase@Example.Com") is still in shipped code — typical of generated boilerplate that was never filled in. (×2) — Tests.cs:138, Tests.cs:160
A placeholder string ("mixedcase@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. (×2) — Tests.cs:147, Tests.cs:169
A placeholder string ("mine@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — Tests.cs:333
A placeholder string ("theirs@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — Tests.cs:334
A placeholder string ("client@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — Tests.cs:96
A placeholder string ("other@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — Tests.cs:358
A placeholder string ("NEW@Example.COM") is still in shipped code — typical of generated boilerplate that was never filled in. — Tests.cs:241
A placeholder string ("new@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — Tests.cs:252
A placeholder string ("noreply@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. (×2) — DependencyInjection.cs:26, SmtpOptions.cs:9
A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. — OutboxWriter.cs:45
A placeholder string ("User@Example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — Tests.cs:852
A placeholder string ("user@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. (×2) — Tests.cs:852, Tests.cs:853
A placeholder string ("Invitee@Example.COM") is still in shipped code — typical of generated boilerplate that was never filled in. — Tests.cs:44
What to do
Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
`ApplyRowAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — ElementImportProcessor.cs:352
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×2) — MessageBus.cs:137, CompressionMiddleware.cs:153
What to do
Clear the softer debt: remove commented-out code and dead branches, re-enable or delete skipped tests, and replace blanket warning suppressions with targeted ones.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a 'Testing' section to the root README — how to run the test suite.
Add a README to the 352 of 352 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Only 27/342 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 342, 3 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Do you agree with this assessment?
P5 · DR & Backup10.0 / 10Exemplary✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
Readiness · Performance — Whether the library protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
No benchmark suite was found. Where code is performance-sensitive, a benchmark guards against silent regressions — but it's a bonus here, not a deduction.
What to do
Add a benchmarking harness for the hot paths and run it in CI to catch regressions (for .NET, a BenchmarkDotNet project with [MemoryDiagnoser] to track allocations).
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Raise allocation-aware density on the hot paths — currently 136 use(s) across 621,139 production line(s) (~0.2/1k). More Span/Memory, pooling (ArrayPool/ObjectPool), stackalloc and ValueTask on the allocation-heavy paths climbs this toward 10.
Readiness · Performance — Whether asynchronous code keeps its host responsive — a library awaits with ConfigureAwait(false) (so it never captures and stalls the host's context) and avoids sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) that wastes threads and risks deadlock.
Method: Production-source scan: sync-over-async blocking (.Wait()/.GetAwaiter().GetResult()) counted everywhere, and — for a library with ≥5 awaits — the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
3 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock in a consumer with a synchronization context.
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult() in library code.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).
Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.
frontend/apps/enduser/src/features/company/company-team-details/state.ts:126 · frontend/apps/master/src/features/company/company-team-details/state.ts:126 · frontend/apps/partner/src/features/company/company-team-details/state.ts:126 — the 3 copies are spread across 3 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same names written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — state.ts:126
frontend/apps/enduser/src/features/company/company-users/state.ts:170 · frontend/apps/master/src/features/company/company-users/state.ts:171 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same names written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — state.ts:170
frontend/apps/partner/src/features/applications/question-editor/state.ts:992 · frontend/apps/partner/src/features/applications/topic-create/state.ts:348 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — state.ts:992
frontend/apps/enduser/src/features/applications/run-application/state.ts:563 · frontend/apps/enduser/src/features/kpi-details/state.ts:158 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — state.ts:563
frontend/apps/partner/src/features/templates/elements/request-support-sheet/state.ts:131 · frontend/apps/partner/src/features/templates/tags/request-support-sheet/state.ts:125 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — state.ts:131
frontend/apps/partner/src/features/templates/data-contexts/request-support-sheet/state.ts:139 · frontend/apps/partner/src/features/templates/elements/request-support-sheet/state.ts:129 · frontend/apps/partner/src/features/templates/tags/request-support-sheet/state.ts:123 · frontend/apps/partner/src/features/templates/units/request-support-sheet/state.ts:130 — 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. — state.ts:139
frontend/apps/enduser/src/features/support/support-overview/state.ts:22 · frontend/apps/partner/src/features/support/support-overview/state.ts:22 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — state.ts:22
frontend/apps/partner/src/features/applications/question-editor/state.ts:954 · frontend/apps/partner/src/features/applications/topic-create/state.ts:336 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — state.ts:954
What to do
Extract the duplicated blocks into shared functions/components.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
frontend/apps/enduser/src/features/applications/run-application/components/drawers/ConfigureElementModal.tsx:8 imports frontend/apps/enduser/src/features/elements/element-type-details/components/ElementTypeDetailsView.tsx against the feature-sliced rules. — ConfigureElementModal.tsx:8
frontend/apps/enduser/src/features/applications/run-application/components/drawers/ConfigureElementModal.tsx:9 imports frontend/apps/enduser/src/features/elements/element-type-details/state.ts against the feature-sliced rules. — ConfigureElementModal.tsx:9
frontend/apps/enduser/src/features/applications/run-application/components/drawers/ConfigureKpiEditDrawer.tsx:17 imports frontend/apps/enduser/src/features/shared-operations/components/KpiElementFrequencySection.tsx against the feature-sliced rules. — ConfigureKpiEditDrawer.tsx:17
frontend/apps/enduser/src/features/applications/run-application/components/drawers/ConfigureProjectEditDrawer.tsx:3 imports frontend/apps/enduser/src/features/shared-operations/components/EditEntitySheet.tsx against the feature-sliced rules. — ConfigureProjectEditDrawer.tsx:3
frontend/apps/enduser/src/features/applications/run-application/components/drawers/ConfigureStrategicPlanEditDrawer.tsx:3 imports frontend/apps/enduser/src/features/shared-operations/components/EditEntitySheet.tsx against the feature-sliced rules. — ConfigureStrategicPlanEditDrawer.tsx:3
frontend/apps/enduser/src/features/elements/element-type-details/components/ElementItemSheet.tsx:28 imports frontend/apps/enduser/src/features/shared-operations/components/ElementKpiFrequencySection.tsx against the feature-sliced rules. — ElementItemSheet.tsx:28
frontend/apps/enduser/src/features/elements/element-type-details/components/ElementTypeDetailsView.tsx:26 imports frontend/apps/enduser/src/features/imports/ImportWizard.tsx against the feature-sliced rules. — ElementTypeDetailsView.tsx:26
frontend/apps/enduser/src/features/kpi-details/components/KpiDetailsView.tsx:12 imports frontend/apps/enduser/src/features/applications/run-application/components/drawers/ConfigureKpiEditDrawer.tsx against the feature-sliced rules. — KpiDetailsView.tsx:12
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
Branch-heavy code is where defects cluster — extract decisions into smaller functions. (×8) — analyser.ts:285, generate-endpoints-registry.ts:92, state.ts:216, …
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.9 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.2 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
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) — ApiTesterPage.tsx, FormulaBuilderPage.tsx, LocalizedInputPage.tsx, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code7.9 / 10Strong✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
4 file(s) (~244 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: frontend/packages/config-env/src/index.ts imports './validator.tsx', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — config-env
Unreachable from the 955 application, 19 tooling and 516 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 (955 application, 19 tooling, 516 test roots considered) (×2) — cookie-debug.ts, OperationsEntityHeader.tsx
Nothing imports this binding — it is safe to review for removal. (×4) — ApplicationsOverviewView.tsx:295, ApplicationsPartnerSelectView.tsx:113, state.ts:68, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in the root package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing. (×2)
Declared in frontend/packages/dev-dependencies/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing.
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Transport security, security headers, secure cookies, input validation, middleware order and crypto hygiene (presence, not runtime).
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×3) — Program.cs:672, Program.cs:642, Program.cs:662
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage.
Only 1101/4574 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×11) — InMemoryConnectionManager.cs:205, InMemoryConnectionManager.cs:227, ContentTypeValidationMiddleware.cs:94, …
No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. (×14) — Tests.cs:172, Tests.cs:190, Tests.cs:206, …
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.3 `!` suppressions per 1k syntax nodes — 1295 suppression(s) across the 4024869 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
What to do
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Not included — 27 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX4 Dependency direction — not applicable to a vertical-slice + CQRS architecture (the inward-dependency rule is for layered/clean styles)
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
D1 Cyclomatic Complexity — Most of this repository's production source (.ts, .tsx) 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.
D11 Test Reliability — Test reliability not measured — no test run produced results
D12 Dependency Hygiene — Dependency hygiene not measured — no packages were read
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .ts, .tsx, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D2 Cognitive Complexity — Most of this repository's production source (.ts, .tsx) 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.
D22 Internal API Consistency — No exposed public API
D27 Navigability — Most of this repository's production source (.ts, .tsx) was not read by navigability analysis, so tracing effort was not assessed — whatever else resolved (another language's projects) is not this repository's navigability. 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 (.ts, .tsx) 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.
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 — The target did not build, so no IL was available to measure.
D42 Runtime Threat Enforcement — The repository ships application workloads but no cluster-governance resources (CRDs, admission webhooks, or a committed policy engine). Runtime threat-detection (Falco/Tetragon) and admission control (Kyverno/OPA-Gatekeeper/PodSecurity) are cluster-OPERATOR controls owned by the platform, not shipped by an application repo/chart — nothing for this repo to assess.
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is mostly .ts, .tsx, which this pass does not read, so cohesion was not assessed for this repository. Not scored — this is a gap in the analyzer, not a finding about this repository.
D8 Code Coverage — Coverage not measured — analyzer environment
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 120 event handler(s); 314 CQRS handler(s)
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
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.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) 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
R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D33 (JS/npm Dependency Vulnerabilities)
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X6 Hand-rolled structured-format parsing — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
X7 Silent fallback defaults — Reported, not scored — this card publishes what it found rather than grading it. Its content is the findings and the key metric above.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
High: dependabot-missing-cooldown .github/dependabot.yml:4— This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is. This configuration file has 3 such entries; one cooldown decision clears them all — reported once.
High: run-shell-injection .github/workflows/build-images.yml:163— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-images.yml:179— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/build-images.yml:192— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: gha-workflow-env-secret .github/workflows/ci.yml:16— A secret is exposed in the workflow-level `env:` block, making it available to every job and step in this workflow — including any untrusted code run in pull-request workflows. Scope secrets as narrowly as possible: prefer step-level `env:` so the secret is only available where it is actually needed. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is.
High: gha-workflow-env-secret .github/workflows/ci.yml:17— A secret is exposed in the workflow-level `env:` block, making it available to every job and step in this workflow — including any untrusted code run in pull-request workflows. Scope secrets as narrowly as possible: prefer step-level `env:` so the secret is only available where it is actually needed. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is.
High: run-shell-injection .github/workflows/ci.yml:49— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/dast.yml:34— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/deploy-preprod-wrx1.yml:53— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v4`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v4 --jq .sha`.
High: run-shell-injection .github/workflows/promote-prod-wrx1.yml:64— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/promote-prod-wrx1.yml:79— Using variable interpolation `${{...}}` with a workflow input in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/promote-prod-wrx1.yml:119— Using variable interpolation `${{...}}` with a workflow input / an expression value in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input / an expression value is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/promote-prod-wrx1.yml:129— Using variable interpolation `${{...}}` with a workflow input / an expression value in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. A workflow input / an expression value is not bounded by this step and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: run-shell-injection .github/workflows/release.yml:34— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
Boundary-crossing change coupling: insightAdapter.ts ↔ insightAdapter.ts frontend/apps/enduser/src/features/insight/insightAdapter.ts— `frontend/apps/enduser/src/features/insight/insightAdapter.ts` (context enduser) and `frontend/apps/partner/src/features/insight/insight-dashboard-detail/insightAdapter.ts` (context partner) sit in DIFFERENT parts of the tree yet change together 74% of the time (14 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: insightAdapter.ts ↔ componentConfig.ts frontend/apps/enduser/src/features/insight/insightAdapter.ts— `frontend/apps/enduser/src/features/insight/insightAdapter.ts` (context enduser) and `frontend/apps/partner/src/features/insight/insight-dashboard-detail/componentConfig.ts` (context partner) sit in DIFFERENT parts of the tree yet change together 70% of the time (16 of the 23 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: insightAdapter.ts ↔ ComponentConfigSheet.tsx frontend/apps/enduser/src/features/insight/insightAdapter.ts— `frontend/apps/enduser/src/features/insight/insightAdapter.ts` (context enduser) and `frontend/apps/partner/src/features/insight/insight-dashboard-detail/components/ComponentConfigSheet.tsx` (context partner) sit in DIFFERENT parts of the tree yet change together 63% of the time (17 of the 27 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: Program.cs ↔ Program.cs backend/src/Enduser/Enduser.Api/Program.cs— `backend/src/Enduser/Enduser.Api/Program.cs` (context Enduser) and `backend/src/Partner/Partner.Api/Program.cs` (context Partner) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: ComponentSettingsDrawer.tsx ↔ componentConfig.ts frontend/apps/enduser/src/features/insight/components/ComponentSettingsDrawer.tsx— `frontend/apps/enduser/src/features/insight/components/ComponentSettingsDrawer.tsx` (context enduser) and `frontend/apps/partner/src/features/insight/insight-dashboard-detail/componentConfig.ts` (context partner) sit in DIFFERENT parts of the tree yet change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: ComponentSettingsDrawer.tsx ↔ ComponentConfigSheet.tsx frontend/apps/enduser/src/features/insight/components/ComponentSettingsDrawer.tsx— `frontend/apps/enduser/src/features/insight/components/ComponentSettingsDrawer.tsx` (context enduser) and `frontend/apps/partner/src/features/insight/insight-dashboard-detail/components/ComponentConfigSheet.tsx` (context partner) sit in DIFFERENT parts of the tree yet change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: insightAdapter.ts ↔ sampleDataEngine.ts frontend/apps/enduser/src/features/insight/insightAdapter.ts— `frontend/apps/enduser/src/features/insight/insightAdapter.ts` (context enduser) and `frontend/apps/partner/src/features/insight/insight-dashboard-detail/sampleDataEngine.ts` (context partner) sit in DIFFERENT parts of the tree yet change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: Program.cs ↔ Program.cs backend/src/Enduser/Enduser.Api/Program.cs— `backend/src/Enduser/Enduser.Api/Program.cs` (context Enduser) and `backend/src/Master/Master.Api/Program.cs` (context Master) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Boundary-crossing change coupling: SyncEndpoints.cs ↔ Feature.cs backend/src/Partner/Partner.Api/Endpoints/SyncEndpoints.cs— `backend/src/Partner/Partner.Api/Endpoints/SyncEndpoints.cs` (context Partner) and `backend/src/Shared/Features/Applications/SubmitAnswer/Feature.cs` (context Shared) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
NoWarnInCsproj backend/Directory.Build.props:23— CS1591 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj backend/Directory.Build.props:23— CS1573 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj backend/Directory.Build.props:23— CS1570 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj backend/Directory.Build.props:23— CS1587 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
NoWarnInCsproj backend/Directory.Build.props:23— CS1574 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
D38 · OSV Dependency Vulnerabilities· High CVE · ×3
High CVE: [GHSA redacted] frontend/bun.lock— brace-expansion 5.0.8: [GHSA redacted] — upgrade to 5.0.9
High CVE: [GHSA redacted] bun.lock— postcss 8.5.6: [GHSA redacted] — postcss is not declared by the manifests that govern this lockfile: it is pulled in transitively here (the 8.5.18 this repo declares for it belongs to a separate install root and does not reach this one), so upgrade the dependency that requires it (or pin postcss to 8.5.12 with an `overrides` entry). This is 1 of 4 advisories with a published fix this scan raises against postcss 8.5.6, and their fixed versions do not agree — anything below 8.5.23 still leaves at least one of them open. Take this package to 8.5.23 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against postcss 8.5.6: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] bun.lock— rollup 4.53.3: [GHSA redacted] — rollup is not declared by the manifests that govern this lockfile: it is pulled in transitively here (the 4.61.0 this repo declares for it belongs to a separate install root and does not reach this one), so upgrade the dependency that requires it (or pin rollup to 4.59.0 with an `overrides` entry).
Leaked secret: signing-key deployment/wrx1/keycloak/everdue-realm.json:36— signing-key detected. Treat the value as compromised: it is readable by everyone who has ever had the repository, and deleting the line does not un-publish it. In order — (1) REVOKE it at whatever issued it and issue a replacement, which is the only step that actually closes the exposure; (2) load the replacement at run time from your platform's secret store or the process environment instead of from the tree, so no future value is committable; (3) remove the file or line and add its path to the repository's ignore rules, so it cannot come back; (4) if the value was ever live, purge it from the history as well, since a clone taken before the deletion still carries it. If this is instead a FIXTURE — key material generated for tests and valid nowhere — then the exposure is nil and the fix is to make that legible: generate it in test setup, or keep it under a test-data path, so a reader (and this scan) can tell it from the real thing.
Off the main sequence: CsvParsing — CsvParsing: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: MessageBus — MessageBus: abstractness 0.00, instability 0.01, distance 0.99 — zone of pain — concrete and depended on by 237 project(s), so it's rigid to change.
Off the main sequence: Shared.Database.Configurations — Shared.Database.Configurations: abstractness 0.02, instability 0.01, distance 0.97 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: Enduser.Database — Enduser.Database: abstractness 0.00, instability 0.04, distance 0.96 — zone of pain — concrete and depended on by 128 project(s), so it's rigid to change.
Off the main sequence: Enduser.Domains — Enduser.Domains: abstractness 0.06, instability 0.02, distance 0.93 — zone of pain — concrete and depended on by 129 project(s), so it's rigid to change.
Off the main sequence: Partner.Database — Partner.Database: abstractness 0.00, instability 0.08, distance 0.92 — zone of pain — concrete and depended on by 70 project(s), so it's rigid to change.
Off the main sequence: Master.Database — Master.Database: abstractness 0.00, instability 0.11, distance 0.89 — zone of pain — concrete and depended on by 47 project(s), so it's rigid to change.
Off the main sequence: Authentication — Authentication: abstractness 0.00, instability 0.13, distance 0.88 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: Email — Email: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: Encryption — Encryption: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: Middleware — Middleware: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: FileStorage — FileStorage: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Off the main sequence: Partner.Domains — Partner.Domains: abstractness 0.13, instability 0.03, distance 0.84 — zone of pain — concrete and depended on by 72 project(s), so it's rigid to change.
Off the main sequence: GitHub — GitHub: abstractness 0.17, instability 0.00, distance 0.83 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Off the main sequence: Master.Domains — Master.Domains: abstractness 0.13, instability 0.04, distance 0.83 — zone of pain — concrete and depended on by 52 project(s), so it's rigid to change.
Off the main sequence: Partner.Features.Common — Partner.Features.Common: abstractness 0.00, instability 0.18, distance 0.82 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: ParentSystem — ParentSystem: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: Shared.Domains — Shared.Domains: abstractness 0.22, instability 0.00, distance 0.77 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
Off the main sequence: Ports — Ports: abstractness 0.23, instability 0.00, distance 0.77 — zone of pain — concrete and depended on by 334 project(s), so it's rigid to change.
Hotspot: frontend/apps/enduser/src/features/insight/insightAdapter.ts frontend/apps/enduser/src/features/insight/insightAdapter.ts— frontend/apps/enduser/src/features/insight/insightAdapter.ts changed 31 times in last 90 days, max complexity 46. 1 of those changes was a fix/bug commit, and the other 30 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: frontend/apps/partner/src/features/insight/insight-dashboard-detail/components/ComponentConfigSheet.tsx frontend/apps/partner/src/features/insight/insight-dashboard-detail/components/ComponentConfigSheet.tsx— frontend/apps/partner/src/features/insight/insight-dashboard-detail/components/ComponentConfigSheet.tsx changed 49 times in last 90 days, max complexity 25. 8 of those changes were fix/bug commits, and the other 41 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: backend/src/Enduser/Enduser.Database/Insight/DashboardDataEngine.cs backend/src/Enduser/Enduser.Database/Insight/DashboardDataEngine.cs— backend/src/Enduser/Enduser.Database/Insight/DashboardDataEngine.cs changed 49 times in last 90 days, max complexity 21. 6 of those changes were fix/bug commits, and the other 43 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: frontend/apps/partner/src/features/insight/insight-dashboard-detail/insightAdapter.ts frontend/apps/partner/src/features/insight/insight-dashboard-detail/insightAdapter.ts— frontend/apps/partner/src/features/insight/insight-dashboard-detail/insightAdapter.ts changed 24 times in last 90 days, max complexity 25. 2 of those changes were fix/bug commits, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: frontend/apps/enduser/src/features/insight/components/ComponentSettingsDrawer.tsx frontend/apps/enduser/src/features/insight/components/ComponentSettingsDrawer.tsx— frontend/apps/enduser/src/features/insight/components/ComponentSettingsDrawer.tsx changed 23 times in last 90 days, max complexity 23. 2 of those changes were fix/bug commits, and the other 21 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: frontend/apps/enduser/src/features/elements/element-type-details/components/ElementItemSheet.tsx frontend/apps/enduser/src/features/elements/element-type-details/components/ElementItemSheet.tsx— frontend/apps/enduser/src/features/elements/element-type-details/components/ElementItemSheet.tsx changed 24 times in last 90 days, max complexity 15. 8 of those changes were fix/bug commits, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: frontend/apps/enduser/src/features/applications/run-application/components/steps/ResultStep.tsx frontend/apps/enduser/src/features/applications/run-application/components/steps/ResultStep.tsx— frontend/apps/enduser/src/features/applications/run-application/components/steps/ResultStep.tsx changed 21 times in last 90 days, max complexity 17. 4 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: frontend/apps/enduser/src/features/insight/components/InsightDashboardDetailView.tsx frontend/apps/enduser/src/features/insight/components/InsightDashboardDetailView.tsx— frontend/apps/enduser/src/features/insight/components/InsightDashboardDetailView.tsx changed 19 times in last 90 days, max complexity 17. 2 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: backend/src/Partner/Partner.Api/Endpoints/SyncEndpoints.cs backend/src/Partner/Partner.Api/Endpoints/SyncEndpoints.cs— backend/src/Partner/Partner.Api/Endpoints/SyncEndpoints.cs changed 20 times in last 90 days, max complexity 15. 3 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: frontend/apps/partner/src/features/applications/question-editor/question-actions/state.ts frontend/apps/partner/src/features/applications/question-editor/question-actions/state.ts— frontend/apps/partner/src/features/applications/question-editor/question-actions/state.ts changed 6 times in last 90 days, max complexity 50. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Duplicated block (7 lines × 2) backend/src/Enduser/Enduser.Database/Configurations/ElementInstanceConfiguration.cs:31— backend/src/Enduser/Enduser.Database/Configurations/ElementInstanceConfiguration.cs:31-37 | backend/src/Enduser/Enduser.Database/Configurations/ElementInstanceConfiguration.cs:44-50 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Configurations/ElementInstanceConfiguration.cs:31` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) backend/src/Enduser/Enduser.Database/Configurations/SyncedDataContextConfiguration.cs:60— backend/src/Enduser/Enduser.Database/Configurations/SyncedDataContextConfiguration.cs:60-66 | backend/src/Enduser/Enduser.Database/Configurations/SyncedDataContextConfiguration.cs:74-80 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Configurations/SyncedDataContextConfiguration.cs:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 2) backend/src/Enduser/Enduser.Database/Services/DataCollectionScheduler.cs:76— backend/src/Enduser/Enduser.Database/Services/DataCollectionScheduler.cs:76-83 | backend/src/Enduser/Enduser.Database/Services/NotificationScheduler.cs:74-80 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (7 lines × 2) backend/src/Master/Master.Database/Configurations/PartnerConfiguration.cs:42— backend/src/Master/Master.Database/Configurations/PartnerConfiguration.cs:42-49 | backend/src/Master/Master.Database/Configurations/PartnerConfiguration.cs:57-63 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Master/Master.Database/Configurations/PartnerConfiguration.cs:42` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) backend/src/Partner/Partner.Database/Configurations/InsightDashboardConfiguration.cs:50— backend/src/Partner/Partner.Database/Configurations/InsightDashboardConfiguration.cs:50-56 | backend/src/Partner/Partner.Database/Configurations/InsightDashboardConfiguration.cs:63-69 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Partner.Database/Configurations/InsightDashboardConfiguration.cs:50` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) backend/src/Partner/Features/Applications/GetApplications/Feature.cs:81— backend/src/Partner/Features/Applications/GetApplications/Feature.cs:81-87 | backend/src/Partner/Features/Applications/GetApplications/Feature.cs:89-95 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Features/Applications/GetApplications/Feature.cs:81` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) backend/src/Partner/Features/Applications/GetApplicationTopics/Feature.cs:98— backend/src/Partner/Features/Applications/GetApplicationTopics/Feature.cs:98-104 | backend/src/Partner/Features/Applications/GetApplicationTopics/Feature.cs:106-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Features/Applications/GetApplicationTopics/Feature.cs:98` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) backend/src/Partner/Features/Applications/GetTopicDetails/Feature.cs:130— backend/src/Partner/Features/Applications/GetTopicDetails/Feature.cs:130-136 | backend/src/Partner/Features/Applications/GetTopicDetails/Feature.cs:138-144 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Features/Applications/GetTopicDetails/Feature.cs:130` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) backend/src/Partner/Features/Clients/GetClients/Feature.cs:59— backend/src/Partner/Features/Clients/GetClients/Feature.cs:59-65 | backend/src/Partner/Features/Clients/GetClients/Feature.cs:67-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Features/Clients/GetClients/Feature.cs:59` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) backend/src/Tools/TypeScriptClientGenerator/Core/ClientGenerator.cs:362— backend/src/Tools/TypeScriptClientGenerator/Core/ClientGenerator.cs:362-368 | backend/src/Tools/TypeScriptClientGenerator/Core/ClientGenerator.cs:378-384 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Tools/TypeScriptClientGenerator/Core/ClientGenerator.cs:362` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) backend/src/Enduser/Enduser.Database/Configurations/SyncedQuestionConfiguration.cs:33— backend/src/Enduser/Enduser.Database/Configurations/SyncedQuestionConfiguration.cs:33-40 | backend/src/Enduser/Enduser.Database/Configurations/SyncedQuestionConfiguration.cs:109-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Configurations/SyncedQuestionConfiguration.cs:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) backend/src/Master/Master.Database/Configurations/DataContextConfiguration.cs:60— backend/src/Master/Master.Database/Configurations/DataContextConfiguration.cs:60-65 | backend/src/Master/Master.Database/Configurations/DataContextConfiguration.cs:80-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Master/Master.Database/Configurations/DataContextConfiguration.cs:60` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) backend/src/Partner/Partner.Database/Configurations/QuestionConfiguration.cs:103— backend/src/Partner/Partner.Database/Configurations/QuestionConfiguration.cs:103-108 | backend/src/Partner/Partner.Database/Configurations/QuestionConfiguration.cs:110-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Partner.Database/Configurations/QuestionConfiguration.cs:103` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) backend/src/Shared/Features/Applications/SubmitAnswer/Feature.cs:394— backend/src/Shared/Features/Applications/SubmitAnswer/Feature.cs:394-399 | backend/src/Shared/Features/Applications/ConfirmActionRecommendations/Feature.cs:144-149 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/Applications/SubmitAnswer/Feature.cs:394` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) backend/src/Shared/Features/MyTasks/GetPersonalTasks/Feature.cs:114— backend/src/Shared/Features/MyTasks/GetPersonalTasks/Feature.cs:114-119 | backend/src/Shared/Features/MyTasks/GetPersonalTasks/Feature.cs:124-129 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) backend/src/SourceGenerators/Features.Generator/Emitters/EndpointMappingEmitter.cs:90— backend/src/SourceGenerators/Features.Generator/Emitters/EndpointMappingEmitter.cs:90-95 | backend/src/SourceGenerators/Features.Generator/Emitters/EndpointMappingEmitter.cs:106-111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/SourceGenerators/Features.Generator/Emitters/EndpointMappingEmitter.cs:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) backend/src/Shared/Features/Applications/GetActionResults/Feature.cs:112— backend/src/Shared/Features/Applications/GetActionResults/Feature.cs:112-117 | backend/src/Shared/Features/Applications/GetActionResults/Feature.cs:118-123 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/Applications/GetActionResults/Feature.cs:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) backend/src/Shared/Adapters/GitHub/GitHubClient.cs:91— backend/src/Shared/Adapters/GitHub/GitHubClient.cs:91-96 | backend/src/Shared/Adapters/GitHub/GitHubClient.cs:104-109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Adapters/GitHub/GitHubClient.cs:91` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) backend/src/Shared/Features/StrategicPlans/GetStrategicPlanStructure/Feature.cs:41— backend/src/Shared/Features/StrategicPlans/GetStrategicPlanStructure/Feature.cs:41-46 | backend/src/Shared/Features/StrategicPlans/GetStrategicPlanStructure/Feature.cs:48-53 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/StrategicPlans/GetStrategicPlanStructure/Feature.cs:41` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
No assertions: ValidateUnitExists_accepts_unit_group_id_directly backend/src/Master/Features/DataContexts/CreateDataContext/Tests.cs:442— Test method exercises code but verifies nothing — add an assertion.
No assertions: ValidateUnitExists_accepts_member_unit_id backend/src/Master/Features/DataContexts/CreateDataContext/Tests.cs:450— Test method exercises code but verifies nothing — add an assertion.
No assertions: ValidateAndWire_allows_automated_root_action_without_parent backend/src/Partner/Features/Questions/CreateQuestion/Tests.cs:408— Test method exercises code but verifies nothing — add an assertion.
No assertions: EnsureCanWriteAsync_is_no_op_when_resolver_allows backend/test/Shared.Tests/ObjectAuthzTests.cs:41— Test method exercises code but verifies nothing — add an assertion.
No assertions: EnsureCanReadAsync_allows_when_user_has_read_grant backend/test/Shared.Tests/ObjectAuthzTests.cs:93— Test method exercises code but verifies nothing — add an assertion.
No assertions: EnsureCanReadAsync_with_requestInfo_allows_when_user_has_read_grant backend/test/Shared.Tests/ObjectAuthzTests.cs:141— Test method exercises code but verifies nothing — add an assertion.
No assertions: Allows_demoting_admin_when_two_or_more_active_admins_exist backend/test/Shared.Tests/LastAdminGuardTests.cs:50— Test method exercises code but verifies nothing — add an assertion.
No assertions: Non_admin_member_is_a_no_op backend/test/Shared.Tests/LastAdminGuardTests.cs:108— Test method exercises code but verifies nothing — add an assertion.
Duplicated block (9 lines × 2) backend/src/Enduser/Enduser.Database/Insight/DashboardDataEngine.cs:485— backend/src/Enduser/Enduser.Database/Insight/DashboardDataEngine.cs:485-493 | backend/src/Enduser/Enduser.Database/Insight/DashboardDataEngine.cs:523-531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Insight/DashboardDataEngine.cs:485` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) backend/src/Master/Features/Partners/GetResponsibleUsers/Feature.cs:98— backend/src/Master/Features/Partners/GetResponsibleUsers/Feature.cs:98-106 | backend/src/Shared/Features/Company/GetOrganizationUsers/Feature.cs:100-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Master/Features/Partners/GetResponsibleUsers/Feature.cs:98` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) backend/src/Partner/Partner.Database/Configurations/ApplicationConfiguration.cs:130— backend/src/Partner/Partner.Database/Configurations/ApplicationConfiguration.cs:130-138 | backend/src/Partner/Partner.Database/Configurations/ApplicationConfiguration.cs:158-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Partner.Database/Configurations/ApplicationConfiguration.cs:130` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) backend/src/Partner/Partner.Database/Configurations/DataContextConfiguration.cs:43— backend/src/Partner/Partner.Database/Configurations/DataContextConfiguration.cs:43-51 | backend/src/Partner/Partner.Database/Configurations/DataContextConfiguration.cs:59-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Partner.Database/Configurations/DataContextConfiguration.cs:43` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) backend/src/Partner/Partner.Database/Configurations/TopicConfiguration.cs:79— backend/src/Partner/Partner.Database/Configurations/TopicConfiguration.cs:79-87 | backend/src/Partner/Partner.Database/Configurations/TopicConfiguration.cs:107-115 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Partner.Database/Configurations/TopicConfiguration.cs:79` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) backend/src/Shared/Features/ActivityLog/GetActivityLogs/Feature.cs:97— backend/src/Shared/Features/ActivityLog/GetActivityLogs/Feature.cs:97-106 | backend/src/Shared/Features/Notifications/GetMyNotifications/Feature.cs:85-93 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (25 lines × 2) backend/src/Enduser/Enduser.Api/Extensions/SecretHelper.cs:31— backend/src/Enduser/Enduser.Api/Extensions/SecretHelper.cs:31-55 | backend/src/Partner/Partner.Api/Extensions/SecretHelper.cs:31-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Extensions/SecretHelper.cs:31` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 2) backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:71— backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:71-95 | backend/src/Partner/Partner.Api/Services/SupportTicketPushHandler.cs:60-84 — before extracting anything, compare `backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs` and `backend/src/Partner/Partner.Api/Services/SupportTicketPushHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) backend/src/Master/Features/Tags/GetTagsForApplications/Feature.cs:37— backend/src/Master/Features/Tags/GetTagsForApplications/Feature.cs:37-61 | backend/src/Partner/Features/Tags/GetTagsForApplications/Feature.cs:31-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Master/Features/Tags/GetTagsForApplications/Feature.cs:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) backend/src/Master/Features/Tags/GetTagsForDataContexts/Feature.cs:37— backend/src/Master/Features/Tags/GetTagsForDataContexts/Feature.cs:37-61 | backend/src/Partner/Features/Tags/GetTagsForDataContexts/Feature.cs:31-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Master/Features/Tags/GetTagsForDataContexts/Feature.cs:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) backend/src/Master/Features/Tags/GetTagsForUsers/Feature.cs:37— backend/src/Master/Features/Tags/GetTagsForUsers/Feature.cs:37-61 | backend/src/Partner/Features/Tags/GetTagsForUsers/Feature.cs:31-55 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Master/Features/Tags/GetTagsForUsers/Feature.cs:37` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) backend/src/Enduser/Enduser.Api/Services/SupportSyncService.cs:284— backend/src/Enduser/Enduser.Api/Services/SupportSyncService.cs:284-294 | backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:166-176 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Services/SupportSyncService.cs:284` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) backend/src/Enduser/Enduser.Database/Services/TagAncestry.cs:48— backend/src/Enduser/Enduser.Database/Services/TagAncestry.cs:48-58 | backend/src/Partner/Partner.Database/Services/TagAncestry.cs:54-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Services/TagAncestry.cs:48` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) backend/src/Shared/Features/Applications/SubmitAnswer/Feature.cs:343— backend/src/Shared/Features/Applications/SubmitAnswer/Feature.cs:343-353 | backend/src/Shared/Features/Applications/ConfirmActionRecommendations/Feature.cs:106-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/Applications/SubmitAnswer/Feature.cs:343` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) backend/src/Shared/Features/Assignments/GrantAssignment/Feature.cs:182— backend/src/Shared/Features/Assignments/GrantAssignment/Feature.cs:182-192 | backend/src/Shared/Features/Assignments/RevokeAssignment/Feature.cs:121-131 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/Assignments/GrantAssignment/Feature.cs:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:296— backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:296-306 | backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:316-326 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:296` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (5 lines × 2) backend/src/Enduser/Enduser.Database/Configurations/SyncedQuestionConfiguration.cs:51— backend/src/Enduser/Enduser.Database/Configurations/SyncedQuestionConfiguration.cs:51-55 | backend/src/Enduser/Enduser.Database/Configurations/SyncedQuestionConfiguration.cs:56-60 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Configurations/SyncedQuestionConfiguration.cs:51` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) backend/src/Enduser/Enduser.Database/Insight/TaskLoad.cs:359— backend/src/Enduser/Enduser.Database/Insight/TaskLoad.cs:359-363 | backend/src/Enduser/Enduser.Database/Insight/TaskLoad.cs:366-370 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Insight/TaskLoad.cs:359` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) backend/src/Shared/Features/MyTasks/GetApplicationTasks/Feature.cs:443— backend/src/Shared/Features/MyTasks/GetApplicationTasks/Feature.cs:443-447 | backend/src/Shared/Features/MyTasks/GetApplicationTasks/Feature.cs:450-454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/MyTasks/GetApplicationTasks/Feature.cs:443` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) backend/src/Shared/Features/MyTasks/GetDataCollectionTasks/Feature.cs:122— backend/src/Shared/Features/MyTasks/GetDataCollectionTasks/Feature.cs:122-126 | backend/src/Shared/Features/MyTasks/GetDataCollectionTasks/Feature.cs:132-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/MyTasks/GetDataCollectionTasks/Feature.cs:122` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) backend/src/Shared/Features/MyTasks/GetPersonalTasks/Feature.cs:47— backend/src/Shared/Features/MyTasks/GetPersonalTasks/Feature.cs:47-51 | backend/src/Shared/Features/MyTasks/GetPersonalTasks/Feature.cs:58-62 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/MyTasks/GetPersonalTasks/Feature.cs:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) backend/src/Enduser/Enduser.Database/Extensions/DatabaseServiceExtensions.cs:52— backend/src/Enduser/Enduser.Database/Extensions/DatabaseServiceExtensions.cs:52-63 | backend/src/Master/Master.Database/Extensions/DatabaseServiceExtensions.cs:48-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) backend/src/Enduser/Enduser.Database/Services/TaskAssigneeResolver.cs:58— backend/src/Enduser/Enduser.Database/Services/TaskAssigneeResolver.cs:58-69 | backend/src/Enduser/Enduser.Database/Services/ValidatorResolver.cs:42-53 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Services/TaskAssigneeResolver.cs:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) backend/src/Shared/Features/Auth/GetCurrentUser/Feature.cs:69— backend/src/Shared/Features/Auth/GetCurrentUser/Feature.cs:69-82 | backend/src/Shared/Features/GetMe/Feature.cs:176-187 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/Auth/GetCurrentUser/Feature.cs:69` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) backend/src/Shared/Features/MyTasks/GetTasksDashboard/Feature.cs:57— backend/src/Shared/Features/MyTasks/GetTasksDashboard/Feature.cs:57-69 | backend/src/Shared/Features/MyTasks/GetTasksDashboard/Feature.cs:171-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/MyTasks/GetTasksDashboard/Feature.cs:57` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Cross-context type ImportRowResult (Enduser → Shared) — ImportRowResult (context Enduser) is exposed in Shared's public surface via DryRunOutcome..ctor — couples the contexts.
Cross-context type ImportRowResult (Enduser → Shared) — ImportRowResult (context Enduser) is exposed in Shared's public surface via DryRunOutcome.Results — couples the contexts.
Cross-context type ImportRowResult (Enduser → Shared) — ImportRowResult (context Enduser) is exposed in Shared's public surface via DryRunOutcome.Deconstruct — couples the contexts.
Medium: wildcard-postmessage-configuration frontend/apps/translator/src/components/PreviewPane.tsx:21— The target origin of the window.postMessage() API is set to "*". This could allow for information disclosure due to the possibility of any origin allowed to receive the message. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: wildcard-postmessage-configuration frontend/apps/translator/src/components/PreviewPane.tsx:45— The target origin of the window.postMessage() API is set to "*". This could allow for information disclosure due to the possibility of any origin allowed to receive the message. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: wildcard-postmessage-configuration frontend/packages/utils/src/i18n/i18n-bridge.ts:59— The target origin of the window.postMessage() API is set to "*". This could allow for information disclosure due to the possibility of any origin allowed to receive the message. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Duplicated block (21 lines × 2) backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/SubscriptionDispatcher.cs:88— backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/SubscriptionDispatcher.cs:88-108 | backend/src/Partner/Partner.Api/Adapters/Subscriptions/SubscriptionDispatcher.cs:88-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/SubscriptionDispatcher.cs:88` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:138— backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:138-158 | backend/src/Partner/Partner.Api/Services/SupportTicketPushHandler.cs:118-138 — before extracting anything, compare `backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs` and `backend/src/Partner/Partner.Api/Services/SupportTicketPushHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) backend/src/Master/Features/Units/UpdateUnitGroup/Feature.cs:109— backend/src/Master/Features/Units/UpdateUnitGroup/Feature.cs:109-129 | backend/src/Master/Features/Units/UpdateUnits/Feature.cs:108-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:107— backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs:107-120 | backend/src/Partner/Partner.Api/Services/SupportTicketPushHandler.cs:100-113 — before extracting anything, compare `backend/src/Enduser/Enduser.Api/Services/SupportTicketPushHandler.cs` and `backend/src/Partner/Partner.Api/Services/SupportTicketPushHandler.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) backend/src/Enduser/Enduser.Database/Services/TaskAssigneeResolver.cs:87— backend/src/Enduser/Enduser.Database/Services/TaskAssigneeResolver.cs:87-100 | backend/src/Enduser/Enduser.Database/Services/ValidatorResolver.cs:71-84 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Database/Services/TaskAssigneeResolver.cs:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) backend/src/SourceGenerators/Features.Generator/SymbolExtensions.cs:64— backend/src/SourceGenerators/Features.Generator/SymbolExtensions.cs:64-78 | backend/src/Tools/TypeScriptClientGenerator/Core/ClientGenerator.cs:725-738 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 3) backend/src/Enduser/Enduser.Api/Middleware/ContentTypeValidationMiddleware.cs:95— backend/src/Enduser/Enduser.Api/Middleware/ContentTypeValidationMiddleware.cs:95-107 | backend/src/Master/Master.Api/Middleware/ContentTypeValidationMiddleware.cs:95-107 | backend/src/Partner/Partner.Api/Middleware/ContentTypeValidationMiddleware.cs:95-107 — before extracting anything, compare `backend/src/Enduser/Enduser.Api/Middleware/ContentTypeValidationMiddleware.cs` and `backend/src/Partner/Partner.Api/Middleware/ContentTypeValidationMiddleware.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Middleware/ContentTypeValidationMiddleware.cs:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) backend/src/Enduser/Enduser.Api/Middleware/ContentTypeValidationMiddleware.cs:113— backend/src/Enduser/Enduser.Api/Middleware/ContentTypeValidationMiddleware.cs:113-125 | backend/src/Master/Master.Api/Middleware/ContentTypeValidationMiddleware.cs:113-125 | backend/src/Partner/Partner.Api/Middleware/ContentTypeValidationMiddleware.cs:113-125 — before extracting anything, compare `backend/src/Enduser/Enduser.Api/Middleware/ContentTypeValidationMiddleware.cs` and `backend/src/Partner/Partner.Api/Middleware/ContentTypeValidationMiddleware.cs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 49 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Middleware/ContentTypeValidationMiddleware.cs:113` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 3) backend/src/Enduser/Enduser.Database/Extensions/DatabaseServiceExtensions.cs:19— backend/src/Enduser/Enduser.Database/Extensions/DatabaseServiceExtensions.cs:19-31 | backend/src/Master/Master.Database/Extensions/DatabaseServiceExtensions.cs:18-30 | backend/src/Partner/Partner.Database/Extensions/DatabaseServiceExtensions.cs:18-30 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (10 lines × 2) backend/src/Enduser/Enduser.Database/UserDisplayNameResolver.cs:24— backend/src/Enduser/Enduser.Database/UserDisplayNameResolver.cs:24-33 | backend/src/Enduser/Enduser.Database/UserDisplayNameResolver.cs:73-82 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 2) backend/src/Master/Features/Partners/GetPartnerSupportRequests/Feature.cs:137— backend/src/Master/Features/Partners/GetPartnerSupportRequests/Feature.cs:137-146 | backend/src/Partner/Features/Clients/GetClientSupportRequests/Feature.cs:137-146 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) backend/src/Shared/Features/Features.Common/Validation/LocalizedTextValidation.cs:33— backend/src/Shared/Features/Features.Common/Validation/LocalizedTextValidation.cs:33-42 | backend/src/Shared/Features/Features.Common/Validation/LocalizedTextValidation.cs:62-71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/Features.Common/Validation/LocalizedTextValidation.cs:33` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Cross-context type ImportMapping (Enduser → Shared) — ImportMapping (context Enduser) is exposed in Shared's public surface via ImportProfileDto.Mapping — couples the contexts.
Cross-context type ImportMapping (Enduser → Shared) — ImportMapping (context Enduser) is exposed in Shared's public surface via Request.Mapping — couples the contexts.
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×2
Medium CVE: [GHSA redacted] frontend/bun.lock— postcss 8.5.18: [GHSA redacted] — upgrade to 8.5.23
Medium CVE: [GHSA redacted] bun.lock— yaml 2.8.2: [GHSA redacted] — yaml is not declared by the manifests that govern this lockfile: it is pulled in transitively here (the 2.9.0 this repo declares for it belongs to a separate install root and does not reach this one), so upgrade the dependency that requires it (or pin yaml to 2.8.3 with an `overrides` entry).
Duplicated block (19 lines × 2) backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/InMemoryConnectionManager.cs:97— backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/InMemoryConnectionManager.cs:97-115 | backend/src/Partner/Partner.Api/Adapters/Subscriptions/InMemoryConnectionManager.cs:97-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/InMemoryConnectionManager.cs:97` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) backend/src/Enduser/Enduser.Api/Services/SyncService.cs:88— backend/src/Enduser/Enduser.Api/Services/SyncService.cs:88-106 | backend/src/Partner/Partner.Api/Services/SyncService.cs:78-97 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (18 lines × 2) backend/src/Enduser/Enduser.Api/Services/SupportSyncService.cs:89— backend/src/Enduser/Enduser.Api/Services/SupportSyncService.cs:89-106 | backend/src/Partner/Partner.Api/Services/SupportSyncService.cs:89-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (18 lines × 2) backend/src/Master/Features/DataContexts/CreateDataContext/Feature.cs:212— backend/src/Master/Features/DataContexts/CreateDataContext/Feature.cs:212-229 | backend/src/Master/Features/DataContexts/UpdateDataContext/Feature.cs:233-250 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (16 lines × 2) backend/src/Enduser/Enduser.Api/Services/SupportSyncService.cs:44— backend/src/Enduser/Enduser.Api/Services/SupportSyncService.cs:44-59 | backend/src/Partner/Partner.Api/Services/SupportSyncService.cs:44-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Services/SupportSyncService.cs:44` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) backend/src/Master/Features/DataContexts/GetDataContextDetails/Feature.cs:138— backend/src/Master/Features/DataContexts/GetDataContextDetails/Feature.cs:138-153 | backend/src/Master/Features/Tags/GetTagDetails/Feature.cs:137-152 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Master/Features/DataContexts/GetDataContextDetails/Feature.cs:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) backend/src/Enduser/Enduser.Api/Endpoints/BootstrapEndpoints.cs:13— backend/src/Enduser/Enduser.Api/Endpoints/BootstrapEndpoints.cs:13-27 | backend/src/Partner/Partner.Api/Endpoints/BootstrapEndpoints.cs:17-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) backend/src/Master/Features/DataContexts/GetDataContexts/Feature.cs:55— backend/src/Master/Features/DataContexts/GetDataContexts/Feature.cs:55-69 | backend/src/Partner/Features/DataContexts/GetDataContexts/Feature.cs:49-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Master/Features/DataContexts/GetDataContexts/Feature.cs:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (10 lines × 3) backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/InMemorySubscriptionStore.cs:19— backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/InMemorySubscriptionStore.cs:19-28 | backend/src/Master/Master.Api/Adapters/Subscriptions/InMemorySubscriptionStore.cs:19-28 | backend/src/Partner/Partner.Api/Adapters/Subscriptions/InMemorySubscriptionStore.cs:19-28 — before extracting anything, compare `backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/InMemorySubscriptionStore.cs` and `backend/src/Master/Master.Api/Adapters/Subscriptions/InMemorySubscriptionStore.cs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 51 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Adapters/Subscriptions/InMemorySubscriptionStore.cs:19` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:253— backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:253-262 | backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:274-283 | backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:295-304 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/SourceGenerators/Features.Generator/FeatureRegistrationGenerator.cs:253` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 3) backend/src/Enduser/Enduser.Api/Program.cs:569— backend/src/Enduser/Enduser.Api/Program.cs:569-576 | backend/src/Master/Master.Api/Program.cs:521-530 | backend/src/Partner/Partner.Api/Program.cs:552-561 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Program.cs:569` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) backend/src/Shared/Features/Applications/GetActiveSurveyDispatches/Feature.cs:95— backend/src/Shared/Features/Applications/GetActiveSurveyDispatches/Feature.cs:95-102 | backend/src/Shared/Features/Applications/GetSurveyByToken/Feature.cs:166-173 | backend/src/Shared/Features/Applications/GetSurveyResults/Feature.cs:162-169 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Shared/Features/Applications/GetActiveSurveyDispatches/Feature.cs:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) backend/src/Enduser/Enduser.Api/Services/SyncService.cs:116— backend/src/Enduser/Enduser.Api/Services/SyncService.cs:116-123 | backend/src/Partner/Partner.Api/Services/SyncService.cs:108-115 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Enduser/Enduser.Api/Services/SyncService.cs:116` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) backend/src/Partner/Partner.Database/Configurations/ClientConfiguration.cs:51— backend/src/Partner/Partner.Database/Configurations/ClientConfiguration.cs:51-58 | backend/src/Partner/Partner.Database/Configurations/ClientConfiguration.cs:66-73 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `backend/src/Partner/Partner.Database/Configurations/ClientConfiguration.cs:51` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D11 · Test Reliability· Test reliability not measured · ×1
Test reliability not measured — no test run produced results — Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
Cross-context type DataContextMessage (Master → Partner) — DataContextMessage (context Master) is exposed in Partner's public surface via Feature.Handle — couples the contexts.
Cross-context type ElementMessage (Master → Partner) — ElementMessage (context Master) is exposed in Partner's public surface via Feature.Handle — couples the contexts.
Cross-context type TagMessage (Master → Partner) — TagMessage (context Master) is exposed in Partner's public surface via Feature.Handle — couples the contexts.
Cross-context type PartnerBrandingChangedMessage (Partner → Shared) — PartnerBrandingChangedMessage (context Partner) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type ApplicationAssignmentChangedMessage (Enduser → Shared) — ApplicationAssignmentChangedMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type SurveyInvitationConsumedMessage (Enduser → Shared) — SurveyInvitationConsumedMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type PartnerBrandingChangedMessage (Enduser → Shared) — PartnerBrandingChangedMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type ElementInstanceMessage (Enduser → Shared) — ElementInstanceMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type ElementOwnershipChangedMessage (Enduser → Shared) — ElementOwnershipChangedMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type ImportOptions (Enduser → Shared) — ImportOptions (context Enduser) is exposed in Shared's public surface via Request.Options — couples the contexts.
Cross-context type OperationalEntityUpdatedMessage (Enduser → Shared) — OperationalEntityUpdatedMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type DataCollectionEntryMessage (Enduser → Shared) — DataCollectionEntryMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type OperationalTaskUpdatedMessage (Enduser → Shared) — OperationalTaskUpdatedMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type PersonalTaskMessage (Enduser → Shared) — PersonalTaskMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type NotificationPreferencesChangedMessage (Enduser → Shared) — NotificationPreferencesChangedMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Cross-context type NotificationMessage (Enduser → Shared) — NotificationMessage (context Enduser) is exposed in Shared's public surface via Feature.Handle — couples the contexts.
Change coupling: en.ts ↔ types.ts frontend/packages/utils/src/i18n/translations/en.ts— `frontend/packages/utils/src/i18n/translations/en.ts` and `frontend/packages/utils/src/insight/types.ts` change together 86% of the time (12 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 1 floating ref(s) across 1 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
D38 · OSV Dependency Vulnerabilities· Medium vulnerability · ×1
Medium vulnerability: [GHSA redacted] bun.lock— esbuild 0.24.2: [GHSA redacted] — upgrade to 0.25.0
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.