Public report — OrchardCore, published 5 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
1056findings with an exact file:lineof 1112 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
85/111dimensions across the health lenses233636 LoC · 235 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.
OrchardCMS/OrchardCore is in a workable but fragile state (51%). 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 Event-Driven (100%) — its messaging keeps components properly decoupled. Security (82%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Accessibility (40%) — it raises ongoing delivery and operational cost. Code Health (53%) is the next concern — changes there are slower and more error-prone.
Leadership focus, highest impact first: text alternative — alt on images (alt="" for purely decorative… (Text alternatives); Make custom controls keyboard-operable (role + tabindex + key handler) (Keyboard semantics); accessibility in the toolchain (A11y enforcement).
For scale: Large (~233,636 production lines); rebuilding it from scratch would take roughly ~6.2 person-years (~3–12 engineers). Approximate, ±~30%.
It builds on a genuinely strong Event-Driven foundation (100%); 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.
~7208 LoC unreachable (28 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 ~6.2 person-years of build effort (about ~€900,000 to rebuild). Its weakest lens is Accessibility at 40% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Very high (×1.9) — microservices, CQRS, event-driven integration, high decision density × a 0.7× quality factor, at €60–95/h; indicative, ±~30%. 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
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Value concentrated against a weak lens · High · Value at risk
This is a Large asset (~6.2 person-years to rebuild), and its weakest lens is Accessibility 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 Accessibility first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
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
1096 modules, 3596 dependencies — 18 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.)
At a glance — Code Health · 53% · Adequate · gated by X5
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
A06:2021 — Vulnerable & Outdated Components
50
High / Critical
A05:2021 — Security Misconfiguration
1
Medium
A04:2021 — Insecure Design
1
Medium
Roadmap
Begin by adding text alternatives for all images, media, and video content to ensure screen reader compatibility. Next, ensure all interactive elements are fully keyboard-operable and anchors function correctly. Integrate accessibility enforcement into the development toolchain by adding relevant linters and automated tests to prevent future regressions. Finally, improve visual safety by maintaining visible focus styles, respecting reduced motion preferences, and ensuring sufficient color contrast. Complete the foundation by declaring page structure, landmarks, and titles to support navigation and SEO.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with vitest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Resolve the 7 EmptyCatchBlock finding(s) in Explicit Debt — start with FormInputElementVisibilityPartDisplayDriver.cs, DataProtectionFilters.cs, SecurityTokenService.cs.
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 85 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 85 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, 1056 of 1112 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
A clean run — every tool resolved and ran, and every applicable dimension was measured at full confidence. No scanner was unavailable, no analysis timed out or crashed, and nothing fell back to a degraded estimate.
When something does degrade — a missing scanner, a shallow clone, an LLM hiccup — it is named here explicitly and its exact cause recorded in diagnostics.md, never absorbed silently into the score.
Repo exclusion declarations: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (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.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
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.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
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.
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.
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.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
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.
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.
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 (6): D19, D20, D21, D24, 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: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
112 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DefaultPluralRuleProvider.DefaultPluralRuleProvider.ctor at 70. A further 8 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being PermissionsPolicySettings.Edit.cshtml › GetPermissionPolicyName at 31 — they are counted neither in the figure above nor in this dimension's score.
+ 107 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 DefaultPluralRuleProvider.DefaultPluralRuleProvider.ctor (cyclomatic 70) finding(s) in Cyclomatic Complexity — start with DefaultPluralRuleProvider.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 getOptions (cyclomatic 56) finding(s) in Cyclomatic Complexity — start with list-management.js. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 DefaultContentsAdminListFilterProvider.Build (cyclomatic 50) finding(s) in Cyclomatic Complexity — start with DefaultContentsAdminListFilterProvider.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 248 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 DefaultPluralRuleProvider.DefaultPluralRuleProvider.ctor (cognitive 105) finding(s) in Cognitive Complexity — start with DefaultPluralRuleProvider.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 DynamicContentTypeBuilder.BuildInternal (cognitive 100) finding(s) in Cognitive Complexity — start with DynamicContentTypeBuilder.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 SeoMetaSettingsHandler.GetContentItemAspectAsync (cognitive 87) finding(s) in Cognitive Complexity — start with SeoMetaSettingsHandler.cs. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.6 / 10Exemplary✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
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.
+ 25 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.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution9.5 / 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.
1463 test methods: 1410 unit, 0 integration, 0 BDD, 53 e2e.
✓ On the Gold path — maintain.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
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.
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.
Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
Enforce License Compliance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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 Factor9.3 / 10Exemplary✓ 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.
67 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/OrchardCore/OrchardCore.SourceGenerators/ShapeFactoryGenerator.cs.
Off-boarding risk: anonymized user #1 · ×3
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
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.
Dead code: CookieOptionsConfiguration · ×6src/OrchardCore.Modules/OrchardCore.Microsoft.Authentication/Configuration/CookieOptionsConfiguration.cs:9
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
✓ On the Gold path — maintain.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D18 · Solution Shape4.6 / 10Weak✓ Tool-verified
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
Resolve the 2 Shell project finding(s) in Solution Shape — start with OrchardCore.ContentPreview.Abstractions.csproj, OrchardCore.Markdown.Abstractions.csproj. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Thin analysable surface across projects finding(s) in Solution Shape. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Orchard Core's documentation is strong and well-structured: the README gives a clear two-project overview (Framework vs CMS), build status badges, project status notes, and links to docs. The test/functional README explains in-process hosting, parallel execution, and how to run tests with Playwright, plus architecture details for each target. A dedicated docs directory covers building SaaS solutions, building a website, different strategies, and the current status. However, there is no single landing page or comprehensive Getting Started guide (the only real one is the README's 'Getting Started' section), and XML-doc coverage across the core projects is thin (<2% for OrchardCore.ContentFields.Core; 10% for OpenApi) with many missing sections. Orchard Core documentation is comprehensive and well-organized across READMEs, architecture/design docs, and XML-doc coverage. The modules reference page gives a clear categorization (CMS vs core modules) plus an overview of features grouped by topic, while the guides section covers both quick-start and deep-tutorial content. However, the quality score sits below 8 because many practical topics are missing: no Getting Started Using `Program.cs` file guide for .NET 6 projects, no troubleshooting or endpoint-not-discovered guidance in the modules reference, and no dedicated documentation for the preview package setup (configured Package Source). Orchard Core's documentation is comprehensive and well-organized across READMEs, architecture/design docs, and XML-doc coverage. The main strengths are the detailed source-generator guide (with a full outline showing every topic) covering arguments generation for named types vs anonymous types with interceptors, and the Security module listing Microsoft, Facebook, Twitter, GitHub, Google, OpenId, Roles, DataProtection, Permissions, Users, and roles-permissions guides. Coverage of search/indexing is strong but thin on practical examples; the Navigation section lists Menu, Navigation, AdminMenu, Add an item to admin menu, Taxonomies, which are all present in the outline. The XML-doc coverage across modules ranges from 0% (e.g. Authorization) to 100% (e.g. OrchardCore.Mvc.Web), with most modules at mid-range. Orchard Core documentation is comprehensive across the project's many modules (e.g. OrchardCore.ContentFields, OrchardCore.Indexing, OrchardCore.Localization), with XML-doc coverage ranging from 0% to 100%. The strongest strength lies in its focused content-relationship guide for BagPart and Content Picker fields, which is a well-written deep dive on the built-in options. However, the documentation lacks a dedicated Getting Started or Quick Start section covering how to set up Orchard Core locally (source fork, dotnet pack, local feed), leaving new contributors with no clear path from clone to first run.
Improve Documentation Quality — currently 6.8/10. — Orchard Core's documentation is strong and well-structured: the README gives a clear two-project overview (Framework vs CMS), build status badges, project status notes, and links to docs. The test/functional README explains in-process hosting, parallel execution, and how to run tests with Playwright, plus architecture details for each target. A dedicated docs directory covers building SaaS solutions, building a website, different strategies, and the current status. However, there is no single landing page or comprehensive Getting Started guide (the only real one is the README's 'Getting Started' section), and XML-doc coverage across the core projects is thin (<2% for OrchardCore.ContentFields.Core; 10% for OpenApi) with many missing sections. Orchard Core documentation is comprehensive and well-organized across READMEs, architecture/design docs, and XML-doc coverage. The modules reference page gives a clear categorization (CMS vs core modules) plus an overview of features grouped by topic, while the guides section covers both quick-start and deep-tutorial content. However, the quality score sits below 8 because many practical topics are missing: no Getting Started Using `Program.cs` file guide for .NET 6 projects, no troubleshooting or endpoint-not-discovered guidance in the modules reference, and no dedicated documentation for the preview package setup (configured Package Source). Orchard Core's documentation is comprehensive and well-organized across READMEs, architecture/design docs, and XML-doc coverage. The main strengths are the detailed source-generator guide (with a full outline showing every topic) covering arguments generation for named types vs anonymous types with interceptors, and the Security module listing Microsoft, Facebook, Twitter, GitHub, Google, OpenId, Roles, DataProtection, Permissions, Users, and roles-permissions guides. Coverage of search/indexing is strong but thin on practical examples; the Navigation section lists Menu, Navigation, AdminMenu, Add an item to admin menu, Taxonomies, which are all present in the outline. The XML-doc coverage across modules ranges from 0% (e.g. Authorization) to 100% (e.g. OrchardCore.Mvc.Web), with most modules at mid-range. Orchard Core documentation is comprehensive across the project's many modules (e.g. OrchardCore.ContentFields, OrchardCore.Indexing, OrchardCore.Localization), with XML-doc coverage ranging from 0% to 100%. The strongest strength lies in its focused content-relationship guide for BagPart and Content Picker fields, which is a well-written deep dive on the built-in options. However, the documentation lacks a dedicated Getting Started or Quick Start section covering how to set up Orchard Core locally (source fork, dotnet pack, local feed), leaving new contributors with no clear path from clone to first run.
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.
0 naming inconsistencies across 200 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.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.
9 of 235 projects flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability7.9 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
92 % of calls cross a namespace and 14 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
What to do
Improve Navigability — currently 7.9/10. — 92 % of calls cross a namespace and 14 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: large — vertical-slice locality expected.
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.
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
Improve Secrets (history) — currently 4.0/10. — 6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
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).
Low IaC: DS-0026Dockerfiledetected by trivy finding
✓ On the Gold path — maintain.
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Exemplary✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR pattern scan via semgrep across the repo, using Watchdog's own ruleset (personal data reaching log/console sinks, URLs and query strings, or unprotected browser storage); matches map to severity and a 0-10 wide normalizer. NotApplicable when the scan runs and detects no PII/GDPR surface (no unearned 10); reported LOUDLY as a measurement gap, never as not-applicable, if the ruleset is missing from the analyzer image. Exhaustive, advisory-leaning; degrades on parse failure.
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.
45 of 1064 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/OrchardCore.Modules/OrchardCore.UrlRewriting/Controllers/AdminController.cs.
Further orphaned files (smaller)
✓ On the Gold path — maintain.
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Secret passed as a command-line argument 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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
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] · ×29yarn.lockdetected by osv-scanner finding
Critical CVE: [GHSA redacted] · ×3yarn.lockdetected by osv-scanner finding
High vulnerability: [GHSA redacted]yarn.lockdetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×14yarn.lockdetected by osv-scanner finding
Low CVE: [GHSA redacted] · ×3yarn.lockdetected by osv-scanner finding
What to do
Resolve the 29 High CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (29). — One of this dimension's main actionable groups (29 issue-level).
Resolve the 3 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D39 · IL Efficiency10.0 / 10Exemplary✓ Tool-verified
Method: IL instruction count per method, read from the BUILT first-party assemblies via Mono.Cecil (the target is compiled on a deep run); scored on the fraction of methods whose emitted IL body exceeds the size threshold. Sees compiler-generated bloat source can't; not-applicable when the target fails to build. Deterministic.
32 of 19512 first-party methods have an oversized IL body.
IL efficiency: 32 authored method(s) exceed the IL budgetsrc/OrchardCore.Modules/OrchardCore.Resources/ResourceManagementOptionsConfiguration.cs:37
✓ On the Gold path — maintain.
Detailed fixes: d39_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 alternatives3.0 / 10Weak✓ Tool-verified
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.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×6) — GalleryCardItem.vue:26, GalleryListItem.vue:18, MediaFieldAttached.vue:136, …
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels7.1 / 10Strong✓ 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 no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×18) — ArchiveLaterPart.Edit.cshtml:11, NumericField-Range.Edit.cshtml:34, EditField.cshtml:63, …
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. — AutoroutePartSettings.Edit.cshtml:61
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×5) — Index.cshtml:109, Index.cshtml:138, InputPart.cshtml:40, …
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — FolderComponent.vue:0
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.
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.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×8) — _Layout.cshtml:2, index.html:2, callback.html:2, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×15) — Edit.cshtml:84, EditPart.cshtml:42, Index.cshtml:121, …
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — Index.cshtml:8
A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — ExternalLogins.cshtml:13
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.
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. (×15) — MultiTextFieldSettings.Edit.cshtml:107, TextFieldPredefinedListEditorSettings.Edit.cshtml:100, ContentTypePicker.cshtml:19, …
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×10) — FileItemsComponent.vue:12, FileItemsComponent.vue:16, FileItemsComponent.vue:20, …
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.
This stylesheet animates but never checks prefers-reduced-motion, so motion-sensitive users can't opt out. Wrap motion in @media (prefers-reduced-motion: no-preference). — Index.cshtml:4
`.md-fenced-code-tabs label` sets color: #fff on background-color: #999 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — code-tabs.css:18
`ul.pager li a:hover` sets color: #0085A1 on background-color: #e9ecef — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — bootstrap-oc.css:222
`.list-group-item-warning.list-group-item-action:hover, .list-group-item-warning.list-group-item-action:focus` sets color: #997404 on background-color: #e6dbb9 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — styles.css:5107
`.dropdown-item.active, .dropdown-item:active` sets color: #fff on background-color: #ffc800 — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — styles.css:3463
`.workflow-canvas .activity.activity-start, .workflow-canvas .activity.activity-blocking` sets color: #ffffff on background-color: #7ab02c — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — orchard.workflows-editor.css:45, orchard.workflows-viewer.css:45
`.leaflet-bar a.leaflet-disabled` sets color: #bbb on background-color: #f4f4f4 — 1.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — leaflet.css:318
`.mf-btn-primary` sets color: #fff on background-color: #7bc143 — 2.2:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — media-field2.css:1
`.ma-page-item.is-disabled .ma-page-link` sets color: #ced4da on background-color: #fff — 1.5:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — media2.css:1
`.ma-page-item.is-disabled .ma-page-link` sets color: #ced4da on background-color: #fff — 1.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — file.css:208
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time.
What to do
Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then 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.
`DataLocalizerFactory` is registered as a SINGLETON but its constructor takes `DataResourceManager dataResourceManager`, which is registered as Transient. The singleton captures one instance of the transient dependency forever — defeating its lifetime (a per-request DbContext shared across all requests is a classic data-corruption/threading bug). Make the singleton resolve `DataResourceManager` per-use (inject `IServiceScopeFactory` or a factory func), or align the lifetimes. — DataLocalizerFactory.cs:7
What to do
Don't inject scoped/transient services into singletons; resolve them per-use via IServiceScopeFactory or a factory delegate, or align the lifetimes.
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.
`RazorCompilationFileProviderAccessor` is a singleton (one shared instance) but mutates instance state outside any lock (_compositeFileProvider; e.g. `_compositeFileProvider` at line 25). — RazorCompilationFileProviderAccessor.cs:9
`TestBackgroundTask` is a singleton (one shared instance) but mutates instance state outside any lock (_count; e.g. `_count` at line 13). — TestBackgroundTask.cs:5
`HomeRouteValuesAddressScheme` is a singleton (one shared instance) but mutates instance state outside any lock (_cachedEndpoint, _cachedEndpointKey; e.g. `_cachedEndpoint` at line 54). — HomeRouteValuesAddressScheme.cs:9
`SitemapEntries` is a singleton (one shared instance) but mutates instance state outside any lock (_document; e.g. `_document` at line 67). — SitemapEntries.cs:5
`RedisService` is a singleton (one shared instance) but mutates instance state outside any lock (Database; e.g. `Database` at line 26). — RedisService.cs:7
`AzureAIClientFactory` is a singleton (one shared instance) but mutates instance state outside any lock (_searchIndexClient; e.g. `_searchIndexClient` at line 76). — AzureAIClientFactory.cs:10
`DocumentOptionsSetup` is a singleton (one shared instance) but mutates instance state outside any lock (_defaultDocumentSerializer; e.g. `_defaultDocumentSerializer` at line 56). — DocumentOptionsSetup.cs:9
`ShellSettingsManager` is a singleton (one shared instance) but mutates instance state outside any lock (_disposed; e.g. `_disposed` at line 308). — ShellSettingsManager.cs:10
`LocalLock` is a singleton (one shared instance) but mutates instance state outside any lock (_disposed; e.g. `_disposed` at line 188). — LocalLock.cs:9
`TenantHttpClientFactory` is a singleton (one shared instance) but mutates instance state outside any lock (_disposed, _services, _scopeFactory, _optionsMonitor, _filters, _entryFactory; e.g. `_disposed` at line 353). — TenantHttpClientFactory.cs:17
`ShellSettings` is a singleton (one shared instance) but mutates instance state outside any lock (_versionId, _tenantId, _requestUrlHost, _requestUrlHosts, _requestUrlPrefix, _requestPathBase; e.g. `_versionId` at line 89). — ShellSettings.cs:14
`RunningShellTable` is a singleton (one shared instance) but mutates instance state outside any lock (_default, _hasStarMapping; e.g. `_default` at line 17). — RunningShellTable.cs:7
`SetFeaturesShellDescriptorManager` is a singleton (one shared instance) but mutates instance state outside any lock (_shellDescriptor; e.g. `_shellDescriptor` at line 34). — SetFeaturesShellDescriptorManager.cs:10
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.
`IContentManager` declares 20 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IContentManager.cs:8
`IContentFieldHandler` declares 27 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IContentFieldHandler.cs:6
`IContentHandler` declares 29 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IContentHandler.cs:3
`IContentPartHandler` declares 27 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IContentPartHandler.cs:6
`IContentDefinitionService` declares 16 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IContentDefinitionService.cs:9
`IContentDefinitionEventHandler` declares 17 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IContentDefinitionEventHandler.cs:3
`IFileStore` declares 16 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IFileStore.cs:16
`ISite` declares 19 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — ISite.cs:6
`IResourceManager` declares 24 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IResourceManager.cs:5
`IActivity` declares 19 members. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — IActivity.cs:9
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.
`AllFeaturesDeploymentSource` (slice 'Deployment') depends on `IModuleService` from slice 'Services'. — AllFeaturesDeploymentSource.cs:7
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
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.
Do you agree with this assessment?
C1 · Data Protection8.5 / 10Strong✓ Tool-verified
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.
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 Trail7.5 / 10Strong✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
An audit mechanism is present, but the trail is not yet complete — missing: an EF SaveChanges interceptor (or equivalent write-side hook, e.g. an event-store append every change flows through), [Audited] per-entity coverage.
What to do
Back the audit convention with a structural mechanism: an EF SaveChanges interceptor (or equivalent) writing every sensitive change to an immutable audit log, and apply [Audited] to the entities that need a who-changed-what trail.
Do you agree with this assessment?
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 · Event-Driven — Whether event handlers stay asynchronous (no blocking remote HTTP/gRPC calls awaited inside a handler).
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
Other · Event-Driven — Whether state changes and message publishes are atomic (a transactional outbox) rather than a crash-unsafe dual write.
Method: Roslyn semantic scan (event-driven gated): event-handler methods scanned for DB-save plus bus-publish without a transactional outbox reference. Deterministic, semantic-resolved.
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.
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 shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×21) — JsonDynamicValue.cs:737, FileDocumentStore.cs:77, Arguments.cs:181, …
A placeholder string ("admin@example.com") is still in shipped code — typical of generated boilerplate that was never filled in. — Program.cs:59
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.
`EditAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×4) — ReCaptchaForgotPasswordFormDisplayDriver.cs:20, ReCaptchaLoginFormDisplayDriver.cs:20, ReCaptchaResetPasswordFormDisplayDriver.cs:20, …
`CommitAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — FileDocumentStore.cs:77
`AddAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — PositionWrapper.cs:46
`PlaceChildContent` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — CoreShapes.cs:13
`Read` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — LocalizedStringConverter.cs:14
`Slugify` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — SlugService.cs:12
A line of code has been commented out rather than removed — dead weight that rots and confuses. Delete it (version control remembers). (×21) — PublishContentViewModel.cs:9, Startup.cs:117, ModuleService.cs:105, …
What to do
Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
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 an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 232 of 235 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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 87/157 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 157, 4 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.
What to do
The .NET analyzers are running but not blocking — tighten them (set <AnalysisMode>All</AnalysisMode>, or treat analyzer warnings as errors on CI) so a security/quality regression fails the build rather than scrolling past as a warning.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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 & Backup7.0 / 10Strong✓ 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.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
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.
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 1200 use(s) across 247,331 production line(s) (~4.9/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.
66 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 Safety6.7 / 10Adequate✓ 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.
135 typed · 66 plain JS — the untyped files are src/OrchardCore.Modules/OrchardCore.AdminMenu/Assets/js/admin-menu-icon-picker.js, src/OrchardCore.Modules/OrchardCore.AdminMenu/Assets/js/admin-menu-permission-picker.js, src/OrchardCore.Modules/OrchardCore.ContentFields/Assets/js/OptionsEditor/optionsEditor.js, src/OrchardCore.Modules/OrchardCore.ContentFields/Assets/js/iconpicker-custom.js, src/OrchardCore.Modules/OrchardCore.ContentFields/Assets/js/vue-multiselect-multitextfieldpicker.js, src/OrchardCore.Modules/OrchardCore.ContentFields/Assets/js/vue-multiselect-userpicker.js (+60 more). 0 production file(s) opt out entirely with @ts-nocheck · 1 @ts-ignore suppression(s).
What to do
Migrate the remaining .js/.jsx files to TypeScript.
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.
src/OrchardCore.Modules/OrchardCore.Apis.GraphQL/Assets/webpack.config.js:18 · src/OrchardCore.Modules/OrchardCore.AuditTrail/Assets/webpack.config.js:17 — 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. — webpack.config.js:18
src/OrchardCore.Modules/OrchardCore.ContentFields/Assets/js/OptionsEditor/optionsEditor.js:65 · src/OrchardCore.Modules/OrchardCore.OpenId/Assets/js/parametersEditor/parametersEditor.js:48 · src/OrchardCore.Modules/OrchardCore.Seo/Assets/js/customMetaTagsEditor.js:49 — the 3 copies are spread across 3 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. — optionsEditor.js:65
src/OrchardCore.Modules/OrchardCore.ContentFields/Assets/js/trumbowyg.media.tag.ts:6 · src/OrchardCore.Modules/OrchardCore.Html/Assets/trumbowyg.media.tag.ts:6 — 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. — trumbowyg.media.tag.ts:6
src/OrchardCore.Modules/OrchardCore.ContentFields/Assets/js/trumbowyg.media.url.ts:7 · src/OrchardCore.Modules/OrchardCore.Html/Assets/trumbowyg.media.url.ts:7 — 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. — trumbowyg.media.url.ts:7
src/OrchardCore.Modules/OrchardCore.Media/Assets/media-gallery/src/services/ConfirmModalService.ts:38 · src/OrchardCore.Modules/OrchardCore.Media/Assets/media-gallery/src/services/FileActionModalService.ts:24 — 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. — ConfirmModalService.ts:38
src/OrchardCore.Modules/OrchardCore.OpenId/Assets/js/parametersEditor/parametersEditor.js:26 · src/OrchardCore.Modules/OrchardCore.Seo/Assets/js/customMetaTagsEditor.js:27 — 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. — parametersEditor.js:26
src/OrchardCore.Modules/OrchardCore.ContentFields/Assets/js/OptionsEditor/optionsEditor.js:21 · src/OrchardCore.Modules/OrchardCore.OpenId/Assets/js/parametersEditor/parametersEditor.js:14 — 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. — optionsEditor.js:21
src/OrchardCore.Modules/OrchardCore.Media/Assets/media-gallery/src/App.vue:337 · src/OrchardCore.Modules/OrchardCore.Media/Assets/media-gallery/src/main.ts:61 · src/OrchardCore.Modules/OrchardCore.Media/Assets/media-picker/src/components/MediaPickerModal.vue:95 — the 3 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. — App.vue:337
What to do
Extract the duplicated blocks into shared functions/components.
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) — list-management.js:84, workflow-canvas.ts:149, form-visibility-rules.js:256, …
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files8.5 / 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.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D33 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D33). Deterministic.
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 Code5.9 / 10Adequate✓ 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.
2 file(s) (~226 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — Assets
1 file(s) (~87 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — Assets
1 file(s) (~238 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — Assets
Unreachable from the 66 application, 20 tooling and 108 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 (66 application, 20 tooling, 108 test roots considered) (×4) — trumbowyg.table.js, trumbowyg.emoji.js, trumbowyg.fontsize.js, …
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.
Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — autocomplete.ts:1, UppyFileUpload.ts:37
Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — apiClient.ts:1
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. (×3)
Only test files import it — move it to devDependencies. — media-gallery-auth.spec.ts:170
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. (×25) — AutorouteValuesAddressScheme.cs:42, ContentMethodsProvider.cs:23, ContentMethodsProvider.cs:32, …
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 206/1461 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. (×25) — MenuController.cs:54, MenuController.cs:122, MenuController.cs:134, …
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.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×7) — FormInputElementVisibilityPartDisplayDriver.cs:146, DataProtectionFilters.cs:53, SecurityTokenService.cs:41, …
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.
3/209 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
~0.8 `!` suppressions per 1k syntax nodes — 27 suppression(s) across the 34650 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 — 26 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)
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
D11 Test Reliability — Test reliability not measured — no test run produced results
D12 Dependency Hygiene — Dependency Hygiene not included (time budget)
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Bounded contexts not declared
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — `dotnet list package --vulnerable` could not read this solution's dependency graph — it reported an error for at least one project and returned no package data at all (typically a packages.config / non-PackageReference project, which the command cannot read; classic .NET Framework projects are packages.config by default). No packages could be enumerated, so there was nothing to scan for NuGet CVEs — excluded rather than scored, because an unreadable dependency graph is not a clean one; migrate the project(s) to PackageReference to enable this scan
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — analyzer environment
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this check looks for
ED2 Event/command shape — no command-shaped messages detected — single-handler-per-command check not applicable
ED3 Event naming — no domain or integration events detected — event-naming check not applicable
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.
P8 Schema migrations — no EF Core usage detected
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
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 108 test file(s) reach none of 94 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
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.
NoWarnInCsproj tools/OpenApiClientGenerator/OpenApiClientGenerator.csproj:9— CA1707 — 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 test/OrchardCore.Tests/OrchardCore.Tests.csproj:7— CA1707 — 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 test/OrchardCore.Tests.Integration/OrchardCore.Tests.Integration.csproj:7— CA1707 — 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 test/OrchardCore.Tests.Functional/OrchardCore.Tests.Functional.csproj:7— CA1707 — 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 test/OrchardCore.Benchmarks/OrchardCore.Benchmarks.csproj:11— CA1707 — 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 test/OrchardCore.Abstractions.Tests/OrchardCore.Abstractions.Tests.csproj:8— CA1707 — 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 test/OrchardCore.Tests/OrchardCore.Tests.csproj:7— EnableGenerateDocumentationFile — 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 test/OrchardCore.Tests.Integration/OrchardCore.Tests.Integration.csproj:7— EnableGenerateDocumentationFile — 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 test/OrchardCore.Benchmarks/OrchardCore.Benchmarks.csproj:11— EnableGenerateDocumentationFile — 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 test/OrchardCore.Abstractions.Tests/OrchardCore.Abstractions.Tests.csproj:8— EnableGenerateDocumentationFile — 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 test/OrchardCore.Tests.Pages/OrchardCore.Application.Pages/OrchardCore.Application.Pages.csproj:10— EnableGenerateDocumentationFile — 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 src/OrchardCore.Mvc.Web/OrchardCore.Mvc.Web.csproj:9— 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 src/OrchardCore.Cms.Web/OrchardCore.Cms.Web.csproj:17— 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 Directory.Build.props:61— 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 src/OrchardCore.Build/OrchardCore.Commons.props:10— 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 src/Templates/OrchardCore.ProjectTemplates/OrchardCore.ProjectTemplates.csproj:22— CS8021 — 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 src/Templates/OrchardCore.ProjectTemplates/OrchardCore.ProjectTemplates.csproj:22— CS2008 — 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 src/Templates/OrchardCore.ProjectTemplates/OrchardCore.ProjectTemplates.csproj:22— CA1016 — 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 Directory.Build.props:23— CA1304 — 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 Directory.Build.props:23— CA1305 — 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 Directory.Build.props:23— CA1310 — 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 Directory.Build.props:26— CA1311 — 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 Directory.Build.props:29— CA1000 — 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 Directory.Build.props:32— CA1848 — 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 Directory.Build.props:35— CA1720 — 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.
+ 12 more in this group — see findings.md.
D38 · OSV Dependency Vulnerabilities· High CVE · ×29
High CVE: [GHSA redacted] yarn.lock— @babel/plugin-transform-modules-systemjs 7.29.0: [GHSA redacted] — @babel/plugin-transform-modules-systemjs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/plugin-transform-modules-systemjs to 7.29.4 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] yarn.lock— axios 0.21.4: [GHSA redacted] — this repo already declares axios ^1.7.0 directly, at or above the fixed 0.31.1; the vulnerable 0.21.4 is a second copy resolved for a dependency that requires an older range. Upgrade those dependents, or pin axios with an `overrides` entry (`resolutions` if you use Yarn) so only one copy resolves. This is 1 of 23 advisories with a published fix this scan raises against axios 0.21.4, and their fixed versions do not agree — anything below 0.33.0 still leaves at least one of them open. Take this package to 0.33.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 23 advisories this scan raises against axios 0.21.4: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— brace-expansion 1.1.13: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.16 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 3 advisories with a published fix this scan raises against brace-expansion 1.1.13, and their fixed versions do not agree — anything below 1.1.18 still leaves at least one of them open. Take this package to 1.1.18 or later: that is the floor for the package, not this row's target alone. This one row stands for the 3 advisories this scan raises against brace-expansion 1.1.13: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— brace-expansion 2.0.3: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 2.1.2 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 3 advisories with a published fix this scan raises against brace-expansion 2.0.3, and their fixed versions do not agree — anything below 2.1.4 still leaves at least one of them open. Take this package to 2.1.4 or later: that is the floor for the package, not this row's target alone. This one row stands for the 3 advisories this scan raises against brace-expansion 2.0.3: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— brace-expansion 2.1.2: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 2.1.3 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against brace-expansion 2.1.2, and their fixed versions do not agree — anything below 2.1.4 still leaves at least one of them open. Take this package to 2.1.4 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against brace-expansion 2.1.2: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— brace-expansion 5.0.5: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 5.0.7 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 4 advisories with a published fix this scan raises against brace-expansion 5.0.5, and their fixed versions do not agree — anything below 5.0.9 still leaves at least one of them open. Take this package to 5.0.9 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 brace-expansion 5.0.5: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— eazy-logger 3.1.0: [GHSA redacted] — eazy-logger is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.1.0 is a MAJOR ahead of the resolved 3.1.0, so an `overrides` pin would force a breaking version under a dependent written against 3.1.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] yarn.lock— engine.io 6.6.6: [GHSA redacted] — engine.io is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin engine.io to 6.6.7 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] yarn.lock— fast-uri 3.1.0: [GHSA redacted] — fast-uri is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fast-uri to 3.1.3 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 5 advisories with a published fix this scan raises against fast-uri 3.1.0, and their fixed versions do not agree — anything below 3.1.5 still leaves at least one of them open. Take this package to 3.1.5 or later: that is the floor for the package, not this row's target alone. This one row stands for the 5 advisories this scan raises against fast-uri 3.1.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— form-data 4.0.5: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin form-data to 4.0.6 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] yarn.lock— immutable 3.8.3: [GHSA redacted] — immutable is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.3.9 is a MAJOR ahead of the resolved 3.8.3, so an `overrides` pin would force a breaking version under a dependent written against 3.8.3; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This one row stands for the 2 advisories this scan raises against immutable 3.8.3: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— immutable 4.3.8: [GHSA redacted] — immutable is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin immutable to 4.3.9 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against immutable 4.3.8: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— immutable 5.1.5: [GHSA redacted] — immutable is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin immutable to 5.1.8 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against immutable 5.1.5: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— ip-address 10.1.0: [GHSA redacted] — ip-address is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ip-address to 10.3.1 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against ip-address 10.1.0, and their fixed versions do not agree — anything below 10.3.1 still leaves at least one of them open. Take this package to 10.3.1 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against ip-address 10.1.0: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— js-cookie 3.0.5: [GHSA redacted] — upgrade to 3.0.7
High CVE: [GHSA redacted] yarn.lock— js-yaml 4.1.1: [GHSA redacted] — js-yaml is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin js-yaml to 4.3.0 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against js-yaml 4.1.1, and their fixed versions do not agree — anything below 4.3.0 still leaves at least one of them open. Take this package to 4.3.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against js-yaml 4.1.1: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— linkify-it 3.0.3: [GHSA redacted] — linkify-it is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 5.0.1 is a MAJOR ahead of the resolved 3.0.3, so an `overrides` pin would force a breaking version under a dependent written against 3.0.3; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories with a published fix this scan raises against linkify-it 3.0.3, and their fixed versions do not agree — anything below 5.0.2 still leaves at least one of them open. Take this package to 5.0.2 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against linkify-it 3.0.3: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— lodash 4.17.23: [GHSA redacted] — this repo declares lodash ^4.17.21, a range that ALREADY admits the fixed 4.18.0, so there is no manifest edit to make here. Re-resolve the lock so lodash moves onto 4.18.0 or later; if the flagged 4.17.23 comes back, a dependency is pinning it — upgrade that dependent, or pin lodash with an `overrides` entry (`resolutions` if you use Yarn) so only one copy resolves. This one row stands for the 2 advisories this scan raises against lodash 4.17.23: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— minimatch 9.0.3: [GHSA redacted] — minimatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimatch to 9.0.7 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 3 advisories with a published fix this scan raises against minimatch 9.0.3, and their fixed versions do not agree — anything below 9.0.7 still leaves at least one of them open. Take this package to 9.0.7 or later: that is the floor for the package, not this row's target alone. This one row stands for the 3 advisories this scan raises against minimatch 9.0.3: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— postcss 7.0.39: [GHSA redacted] — this repo declares postcss 8.5.3, but the vulnerable 7.0.39 is a SEPARATE copy on another release line, so editing your own postcss entry cannot move it: upgrade the dependency that pulls it in (— 8.5.12 is a MAJOR ahead of the resolved 7.0.39, so an `overrides` pin would force a breaking version under a dependent written against 7.0.39; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 5 advisories with a published fix this scan raises against postcss 7.0.39, 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 5 advisories this scan raises against postcss 7.0.39: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— postcss 8.4.21: [GHSA redacted] — upgrade to 8.5.12. This is 1 of 5 advisories with a published fix this scan raises against postcss 8.4.21, 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 5 advisories this scan raises against postcss 8.4.21: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— postcss 8.5.3: [GHSA redacted] — upgrade to 8.5.12. This is 1 of 4 advisories with a published fix this scan raises against postcss 8.5.3, 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.3: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— postcss 8.5.8: [GHSA redacted] — upgrade to 8.5.12. This is 1 of 4 advisories with a published fix this scan raises against postcss 8.5.8, 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.8: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— qs 6.2.3: [GHSA redacted] — qs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin qs to 6.2.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against qs 6.2.3, and their fixed versions do not agree — anything below 6.14.1 still leaves at least one of them open. Take this package to 6.14.1 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against qs 6.2.3: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] yarn.lock— socket.io-parser 4.2.6: [GHSA redacted] — socket.io-parser is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin socket.io-parser to 4.2.7 with an `overrides` entry (`resolutions` if you use Yarn)).
EmptyCatchBlock src/OrchardCore.Modules/OrchardCore.Forms/Drivers/FormInputElementVisibilityPartDisplayDriver.cs:146— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/OrchardCore.Modules/OrchardCore.Liquid/Filters/DataProtectionFilters.cs:53— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/OrchardCore.Modules/OrchardCore.Workflows/Services/SecurityTokenService.cs:41— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/OrchardCore/OrchardCore.Abstractions/Json/Dynamic/JsonDynamicValue.cs:154— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/OrchardCore/OrchardCore.Data.YesSql/DbConnectionValidator.cs:159— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/OrchardCore/OrchardCore.Lucene.Core/LuceneIndexStore.cs:100— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
EmptyCatchBlock src/OrchardCore/OrchardCore/Shell/Distributed/DistributedShellHostedService.cs:769— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Narrow the catch to the exception you actually expect, record it through whatever this codebase already uses to report problems, or — where swallowing really is correct, as it often is on a teardown/dispose path where throwing would mask the original failure — write down WHY in a comment on the catch. The comment has to give the reason: a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all and leaves this row in place. Any of the three makes the decision reviewable; all three clear this row.
Critical CVE: [GHSA redacted] yarn.lock— shell-quote 1.8.3: [GHSA redacted] — shell-quote is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin shell-quote to 1.8.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against shell-quote 1.8.3, and their fixed versions do not agree — anything below 1.9.0 still leaves at least one of them open. Take this package to 1.9.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against shell-quote 1.8.3: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] yarn.lock— tar 7.5.13: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin tar to 7.5.19 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 6 advisories with a published fix this scan raises against tar 7.5.13, and their fixed versions do not agree — anything below 7.5.21 still leaves at least one of them open. Take this package to 7.5.21 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against tar 7.5.13: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] yarn.lock— websocket-driver 0.7.4: [GHSA redacted] — websocket-driver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin websocket-driver to 0.7.5 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against websocket-driver 0.7.4: [GHSA redacted], [GHSA redacted].
Boundary-crossing change coupling: LocalizationEntries.cs ↔ AutorouteEntries.cs src/OrchardCore.Modules/OrchardCore.ContentLocalization/Services/LocalizationEntries.cs— `src/OrchardCore.Modules/OrchardCore.ContentLocalization/Services/LocalizationEntries.cs` (context OrchardCore.Modules) and `src/OrchardCore/OrchardCore.Autoroute.Core/Services/AutorouteEntries.cs` (context OrchardCore) 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.
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×1
High vulnerability: [GHSA redacted] yarn.lock— serialize-javascript 6.0.2: [GHSA redacted] — serialize-javascript is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 7.0.3 is a MAJOR ahead of the resolved 6.0.2, so an `overrides` pin would force a breaking version under a dependent written against 6.0.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories with a published fix this scan raises against serialize-javascript 6.0.2, and their fixed versions do not agree — anything below 7.0.5 still leaves at least one of them open. Take this package to 7.0.5 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against serialize-javascript 6.0.2: [GHSA redacted], [GHSA redacted].
TodoComment src/OrchardCore.Modules/OrchardCore.AdminMenu/AdminNodes/LinkAdminNodeNavigationBuilder.cs:74— // Todo: This logic can be shared by all TreeNodeNavigationBuilders. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.AdminMenu/AdminNodes/PlaceholderAdminNodeNavigationBuilder.cs:50— // todo: this logic can be shared by all TreeNodeNavigationBuilders — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/MenuController.cs:74— // todo: handle the case where there is a deserialization exception on some of the presets. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Apis.GraphQL/OrchardFieldNameConverter.cs:10— // todo: custom argument name? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Apis.GraphQL/OrchardFieldNameConverter.cs:16— // TODO: check functionality. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Apis.GraphQL/ValidationRules/RequiresPermissionValidationRule.cs:56— // AuthorizeNodePermissionAsync(fieldAst, fieldDef.ResolvedType.GetNamedType(), validationContext, userContext).GetAwaiter().GetResult(); // TODO: need to think of something to avoid this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.AuditTrail/Services/DefaultAuditTrailAdminListFilterProvider.cs:153— // TODO add a context property to the mapping func. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.AuditTrail/Services/DefaultAuditTrailAdminListFilterProvider.cs:161— // TODO add a context property to the mapping func. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.ContentPreview/Controllers/PreviewController.cs:87— // TODO: we should probably get this value from the main editor as it might impact validators. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.ContentTypes/Startup.cs:56— // TODO: Put in its own feature to be able to execute this recipe without having to enable — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Contents/Deployment/ContentDeploymentSource.cs:22— // TODO: Batch and create separate content files in the result. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Contents/Drivers/OwnerEditorDriver.cs:51— // TODO Move this editor to a user picker. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Email/Workflows/Activities/EmailTask.cs:52— // TODO: Add support for the following format: Jack Bauer<jack@ctu.com>, ... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Flows/Drivers/BagPartDisplayDriver.cs:187— // TODO, some how here contentItems should be sorted by a defined order — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Forms/Workflows/Activities/ValidateFormFieldTask.cs:10— // TODO: Add the ability to configure various types of validators. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Lists/Handlers/ContainedPartLocalizationHandler.cs:25— // todo: remove this check and change the handler to target ContainedPart when issue 3890 is fixed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Markdown/Razor/ContentRazorHelperExtensions.cs:42— // TODO: provide context argument (optional on this helper as with the liquid helper?). — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Settings/Services/SetupEventHandler.cs:29— // TODO: Add Encryption Settings in. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Taxonomies/Indexing/TaxonomyFieldIndexHandler.cs:21— // TODO: Also add the parents of each term, probably as a separate field — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Taxonomies/Services/TaxonomyContentsAdminListFilter.cs:13— // TODO Create a Terms Index independent of the standard index, which can index taxonomy terms by their display text
TodoComment src/OrchardCore.Modules/OrchardCore.Themes/Services/ThemeService.cs:81— // TODO: MWP: probably follow on issue: should this be recursive? maybe with a depth limit? i.e. base3->base2->base1 ... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Users/Controllers/AdminController.cs:171— // TODO Candidate for dynamic localization. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Users/Deployment/CustomUserSettingsDeploymentSource.cs:29— // Todo: check permissions for each settings type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Users/Liquid/UserEmailFilter.cs:29— // Todo: Use 'IdentityOptions.ClaimsIdentity.EmailClaimType' that will be supported in a future version. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/OrchardCore.Modules/OrchardCore.Users/Migrations.cs:19— // TODO These should have defaults. on SQL Server they will fall at 255. Exceptions are currently thrown if you go over that. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TooManyMethods: JsonDynamicValue src/OrchardCore/OrchardCore.Abstractions/Json/Dynamic/JsonDynamicValue.cs:0— TooManyMethods — 351 significant lines (blank, comment-only and punctuation-only lines excluded), 112 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UserStore src/OrchardCore/OrchardCore.Users.Core/Services/UserStore.cs:0— TooManyMethods — 408 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ContentPartHandler src/OrchardCore/OrchardCore.ContentManagement.Abstractions/Handlers/ContentPartHandler.cs:0— TooManyMethods — 142 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: ContentFieldHandler src/OrchardCore/OrchardCore.ContentManagement.Abstractions/Handlers/ContentFieldHandler.cs:0— TooManyMethods — 134 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
TooManyMethods: OpenIdApplicationStore src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdApplicationStore.cs:0— TooManyMethods — 208 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OpenIdTokenStore src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:0— TooManyMethods — 288 significant lines (blank, comment-only and punctuation-only lines excluded), 46 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AdminController src/OrchardCore.Modules/OrchardCore.RateLimits/Controllers/AdminController.cs:0— TooManyMethods — 490 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ResourceManager src/OrchardCore/OrchardCore.ResourceManagement/ResourceManager.cs:0— TooManyMethods — 326 significant lines (blank, comment-only and punctuation-only lines excluded), 39 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AdminController src/OrchardCore.Modules/OrchardCore.ContentTypes/Controllers/AdminController.cs:0— TooManyMethods — 583 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ShellScope src/OrchardCore/OrchardCore.Abstractions/Shell/Scope/ShellScope.cs:0— TooManyMethods — 210 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SqlTranslator src/OrchardCore.Modules/OrchardCore.Queries/Sql/SqlTranslator.cs:0— TooManyMethods — 401 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OpenIdAuthorizationStore src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:0— TooManyMethods — 252 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ContentPartHandlerCoordinator src/OrchardCore/OrchardCore.ContentManagement/Handlers/ContentPartHandlerCoordinator.cs:0— TooManyMethods — 287 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ContentDefinitionManager src/OrchardCore/OrchardCore.ContentManagement/ContentDefinitionManager.cs:0— TooManyMethods — 237 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: OpenIdScopeStore src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdScopeStore.cs:0— TooManyMethods — 141 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Off the main sequence: OrchardCore.ContentPreview.Abstractions — OrchardCore.ContentPreview.Abstractions: abstractness 0.00, instability 0.00, distance 1.00 — 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: OrchardCore.ResourceManagement.Core — OrchardCore.ResourceManagement.Core: abstractness 0.00, instability 0.02, distance 0.98 — zone of pain — concrete and depended on by 80 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.Data — OrchardCore.Data: abstractness 0.00, instability 0.03, distance 0.97 — zone of pain — concrete and depended on by 69 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.ResourceManagement — OrchardCore.ResourceManagement: abstractness 0.00, instability 0.04, distance 0.96 — zone of pain — concrete and depended on by 78 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.Data.YesSql — OrchardCore.Data.YesSql: abstractness 0.00, instability 0.06, distance 0.94 — zone of pain — concrete and depended on by 67 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.Mvc.Core — OrchardCore.Mvc.Core: abstractness 0.05, instability 0.02, distance 0.94 — zone of pain — concrete and depended on by 124 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.ResourceManagement.Abstractions — OrchardCore.ResourceManagement.Abstractions: abstractness 0.17, instability 0.00, distance 0.83 — 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: OrchardCore.Admin.Abstractions — OrchardCore.Admin.Abstractions: abstractness 0.14, instability 0.05, distance 0.81 — 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: OrchardCore.Roles.Core — OrchardCore.Roles.Core: abstractness 0.00, instability 0.21, distance 0.79 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.ContentManagement — OrchardCore.ContentManagement: abstractness 0.00, instability 0.21, distance 0.79 — zone of pain — concrete and depended on by 59 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.ContentFields.Core — OrchardCore.ContentFields.Core: abstractness 0.00, instability 0.22, distance 0.78 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.Liquid.Abstractions — OrchardCore.Liquid.Abstractions: abstractness 0.22, instability 0.01, 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: OrchardCore.ContentManagement.Abstractions — OrchardCore.ContentManagement.Abstractions: abstractness 0.22, instability 0.03, distance 0.75 — 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: OrchardCore — OrchardCore: abstractness 0.01, instability 0.25, distance 0.74 — zone of pain — concrete and depended on by 15 project(s), so it's rigid to change.
Off the main sequence: OrchardCore.Feeds.Core — OrchardCore.Feeds.Core: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×14
Medium CVE: [GHSA redacted] yarn.lock— @parcel/reporter-dev-server 2.13.3: [GHSA redacted] — @parcel/reporter-dev-server is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @parcel/reporter-dev-server to 2.16.4 with an `overrides` entry (`resolutions` if you use Yarn)).
Medium CVE: [GHSA redacted] yarn.lock— follow-redirects 1.15.11: [GHSA redacted] — follow-redirects is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin follow-redirects to 1.16.0 with an `overrides` entry (`resolutions` if you use Yarn)).
Medium CVE: [GHSA redacted] yarn.lock— http-proxy-middleware 2.0.9: [GHSA redacted] — http-proxy-middleware is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin http-proxy-middleware to 2.0.10 with an `overrides` entry (`resolutions` if you use Yarn)).
Medium CVE: [GHSA redacted] yarn.lock— jquery 3.4.1: [GHSA redacted] — this repo already declares jquery 3.7.1 directly, at or above the fixed 3.5.0; the vulnerable 3.4.1 is a second copy resolved for a dependency that requires an older range. Upgrade those dependents, or pin jquery with an `overrides` entry (`resolutions` if you use Yarn) so only one copy resolves. This one row stands for the 2 advisories this scan raises against jquery 3.4.1: [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] yarn.lock— launch-editor 2.13.2: [GHSA redacted] — launch-editor is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin launch-editor to 2.14.1 with an `overrides` entry (`resolutions` if you use Yarn)).
Medium CVE: [GHSA redacted] yarn.lock— markdown-it 12.3.2: [GHSA redacted] — markdown-it is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 14.2.0 is a MAJOR ahead of the resolved 12.3.2, so an `overrides` pin would force a breaking version under a dependent written against 12.3.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Medium CVE: [GHSA redacted] yarn.lock— postcss 8.5.20: [GHSA redacted] — upgrade to 8.5.23
Medium CVE: [GHSA redacted] yarn.lock— pug 3.0.2: [GHSA redacted] — upgrade to 3.0.3
Medium CVE: [GHSA redacted] yarn.lock— qs 6.14.2: [GHSA redacted] — qs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin qs to 6.15.2 with an `overrides` entry (`resolutions` if you use Yarn)).
Medium CVE: [GHSA redacted] yarn.lock— qs 6.15.0: [GHSA redacted] — qs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin qs to 6.15.2 with an `overrides` entry (`resolutions` if you use Yarn)).
Medium CVE: [GHSA redacted] yarn.lock— uuid 8.3.2: [GHSA redacted] — this repo declares uuid 9.0.1, but the vulnerable 8.3.2 is a SEPARATE copy on another release line, so editing your own uuid entry cannot move it: upgrade the dependency that pulls it in (— 11.1.1 is a MAJOR ahead of the resolved 8.3.2, so an `overrides` pin would force a breaking version under a dependent written against 8.3.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Medium CVE: [GHSA redacted] yarn.lock— uuid 9.0.1: [GHSA redacted] — upgrade to 11.1.1
Medium CVE: [GHSA redacted] yarn.lock— vue-template-compiler 2.7.16: [GHSA redacted] — no fixed version has been published yet. Track the advisory; vue-template-compiler is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent.
Medium CVE: [GHSA redacted] yarn.lock— webpack-dev-server 5.2.3: [GHSA redacted] — this repo declares webpack-dev-server ^5.2.0, a range that ALREADY admits the fixed 5.2.4, so there is no manifest edit to make here. Re-resolve the lock so webpack-dev-server moves onto 5.2.4 or later; if the flagged 5.2.3 comes back, a dependency is pinning it — upgrade that dependent, or pin webpack-dev-server with an `overrides` entry (`resolutions` if you use Yarn) so only one copy resolves. This is 1 of 4 advisories with a published fix this scan raises against webpack-dev-server 5.2.3, and their fixed versions do not agree — anything below 5.2.6 still leaves at least one of them open. Take this package to 5.2.6 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 webpack-dev-server 5.2.3: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Duplicated block (16 lines × 2) src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:322— src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:322-337 | src/OrchardCore/OrchardCore.ContentManagement.Abstractions/Utilities/StringExtensions.cs:251-266 — 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 `src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:322` 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 (16 lines × 2) src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:346— src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:346-361 | src/OrchardCore/OrchardCore.ContentManagement.Abstractions/Utilities/StringExtensions.cs:270-285 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:346` 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 (16 lines × 2) src/OrchardCore.Modules/OrchardCore.AzureAI/Migrations/AzureAISearchIndexSettingsMigrations.cs:267— src/OrchardCore.Modules/OrchardCore.AzureAI/Migrations/AzureAISearchIndexSettingsMigrations.cs:267-282 | src/OrchardCore.Modules/OrchardCore.Elasticsearch/Migrations/IndexingMigrations.cs:242-257 — 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 (16 lines × 2) src/OrchardCore.Modules/OrchardCore.Contents/Deployment/Download/DownloadController.cs:30— src/OrchardCore.Modules/OrchardCore.Contents/Deployment/Download/DownloadController.cs:30-45 | src/OrchardCore.Modules/OrchardCore.Contents/Deployment/Download/DownloadController.cs:61-76 — 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 `src/OrchardCore.Modules/OrchardCore.Contents/Deployment/Download/DownloadController.cs:30` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/OrchardCore.Modules/OrchardCore.Contents/Sitemaps/ContentTypesSitemapSourceUpdateHandler.cs:37— src/OrchardCore.Modules/OrchardCore.Contents/Sitemaps/ContentTypesSitemapSourceUpdateHandler.cs:37-54 | src/OrchardCore.Modules/OrchardCore.Sitemaps/Handlers/SitemapIndexTypeUpdateHandler.cs:40-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 `src/OrchardCore.Modules/OrchardCore.Contents/Sitemaps/ContentTypesSitemapSourceUpdateHandler.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexStep.cs:32— src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexStep.cs:32-47 | src/OrchardCore/OrchardCore.Elasticsearch.Core/Recipes/ElasticsearchIndexStep.cs:34-49 — 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 `src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexStep.cs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/AdminController.cs:81— src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/AdminController.cs:81-96 | src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/SitemapIndexController.cs:75-90 — 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 `src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/AdminController.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 (16 lines × 2) src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/AdminController.cs:285— src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/AdminController.cs:285-300 | src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/SitemapIndexController.cs:287-302 — 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 `src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/AdminController.cs:285` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) src/OrchardCore.Modules/OrchardCore.Templates/Services/AdminPreviewTemplatesProvider.cs:22— src/OrchardCore.Modules/OrchardCore.Templates/Services/AdminPreviewTemplatesProvider.cs:22-37 | src/OrchardCore.Modules/OrchardCore.Templates/Services/PreviewTemplatesProvider.cs:22-37 — 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 `src/OrchardCore.Modules/OrchardCore.Templates/Services/AdminPreviewTemplatesProvider.cs:22` 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) src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/AdminController.cs:598— src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/AdminController.cs:598-613 | src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/AdminController.cs:633-648 — 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 (16 lines × 2) src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/TenantApiController.cs:239— src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/TenantApiController.cs:239-254 | src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/TenantApiController.cs:269-284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) src/OrchardCore/OrchardCore.AzureAI.Core/Handlers/AzureAISearchIndexProfileHandler.cs:95— src/OrchardCore/OrchardCore.AzureAI.Core/Handlers/AzureAISearchIndexProfileHandler.cs:95-110 | src/OrchardCore/OrchardCore.Elasticsearch.Core/Handlers/ElasticsearchIndexProfileHandler.cs:129-144 — 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 `src/OrchardCore/OrchardCore.AzureAI.Core/Handlers/AzureAISearchIndexProfileHandler.cs:95` 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 (16 lines × 2) src/OrchardCore/OrchardCore.UrlRewriting.Core/Services/UrlRedirectRuleSource.cs:34— src/OrchardCore/OrchardCore.UrlRewriting.Core/Services/UrlRedirectRuleSource.cs:34-49 | src/OrchardCore/OrchardCore.UrlRewriting.Core/Services/UrlRewriteRuleSource.cs:34-49 — 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 `src/OrchardCore/OrchardCore.UrlRewriting.Core/Services/UrlRedirectRuleSource.cs:34` 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 (17 lines × 2) src/OrchardCore/OrchardCore.Mvc.Core/ModuleProjectRazorFileProvider.cs:135— src/OrchardCore/OrchardCore.Mvc.Core/ModuleProjectRazorFileProvider.cs:135-151 | src/OrchardCore/OrchardCore.Abstractions/Modules/ModuleEmbeddedFileProvider.cs:69-85 — 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 `src/OrchardCore/OrchardCore.Mvc.Core/ModuleProjectRazorFileProvider.cs:135` 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 (17 lines × 2) src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/NodeController.cs:257— src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/NodeController.cs:257-273 | src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/NodeController.cs:292-308 — 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 `src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/NodeController.cs:257` 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 (17 lines × 2) src/OrchardCore.Modules/OrchardCore.Menu/Controllers/AdminController.cs:80— src/OrchardCore.Modules/OrchardCore.Menu/Controllers/AdminController.cs:80-96 | src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:102-118 — 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 (17 lines × 2) src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/AdminController.cs:308— src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/AdminController.cs:308-324 | src/OrchardCore.Modules/OrchardCore.Sitemaps/Controllers/SitemapIndexController.cs:310-326 — 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 (17 lines × 2) src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:53— src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:53-69 | src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:84-100 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:53` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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 (17 lines × 2) src/OrchardCore.Modules/OrchardCore.Features/Controllers/AdminController.cs:110— src/OrchardCore.Modules/OrchardCore.Features/Controllers/AdminController.cs:110-126 | src/OrchardCore.Modules/OrchardCore.Features/Controllers/AdminController.cs:150-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 `src/OrchardCore.Modules/OrchardCore.Features/Controllers/AdminController.cs:110` 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 (17 lines × 2) src/OrchardCore/OrchardCore.DisplayManagement/Razor/RazorPage.cs:70— src/OrchardCore/OrchardCore.DisplayManagement/Razor/RazorPage.cs:70-87 | src/OrchardCore/OrchardCore.DisplayManagement/RazorPages/Page.cs:67-83 — 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 (17 lines × 2) src/OrchardCore/OrchardCore.Infrastructure/Shells.Database/Configuration/DatabaseShellsSettingsSources.cs:77— src/OrchardCore/OrchardCore.Infrastructure/Shells.Database/Configuration/DatabaseShellsSettingsSources.cs:77-94 | src/OrchardCore/OrchardCore/Shell/Configuration/ShellsSettingsSources.cs:35-51 — 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 `src/OrchardCore/OrchardCore.Infrastructure/Shells.Database/Configuration/DatabaseShellsSettingsSources.cs:77` 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 (17 lines × 2) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Migrations/OpenIdMigrations.cs:27— src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Migrations/OpenIdMigrations.cs:27-43 | src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Migrations/OpenIdMigrations.cs:406-422 — 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 `src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Migrations/OpenIdMigrations.cs:27` 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 (17 lines × 2) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Migrations/OpenIdMigrations.cs:98— src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Migrations/OpenIdMigrations.cs:98-114 | src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Migrations/OpenIdMigrations.cs:449-465 — 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 `src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Migrations/OpenIdMigrations.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 (17 lines × 2) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:415— src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:415-431 | src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:448-464 — 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 `src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:415` 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 (17 lines × 2) src/OrchardCore/OrchardCore/Shell/Removing/ShellSiteFolderRemovingHandler.cs:34— src/OrchardCore/OrchardCore/Shell/Removing/ShellSiteFolderRemovingHandler.cs:34-50 | src/OrchardCore/OrchardCore/Shell/Removing/ShellWebRootRemovingHandler.cs:38-54 — 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 `src/OrchardCore/OrchardCore/Shell/Removing/ShellSiteFolderRemovingHandler.cs:34` 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) src/OrchardCore.Modules/OrchardCore.Html/Migrations.cs:69— src/OrchardCore.Modules/OrchardCore.Html/Migrations.cs:69-83 | src/OrchardCore.Modules/OrchardCore.Title/Migrations.cs:47-61 — 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 `src/OrchardCore.Modules/OrchardCore.Html/Migrations.cs:69` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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 (15 lines × 2) src/OrchardCore.Modules/OrchardCore.Media/Liquid/MediaAnchorTag.cs:80— src/OrchardCore.Modules/OrchardCore.Media/Liquid/MediaAnchorTag.cs:80-94 | src/OrchardCore/OrchardCore.DisplayManagement.Liquid/Tags/AnchorTag.cs:184-198 — 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 `src/OrchardCore.Modules/OrchardCore.Media/Liquid/MediaAnchorTag.cs:80` 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) src/OrchardCore.Modules/OrchardCore.Taxonomies/Drivers/TaxonomyFieldDisplayDriver.cs:48— src/OrchardCore.Modules/OrchardCore.Taxonomies/Drivers/TaxonomyFieldDisplayDriver.cs:48-62 | src/OrchardCore.Modules/OrchardCore.Taxonomies/Drivers/TaxonomyFieldTagsDisplayDriver.cs:50-64 — 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 (15 lines × 2) src/OrchardCore.Modules/OrchardCore.BackgroundTasks/Controllers/BackgroundTaskController.cs:229— src/OrchardCore.Modules/OrchardCore.BackgroundTasks/Controllers/BackgroundTaskController.cs:229-243 | src/OrchardCore.Modules/OrchardCore.BackgroundTasks/Controllers/BackgroundTaskController.cs:258-272 — 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 `src/OrchardCore.Modules/OrchardCore.BackgroundTasks/Controllers/BackgroundTaskController.cs:229` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/OrchardCore.Modules/OrchardCore.Email.Azure/Services/AzureEmailProviderBase.cs:113— src/OrchardCore.Modules/OrchardCore.Email.Azure/Services/AzureEmailProviderBase.cs:113-127 | src/OrchardCore.Modules/OrchardCore.Email.Smtp/Services/SmtpEmailProviderBase.cs:49-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 `src/OrchardCore.Modules/OrchardCore.Email.Azure/Services/AzureEmailProviderBase.cs:113` 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 (15 lines × 2) src/OrchardCore.Modules/OrchardCore.OpenId/Controllers/ServerConfigurationController.cs:80— src/OrchardCore.Modules/OrchardCore.OpenId/Controllers/ServerConfigurationController.cs:80-94 | src/OrchardCore.Modules/OrchardCore.OpenId/Controllers/ValidationConfigurationController.cs:80-94 — 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 (15 lines × 2) src/OrchardCore.Modules/OrchardCore.Resources/Liquid/ScriptBlock.cs:22— src/OrchardCore.Modules/OrchardCore.Resources/Liquid/ScriptBlock.cs:22-36 | src/OrchardCore.Modules/OrchardCore.Resources/Liquid/StyleBlock.cs:22-36 — 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 `src/OrchardCore.Modules/OrchardCore.Resources/Liquid/ScriptBlock.cs:22` 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 (15 lines × 2) src/OrchardCore.Modules/OrchardCore.Resources/Liquid/ScriptTag.cs:25— src/OrchardCore.Modules/OrchardCore.Resources/Liquid/ScriptTag.cs:25-39 | src/OrchardCore.Modules/OrchardCore.Resources/Liquid/StyleTag.cs:25-39 — 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 `src/OrchardCore.Modules/OrchardCore.Resources/Liquid/ScriptTag.cs:25` 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 (15 lines × 2) src/OrchardCore/OrchardCore.AzureAI.Core/Recipes/AzureAISearchIndexRebuildStep.cs:20— src/OrchardCore/OrchardCore.AzureAI.Core/Recipes/AzureAISearchIndexRebuildStep.cs:20-34 | src/OrchardCore/OrchardCore.AzureAI.Core/Recipes/AzureAISearchIndexResetStep.cs:20-34 — 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 `src/OrchardCore/OrchardCore.AzureAI.Core/Recipes/AzureAISearchIndexRebuildStep.cs:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/OrchardCore/OrchardCore.DisplayManagement.Liquid/Cache/CacheExpiresAfterTag.cs:15— src/OrchardCore/OrchardCore.DisplayManagement.Liquid/Cache/CacheExpiresAfterTag.cs:15-29 | src/OrchardCore/OrchardCore.DisplayManagement.Liquid/Cache/CacheExpiresSlidingTag.cs:15-29 — 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 `src/OrchardCore/OrchardCore.DisplayManagement.Liquid/Cache/CacheExpiresAfterTag.cs:15` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) src/OrchardCore/OrchardCore.Lucene.Core/QueryProviders/BooleanQueryProvider.cs:88— src/OrchardCore/OrchardCore.Lucene.Core/QueryProviders/BooleanQueryProvider.cs:88-102 | src/OrchardCore/OrchardCore.Lucene.Core/QueryProviders/BooleanQueryProvider.cs:107-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:239— src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:239-253 | src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/StyleTagHelper.cs:238-252 — 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 `src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:239` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Low cohesion: UserStore (LCOM4 41) src/OrchardCore/OrchardCore.Users.Core/Services/UserStore.cs:14— UserStore's methods form 41 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: OpenIdApplicationStore (LCOM4 33) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdApplicationStore.cs:16— OpenIdApplicationStore's methods form 33 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: OpenIdTokenStore (LCOM4 25) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:17— OpenIdTokenStore's methods form 25 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: OpenIdScopeStore (LCOM4 17) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdScopeStore.cs:15— OpenIdScopeStore's methods form 17 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: OpenIdAuthorizationStore (LCOM4 16) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:18— OpenIdAuthorizationStore's methods form 16 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: RoleStore (LCOM4 9) src/OrchardCore.Modules/OrchardCore.Roles/Services/RoleStore.cs:13— RoleStore's methods form 9 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: ViewBufferTextWriterContent (LCOM4 6) src/OrchardCore/OrchardCore.DisplayManagement.Liquid/ViewBufferTextWriterContent.cs:11— ViewBufferTextWriterContent's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: ZoneOnDemand (LCOM4 6) src/OrchardCore/OrchardCore.DisplayManagement/Zones/ZoneOnDemand.cs:11— ZoneOnDemand's methods form 6 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: HomeController (LCOM4 4) src/OrchardCore.Modules/OrchardCore.Demo/Controllers/HomeController.cs:15— HomeController's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: TwoFactorAuthenticationController (LCOM4 4) src/OrchardCore.Modules/OrchardCore.Users/Controllers/TwoFactorAuthenticationController.cs:23— TwoFactorAuthenticationController's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: ShapeMetadata (LCOM4 4) src/OrchardCore/OrchardCore.DisplayManagement/Shapes/ShapeMetadata.cs:9— ShapeMetadata's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Low cohesion: ContentIndexProfileHandler (LCOM4 4) src/OrchardCore/OrchardCore.Indexing.Core/Handlers/ContentIndexProfileHandler.cs:13— ContentIndexProfileHandler's methods form 4 groups that share no state and don't call each other — a sign it may have several responsibilities. Review whether it splits into focused classes.
Duplicated block (18 lines × 2) src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:365— src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:365-382 | src/OrchardCore/OrchardCore.ContentManagement.Abstractions/Utilities/StringExtensions.cs:289-306 — 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 `src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:365` 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 (18 lines × 2) src/OrchardCore.Modules/OrchardCore.ContentTypes/Controllers/AdminController.cs:1117— src/OrchardCore.Modules/OrchardCore.ContentTypes/Controllers/AdminController.cs:1117-1134 | src/OrchardCore.Modules/OrchardCore.ContentTypes/Controllers/AdminController.cs:1145-1162 — 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 `src/OrchardCore.Modules/OrchardCore.ContentTypes/Controllers/AdminController.cs:1117` 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 (18 lines × 2) src/OrchardCore.Modules/OrchardCore.Elasticsearch/GraphQL/ElasticsearchQueryFieldTypeProvider.cs:73— src/OrchardCore.Modules/OrchardCore.Elasticsearch/GraphQL/ElasticsearchQueryFieldTypeProvider.cs:73-90 | src/OrchardCore.Modules/OrchardCore.Queries/Sql/GraphQL/SqlQueryFieldTypeProvider.cs:77-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/OrchardCore.Modules/OrchardCore.Elasticsearch/GraphQL/ElasticsearchQueryFieldTypeProvider.cs:73` 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 (18 lines × 2) src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexRebuildStep.cs:43— src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexRebuildStep.cs:43-60 | src/OrchardCore/OrchardCore.Elasticsearch.Core/Recipes/ElasticsearchIndexRebuildStep.cs:44-61 — 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 `src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexRebuildStep.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.
Duplicated block (18 lines × 2) src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexResetStep.cs:43— src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexResetStep.cs:43-60 | src/OrchardCore/OrchardCore.Elasticsearch.Core/Recipes/ElasticsearchIndexResetStep.cs:44-61 — 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 `src/OrchardCore.Modules/OrchardCore.Lucene/Recipes/LuceneIndexResetStep.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.
Duplicated block (18 lines × 2) src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:185— src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:185-202 | src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:243-260 — 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 `src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:185` 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 (18 lines × 2) src/OrchardCore.Modules/OrchardCore.RateLimits/Controllers/LimiterController.cs:155— src/OrchardCore.Modules/OrchardCore.RateLimits/Controllers/LimiterController.cs:155-172 | src/OrchardCore.Modules/OrchardCore.RateLimits/Controllers/LimiterController.cs:187-204 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) src/OrchardCore.Modules/OrchardCore.Tenants/Workflows/Activities/DisableTenantTask.cs:35— src/OrchardCore.Modules/OrchardCore.Tenants/Workflows/Activities/DisableTenantTask.cs:35-52 | src/OrchardCore.Modules/OrchardCore.Tenants/Workflows/Activities/EnableTenantTask.cs:36-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.
Duplicated block (18 lines × 2) src/OrchardCore/OrchardCore.Elasticsearch.Core/Services/ElasticsearchIndexManager.cs:130— src/OrchardCore/OrchardCore.Elasticsearch.Core/Services/ElasticsearchIndexManager.cs:130-147 | src/OrchardCore/OrchardCore.Elasticsearch.Core/Services/ElasticsearchIndexManager.cs:279-297 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:111— src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:111-128 | src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/StyleTagHelper.cs:112-129 — 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 `src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) src/OrchardCore/OrchardCore.Shells.Azure/Configuration/BlobShellConfigurationSources.cs:67— src/OrchardCore/OrchardCore.Shells.Azure/Configuration/BlobShellConfigurationSources.cs:67-84 | src/OrchardCore/OrchardCore/Shell/Configuration/ShellConfigurationSources.cs:40-57 — 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 `src/OrchardCore/OrchardCore.Shells.Azure/Configuration/BlobShellConfigurationSources.cs:67` 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.
Hotspot: src/OrchardCore.Modules/OrchardCore.Users/Controllers/ExternalAuthenticationsController.cs src/OrchardCore.Modules/OrchardCore.Users/Controllers/ExternalAuthenticationsController.cs— src/OrchardCore.Modules/OrchardCore.Users/Controllers/ExternalAuthenticationsController.cs changed 6 times in last 90 days, max complexity 25. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/OrchardCore.Modules/OrchardCore.Media/Startup.cs src/OrchardCore.Modules/OrchardCore.Media/Startup.cs— src/OrchardCore.Modules/OrchardCore.Media/Startup.cs changed 6 times in last 90 days, max complexity 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/OrchardCore/OrchardCore.DisplayManagement.Liquid/Tags/AnchorTag.cs src/OrchardCore/OrchardCore.DisplayManagement.Liquid/Tags/AnchorTag.cs— src/OrchardCore/OrchardCore.DisplayManagement.Liquid/Tags/AnchorTag.cs changed 2 times in last 90 days, max complexity 48. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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: src/OrchardCore.Modules/OrchardCore.Security/Views/PermissionsPolicySettings.Edit.cshtml src/OrchardCore.Modules/OrchardCore.Security/Views/PermissionsPolicySettings.Edit.cshtml— src/OrchardCore.Modules/OrchardCore.Security/Views/PermissionsPolicySettings.Edit.cshtml changed 3 times in last 90 days, max complexity 31. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. 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: src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/TenantApiController.cs src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/TenantApiController.cs— src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/TenantApiController.cs changed 2 times in last 90 days, max complexity 33. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/OrchardCore.Modules/OrchardCore.Users/Startup.cs src/OrchardCore.Modules/OrchardCore.Users/Startup.cs— src/OrchardCore.Modules/OrchardCore.Users/Startup.cs changed 4 times in last 90 days, max complexity 16. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. 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: src/OrchardCore.Modules/OrchardCore.Setup/Controllers/SetupController.cs src/OrchardCore.Modules/OrchardCore.Setup/Controllers/SetupController.cs— src/OrchardCore.Modules/OrchardCore.Setup/Controllers/SetupController.cs changed 3 times in last 90 days, max complexity 19. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs— src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs changed 2 times in last 90 days, max complexity 28. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: src/OrchardCore/OrchardCore/Extensions/ExtensionManager.cs src/OrchardCore/OrchardCore/Extensions/ExtensionManager.cs— src/OrchardCore/OrchardCore/Extensions/ExtensionManager.cs changed 2 times in last 90 days, max complexity 21. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. 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: src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/AdminController.cs src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/AdminController.cs— src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/AdminController.cs changed 2 times in last 90 days, max complexity 20. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Duplicated block (13 lines × 2) src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:288— src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:288-300 | src/OrchardCore/OrchardCore.ContentManagement.Abstractions/Utilities/StringExtensions.cs:217-229 — 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 × 2) src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:305— src/OrchardCore/OrchardCore.Mvc.Core/Utilities/StringExtensions.cs:305-317 | src/OrchardCore/OrchardCore.ContentManagement.Abstractions/Utilities/StringExtensions.cs:234-246 — 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 × 2) src/OrchardCore.Modules/OrchardCore.Contents/AuditTrail/Drivers/AuditTrailContentEventDisplayDriver.cs:64— src/OrchardCore.Modules/OrchardCore.Contents/AuditTrail/Drivers/AuditTrailContentEventDisplayDriver.cs:64-76 | src/OrchardCore.Modules/OrchardCore.Contents/AuditTrail/Drivers/AuditTrailContentEventDisplayDriver.cs:91-103 — 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 `src/OrchardCore.Modules/OrchardCore.Contents/AuditTrail/Drivers/AuditTrailContentEventDisplayDriver.cs:64` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs:405— src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs:405-417 | src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs:505-517 — 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 `src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs:405` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api/CreateEndpoint.cs:81— src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api/CreateEndpoint.cs:81-93 | src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api/CreateEndpoint.cs:109-121 — 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 `src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api/CreateEndpoint.cs:81` 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 × 2) src/OrchardCore.Modules/OrchardCore.Notifications/Controllers/AdminController.cs:189— src/OrchardCore.Modules/OrchardCore.Notifications/Controllers/AdminController.cs:189-201 | src/OrchardCore.Modules/OrchardCore.Notifications/Controllers/AdminController.cs:211-223 — 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 `src/OrchardCore.Modules/OrchardCore.Notifications/Controllers/AdminController.cs:189` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/OrchardCore.Modules/OrchardCore.Themes/Controllers/AdminController.cs:189— src/OrchardCore.Modules/OrchardCore.Themes/Controllers/AdminController.cs:189-201 | src/OrchardCore.Modules/OrchardCore.Themes/Controllers/AdminController.cs:212-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) src/OrchardCore/OrchardCore.ContentManagement.GraphQL/Extensions/DataLoaderExtensions.cs:40— src/OrchardCore/OrchardCore.ContentManagement.GraphQL/Extensions/DataLoaderExtensions.cs:40-52 | src/OrchardCore/OrchardCore.ContentManagement.GraphQL/Queries/ContentItemsFieldType.cs:236-248 — 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 `src/OrchardCore/OrchardCore.ContentManagement.GraphQL/Extensions/DataLoaderExtensions.cs:40` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) src/OrchardCore/OrchardCore.Elasticsearch.Core/Handlers/ElasticsearchIndexProfileHandler.cs:95— src/OrchardCore/OrchardCore.Elasticsearch.Core/Handlers/ElasticsearchIndexProfileHandler.cs:95-107 | src/OrchardCore/OrchardCore.Lucene.Core/Handlers/LuceneContentIndexProfileHandler.cs:86-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:175— src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:175-187 | src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/StyleTagHelper.cs:172-184 — 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 `src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:175` 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) src/OrchardCore.Modules/OrchardCore.Features/Services/ModuleService.cs:60— src/OrchardCore.Modules/OrchardCore.Features/Services/ModuleService.cs:60-68 | src/OrchardCore.Modules/OrchardCore.Themes/Services/ThemeService.cs:111-119 — 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 `src/OrchardCore.Modules/OrchardCore.Features/Services/ModuleService.cs:60` 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) src/OrchardCore.Modules/OrchardCore.Features/Services/ModuleService.cs:87— src/OrchardCore.Modules/OrchardCore.Features/Services/ModuleService.cs:87-95 | src/OrchardCore.Modules/OrchardCore.Themes/Services/ThemeService.cs:138-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. Read the line range as the matched WINDOW rather than a finished unit: at `src/OrchardCore.Modules/OrchardCore.Features/Services/ModuleService.cs:87` 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) src/OrchardCore/OrchardCore.Lucene.Core/QueryProviders/Filters/GeoBoundingBoxFilterProvider.cs:54— src/OrchardCore/OrchardCore.Lucene.Core/QueryProviders/Filters/GeoBoundingBoxFilterProvider.cs:54-62 | src/OrchardCore/OrchardCore.Lucene.Core/QueryProviders/Filters/GeoDistanceFilterProvider.cs:77-85 — 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 (9 lines × 2) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:72— src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:72-80 | src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:88-96 — 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 `src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:72` 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) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:345— src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:345-353 | src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:361-369 — 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 `src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdAuthorizationStore.cs:345` 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) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:70— src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:70-78 | src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:86-94 — 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 `src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:70` 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) src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:387— src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:387-395 | src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:403-411 — 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 `src/OrchardCore/OrchardCore.OpenId.Core/YesSql/Stores/OpenIdTokenStore.cs:387` 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) src/OrchardCore/OrchardCore.SourceGenerators/ShapeFactoryGenerator.cs:692— src/OrchardCore/OrchardCore.SourceGenerators/ShapeFactoryGenerator.cs:692-700 | src/OrchardCore/OrchardCore.SourceGenerators/ShapeFactoryGenerator.cs:707-715 — 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.
FileTooLong: OrchardCore.Resources/ResourceManagementOptionsConfiguration.cs src/OrchardCore.Modules/OrchardCore.Resources/ResourceManagementOptionsConfiguration.cs:0— FileTooLong — 984 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: OrchardCore.ContentManagement/DefaultContentManager.cs src/OrchardCore/OrchardCore.ContentManagement/DefaultContentManager.cs:0— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Controllers/AdminController.cs src/OrchardCore.Modules/OrchardCore.ContentTypes/Controllers/AdminController.cs:0— FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: OrchardCore.SourceGenerators/ShapeFactoryGenerator.cs src/OrchardCore/OrchardCore.SourceGenerators/ShapeFactoryGenerator.cs:0— FileTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: SQL/Migrations.cs src/OrchardCore.Modules/OrchardCore.ContentFields/Indexing/SQL/Migrations.cs:0— FileTooLong — 559 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Controllers/AdminController.cs src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs:0— FileTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Controllers/AdminController.cs src/OrchardCore.Modules/OrchardCore.RateLimits/Controllers/AdminController.cs:0— FileTooLong — 515 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
Duplicated block (14 lines × 2) src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/NodeController.cs:83— src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/NodeController.cs:83-96 | src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/NodeController.cs:160-174 — 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 `src/OrchardCore.Modules/OrchardCore.AdminMenu/Controllers/NodeController.cs:83` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note 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 (14 lines × 2) src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api/DeleteEndpoint.cs:31— src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api/DeleteEndpoint.cs:31-44 | src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api/GetEndpoint.cs:31-44 — 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 `src/OrchardCore.Modules/OrchardCore.Contents/Endpoints/Api/DeleteEndpoint.cs:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/OrchardCore.Modules/OrchardCore.Contents/Liquid/ContentAnchorTag.cs:200— src/OrchardCore.Modules/OrchardCore.Contents/Liquid/ContentAnchorTag.cs:200-213 | src/OrchardCore.Modules/OrchardCore.Media/Liquid/MediaAnchorTag.cs:79-92 — 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 `src/OrchardCore.Modules/OrchardCore.Contents/Liquid/ContentAnchorTag.cs:200` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/OrchardCore.Modules/OrchardCore.Media/Endpoints/Api/GetDirectoryContentEndpoint.cs:41— src/OrchardCore.Modules/OrchardCore.Media/Endpoints/Api/GetDirectoryContentEndpoint.cs:41-54 | src/OrchardCore.Modules/OrchardCore.Media/Endpoints/Api/GetMediaItemsEndpoint.cs:43-56 — 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 `src/OrchardCore.Modules/OrchardCore.Media/Endpoints/Api/GetDirectoryContentEndpoint.cs:41` 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 (14 lines × 2) src/OrchardCore.Modules/OrchardCore.Deployment/Controllers/StepController.cs:124— src/OrchardCore.Modules/OrchardCore.Deployment/Controllers/StepController.cs:124-137 | src/OrchardCore.Modules/OrchardCore.Deployment/Controllers/StepController.cs:202-215 — 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 `src/OrchardCore.Modules/OrchardCore.Deployment/Controllers/StepController.cs:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/OrchardCore.Modules/OrchardCore.OpenId/Services/OpenIdServerService.cs:313— src/OrchardCore.Modules/OrchardCore.OpenId/Services/OpenIdServerService.cs:313-326 | src/OrchardCore.Modules/OrchardCore.OpenId/Services/OpenIdServerService.cs:385-398 — 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 `src/OrchardCore.Modules/OrchardCore.OpenId/Services/OpenIdServerService.cs:313` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) src/OrchardCore/OrchardCore.DisplayManagement/Descriptors/PlacementInfo.cs:412— src/OrchardCore/OrchardCore.DisplayManagement/Descriptors/PlacementInfo.cs:412-425 | src/OrchardCore/OrchardCore.DisplayManagement/Descriptors/PlacementInfo.cs:442-455 — 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.
Dead code: CookieOptionsConfiguration src/OrchardCore.Modules/OrchardCore.Microsoft.Authentication/Configuration/CookieOptionsConfiguration.cs:9— NamedType CookieOptionsConfiguration — no references found in solution.
Dead code: Deconstruct test/OrchardCore.Abstractions.Tests/Modules/Manifest/FeatureAttributeTests.Attribute.cs:253— Method Deconstruct — no references found in solution.
Dead code: Deconstruct test/OrchardCore.Abstractions.Tests/Modules/Manifest/FeatureAttributeTests.Attribute.cs:266— Method Deconstruct — no references found in solution.
Dead code: TestModuleInitializer test/OrchardCore.Tests.Functional/Helpers/TestModuleInitializer.cs:11— NamedType TestModuleInitializer — no references found in solution.
Dead code: StubResourceManifestProvider test/OrchardCore.Tests/ResourceManagement/ResourceManagerTests.cs:906— NamedType StubResourceManifestProvider — no references found in solution.
Dead code: JintHostContractVerification test/OrchardCore.Tests/Scripting/JintHostContractVerification.cs:27— NamedType JintHostContractVerification — no references found in solution.
ClassTooLong: ResourceManagementOptionsConfiguration src/OrchardCore.Modules/OrchardCore.Resources/ResourceManagementOptionsConfiguration.cs:0— ClassTooLong — 978 significant lines (blank, comment-only and punctuation-only lines excluded), 3 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DefaultContentManager src/OrchardCore/OrchardCore.ContentManagement/DefaultContentManager.cs:0— ClassTooLong — 599 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ShapeFactoryGenerator src/OrchardCore/OrchardCore.SourceGenerators/ShapeFactoryGenerator.cs:0— ClassTooLong — 574 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
ClassTooLong: Migrations src/OrchardCore.Modules/OrchardCore.ContentFields/Indexing/SQL/Migrations.cs:0— ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AdminController src/OrchardCore.Modules/OrchardCore.Contents/Controllers/AdminController.cs:0— ClassTooLong — 506 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AdminController src/OrchardCore.Modules/OrchardCore.Tenants/Controllers/AdminController.cs:0— ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Change coupling: EmailTask.cs ↔ EmailTaskViewModel.cs src/OrchardCore.Modules/OrchardCore.Email/Workflows/Activities/EmailTask.cs— `src/OrchardCore.Modules/OrchardCore.Email/Workflows/Activities/EmailTask.cs` and `src/OrchardCore.Modules/OrchardCore.Email/Workflows/ViewModels/EmailTaskViewModel.cs` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: AccountController.cs ↔ RegistrationSettings.cs src/OrchardCore.Modules/OrchardCore.Users/Controllers/AccountController.cs— `src/OrchardCore.Modules/OrchardCore.Users/Controllers/AccountController.cs` and `src/OrchardCore.Modules/OrchardCore.Users/Models/RegistrationSettings.cs` 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: AdminController.cs ↔ EditUserViewModel.cs src/OrchardCore.Modules/OrchardCore.Users/Controllers/AdminController.cs— `src/OrchardCore.Modules/OrchardCore.Users/Controllers/AdminController.cs` and `src/OrchardCore.Modules/OrchardCore.Users/ViewModels/EditUserViewModel.cs` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: OrchardRazorHelperExtensions.cs ↔ ImageResizeTagHelper.cs src/OrchardCore.Modules/OrchardCore.Media/Razor/OrchardRazorHelperExtensions.cs— `src/OrchardCore.Modules/OrchardCore.Media/Razor/OrchardRazorHelperExtensions.cs` and `src/OrchardCore.Modules/OrchardCore.Media/TagHelpers/ImageResizeTagHelper.cs` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: ServiceCollectionExtensions.cs ↔ AzureAISearchIndexManager.cs src/OrchardCore/OrchardCore.AzureAI.Core/Extensions/ServiceCollectionExtensions.cs— `src/OrchardCore/OrchardCore.AzureAI.Core/Extensions/ServiceCollectionExtensions.cs` and `src/OrchardCore/OrchardCore.AzureAI.Core/Services/AzureAISearchIndexManager.cs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Change coupling: ScheduledArchivingBackgroundTask.cs ↔ ScheduledPublishingBackgroundTask.cs src/OrchardCore.Modules/OrchardCore.ArchiveLater/Services/ScheduledArchivingBackgroundTask.cs— `src/OrchardCore.Modules/OrchardCore.ArchiveLater/Services/ScheduledArchivingBackgroundTask.cs` and `src/OrchardCore.Modules/OrchardCore.PublishLater/Services/ScheduledPublishingBackgroundTask.cs` 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking.
Duplicated block (19 lines × 2) src/OrchardCore.Modules/OrchardCore.Elasticsearch/Extensions/ElasticsearchOptionsExtensions.cs:13— src/OrchardCore.Modules/OrchardCore.Elasticsearch/Extensions/ElasticsearchOptionsExtensions.cs:13-31 | src/OrchardCore.Modules/OrchardCore.Elasticsearch/Extensions/ElasticsearchOptionsExtensions.cs:51-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 `src/OrchardCore.Modules/OrchardCore.Elasticsearch/Extensions/ElasticsearchOptionsExtensions.cs:13` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) src/OrchardCore.Modules/OrchardCore.Indexing/Controllers/AdminController.cs:157— src/OrchardCore.Modules/OrchardCore.Indexing/Controllers/AdminController.cs:157-175 | src/OrchardCore.Modules/OrchardCore.Indexing/Controllers/AdminController.cs:192-210 — 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 `src/OrchardCore.Modules/OrchardCore.Indexing/Controllers/AdminController.cs:157` 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) src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:234— src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:234-252 | src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:314-332 — 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 `src/OrchardCore.Modules/OrchardCore.Taxonomies/Controllers/AdminController.cs:234` 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 (19 lines × 2) src/OrchardCore.Modules/OrchardCore.UrlRewriting/Controllers/AdminController.cs:102— src/OrchardCore.Modules/OrchardCore.UrlRewriting/Controllers/AdminController.cs:102-120 | src/OrchardCore.Modules/OrchardCore.UrlRewriting/Controllers/AdminController.cs:138-156 — 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 `src/OrchardCore.Modules/OrchardCore.UrlRewriting/Controllers/AdminController.cs:102` 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) src/OrchardCore/OrchardCore.ContentManagement.Display/ContentItemDisplayManager.cs:109— src/OrchardCore/OrchardCore.ContentManagement.Display/ContentItemDisplayManager.cs:109-127 | src/OrchardCore/OrchardCore.ContentManagement.Display/ContentItemDisplayManager.cs:154-172 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:264— src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:264-282 | src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/StyleTagHelper.cs:260-278 — 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 `src/OrchardCore/OrchardCore.ResourceManagement/TagHelpers/ScriptTagHelper.cs:264` 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.
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.