Public report of ventrian/Property-Agent, published 15 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 02:55 UTC · Survey ID cd_4e7af1750922454db189aa0f51529d09

ventrian/Property-Agent

Measured 15 November 2026, 02:54 UTC, at code version 5b7b207

Boundary Type-Coupling is not measured: Bounded contexts not declared.

CAI score 33out of 100 Weak
CriticalWeakAdequateStrongExemplary
Down 6 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 38,196 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 17

Findings by how serious they are

65 critical 512 serious 118 minor

37 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 02:54 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

30of 30 dimensions measured by tools.
685of 695 findings point to an exact file and line, so you can open each one in the code. The other 10 concern the repository as a whole, such as missing documentation.
30dimensions across 5 lenses, read from 38,196 lines of product code in 2 projects.
Chapters

Executive summary

ventrian/Property-Agent falls short of our standard for production because the project has no automated tests and we found no working pipeline that builds or tests changes to the code. It scores 33 out of 100 and is rated Weak, and two of its 65 critical findings are security problems.

Production Readiness, at 17, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the nine comments that repeat the code, or contradict it, worth about 7 points. Adding automated tests would lift Production Readiness itself, worth about 16 points. Raising Production Readiness to 70 would lift the score to about 47.

One password or key is open to anyone who can read the repository. One place in the code runs text as code, which an attacker could use, and sixty-two errors are caught and ignored, so failures can go unnoticed. Replacing the exposed password or key, replacing text run as code with direct calls and handling or logging the ignored errors would close these risks.

The product code is 38,196 lines, about €28,000 to rebuild.

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 17 · counts for 47%Maturity 33 · counts for 26%Code Health 51 · counts for 14%Security and Compliance 66 · counts for 8%Architecture 74 · counts for 4%

If Production Readiness rose from 17 to 70, the lowest score rated Strong, the score would rise from 33 to about 47.

Code composition: what the lines of code are
Product code 100%
New since the last survey: 58 findings

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

  • Code Duplication · Near-duplicate member pair (240 shared lines) LandingPage.ascx.vb
  • Code Duplication · Edited copy of a member (97 corresponding lines) Entities/Reminders/NotificationJob.vb
  • Code Duplication · Edited copy of a member (82 corresponding lines) Entities/Layout/LayoutController.vb
  • Code Duplication · Edited copy of a member (37 corresponding lines) EditPermissions.ascx.vb
  • Code Duplication · Edited copy of a member (56 corresponding lines) EditContactField.ascx.vb
  • Code Duplication · Edited copy of a member (22 corresponding lines) Xml.ascx.vb
  • Code Duplication · Edited copies of one member (3 members, 49+ corresponding lines) EditContactFields.ascx.vb
  • Code Duplication · Edited copy of a member (28 corresponding lines) Search.ascx.vb
  • Code Duplication · Edited copy of a member (40 corresponding lines) EditCustomField.ascx.vb
  • Code Duplication · Edited copy of a member (30 corresponding lines) Latest.ascx.vb
  • Code Duplication · Edited copies of one member (3 members, 46+ corresponding lines) EditContactFields.ascx.vb
  • Code Duplication · Edited copy of a member (47 corresponding lines) Controls/UploadPhotoSWF.ascx.vb
  • Code Duplication · Edited copy of a member (29 corresponding lines) Search.ascx.vb
  • Code Duplication · Edited copy of a member (29 corresponding lines) LandingPage.ascx.vb
  • Code Duplication · Edited copy of a member (3 corresponding lines) Entities/CustomFields/CustomFieldController.vb
  • Code Duplication · Edited copy of a member (31 corresponding lines) EditContactField.ascx.vb
  • Code Duplication · Edited copy of a member (25 corresponding lines) ImageHandlerExt.ashx.vb
  • Code Duplication · Edited copy of a member (23 corresponding lines) Entities/Social/Journal.vb
  • Code Duplication · Edited copy of a member (20 corresponding lines) Entities/Layout/LayoutController.vb
  • Code Duplication · Edited copy of a member (8 corresponding lines) EditEmailFiles.ascx.vb
  • Code Duplication · Edited copy of a member (27 corresponding lines) EditPropertyNotifications.ascx.vb
  • Code Duplication · Edited copy of a member (14 corresponding lines) Entities/AgentController.vb
  • Code Duplication · Edited copy of a member (9 corresponding lines) LatestOptions.ascx.vb
  • Code Duplication · Edited copy of a member (1 corresponding lines) Providers/DataProviders/SqlDataProvider/SqlDataProvider.vb
  • Code Duplication · Edited copy of a member (4 corresponding lines) EditLayoutSettings.ascx.vb
  • Code Duplication · Edited copy of a member (12 corresponding lines) EditProperties.ascx.vb
  • Code Duplication · Edited copy of a member (10 corresponding lines) EditLayoutSettings.ascx.vb
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) Entities/Property/PropertySettings.vb
  • Code Duplication · Edited copy of a member (179 corresponding lines) Entities/Reminders/NotificationJob.vb
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) Entities/Layout/LayoutController.vb
  • Code Duplication · Edited copy of a member (1 corresponding lines) Entities/Property/PropertyController.vb
  • Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) Entities/WebControls/PagingControl.vb
  • Code Duplication · Edited copy of a member (7 corresponding lines) Search.ascx.vb
  • Code Duplication · Edited copy of a member (4 corresponding lines) LandingPage.ascx.vb
  • Code Duplication · Edited copy of a member (9 corresponding lines) CommentForm.ascx.vb
  • Code Duplication · Edited copy of a member (6 corresponding lines) EditCustomField.ascx.vb
  • Code Duplication · Edited copy of a member (1 corresponding lines) Entities/Property/PropertyController.vb
  • Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) LandingPage.ascx.vb
  • Code Duplication · Edited copies of one member (4 members, 2+ corresponding lines) Entities/ContactFields/ContactFieldController.vb
  • Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) EditContactFields.ascx.vb
  • Code Duplication · Edited copy of a member (8 corresponding lines) Entities/Layout/LayoutController.vb
  • Code Duplication · Edited copy of a member (3 corresponding lines) Entities/PropertyAgentBase.vb
  • Code Duplication · Edited copy of a member (7 corresponding lines) Latest.ascx.vb
  • Code Duplication · Edited copy of a member (13 corresponding lines) Controls/UploadPhotoStandard.ascx.vb
  • Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) EditContactFields.ascx.vb
  • Code Duplication · Edited copy of a member (5 corresponding lines) Entities/Property/PropertySettings.vb
  • Code Duplication · Edited copy of a member (5 corresponding lines) Entities/Property/PropertySettingsTypes.vb
  • Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) Entities/Property/PropertySettings.vb
  • Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) Entities/Property/PropertySettings.vb
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) Entities/ContactFields/ContactFieldController.vb
  • Code Duplication · Edited copy of a member (2 corresponding lines) Entities/Templates/TemplateWriter.vb
  • Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) Entities/PropertyAgentLatestBase.vb
  • Code Duplication · Edited copy of a member (6 corresponding lines) DeleteReview.ascx.vb
  • Code Duplication · Edited copy of a member (7 corresponding lines) Controls/UploadPhotoHTML5.ascx.vb
  • Code Duplication · Edited copy of a member (10 corresponding lines) Controls/SWFUploader.ashx.vb
  • Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) Entities/PropertyAgentLatestBase.vb
  • Code Duplication · Edited copy of a member (5 corresponding lines) Latest.ascx.vb
  • Code Coverage · No automated tests

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

Fixed since the last survey: 4 findings

These 4 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one.

  • Code Duplication · Near-duplicate member pair (228 shared lines) LandingPage.ascx.vb
  • Code Duplication · Duplicated block (80 lines × 2) LandingPage.ascx.vb
  • Code Duplication · Duplicated block (8 lines × 3) EditProperty.ascx.vb
  • Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €28,000 · Estimate
Cost to rebuild€9,200 to €46,000, for 153 to 485 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemLow, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 33. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 38,196 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 9 redundant comment finding(s) in Comment Value — start with TemplateWriter.vb (4), LayoutController.vb (3), ChangeTemplate.ascx.vb (2).
Raises the score by about 7 points · Low effort · Comment Value
2
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 16 points · High effort · Code Coverage
3
Resolve the 87 Orphaned file finding(s) in Knowledge Freshness — start with LandingPage.ascx.vb, EditProperty.ascx.vb, Search.ascx.vb.
Raises the score by about 8 points · Medium effort · Knowledge Freshness

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €28,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 17 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 9 redundant comment finding(s) in Comment Value. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for low effort, because it clears the 9 Comment Value findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 9% to 19% on every change. The history of the code shows how much it changes: about 282 lines over the last 90 days, which is about 1,144 lines a year. At that pace, the extra work comes to an estimated 0.2 to 1.5 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch Ventrian.PropertyAgent PropertyAgent Ventrian.PropertyAgent.SqlDataProvider SqlDataProvider Ventrian.PropertyAgent.SqlDataProvider->Ventrian.PropertyAgent

Architecture: which parts of the code depend on which

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

12 modules, with 5 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 (global)2 JS.Lightbox3 JS.Rating4 JS.SWFUpload5 Microsoft.VisualBasic6 My7 Templates.RealEstateRodMerritt8 Templates.Rod9 Ventrian.PropertyAgent.Controls10 Ventrian.PropertyAgent.Mapping11 Ventrian.PropertyAgent12 Ventrian.PropertyAgent.Social
1 (global)
2 JS.Lightbox
3 JS.Rating
4 JS.SWFUpload
5 Microsoft.VisualBasic
6 My
7 Templates.RealEstateRodMerritt
8 Templates.Rod
9 Ventrian.PropertyAgent.Controls8
10 Ventrian.PropertyAgent.Mapping1
11 Ventrian.PropertyAgent42
12 Ventrian.PropertyAgent.Social2
Uses a module listed above itPart of a loopThe module itself
1 (global)2 JS.Lightbox3 JS.Rating4 JS.SWFUpload5 Microsoft.VisualBasic6 My7 Templates.RealEstateRodMerritt8 Templates.Rod9 Ventrian.PropertyAgent.Controls10 Ventrian.PropertyAgent.Mapping11 Ventrian.PropertyAgent12 Ventrian.PropertyAgent.Social(global)1JS.Lightbox2JS.Rating3JS.SWFUpload4Microsoft.VisualBasic5My6Templates.RealEstateRodMerritt7Templates.Rod8Ventrian.PropertyAgent.Controls9Ventrian.PropertyAgent.Mapping10Ventrian.PropertyAgent11Ventrian.PropertyAgent.Social1281422

At a glance — Code Health · 51% · Checked 5 of 12 · gated by D1, D2 ·

At a glance — Architecture · 74% · Adequate · gated by AX5 ·

At a glance — Maturity · 33% · Weak · gated by D34, M2 ·

At a glance — Readiness · 17% · Critical · gated by D8, P1, P3 ·

At a glance — Security · 66% · Checked 3 of 9 · gated by D29 ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A05:2025 — Injection35High / Critical
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 87 Orphaned file finding(s) in Knowledge Freshness — start with LandingPage.ascx.vb, EditProperty.ascx.vb, Search.ascx.vb; Add a CI workflow that builds and runs the test suite on every push/PR.

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

Do thisHelpsEffortDimension
Resolve the 9 redundant comment finding(s) in Comment Value — start with TemplateWriter.vb (4), LayoutController.vb (3), ChangeTemplate.ascx.vb (2).+6.9 ptsLowComment Value
Resolve the 1 No automated tests finding(s) in Code Coverage.+16.1 ptsHighCode Coverage
Resolve the 87 Orphaned file finding(s) in Knowledge Freshness — start with LandingPage.ascx.vb, EditProperty.ascx.vb, Search.ascx.vb.+7.7 ptsMediumKnowledge Freshness
Add a CI workflow that builds and runs the test suite on every push/PR.+7.6 ptsMediumCI/CD gates
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+5.9 ptsMediumArchitecture documentation
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+3.3 ptsMediumRelease Hygiene
Resolve the 62 EmptyCatchBlock finding(s) in Explicit Debt — start with SearchSmall.ascx.vb (10), EditProperty.ascx.vb (9), LayoutController.vb (7).+3.1 ptsMediumExplicit Debt
Expand the README with getting-started, architecture overview and a project map.+2.1 ptsMediumDocumentation (README)

File quality

Per-file score 0–10 — a quality signature. Of 94 files carrying findings, judged against the Production bar: 11% slop · 68% mixed · 21% near-clean.

FileScoreBandWorst signal
Entities/AgentController.vb1.0SlopExplicit Debt: EmptyCatchBlock
Entities/Layout/LayoutController.vb1.4SlopExplicit Debt: EmptyCatchBlock
SearchSmall.ascx.vb2.2SlopExplicit Debt: EmptyCatchBlock
EditProperty.ascx.vb2.2SlopExplicit Debt: EmptyCatchBlock
Search.ascx.vb2.3SlopExplicit Debt: EmptyCatchBlock
LandingPage.ascx.vb2.3SlopExplicit Debt: EmptyCatchBlock
CommentForm.ascx.vb2.5SlopExplicit Debt: EmptyCatchBlock
ChangeTemplate.ascx.vb3.0SlopExplicit Debt: EmptyCatchBlock
ReviewForm.ascx.vb3.5SlopExplicit Debt: EmptyCatchBlock
ImageHandlerExt.ashx.vb3.6SlopExplicit Debt: EmptyCatchBlock
REDACTED4.6MixedStatic Analysis (SAST): Medium: REDACTED
EditPermissions.ascx.vb4.6MixedExplicit Debt: EmptyCatchBlock
Entities/Reminders/ReminderJob.vb4.7MixedExplicit Debt: EmptyCatchBlock
Controls/SWFUploader.ashx.vb4.7MixedExplicit Debt: EmptyCatchBlock
Controls/UploadPhotoSWF.ascx.vb4.7MixedExplicit Debt: EmptyCatchBlock
EditTemplateDefinition.ascx.vb4.8MixedExplicit Debt: EmptyCatchBlock
Controls/UploadPhotoHTML5.ascx.vb5.6MixedCognitive Complexity: UploadPhotoHTML5.GetImageByUrl (cognitive 18)
REDACTED6.2MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED6.9MixedStatic Analysis (SAST): Medium: REDACTED
ViewType.ascx.vb7.0MixedCyclomatic Complexity: ViewType.ProcessHeaderFooter (cyclomatic 87)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 65

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 512

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 118

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

Could not be resolved — 37

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 30 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 30 dimensions across the health lenses
D1D2D3D4D5D6D8D13D15D17D24D26D27D28D29D34D35AX10AX3AX4AX5ED5GD1M1M2M3P1P3P6S1

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
  1. 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, 685 of 695 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1dd20-f05f-7707-af1b-78dc105b95d3.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
  • D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. License scan produced no result — the tool ran but wrote no JSON report (no package reference resolved); the offline NuGet fallback resolved nothing.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (4 contributor(s) across 69 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 3 hold 4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Ventrian.PropertyAgent.vbproj' with message: The referenced project ../VentrianImageResizer/Ventrian.ImageResizer.csproj does not exist.
  • D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
  • D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (38,196 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 227 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X14 Bypassable address classification — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X15 Unvalidated length from an untrusted reader — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X20 Mistyped argument guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X22 Contradicted release guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X25 Inert configuration knob — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X26 Unsynchronised callback handoff — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X32 Type resolved by simple name across every loaded assembly — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D13 REDACTED Scanning: REDACTED 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").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • 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").
  • 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.
  • 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.
  • ED5 Idempotency: Idempotency is read from the handler body and one hop below: a mutation is flagged only on structural double-apply evidence (a fresh-identity insert, an accumulation, a growing list, an unkeyed POST/send/charge), so a duplicate effect through a home-grown gateway two hops down, or an insert keyed on the message with no unique constraint, is not flagged but counted as not classified; a guard enforced by a database constraint or a broker's exactly-once delivery is invisible either way. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

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

77 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LayoutController.ProcessItem at 686. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being EditLayoutFiles.cmdUpdate_Click at 22 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: EditLayoutFiles.ascx.vb (EditLayoutFiles.cmdUpdate_Click at 22). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

LayoutController.ProcessItem (cyclomatic 686)Entities/Layout/LayoutController.vb:3429
LayoutController.ProcessRSSItem (cyclomatic 221)Entities/Layout/LayoutController.vb:2422
Search.rptDetails_OnItemDataBound (cyclomatic 205)Search.ascx.vb:370
SearchSmall.rptDetails_OnItemDataBound (cyclomatic 188)SearchSmall.ascx.vb:1792
LandingPage.RenderCustomField (cyclomatic 160)LandingPage.ascx.vb:910

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

What to do

  1. Bring the 1 body over 240 down to 240 or less in Cyclomatic Complexity — start with LayoutController.ProcessItem (cyclomatic 686). — Refactoring it lifts Cyclomatic Complexity from 2.0 to about 3.1/10.

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

D2 · Cognitive Complexity2.0 / 10Critical✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

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

146 method(s) exceeded the cognitive complexity threshold of 15; the worst was LayoutController.ProcessItem at 2844.

LayoutController.ProcessItem (cognitive 2844)Entities/Layout/LayoutController.vb:3429
Search.rptDetails_OnItemDataBound (cognitive 1349)Search.ascx.vb:370
SearchSmall.rptDetails_OnItemDataBound (cognitive 1160)SearchSmall.ascx.vb:1792
LayoutController.ProcessRSSItem (cognitive 869)Entities/Layout/LayoutController.vb:2422
EditProperty.rptDetails_OnItemDataBound (cognitive 832)EditProperty.ascx.vb:1298

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

What to do

  1. Bring the 146 bodies over 15 down to 15 or less in Cognitive Complexity — start with LayoutController.ProcessItem (cognitive 2844), Search.rptDetails_OnItemDataBound (cognitive 1349), SearchSmall.rptDetails_OnItemDataBound (cognitive 1160). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 146 together lifts Cognitive Complexity from 2.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes6.1 / 10Adequate✓ Tool-verified

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

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

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

86 god class(es) detected.

MethodTooLong: LayoutController.ProcessItem · ×50Entities/Layout/LayoutController.vb:3429
ClassTooLong: SearchSmall · ×17SearchSmall.ascx.vb
FileTooLong: Layout/LayoutController.vb · ×15Entities/Layout/LayoutController.vb
TooManyMethods: SqlDataProvider · ×3Providers/DataProviders/SqlDataProvider/SqlDataProvider.vb
FunctionTooLong: jquery.lightbox-0.4.$.fn.lightBoxJS/Lightbox/jquery.lightbox-0.4.js:21

What to do

  1. Resolve the 50 MethodTooLong finding(s) in God Classes — start with LayoutController.vb (9), SearchSmall.ascx.vb (5), LandingPage.ascx.vb (3). — One of this dimension's main actionable groups (50 warning-level).
  2. Resolve the 17 ClassTooLong finding(s) in God Classes — start with SearchSmall.ascx.vb, PropertySettings.vb, LandingPage.ascx.vb. — One of this dimension's main actionable groups (17 warning-level).
  3. Resolve the 15 FileTooLong finding(s) in God Classes — start with LayoutController.vb, SearchSmall.ascx.vb, PropertySettings.vb. — One of this dimension's main actionable groups (15 warning-level).

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

D4 · Code Duplication4.8 / 10Weak✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

108 duplicated block group(s) detected. 12.9 % of the production lines (4,919 of 38,196) are in a reported copy. A further 66 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (6 lines × 2) · ×8LandingPage.ascx.vb:2037
Duplicated block (11 lines × 2) · ×7EditCustomFields.ascx.vb:337
Duplicated block (13 lines × 2) · ×6Rss.ascx.vb:135
Duplicated block (5 lines × 2) · ×6EditProperties.ascx.vb:570
Duplicated block (9 lines × 2) · ×5EditLayoutFiles.ascx.vb:213

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

What to do

  1. Resolve the 8 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with EditLayoutSettings.ascx.vb (2), LandingPage.ascx.vb, EditEmailFiles.ascx.vb. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 7 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with EditCustomFields.ascx.vb, Journal.vb, ImageHandler.ashx.vb. — One of this dimension's main actionable groups (7 warning-level).
  3. Resolve the 6 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with LayoutController.vb (3), Rss.ascx.vb, EditPermissions.ascx.vb. — One of this dimension's main actionable groups (6 warning-level).

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

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

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

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

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

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

2 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)9.3 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

1 of 17 classes have LCOM4 above 3.

Low cohesion: UploadPhotoHTML5 (LCOM4 4)Controls/UploadPhotoHTML5.ascx.vb:23

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with UploadPhotoHTML5.ascx.vb. — One of this dimension's main actionable groups (1 warning-level).

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

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

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

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).

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

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

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt6.9 / 10Adequate✓ Tool-verified

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

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

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

64 deducted debt markers + unmeasured dead symbols across 38196 LoC in the .NET projects (1.5/KLoC) → score 6.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

EmptyCatchBlock · ×62ChangeTemplate.ascx.vb:318
TodoComment · ×2Entities/AgentController.vb:165

What to do

  1. Resolve the 62 EmptyCatchBlock finding(s) in Explicit Debt — start with SearchSmall.ascx.vb (10), EditProperty.ascx.vb (9), LayoutController.vb (7). — One of this dimension's main actionable groups (62 issue-level).
  2. Resolve the 2 TodoComment finding(s) in Explicit Debt — start with AgentController.vb (2). — One of this dimension's main actionable groups (2 warning-level).

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

D24 · Comment Value6.5 6.4 / 10Adequate✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 6.4 / 10 · rule-coverage 98% · ceiling Documented

9 of 259 judged comments only repeat the code they sit on (3.5 %). 10 comment(s) in another language or script were not judged.

redundant comment · ×9ChangeTemplate.ascx.vb:110

What to do

  1. Resolve the 9 redundant comment finding(s) in Comment Value — start with TemplateWriter.vb (4), LayoutController.vb (3), ChangeTemplate.ascx.vb (2). — One of this dimension's main actionable groups (9 recommendation-level).

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

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 2 projects flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability10.0 / 10Exemplary✓ 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. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

80 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)9.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

37 finding(s): 0 critical, 1 high, 23 medium, 13 low. semgrep hit a parse error in 12 file(s) — `Templates/Agri/Listing.Alternate.html` (line 16), `Templates/Agri/Listing.Item.html` (line 16), `Templates/Cars/Featured.Footer.html` (lines 3–8), `Templates/Conferences/Featured.Footer.html` (line 1), `REDACTED` (line 1, line 35), … (+7 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (7 warning-level).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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

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

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

90 of 90 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Entities/Layout/LayoutController.vb. Counted over 90 of the 158 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×87LandingPage.ascx.vb:1
Most significant orphaned file · ×3Entities/Layout/LayoutController.vb:1
Dormant codebase

What to do

  1. Resolve the 87 Orphaned file finding(s) in Knowledge Freshness — start with LandingPage.ascx.vb, EditProperty.ascx.vb, Search.ascx.vb. — One of this dimension's main actionable groups (87 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with LayoutController.vb, SearchSmall.ascx.vb, PropertySettings.vb. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Frontend & cross-cutting dimensions

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

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

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

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

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

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

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

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

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

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

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

AX5 · Architecture & structure3.0 / 10Weak✓ Tool-verified

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.

  • ~38.2k production LoC (184 types) across 2 project(s) / 13 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.

What to do

  • Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
ED5 · Idempotency10.0 / 10Exemplary○ Nothing flagged

Other · Readiness — Whether retry-prone mutations (command handlers and message or event consumers) are idempotent, so an at-least-once redelivery or a client retry does not apply the effect twice.

Method: Roslyn (any mutation, ungated): each persistent write of a command handler or message/event consumer is idempotent when a guard is visible (an exists/dedup read that gates an exit, upsert, idempotency-key/inbox used in a condition or store call, versioned or fixed-value write, dedup envelope or pipeline), at risk only on positive double-apply evidence (a fresh-identity insert, an accumulation on a loaded and saved object, a growing member list, an unkeyed POST/SMTP send/Stripe charge), and otherwise not classified. Deterministic, no model; not scored when more than half are not classified. Advisory.

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. Every mutation is classified exhaustively and deterministically: guarded, at risk on positive evidence, or not classified; the score is over the classified ones and is withheld when they are fewer than half.

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

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.

M1 · Documentation (README)5.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

  • The root README is 32 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1

What to do

  • Expand the README with getting-started, architecture overview and a project map.
  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

  • Production code is mixed at the repository root with everything else the repository holds, so nothing marks which files are the product.
P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `https://www.plaxo.com/ab_chooser/abc_comm.jsdyn` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 5 such include(s) across the repository's markup. — Includes/plaxo_cb.html:1

What to do

  • Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.

Reference — by lens

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

LensScoreRatingImpact
Code Health51%Checked 5 of 12Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture74%Adequate — gated by AX5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity33%Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness17%Critical — gated by D8, P1, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security66%Checked 3 of 9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not evidenced — 5 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 80 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.

  • AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX6 Interface segregation — no public interfaces
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
  • D14 License Compliance — Licence collector did not produce a result
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • D18 Solution Shape — Dimension evaluation failed
  • D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D21 Naming Consistency — Naming consistency does not read Visual Basic, html yet; not measured.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • 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.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (41 event handler(s))
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
  • P12 CI test-gate honesty — no CI workflow found
  • P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
  • X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X20 Mistyped argument guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 65 finding(s)
D17 · Explicit Debt · EmptyCatchBlock · ×62
  • EmptyCatchBlock ChangeTemplate.ascx.vb:318 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock ChangeTemplate.ascx.vb:326 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock CommentForm.ascx.vb:377 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock CommentForm.ascx.vb:412 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock CommentForm.ascx.vb:446 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock CommentForm.ascx.vb:631 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Controls/SWFUploader.ashx.vb:320 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Controls/UploadPhotoSWF.ascx.vb:91 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditPermissions.ascx.vb:85 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:738 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:761 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:796 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:827 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:883 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:1710 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:1721 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:2158 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditProperty.ascx.vb:2162 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock EditTemplateDefinition.ascx.vb:240 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Entities/AgentController.vb:205 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Entities/AgentController.vb:243 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Entities/AgentController.vb:248 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Entities/AgentController.vb:256 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Entities/AgentController.vb:260 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock Entities/AgentController.vb:266 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • + 37 more in this group — see findings.md.
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Serious — 512 finding(s)
D3 · God Classes · MethodTooLong · ×50
  • MethodTooLong: LayoutController.ProcessItem Entities/Layout/LayoutController.vb:3429 — MethodTooLong — ProcessItem runs 2492 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2392 over it, 24.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LayoutController.ProcessRSSItem Entities/Layout/LayoutController.vb:2422 — MethodTooLong — ProcessRSSItem runs 775 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 675 over it, 7.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Search.rptDetails_OnItemDataBound Search.ascx.vb:370 — MethodTooLong — rptDetails_OnItemDataBound runs 775 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 675 over it, 7.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SearchSmall.rptDetails_OnItemDataBound SearchSmall.ascx.vb:1792 — MethodTooLong — rptDetails_OnItemDataBound runs 721 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 621 over it, 7.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LandingPage.RenderCustomField LandingPage.ascx.vb:910 — MethodTooLong — RenderCustomField runs 621 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 521 over it, 6.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SearchSmall.RenderCustomField SearchSmall.ascx.vb:707 — MethodTooLong — RenderCustomField runs 589 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 489 over it, 5.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EditProperty.rptDetails_OnItemDataBound EditProperty.ascx.vb:1298 — MethodTooLong — rptDetails_OnItemDataBound runs 549 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 449 over it, 5.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EditProperty.Update EditProperty.ascx.vb:575 — MethodTooLong — Update runs 404 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 304 over it, 4.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LayoutController.ProcessOptionItem Entities/Layout/LayoutController.vb:6524 — MethodTooLong — ProcessOptionItem runs 401 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 301 over it, 4.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: _Default.ReadQueryString Default.ascx.vb:31 — MethodTooLong — ReadQueryString runs 332 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 232 over it, 3.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EditLayoutSettings.BindSettings EditLayoutSettings.ascx.vb:374 — MethodTooLong — BindSettings runs 328 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 228 over it, 3.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ViewType.ProcessHeaderFooter ViewType.ascx.vb:725 — MethodTooLong — ProcessHeaderFooter runs 301 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 201 over it, 3.01× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LandingPage.ProcessSearch LandingPage.ascx.vb:488 — MethodTooLong — ProcessSearch runs 297 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 197 over it, 2.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SearchSmall.ProcessSearch SearchSmall.ascx.vb:353 — MethodTooLong — ProcessSearch runs 275 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 175 over it, 2.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EditLayoutSettings.cmdUpdate_Click EditLayoutSettings.ascx.vb:824 — MethodTooLong — cmdUpdate_Click runs 268 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 168 over it, 2.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LayoutController.ProcessComment Entities/Layout/LayoutController.vb:1482 — MethodTooLong — ProcessComment runs 263 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 163 over it, 2.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SearchSmall.Search_Click SearchSmall.ascx.vb:1502 — MethodTooLong — Search_Click runs 247 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 147 over it, 2.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SearchSmall.cmdSearch_Click SearchSmall.ascx.vb:2714 — MethodTooLong — cmdSearch_Click runs 246 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 146 over it, 2.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Search.cmdSearch_Click Search.ascx.vb:1292 — MethodTooLong — cmdSearch_Click runs 237 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 137 over it, 2.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LandingPage.Search_Click LandingPage.ascx.vb:1718 — MethodTooLong — Search_Click runs 236 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 136 over it, 2.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LayoutController.ProcessExportItem Entities/Layout/LayoutController.vb:1836 — MethodTooLong — ProcessExportItem runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: LayoutController.GetFieldValue Entities/Layout/LayoutController.vb:466 — MethodTooLong — GetFieldValue runs 228 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EditLayoutFiles.BindDetails EditLayoutFiles.ascx.vb:59 — MethodTooLong — BindDetails runs 227 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 127 over it, 2.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: ViewType.BindProperty ViewType.ascx.vb:422 — MethodTooLong — BindProperty runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: EditPermissions.cmdUpdate_Click EditPermissions.ascx.vb:151 — MethodTooLong — cmdUpdate_Click runs 224 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 124 over it, 2.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 25 more in this group — see findings.md.
D3 · God Classes · ClassTooLong · ×17
  • ClassTooLong: SearchSmall SearchSmall.ascx.vb — ClassTooLong — 2571 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 2171 over it, 6.43× the bar. 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: PropertySettings Entities/Property/PropertySettings.vb — ClassTooLong — 1933 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 1533 over it, 4.83× the bar. 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: LandingPage LandingPage.ascx.vb — ClassTooLong — 1731 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 1331 over it, 4.33× the bar. 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: EditProperty EditProperty.ascx.vb — ClassTooLong — 1677 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 1277 over it, 4.19× the bar. 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: Search Search.ascx.vb — ClassTooLong — 1269 significant lines (blank, comment-only and punctuation-only lines excluded), 13 methods. The bar is 400 significant lines; this is 869 over it, 3.17× the bar. 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: ViewType ViewType.ascx.vb — ClassTooLong — 1109 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 709 over it, 2.77× the bar. 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: Latest Latest.ascx.vb — ClassTooLong — 680 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 280 over it, 1.70× the bar. 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: EditCustomField EditCustomField.ascx.vb — ClassTooLong — 658 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 258 over it, 1.65× the bar. 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: Constants Entities/Constants.vb — ClassTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 242 over it, 1.61× the bar. 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: LatestOptions LatestOptions.ascx.vb — ClassTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 188 over it, 1.47× the bar. 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: ContactForm ContactForm.ascx.vb — ClassTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 112 over it, 1.28× the bar. 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: CommentForm CommentForm.ascx.vb — ClassTooLong — 509 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 109 over it, 1.27× the bar. 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: UploadPhotoHTML5 Controls/UploadPhotoHTML5.ascx.vb — ClassTooLong — 496 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 96 over it, 1.24× the bar. 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: EditPermissions EditPermissions.ascx.vb — ClassTooLong — 457 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 57 over it, 1.14× the bar. 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: PropertyInfo Entities/Property/PropertyInfo.vb — ClassTooLong — 442 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 42 over it, 1.11× the bar. 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: _Default Default.ascx.vb — ClassTooLong — 437 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 37 over it, 1.09× the bar. 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: EditProperties EditProperties.ascx.vb — ClassTooLong — 422 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 22 over it, 1.06× the bar. 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · FileTooLong · ×15
  • FileTooLong: Layout/LayoutController.vb Entities/Layout/LayoutController.vb — FileTooLong — 6034 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 5534 over it, 12.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./SearchSmall.ascx.vb SearchSmall.ascx.vb — FileTooLong — 2579 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2079 over it, 5.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Property/PropertySettings.vb Entities/Property/PropertySettings.vb — FileTooLong — 1939 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1439 over it, 3.88× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./LandingPage.ascx.vb LandingPage.ascx.vb — FileTooLong — 1741 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1241 over it, 3.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./EditProperty.ascx.vb EditProperty.ascx.vb — FileTooLong — 1692 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1192 over it, 3.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./Search.ascx.vb Search.ascx.vb — FileTooLong — 1277 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 777 over it, 2.55× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./ViewType.ascx.vb ViewType.ascx.vb — FileTooLong — 1118 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 618 over it, 2.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./EditLayoutSettings.ascx.vb EditLayoutSettings.ascx.vb — FileTooLong — 999 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 499 over it, 2.00× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./Latest.ascx.vb Latest.ascx.vb — FileTooLong — 689 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 189 over it, 1.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./EditCustomField.ascx.vb EditCustomField.ascx.vb — FileTooLong — 665 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 165 over it, 1.33× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Entities/Constants.vb Entities/Constants.vb — FileTooLong — 645 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 145 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./LatestOptions.ascx.vb LatestOptions.ascx.vb — FileTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 98 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./CommentForm.ascx.vb CommentForm.ascx.vb — FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 18 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ./ContactForm.ascx.vb ContactForm.ascx.vb — FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 18 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Controls/UploadPhotoHTML5.ascx.vb Controls/UploadPhotoHTML5.ascx.vb — FileTooLong — 515 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 15 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×8
  • Duplicated block (6 lines × 2) LandingPage.ascx.vb:2037 — LandingPage.ascx.vb:2037-2042 | SearchSmall.ascx.vb:3024-3029 — before extracting anything, compare `LandingPage.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 345 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) EditEmailFiles.ascx.vb:50 — EditEmailFiles.ascx.vb:50-55 | EditLayoutFiles.ascx.vb:50-55 — before extracting anything, compare `EditEmailFiles.ascx.vb` and `EditLayoutFiles.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) EditLayoutSettings.ascx.vb:897 — EditLayoutSettings.ascx.vb:897-902 | LatestOptions.ascx.vb:743-748 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `EditLayoutSettings.ascx.vb:893` calls `UpdateModuleSetting`, `ToString` and `LatestOptions.ascx.vb:741` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) Entities/Reminders/NotificationJob.vb:55 — Entities/Reminders/NotificationJob.vb:55-61 | Entities/Reminders/ReminderJob.vb:55-60 — before extracting anything, compare `Entities/Reminders/NotificationJob.vb` and `Entities/Reminders/ReminderJob.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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 (6 lines × 2) EditLayoutSettings.ascx.vb:263 — EditLayoutSettings.ascx.vb:263-268 | TypesOptions.ascx.vb:147-152 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) Entities/Layout/LayoutController.vb:997 — Entities/Layout/LayoutController.vb:997-1002 | Entities/Layout/LayoutController.vb:1008-1013 — 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 (6 lines × 2) LatestOptions.ascx.vb:791 — LatestOptions.ascx.vb:791-796 | TypesOptions.ascx.vb:264-269 — before extracting anything, compare `LatestOptions.ascx.vb` and `TypesOptions.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `LatestOptions.ascx.vb:797` calls `ToInt32` and `TypesOptions.ascx.vb:271` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) ViewType.ascx.vb:614 — ViewType.ascx.vb:614-619 | ViewType.ascx.vb:654-659 — 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×7
  • Duplicated block (11 lines × 2) EditCustomFields.ascx.vb:337 — EditCustomFields.ascx.vb:337-347 | EditPropertyTypes.ascx.vb:381-391 — before extracting anything, compare `EditCustomFields.ascx.vb` and `EditPropertyTypes.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) Entities/Social/Journal.vb:16 — Entities/Social/Journal.vb:16-26 | Entities/Social/Journal.vb:48-58 — 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 (11 lines × 2) ImageHandler.ashx.vb:29 — ImageHandler.ashx.vb:29-39 | ImageHandlerExt.ashx.vb:80-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) EditContactField.ascx.vb:76 — EditContactField.ascx.vb:76-86 | EditContactFields.ascx.vb:52-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) EditReviewField.ascx.vb:76 — EditReviewField.ascx.vb:76-86 | EditReviewFields.ascx.vb:52-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) EditCustomField.ascx.vb:36 — EditCustomField.ascx.vb:36-46 | EditCustomFields.ascx.vb:52-62 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (11 lines × 2) EditPropertyType.ascx.vb:38 — EditPropertyType.ascx.vb:38-48 | EditPropertyTypes.ascx.vb:56-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×6
  • Duplicated block (13 lines × 2) Rss.ascx.vb:135 — Rss.ascx.vb:135-147 | Xml.ascx.vb:135-147 — before extracting anything, compare `Rss.ascx.vb` and `Xml.ascx.vb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 121 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (13 lines × 2) EditPermissions.ascx.vb:204 — EditPermissions.ascx.vb:204-216 | EditPermissions.ascx.vb:222-234 — 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) Entities/Layout/LayoutController.vb:103 — Entities/Layout/LayoutController.vb:103-115 | Entities/Layout/LayoutController.vb:139-151 — 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) Entities/Layout/LayoutController.vb:121 — Entities/Layout/LayoutController.vb:121-133 | Entities/Layout/LayoutController.vb:157-169 — 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) Entities/Layout/LayoutController.vb:334 — Entities/Layout/LayoutController.vb:334-346 | ViewType.ascx.vb:147-159 — 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) EditEmailFiles.ascx.vb:147 — EditEmailFiles.ascx.vb:147-159 | EditLayoutFiles.ascx.vb:353-365 — before extracting anything, compare `EditEmailFiles.ascx.vb` and `EditLayoutFiles.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×6
  • Duplicated block (5 lines × 2) EditProperties.ascx.vb:570 — EditProperties.ascx.vb:570-574 | EditProperty.ascx.vb:2175-2179 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (5 lines × 2) Entities/Reminders/NotificationJob.vb:118 — Entities/Reminders/NotificationJob.vb:118-122 | Entities/Reminders/ReminderJob.vb:161-165 — before extracting anything, compare `Entities/Reminders/NotificationJob.vb` and `Entities/Reminders/ReminderJob.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) LatestOptions.ascx.vb:660 — LatestOptions.ascx.vb:660-664 | TypesOptions.ascx.vb:176-180 — before extracting anything, compare `LatestOptions.ascx.vb` and `TypesOptions.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) EditEmailFiles.ascx.vb:61 — EditEmailFiles.ascx.vb:61-65 | EditLayoutFiles.ascx.vb:61-65 — before extracting anything, compare `EditEmailFiles.ascx.vb` and `EditLayoutFiles.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (5 lines × 2) LatestOptions.ascx.vb:661 — LatestOptions.ascx.vb:661-665 | LatestOptions.ascx.vb:793-797 — 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 (5 lines × 2) Entities/Property/PropertySettings.vb:480 — Entities/Property/PropertySettings.vb:480-484 | Entities/Property/PropertySettingsTypes.vb:154-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×5
  • Duplicated block (9 lines × 2) EditLayoutFiles.ascx.vb:213 — EditLayoutFiles.ascx.vb:213-221 | EditLayoutFiles.ascx.vb:279-287 — 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 what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
  • Duplicated block (9 lines × 2) LandingPage.ascx.vb:1763 — LandingPage.ascx.vb:1763-1771 | SearchSmall.ascx.vb:1542-1550 — before extracting anything, compare `LandingPage.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 345 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Controls/SWFUploader.ashx.vb:335 — Controls/SWFUploader.ashx.vb:335-343 | Controls/UploadPhotoHTML5.ascx.vb:402-410 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (9 lines × 2) EditProperty.ascx.vb:791 — EditProperty.ascx.vb:791-800 | EditProperty.ascx.vb:823-831 — 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 `EditProperty.ascx.vb:791` 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) LatestOptions.ascx.vb:197 — LatestOptions.ascx.vb:197-205 | TypesOptions.ascx.vb:73-81 — before extracting anything, compare `LatestOptions.ascx.vb` and `TypesOptions.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×5
  • Duplicated block (7 lines × 2) Search.ascx.vb:327 — Search.ascx.vb:327-333 | SearchSmall.ascx.vb:64-70 — before extracting anything, compare `Search.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) EditProperties.ascx.vb:294 — EditProperties.ascx.vb:294-300 | SearchSmallOptions.ascx.vb:304-310 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (7 lines × 2) ViewType.ascx.vb:604 — ViewType.ascx.vb:604-610 | ViewType.ascx.vb:645-651 — 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 (7 lines × 2) EditTemplateDefinition.ascx.vb:220 — EditTemplateDefinition.ascx.vb:220-226 | ExportTemplateDefinition.ascx.vb:116-122 — before extracting anything, compare `EditTemplateDefinition.ascx.vb` and `ExportTemplateDefinition.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (7 lines × 2) ViewProperty.ascx.vb:387 — ViewProperty.ascx.vb:387-393 | ViewType.ascx.vb:1158-1164 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×4
  • Duplicated block (14 lines × 2) EditCustomFields.ascx.vb:245 — EditCustomFields.ascx.vb:245-258 | EditPropertyTypes.ascx.vb:318-331 — before extracting anything, compare `EditCustomFields.ascx.vb` and `EditPropertyTypes.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) ContactForm.ascx.vb:335 — ContactForm.ascx.vb:335-348 | SendToFriendForm.ascx.vb:208-221 — before extracting anything, compare `ContactForm.ascx.vb` and `SendToFriendForm.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (14 lines × 2) Entities/Layout/LayoutController.vb:310 — Entities/Layout/LayoutController.vb:310-323 | ViewType.ascx.vb:123-136 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (14 lines × 2) Entities/PropertyAgentBase.vb:79 — Entities/PropertyAgentBase.vb:79-92 | Latest.ascx.vb:90-103 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×4
  • Duplicated block (8 lines × 2) EditContactField.ascx.vb:254 — EditContactField.ascx.vb:254-261 | EditReviewField.ascx.vb:222-229 — before extracting anything, compare `EditContactField.ascx.vb` and `EditReviewField.ascx.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) EditProperties.ascx.vb:122 — EditProperties.ascx.vb:122-129 | EditProperty.ascx.vb:119-126 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) Controls/EditPropertyPhotos.ascx.vb:238 — Controls/EditPropertyPhotos.ascx.vb:238-246 | Controls/EditPropertyPhotos.ascx.vb:262-269 — 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 (8 lines × 2) ShortListForm.ascx.vb:21 — ShortListForm.ascx.vb:21-28 | SubscribeForm.ascx.vb:19-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D3 · God Classes · TooManyMethods · ×3
  • TooManyMethods: SqlDataProvider Providers/DataProviders/SqlDataProvider/SqlDataProvider.vb — TooManyMethods — 285 significant lines (blank, comment-only and punctuation-only lines excluded), 82 methods. The bar is 30 methods; this is 52 over it, 2.73× the bar. 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: LayoutController Entities/Layout/LayoutController.vb — TooManyMethods — 6010 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. 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: EditLayoutSettings EditLayoutSettings.ascx.vb — TooManyMethods — 991 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. 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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (4 members, 50+ identical tokens) EditEmailFiles.ascx.vb:61 — EditEmailFiles.ascx.vb:61-125 | EditEmailFiles.ascx.vb:178-219 | EditLayoutFiles.ascx.vb:61-331 | EditLayoutFiles.ascx.vb:384-500 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) EditProperties.ascx.vb:216 — EditProperties.ascx.vb:216-244 | Latest.ascx.vb:793-802 | LatestOptions.ascx.vb:173-182 | ViewType.ascx.vb:394-418 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) LatestOptions.ascx.vb:560 — LatestOptions.ascx.vb:560-683 | LatestOptions.ascx.vb:791-801 | TypesOptions.ascx.vb:138-199 | TypesOptions.ascx.vb:264-273 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (1 corresponding lines) · ×3
  • Edited copy of a member (1 corresponding lines) Providers/DataProviders/SqlDataProvider/SqlDataProvider.vb:188 — Providers/DataProviders/SqlDataProvider/SqlDataProvider.vb:188-188 | Providers/DataProviders/SqlDataProvider/SqlDataProvider.vb:192-192 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) Entities/Property/PropertyController.vb:101 — Entities/Property/PropertyController.vb:101-101 | Entities/Property/PropertyController.vb:107-107 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (1 corresponding lines) Entities/Property/PropertyController.vb:177 — Entities/Property/PropertyController.vb:177-177 | Entities/Property/PropertyController.vb:201-201 — These two members are one piece of code written twice and then edited apart: 1 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 7+ corresponding lines) Entities/Layout/LayoutController.vb:954 — Entities/Layout/LayoutController.vb:954-960 | Entities/Layout/LayoutController.vb:966-973 | Entities/Layout/LayoutController.vb:979-985 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Entities/ContactFields/ContactFieldController.vb:53 — Entities/ContactFields/ContactFieldController.vb:53-59 | Entities/CustomFields/CustomFieldController.vb:56-63 | Entities/ReviewFields/ReviewFieldController.vb:48-54 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Entities/PropertyAgentLatestBase.vb:60 — Entities/PropertyAgentLatestBase.vb:60-67 | Entities/PropertyAgentSearchBase.vb:57-63 | Entities/PropertyAgentTypesBase.vb:45-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) Search.ascx.vb:39 — Search.ascx.vb:39-45 | SearchSmall.ascx.vb:264-270 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Latest.ascx.vb:64 — Latest.ascx.vb:64-70 | ViewType.ascx.vb:85-91 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) Controls/UploadPhotoHTML5.ascx.vb:180 — Controls/UploadPhotoHTML5.ascx.vb:180-186 | Controls/UploadPhotoSWF.ascx.vb:159-165 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×3
  • Edited copy of a member (5 corresponding lines) Entities/Property/PropertySettings.vb:250 — Entities/Property/PropertySettings.vb:250-254 | Entities/Property/PropertySettingsLatest.vb:164-168 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Entities/Property/PropertySettingsTypes.vb:64 — Entities/Property/PropertySettingsTypes.vb:64-68 | Entities/Property/PropertySettingsLatest.vb:154-158 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) Latest.ascx.vb:76 — Latest.ascx.vb:76-80 | ViewType.ascx.vb:97-101 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×3
  • Duplicated block (11 lines × 3) Entities/Layout/LayoutController.vb:446 — Entities/Layout/LayoutController.vb:446-456 | Entities/Layout/LayoutController.vb:7221-7231 | Entities/WebControls/PagingControl.vb:284-294 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (11 lines × 3) LandingPage.ascx.vb:67 — LandingPage.ascx.vb:67-77 | ViewType.ascx.vb:1299-1309 | ViewType.ascx.vb:1354-1364 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (11 lines × 3) LandingPage.ascx.vb:311 — LandingPage.ascx.vb:311-321 | Search.ascx.vb:241-251 | SearchSmall.ascx.vb:1446-1456 — before extracting anything, compare `LandingPage.ascx.vb` and `Search.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×3
  • Duplicated block (12 lines × 2) EditContactFields.ascx.vb:35 — EditContactFields.ascx.vb:35-46 | EditReviewFields.ascx.vb:35-46 — before extracting anything, compare `EditContactFields.ascx.vb` and `EditReviewFields.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (12 lines × 2) EditLayoutSettings.ascx.vb:946 — EditLayoutSettings.ascx.vb:946-958 | LatestOptions.ascx.vb:760-771 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) EditLayoutSettings.ascx.vb:809 — EditLayoutSettings.ascx.vb:809-820 | EditPermissions.ascx.vb:124-135 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×3
  • Duplicated block (10 lines × 2) EditLayoutFiles.ascx.vb:256 — EditLayoutFiles.ascx.vb:256-265 | EditLayoutFiles.ascx.vb:300-309 — 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 what the matched lines are: every one of them assigns one field to another, so the block is a hand-written mapper between two data shapes rather than behaviour with a helper inside it. Extracting one shared function only works if both sites map the SAME pair of types in the same direction — check that first, because inverse or differently-typed mappers have no single function they can both call. Where they do not, the moves that exist are a generated or reflective mapper, a common embedded/base type the fields live on once, or accepting the run and covering it with a test that fails when a field is added to one side only.
  • Duplicated block (10 lines × 2) Entities/Reminders/NotificationJob.vb:177 — Entities/Reminders/NotificationJob.vb:177-186 | Entities/Reminders/ReminderJob.vb:211-220 — before extracting anything, compare `Entities/Reminders/NotificationJob.vb` and `Entities/Reminders/ReminderJob.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (10 lines × 2) EditCustomField.ascx.vb:349 — EditCustomField.ascx.vb:349-358 | EditReviewField.ascx.vb:137-146 — before extracting anything, compare `EditCustomField.ascx.vb` and `EditReviewField.ascx.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D17 · Explicit Debt · TodoComment · ×2
  • TodoComment Entities/AgentController.vb:165 — 'TODO: optimize? — 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 Entities/AgentController.vb:169 — 'TODO: understand why I have to tho this, for "Membership.Approved" return the REAL value — 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.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (5 members, 50+ identical tokens) EditContactFields.ascx.vb:224 — EditContactFields.ascx.vb:224-249 | EditCustomFields.ascx.vb:224-292 | EditLayoutSettings.ascx.vb:1148-1179 | EditPropertyTypes.ascx.vb:297-336 | EditReviewFields.ascx.vb:224-249 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) LandingPage.ascx.vb:61 — LandingPage.ascx.vb:61-87 | Latest.ascx.vb:861-886 | Latest.ascx.vb:892-917 | ViewType.ascx.vb:1276-1325 | ViewType.ascx.vb:1331-1380 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×2
  • Edited copy of a member (29 corresponding lines) Search.ascx.vb:305 — Search.ascx.vb:305-333 | SearchSmall.ascx.vb:38-70 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) LandingPage.ascx.vb:2033 — LandingPage.ascx.vb:2033-2061 | SearchSmall.ascx.vb:3020-3052 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×2
  • Edited copy of a member (3 corresponding lines) Entities/CustomFields/CustomFieldController.vb:40 — Entities/CustomFields/CustomFieldController.vb:40-42 | Entities/CustomFields/CustomFieldController.vb:48-50 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (3 corresponding lines) Entities/PropertyAgentBase.vb:55 — Entities/PropertyAgentBase.vb:55-57 | Entities/PropertyAgentLatestBase.vb:30-32 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×2
  • Edited copy of a member (8 corresponding lines) EditEmailFiles.ascx.vb:48 — EditEmailFiles.ascx.vb:48-55 | EditLayoutFiles.ascx.vb:48-55 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) Entities/Layout/LayoutController.vb:1331 — Entities/Layout/LayoutController.vb:1331-1341 | Entities/Layout/LayoutController.vb:1347-1354 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×2
  • Edited copy of a member (9 corresponding lines) LatestOptions.ascx.vb:211 — LatestOptions.ascx.vb:211-219 | SearchSmallOptions.ascx.vb:104-112 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) CommentForm.ascx.vb:184 — CommentForm.ascx.vb:184-192 | ContactForm.ascx.vb:169-178 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×2
  • Edited copy of a member (4 corresponding lines) EditLayoutSettings.ascx.vb:784 — EditLayoutSettings.ascx.vb:784-787 | LatestOptions.ascx.vb:188-191 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) LandingPage.ascx.vb:1997 — LandingPage.ascx.vb:1997-2000 | LandingPage.ascx.vb:2006-2009 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×2
  • Edited copy of a member (10 corresponding lines) EditLayoutSettings.ascx.vb:24 — EditLayoutSettings.ascx.vb:24-33 | EditLayoutSettings.ascx.vb:39-48 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) Controls/SWFUploader.ashx.vb:358 — Controls/SWFUploader.ashx.vb:358-370 | Print.aspx.vb:211-220 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×2
  • Edited copy of a member (6 corresponding lines) EditCustomField.ascx.vb:124 — EditCustomField.ascx.vb:124-129 | LatestOptions.ascx.vb:291-298 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) DeleteReview.ascx.vb:23 — DeleteReview.ascx.vb:23-29 | DeleteComment.ascx.vb:23-28 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 5+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 5+ corresponding lines) Entities/Property/PropertySettings.vb:280 — Entities/Property/PropertySettings.vb:280-284 | Entities/Property/PropertySettingsLatest.vb:324-328 | Entities/Property/PropertySettingsSearch.vb:205-209 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Entities/Property/PropertySettings.vb:300 — Entities/Property/PropertySettings.vb:300-304 | Entities/Property/PropertySettingsLatest.vb:344-348 | Entities/Property/PropertySettingsSearch.vb:225-229 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (43 lines × 2) · ×2
  • Duplicated block (43 lines × 2) Entities/Layout/LayoutController.vb:774 — Entities/Layout/LayoutController.vb:774-816 | Entities/Layout/LayoutController.vb:826-868 — 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 (43 lines × 2) Entities/PropertyAgentBase.vb:98 — Entities/PropertyAgentBase.vb:98-140 | Latest.ascx.vb:109-151 — 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×2
  • Duplicated block (19 lines × 2) Search.ascx.vb:309 — Search.ascx.vb:309-327 | SearchSmall.ascx.vb:42-60 — before extracting anything, compare `Search.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `SearchSmall.ascx.vb:62` calls `Not`, `Request` and `Search.ascx.vb:329` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (19 lines × 2) Entities/Layout/LayoutController.vb:440 — Entities/Layout/LayoutController.vb:440-458 | Entities/Layout/LayoutController.vb:7215-7233 — 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.
D4 · Code Duplication · Duplicated block (18 lines × 5) · ×2
  • Duplicated block (18 lines × 5) Export.ascx.vb:86 — Export.ascx.vb:86-103 | Latest.ascx.vb:428-445 | Rss.ascx.vb:76-93 | ViewType.ascx.vb:168-185 | Xml.ascx.vb:76-93 — before extracting anything, compare `Export.ascx.vb` and `Latest.ascx.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (18 lines × 5) EditPermissions.ascx.vb:226 — EditPermissions.ascx.vb:226-243 | EditPermissions.ascx.vb:250-268 | EditPermissions.ascx.vb:287-304 | EditPermissions.ascx.vb:340-357 | EditPermissions.ascx.vb:364-381 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×2
  • Duplicated block (16 lines × 2) Search.ascx.vb:85 — Search.ascx.vb:85-100 | SearchSmall.ascx.vb:144-160 — before extracting anything, compare `Search.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 124 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Search.ascx.vb:84` calls `List`, `ListAll`, `NullString` and `SearchSmall.ascx.vb:143` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16 lines × 2) Entities/Reminders/NotificationJob.vb:35 — Entities/Reminders/NotificationJob.vb:35-50 | Entities/Reminders/ReminderJob.vb:35-50 — before extracting anything, compare `Entities/Reminders/NotificationJob.vb` and `Entities/Reminders/ReminderJob.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) Controls/UploadPhotoSWF.ascx.vb:144 — Controls/UploadPhotoSWF.ascx.vb:144-153 | Latest.ascx.vb:196-205 | ViewProperty.ascx.vb:409-418 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (10 lines × 3) EditProperties.ascx.vb:216 — EditProperties.ascx.vb:216-225 | LatestOptions.ascx.vb:173-182 | ViewType.ascx.vb:394-403 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×2
  • Duplicated block (8 lines × 3) EditContactField.ascx.vb:254 — EditContactField.ascx.vb:254-261 | EditCustomField.ascx.vb:590-597 | EditReviewField.ascx.vb:222-229 — before extracting anything, compare `EditContactField.ascx.vb` and `EditReviewField.ascx.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 3) LatestOptions.ascx.vb:689 — LatestOptions.ascx.vb:689-696 | SearchSmallOptions.ascx.vb:282-289 | TypesOptions.ascx.vb:205-212 — before extracting anything, compare `LatestOptions.ascx.vb` and `TypesOptions.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×2
  • Duplicated block (6 lines × 4) Latest.ascx.vb:876 — Latest.ascx.vb:876-881 | Latest.ascx.vb:907-912 | ViewType.ascx.vb:1304-1309 | ViewType.ascx.vb:1359-1364 — before extracting anything, compare `Latest.ascx.vb` and `ViewType.ascx.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 4) EditProperties.ascx.vb:216 — EditProperties.ascx.vb:216-221 | Latest.ascx.vb:793-798 | LatestOptions.ascx.vb:173-178 | ViewType.ascx.vb:394-399 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×2
  • Duplicated block (6 lines × 3) EditPermissions.ascx.vb:435 — EditPermissions.ascx.vb:435-440 | EditPermissions.ascx.vb:525-530 | EditPermissions.ascx.vb:580-585 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
  • Duplicated block (6 lines × 3) EditEmailFiles.ascx.vb:64 — EditEmailFiles.ascx.vb:64-69 | EditEmailFiles.ascx.vb:180-185 | EditLayoutFiles.ascx.vb:386-391 — before extracting anything, compare `EditEmailFiles.ascx.vb` and `EditLayoutFiles.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×2
  • Duplicated block (7 lines × 3) Controls/UploadPhotoStandard.ascx.vb:39 — Controls/UploadPhotoStandard.ascx.vb:39-45 | PdfRender.ascx.vb:110-116 | ViewProperty.ascx.vb:59-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (7 lines × 3) EditContactFields.ascx.vb:23 — EditContactFields.ascx.vb:23-29 | EditCustomFields.ascx.vb:23-29 | EditReviewFields.ascx.vb:23-29 — before extracting anything, compare `EditContactFields.ascx.vb` and `EditCustomFields.ascx.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×2
  • Duplicated block (9 lines × 3) Export.ascx.vb:36 — Export.ascx.vb:36-44 | Rss.ascx.vb:34-42 | Xml.ascx.vb:34-42 — before extracting anything, compare `Export.ascx.vb` and `Rss.ascx.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 3) Export.ascx.vb:50 — Export.ascx.vb:50-58 | Rss.ascx.vb:48-56 | Xml.ascx.vb:48-56 — before extracting anything, compare `Export.ascx.vb` and `Rss.ascx.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
AX5 · Architecture & structure · Appears unstructured (no recognised architecture) · ×1
  • Appears unstructured (no recognised architecture) — ~38.2k production LoC (184 types) across 2 project(s) / 13 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
D1 · Cyclomatic Complexity · LayoutController.ProcessItem (cyclomatic 686) · ×1
  • LayoutController.ProcessItem (cyclomatic 686) Entities/Layout/LayoutController.vb:3429 — LayoutController.ProcessItem has cyclomatic complexity 686 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · LayoutController.ProcessRSSItem (cyclomatic 221) · ×1
  • LayoutController.ProcessRSSItem (cyclomatic 221) Entities/Layout/LayoutController.vb:2422 — LayoutController.ProcessRSSItem has cyclomatic complexity 221 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · Search.rptDetails_OnItemDataBound (cyclomatic 205) · ×1
  • Search.rptDetails_OnItemDataBound (cyclomatic 205) Search.ascx.vb:370 — Search.rptDetails_OnItemDataBound has cyclomatic complexity 205 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SearchSmall.rptDetails_OnItemDataBound (cyclomatic 188) · ×1
  • SearchSmall.rptDetails_OnItemDataBound (cyclomatic 188) SearchSmall.ascx.vb:1792 — SearchSmall.rptDetails_OnItemDataBound has cyclomatic complexity 188 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LandingPage.RenderCustomField (cyclomatic 160) · ×1
  • LandingPage.RenderCustomField (cyclomatic 160) LandingPage.ascx.vb:910 — LandingPage.RenderCustomField has cyclomatic complexity 160 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SearchSmall.RenderCustomField (cyclomatic 152) · ×1
  • SearchSmall.RenderCustomField (cyclomatic 152) SearchSmall.ascx.vb:707 — SearchSmall.RenderCustomField has cyclomatic complexity 152 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditProperty.rptDetails_OnItemDataBound (cyclomatic 142) · ×1
  • EditProperty.rptDetails_OnItemDataBound (cyclomatic 142) EditProperty.ascx.vb:1298 — EditProperty.rptDetails_OnItemDataBound has cyclomatic complexity 142 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.ProcessOptionItem (cyclomatic 133) · ×1
  • LayoutController.ProcessOptionItem (cyclomatic 133) Entities/Layout/LayoutController.vb:6524 — LayoutController.ProcessOptionItem has cyclomatic complexity 133 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · _Default.ReadQueryString (cyclomatic 105) · ×1
  • _Default.ReadQueryString (cyclomatic 105) Default.ascx.vb:31 — _Default.ReadQueryString has cyclomatic complexity 105 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditProperty.Update (cyclomatic 102) · ×1
  • EditProperty.Update (cyclomatic 102) EditProperty.ascx.vb:575 — EditProperty.Update has cyclomatic complexity 102 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ViewType.ProcessHeaderFooter (cyclomatic 87) · ×1
  • ViewType.ProcessHeaderFooter (cyclomatic 87) ViewType.ascx.vb:725 — ViewType.ProcessHeaderFooter has cyclomatic complexity 87 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.ProcessComment (cyclomatic 82) · ×1
  • LayoutController.ProcessComment (cyclomatic 82) Entities/Layout/LayoutController.vb:1482 — LayoutController.ProcessComment has cyclomatic complexity 82 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · LandingPage.ProcessSearch (cyclomatic 72) · ×1
  • LandingPage.ProcessSearch (cyclomatic 72) LandingPage.ascx.vb:488 — LandingPage.ProcessSearch has cyclomatic complexity 72 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SearchSmall.Search_Click (cyclomatic 70) · ×1
  • SearchSmall.Search_Click (cyclomatic 70) SearchSmall.ascx.vb:1502 — SearchSmall.Search_Click has cyclomatic complexity 70 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SearchSmall.cmdSearch_Click (cyclomatic 69) · ×1
  • SearchSmall.cmdSearch_Click (cyclomatic 69) SearchSmall.ascx.vb:2714 — SearchSmall.cmdSearch_Click has cyclomatic complexity 69 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Search.cmdSearch_Click (cyclomatic 68) · ×1
  • Search.cmdSearch_Click (cyclomatic 68) Search.ascx.vb:1292 — Search.cmdSearch_Click has cyclomatic complexity 68 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LandingPage.Search_Click (cyclomatic 67) · ×1
  • LandingPage.Search_Click (cyclomatic 67) LandingPage.ascx.vb:1718 — LandingPage.Search_Click has cyclomatic complexity 67 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.GetFieldValue (cyclomatic 66) · ×1
  • LayoutController.GetFieldValue (cyclomatic 66) Entities/Layout/LayoutController.vb:466 — LayoutController.GetFieldValue has cyclomatic complexity 66 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · SearchSmall.ProcessSearch (cyclomatic 65) · ×1
  • SearchSmall.ProcessSearch (cyclomatic 65) SearchSmall.ascx.vb:353 — SearchSmall.ProcessSearch has cyclomatic complexity 65 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditLayoutSettings.BindSettings (cyclomatic 64) · ×1
  • EditLayoutSettings.BindSettings (cyclomatic 64) EditLayoutSettings.ascx.vb:374 — EditLayoutSettings.BindSettings has cyclomatic complexity 64 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Latest.ProcessEmpty (cyclomatic 58) · ×1
  • Latest.ProcessEmpty (cyclomatic 58) Latest.ascx.vb:489 — Latest.ProcessEmpty has cyclomatic complexity 58 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CommentForm.cmdSubmit_Click (cyclomatic 55) · ×1
  • CommentForm.cmdSubmit_Click (cyclomatic 55) CommentForm.ascx.vb:244 — CommentForm.cmdSubmit_Click has cyclomatic complexity 55 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.ProcessExportItem (cyclomatic 53) · ×1
  • LayoutController.ProcessExportItem (cyclomatic 53) Entities/Layout/LayoutController.vb:1836 — LayoutController.ProcessExportItem has cyclomatic complexity 53 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · EditPermissions.cmdUpdate_Click (cyclomatic 48) · ×1
  • EditPermissions.cmdUpdate_Click (cyclomatic 48) EditPermissions.ascx.vb:151 — EditPermissions.cmdUpdate_Click has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.ProcessType (cyclomatic 48) · ×1
  • LayoutController.ProcessType (cyclomatic 48) Entities/Layout/LayoutController.vb:7237 — LayoutController.ProcessType has cyclomatic complexity 48 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · EditProperty.BindDetails (cyclomatic 45) · ×1
  • EditProperty.BindDetails (cyclomatic 45) EditProperty.ascx.vb:140 — EditProperty.BindDetails has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ViewType.BindProperty (cyclomatic 45) · ×1
  • ViewType.BindProperty (cyclomatic 45) ViewType.ascx.vb:422 — ViewType.BindProperty has cyclomatic complexity 45 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ChangeTemplate.InitializeTemplate (cyclomatic 44) · ×1
  • ChangeTemplate.InitializeTemplate (cyclomatic 44) ChangeTemplate.ascx.vb:74 — ChangeTemplate.InitializeTemplate has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ContactForm.cmdSubmit_Click (cyclomatic 44) · ×1
  • ContactForm.cmdSubmit_Click (cyclomatic 44) ContactForm.ascx.vb:237 — ContactForm.cmdSubmit_Click has cyclomatic complexity 44 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · NotificationJob.FormatTokens (cyclomatic 40) · ×1
  • NotificationJob.FormatTokens (cyclomatic 40) Entities/Reminders/NotificationJob.vb:175 — NotificationJob.FormatTokens has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ReminderJob.FormatTokens (cyclomatic 40) · ×1
  • ReminderJob.FormatTokens (cyclomatic 40) Entities/Reminders/ReminderJob.vb:209 — ReminderJob.FormatTokens has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Latest.BindLatest (cyclomatic 40) · ×1
  • Latest.BindLatest (cyclomatic 40) Latest.ascx.vb:209 — Latest.BindLatest has cyclomatic complexity 40 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · jquery.lightbox-0.4.$.fn.lightBox (cyclomatic 39) · ×1
  • jquery.lightbox-0.4.$.fn.lightBox (cyclomatic 39) JS/Lightbox/jquery.lightbox-0.4.js:21 — jquery.lightbox-0.4.$.fn.lightBox has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 9 function items inside it that branch (_keyboard_action, ___getPageSize, ___getPageScroll, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D1 · Cyclomatic Complexity · LayoutController.GetLayout (cyclomatic 38) · ×1
  • LayoutController.GetLayout (cyclomatic 38) Entities/Layout/LayoutController.vb:1162 — LayoutController.GetLayout has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · ViewProperty.BindProperty (cyclomatic 38) · ×1
  • ViewProperty.BindProperty (cyclomatic 38) ViewProperty.ascx.vb:152 — ViewProperty.BindProperty has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ContactForm.rptDetails_OnItemDataBound (cyclomatic 36) · ×1
  • ContactForm.rptDetails_OnItemDataBound (cyclomatic 36) ContactForm.ascx.vb:423 — ContactForm.rptDetails_OnItemDataBound has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.ProcessReview (cyclomatic 36) · ×1
  • LayoutController.ProcessReview (cyclomatic 36) Entities/Layout/LayoutController.vb:2116 — LayoutController.ProcessReview has cyclomatic complexity 36 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · LayoutController.ProcessPhoto (cyclomatic 31) · ×1
  • LayoutController.ProcessPhoto (cyclomatic 31) Entities/Layout/LayoutController.vb:7010 — LayoutController.ProcessPhoto has cyclomatic complexity 31 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · CurrencyConverter.ConvertCurrency (cyclomatic 30) · ×1
  • CurrencyConverter.ConvertCurrency (cyclomatic 30) CurrencyConverter.ascx.vb:42 — CurrencyConverter.ConvertCurrency has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditProperty.Page_Load (cyclomatic 30) · ×1
  • EditProperty.Page_Load (cyclomatic 30) EditProperty.ascx.vb:1192 — EditProperty.Page_Load has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ViewType.BindSortBy (cyclomatic 30) · ×1
  • ViewType.BindSortBy (cyclomatic 30) ViewType.ascx.vb:261 — ViewType.BindSortBy has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SendToFriendForm.cmdSubmit_Click (cyclomatic 29) · ×1
  • SendToFriendForm.cmdSubmit_Click (cyclomatic 29) SendToFriendForm.ascx.vb:144 — SendToFriendForm.cmdSubmit_Click has cyclomatic complexity 29 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ReviewForm.cmdSubmit_Click (cyclomatic 28) · ×1
  • ReviewForm.cmdSubmit_Click (cyclomatic 28) ReviewForm.ascx.vb:110 — ReviewForm.cmdSubmit_Click has cyclomatic complexity 28 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditLayoutSettings.cmdUpdate_Click (cyclomatic 27) · ×1
  • EditLayoutSettings.cmdUpdate_Click (cyclomatic 27) EditLayoutSettings.ascx.vb:824 — EditLayoutSettings.cmdUpdate_Click has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Latest.BindSortBy (cyclomatic 27) · ×1
  • Latest.BindSortBy (cyclomatic 27) Latest.ascx.vb:676 — Latest.BindSortBy has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SearchSmall.drpLinked_SelectedIndexChanged (cyclomatic 27) · ×1
  • SearchSmall.drpLinked_SelectedIndexChanged (cyclomatic 27) SearchSmall.ascx.vb:3144 — SearchSmall.drpLinked_SelectedIndexChanged has cyclomatic complexity 27 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ReminderJob.SendReminders (cyclomatic 26) · ×1
  • ReminderJob.SendReminders (cyclomatic 26) Entities/Reminders/ReminderJob.vb:53 — ReminderJob.SendReminders has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditCustomField.BindCustomField (cyclomatic 26) · ×1
  • EditCustomField.BindCustomField (cyclomatic 26) EditCustomField.ascx.vb:334 — EditCustomField.BindCustomField has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PropertyController.GetModifiedSearchDocuments (cyclomatic 25) · ×1
  • PropertyController.GetModifiedSearchDocuments (cyclomatic 25) Entities/Property/PropertyController.vb:221 — PropertyController.GetModifiedSearchDocuments has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LatestOptions.LoadSettings (cyclomatic 25) · ×1
  • LatestOptions.LoadSettings (cyclomatic 25) LatestOptions.ascx.vb:558 — LatestOptions.LoadSettings has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LandingPage.ProcessHeaderFooter (cyclomatic 24) · ×1
  • LandingPage.ProcessHeaderFooter (cyclomatic 24) LandingPage.ascx.vb:366 — LandingPage.ProcessHeaderFooter has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · UploadPhotoStandard.cmdUploadPhoto_Click (cyclomatic 23) · ×1
  • UploadPhotoStandard.cmdUploadPhoto_Click (cyclomatic 23) Controls/UploadPhotoStandard.ascx.vb:66 — UploadPhotoStandard.cmdUploadPhoto_Click has cyclomatic complexity 23 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · PdfRender.ProcessHeaderFooter (cyclomatic 22) · ×1
  • PdfRender.ProcessHeaderFooter (cyclomatic 22) PdfRender.ascx.vb:40 — PdfRender.ProcessHeaderFooter has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ReviewForm.rptDetails_OnItemDataBound (cyclomatic 22) · ×1
  • ReviewForm.rptDetails_OnItemDataBound (cyclomatic 22) ReviewForm.ascx.vb:272 — ReviewForm.rptDetails_OnItemDataBound has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditCustomField.cmdUpdate_Click (cyclomatic 22) · ×1
  • EditCustomField.cmdUpdate_Click (cyclomatic 22) EditCustomField.ascx.vb:531 — EditCustomField.cmdUpdate_Click has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.ProcessMessage (cyclomatic 22) · ×1
  • LayoutController.ProcessMessage (cyclomatic 22) Entities/Layout/LayoutController.vb:7495 — LayoutController.ProcessMessage has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · LandingPage.drpPropertyType_SelectedIndexChanged (cyclomatic 22) · ×1
  • LandingPage.drpPropertyType_SelectedIndexChanged (cyclomatic 22) LandingPage.ascx.vb:2065 — LandingPage.drpPropertyType_SelectedIndexChanged has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SearchSmall.drpPropertyType_SelectedIndexChanged (cyclomatic 22) · ×1
  • SearchSmall.drpPropertyType_SelectedIndexChanged (cyclomatic 22) SearchSmall.ascx.vb:3056 — SearchSmall.drpPropertyType_SelectedIndexChanged has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ViewProperty.ProcessHeaderFooter (cyclomatic 22) · ×1
  • ViewProperty.ProcessHeaderFooter (cyclomatic 22) ViewProperty.ascx.vb:84 — ViewProperty.ProcessHeaderFooter has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · CommentForm.rptDetails_OnItemDataBound (cyclomatic 20) · ×1
  • CommentForm.rptDetails_OnItemDataBound (cyclomatic 20) CommentForm.ascx.vb:511 — CommentForm.rptDetails_OnItemDataBound has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · _Default.ModuleActions.Get (cyclomatic 20) · ×1
  • _Default.ModuleActions.Get (cyclomatic 20) Default.ascx.vb:490 — _Default.ModuleActions.Get has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LandingPage.drpLinked_SelectedIndexChanged (cyclomatic 20) · ×1
  • LandingPage.drpLinked_SelectedIndexChanged (cyclomatic 20) LandingPage.ascx.vb:2153 — LandingPage.drpLinked_SelectedIndexChanged has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SWFUploader.ProcessRequest (cyclomatic 19) · ×1
  • SWFUploader.ProcessRequest (cyclomatic 19) Controls/SWFUploader.ashx.vb:150 — SWFUploader.ProcessRequest has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.GetTypeLink (cyclomatic 19) · ×1
  • LayoutController.GetTypeLink (cyclomatic 19) Entities/Layout/LayoutController.vb:7137 — LayoutController.GetTypeLink has cyclomatic complexity 19 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · CommentForm.CommentFormFields.Get (cyclomatic 18) · ×1
  • CommentForm.CommentFormFields.Get (cyclomatic 18) CommentForm.ascx.vb:33 — CommentForm.CommentFormFields.Get has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SearchSmall.BindSearch (cyclomatic 18) · ×1
  • SearchSmall.BindSearch (cyclomatic 18) SearchSmall.ascx.vb:74 — SearchSmall.BindSearch has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ViewContactLog.BindContactLog (cyclomatic 17) · ×1
  • ViewContactLog.BindContactLog (cyclomatic 17) ViewContactLog.ascx.vb:16 — ViewContactLog.BindContactLog has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.GetPropertyLink (cyclomatic 17) · ×1
  • LayoutController.GetPropertyLink (cyclomatic 17) Entities/Layout/LayoutController.vb:376 — LayoutController.GetPropertyLink has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · LayoutController.ProcessRSSHeader (cyclomatic 17) · ×1
  • LayoutController.ProcessRSSHeader (cyclomatic 17) Entities/Layout/LayoutController.vb:2335 — LayoutController.ProcessRSSHeader has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · ViewType.GetAdditionalParams (cyclomatic 17) · ×1
  • ViewType.GetAdditionalParams (cyclomatic 17) ViewType.ascx.vb:1072 — ViewType.GetAdditionalParams has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditPropertyPhotos.dlPhotos_OnItemCommand (cyclomatic 16) · ×1
  • EditPropertyPhotos.dlPhotos_OnItemCommand (cyclomatic 16) Controls/EditPropertyPhotos.ascx.vb:212 — EditPropertyPhotos.dlPhotos_OnItemCommand has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · EditProperty.Page_Initialization (cyclomatic 16) · ×1
  • EditProperty.Page_Initialization (cyclomatic 16) EditProperty.ascx.vb:1122 — EditProperty.Page_Initialization has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · LayoutController.LoadStyleSheet (cyclomatic 16) · ×1
  • LayoutController.LoadStyleSheet (cyclomatic 16) Entities/Layout/LayoutController.vb:1358 — LayoutController.LoadStyleSheet has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: Entities/Layout/LayoutController.vb holds 15 of the 77 methods over the threshold — including the worst — and 1260 of the 3272 points over it (39%), 2.6× the next-largest file (SearchSmall.ascx.vb at 491). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · Latest.ReadQueryStringTotal (cyclomatic 16) · ×1
  • Latest.ReadQueryStringTotal (cyclomatic 16) Latest.ascx.vb:426 — Latest.ReadQueryStringTotal has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Search.BindDetails (cyclomatic 16) · ×1
  • Search.BindDetails (cyclomatic 16) Search.ascx.vb:49 — Search.BindDetails has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SearchSmallOptions.LoadSettings (cyclomatic 16) · ×1
  • SearchSmallOptions.LoadSettings (cyclomatic 16) SearchSmallOptions.ascx.vb:201 — SearchSmallOptions.LoadSettings has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · ViewType.ReadQueryString (cyclomatic 16) · ×1
  • ViewType.ReadQueryString (cyclomatic 16) ViewType.ascx.vb:166 — ViewType.ReadQueryString has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D2 · Cognitive Complexity · LayoutController.ProcessItem (cognitive 2844) · ×1
  • LayoutController.ProcessItem (cognitive 2844) Entities/Layout/LayoutController.vb:3429 — LayoutController.ProcessItem has cognitive complexity 2844 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Search.rptDetails_OnItemDataBound (cognitive 1349) · ×1
  • Search.rptDetails_OnItemDataBound (cognitive 1349) Search.ascx.vb:370 — Search.rptDetails_OnItemDataBound has cognitive complexity 1349 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.rptDetails_OnItemDataBound (cognitive 1160) · ×1
  • SearchSmall.rptDetails_OnItemDataBound (cognitive 1160) SearchSmall.ascx.vb:1792 — SearchSmall.rptDetails_OnItemDataBound has cognitive complexity 1160 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessRSSItem (cognitive 869) · ×1
  • LayoutController.ProcessRSSItem (cognitive 869) Entities/Layout/LayoutController.vb:2422 — LayoutController.ProcessRSSItem has cognitive complexity 869 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperty.rptDetails_OnItemDataBound (cognitive 832) · ×1
  • EditProperty.rptDetails_OnItemDataBound (cognitive 832) EditProperty.ascx.vb:1298 — EditProperty.rptDetails_OnItemDataBound has cognitive complexity 832 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessOptionItem (cognitive 676) · ×1
  • LayoutController.ProcessOptionItem (cognitive 676) Entities/Layout/LayoutController.vb:6524 — LayoutController.ProcessOptionItem has cognitive complexity 676 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LandingPage.RenderCustomField (cognitive 538) · ×1
  • LandingPage.RenderCustomField (cognitive 538) LandingPage.ascx.vb:910 — LandingPage.RenderCustomField has cognitive complexity 538 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.RenderCustomField (cognitive 495) · ×1
  • SearchSmall.RenderCustomField (cognitive 495) SearchSmall.ascx.vb:707 — SearchSmall.RenderCustomField has cognitive complexity 495 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Search.cmdSearch_Click (cognitive 454) · ×1
  • Search.cmdSearch_Click (cognitive 454) Search.ascx.vb:1292 — Search.cmdSearch_Click has cognitive complexity 454 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperty.Update (cognitive 429) · ×1
  • EditProperty.Update (cognitive 429) EditProperty.ascx.vb:575 — EditProperty.Update has cognitive complexity 429 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.cmdSearch_Click (cognitive 424) · ×1
  • SearchSmall.cmdSearch_Click (cognitive 424) SearchSmall.ascx.vb:2714 — SearchSmall.cmdSearch_Click has cognitive complexity 424 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.Search_Click (cognitive 387) · ×1
  • SearchSmall.Search_Click (cognitive 387) SearchSmall.ascx.vb:1502 — SearchSmall.Search_Click has cognitive complexity 387 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LandingPage.Search_Click (cognitive 379) · ×1
  • LandingPage.Search_Click (cognitive 379) LandingPage.ascx.vb:1718 — LandingPage.Search_Click has cognitive complexity 379 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LandingPage.ProcessSearch (cognitive 358) · ×1
  • LandingPage.ProcessSearch (cognitive 358) LandingPage.ascx.vb:488 — LandingPage.ProcessSearch has cognitive complexity 358 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.ProcessSearch (cognitive 320) · ×1
  • SearchSmall.ProcessSearch (cognitive 320) SearchSmall.ascx.vb:353 — SearchSmall.ProcessSearch has cognitive complexity 320 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewType.ProcessHeaderFooter (cognitive 284) · ×1
  • ViewType.ProcessHeaderFooter (cognitive 284) ViewType.ascx.vb:725 — ViewType.ProcessHeaderFooter has cognitive complexity 284 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · _Default.ReadQueryString (cognitive 270) · ×1
  • _Default.ReadQueryString (cognitive 270) Default.ascx.vb:31 — _Default.ReadQueryString has cognitive complexity 270 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessComment (cognitive 266) · ×1
  • LayoutController.ProcessComment (cognitive 266) Entities/Layout/LayoutController.vb:1482 — LayoutController.ProcessComment has cognitive complexity 266 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CommentForm.cmdSubmit_Click (cognitive 191) · ×1
  • CommentForm.cmdSubmit_Click (cognitive 191) CommentForm.ascx.vb:244 — CommentForm.cmdSubmit_Click has cognitive complexity 191 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ContactForm.cmdSubmit_Click (cognitive 184) · ×1
  • ContactForm.cmdSubmit_Click (cognitive 184) ContactForm.ascx.vb:237 — ContactForm.cmdSubmit_Click has cognitive complexity 184 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditPermissions.cmdUpdate_Click (cognitive 184) · ×1
  • EditPermissions.cmdUpdate_Click (cognitive 184) EditPermissions.ascx.vb:151 — EditPermissions.cmdUpdate_Click has cognitive complexity 184 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PropertyController.GetModifiedSearchDocuments (cognitive 176) · ×1
  • PropertyController.GetModifiedSearchDocuments (cognitive 176) Entities/Property/PropertyController.vb:221 — PropertyController.GetModifiedSearchDocuments has cognitive complexity 176 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.drpLinked_SelectedIndexChanged (cognitive 165) · ×1
  • SearchSmall.drpLinked_SelectedIndexChanged (cognitive 165) SearchSmall.ascx.vb:3144 — SearchSmall.drpLinked_SelectedIndexChanged has cognitive complexity 165 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessReview (cognitive 158) · ×1
  • LayoutController.ProcessReview (cognitive 158) Entities/Layout/LayoutController.vb:2116 — LayoutController.ProcessReview has cognitive complexity 158 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessType (cognitive 157) · ×1
  • LayoutController.ProcessType (cognitive 157) Entities/Layout/LayoutController.vb:7237 — LayoutController.ProcessType has cognitive complexity 157 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewType.BindSortBy (cognitive 141) · ×1
  • ViewType.BindSortBy (cognitive 141) ViewType.ascx.vb:261 — ViewType.BindSortBy has cognitive complexity 141 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LandingPage.drpPropertyType_SelectedIndexChanged (cognitive 139) · ×1
  • LandingPage.drpPropertyType_SelectedIndexChanged (cognitive 139) LandingPage.ascx.vb:2065 — LandingPage.drpPropertyType_SelectedIndexChanged has cognitive complexity 139 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.drpPropertyType_SelectedIndexChanged (cognitive 139) · ×1
  • SearchSmall.drpPropertyType_SelectedIndexChanged (cognitive 139) SearchSmall.ascx.vb:3056 — SearchSmall.drpPropertyType_SelectedIndexChanged has cognitive complexity 139 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · NotificationJob.FormatTokens (cognitive 137) · ×1
  • NotificationJob.FormatTokens (cognitive 137) Entities/Reminders/NotificationJob.vb:175 — NotificationJob.FormatTokens has cognitive complexity 137 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ReminderJob.FormatTokens (cognitive 137) · ×1
  • ReminderJob.FormatTokens (cognitive 137) Entities/Reminders/ReminderJob.vb:209 — ReminderJob.FormatTokens has cognitive complexity 137 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ContactForm.rptDetails_OnItemDataBound (cognitive 134) · ×1
  • ContactForm.rptDetails_OnItemDataBound (cognitive 134) ContactForm.ascx.vb:423 — ContactForm.rptDetails_OnItemDataBound has cognitive complexity 134 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.GetFieldValue (cognitive 128) · ×1
  • LayoutController.GetFieldValue (cognitive 128) Entities/Layout/LayoutController.vb:466 — LayoutController.GetFieldValue has cognitive complexity 128 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Latest.BindSortBy (cognitive 125) · ×1
  • Latest.BindSortBy (cognitive 125) Latest.ascx.vb:676 — Latest.BindSortBy has cognitive complexity 125 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LandingPage.drpLinked_SelectedIndexChanged (cognitive 124) · ×1
  • LandingPage.drpLinked_SelectedIndexChanged (cognitive 124) LandingPage.ascx.vb:2153 — LandingPage.drpLinked_SelectedIndexChanged has cognitive complexity 124 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ReviewForm.cmdSubmit_Click (cognitive 120) · ×1
  • ReviewForm.cmdSubmit_Click (cognitive 120) ReviewForm.ascx.vb:110 — ReviewForm.cmdSubmit_Click has cognitive complexity 120 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SendToFriendForm.cmdSubmit_Click (cognitive 112) · ×1
  • SendToFriendForm.cmdSubmit_Click (cognitive 112) SendToFriendForm.ascx.vb:144 — SendToFriendForm.cmdSubmit_Click has cognitive complexity 112 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditLayoutSettings.BindSettings (cognitive 111) · ×1
  • EditLayoutSettings.BindSettings (cognitive 111) EditLayoutSettings.ascx.vb:374 — EditLayoutSettings.BindSettings has cognitive complexity 111 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessExportItem (cognitive 109) · ×1
  • LayoutController.ProcessExportItem (cognitive 109) Entities/Layout/LayoutController.vb:1836 — LayoutController.ProcessExportItem has cognitive complexity 109 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewType.BindProperty (cognitive 107) · ×1
  • ViewType.BindProperty (cognitive 107) ViewType.ascx.vb:422 — ViewType.BindProperty has cognitive complexity 107 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperty.BindDetails (cognitive 105) · ×1
  • EditProperty.BindDetails (cognitive 105) EditProperty.ascx.vb:140 — EditProperty.BindDetails has cognitive complexity 105 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Latest.BindLatest (cognitive 105) · ×1
  • Latest.BindLatest (cognitive 105) Latest.ascx.vb:209 — Latest.BindLatest has cognitive complexity 105 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LandingPage.ProcessHeaderFooter (cognitive 95) · ×1
  • LandingPage.ProcessHeaderFooter (cognitive 95) LandingPage.ascx.vb:366 — LandingPage.ProcessHeaderFooter has cognitive complexity 95 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Latest.ProcessEmpty (cognitive 92) · ×1
  • Latest.ProcessEmpty (cognitive 92) Latest.ascx.vb:489 — Latest.ProcessEmpty has cognitive complexity 92 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewProperty.BindProperty (cognitive 91) · ×1
  • ViewProperty.BindProperty (cognitive 91) ViewProperty.ascx.vb:152 — ViewProperty.BindProperty has cognitive complexity 91 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditCustomField.BindCustomField (cognitive 85) · ×1
  • EditCustomField.BindCustomField (cognitive 85) EditCustomField.ascx.vb:334 — EditCustomField.BindCustomField has cognitive complexity 85 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessMessage (cognitive 80) · ×1
  • LayoutController.ProcessMessage (cognitive 80) Entities/Layout/LayoutController.vb:7495 — LayoutController.ProcessMessage has cognitive complexity 80 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ChangeTemplate.InitializeTemplate (cognitive 79) · ×1
  • ChangeTemplate.InitializeTemplate (cognitive 79) ChangeTemplate.ascx.vb:74 — ChangeTemplate.InitializeTemplate has cognitive complexity 79 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditLayoutSettings.cmdUpdate_Click (cognitive 76) · ×1
  • EditLayoutSettings.cmdUpdate_Click (cognitive 76) EditLayoutSettings.ascx.vb:824 — EditLayoutSettings.cmdUpdate_Click has cognitive complexity 76 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ApproveReviews.cmdApprove_Click (cognitive 70) · ×1
  • ApproveReviews.cmdApprove_Click (cognitive 70) ApproveReviews.ascx.vb:168 — ApproveReviews.cmdApprove_Click has cognitive complexity 70 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditCustomField.cmdUpdate_Click (cognitive 68) · ×1
  • EditCustomField.cmdUpdate_Click (cognitive 68) EditCustomField.ascx.vb:531 — EditCustomField.cmdUpdate_Click has cognitive complexity 68 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PdfRender.ProcessHeaderFooter (cognitive 66) · ×1
  • PdfRender.ProcessHeaderFooter (cognitive 66) PdfRender.ascx.vb:40 — PdfRender.ProcessHeaderFooter has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewProperty.ProcessHeaderFooter (cognitive 66) · ×1
  • ViewProperty.ProcessHeaderFooter (cognitive 66) ViewProperty.ascx.vb:84 — ViewProperty.ProcessHeaderFooter has cognitive complexity 66 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ReviewForm.rptDetails_OnItemDataBound (cognitive 61) · ×1
  • ReviewForm.rptDetails_OnItemDataBound (cognitive 61) ReviewForm.ascx.vb:272 — ReviewForm.rptDetails_OnItemDataBound has cognitive complexity 61 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.LoadStyleSheet (cognitive 59) · ×1
  • LayoutController.LoadStyleSheet (cognitive 59) Entities/Layout/LayoutController.vb:1358 — LayoutController.LoadStyleSheet has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LatestOptions.LoadSettings (cognitive 59) · ×1
  • LatestOptions.LoadSettings (cognitive 59) LatestOptions.ascx.vb:558 — LatestOptions.LoadSettings has cognitive complexity 59 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LatestOptions.BindModules (cognitive 55) · ×1
  • LatestOptions.BindModules (cognitive 55) LatestOptions.ascx.vb:64 — LatestOptions.BindModules has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmallOptions.BindModules (cognitive 55) · ×1
  • SearchSmallOptions.BindModules (cognitive 55) SearchSmallOptions.ascx.vb:36 — SearchSmallOptions.BindModules has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TypesOptions.BindModules (cognitive 55) · ×1
  • TypesOptions.BindModules (cognitive 55) TypesOptions.ascx.vb:85 — TypesOptions.BindModules has cognitive complexity 55 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · _Default.ModuleActions.Get (cognitive 53) · ×1
  • _Default.ModuleActions.Get (cognitive 53) Default.ascx.vb:490 — _Default.ModuleActions.Get has cognitive complexity 53 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewContactLog.BindContactLog (cognitive 52) · ×1
  • ViewContactLog.BindContactLog (cognitive 52) ViewContactLog.ascx.vb:16 — ViewContactLog.BindContactLog has cognitive complexity 52 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CommentForm.rptDetails_OnItemDataBound (cognitive 51) · ×1
  • CommentForm.rptDetails_OnItemDataBound (cognitive 51) CommentForm.ascx.vb:511 — CommentForm.rptDetails_OnItemDataBound has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.BindSearch (cognitive 51) · ×1
  • SearchSmall.BindSearch (cognitive 51) SearchSmall.ascx.vb:74 — SearchSmall.BindSearch has cognitive complexity 51 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · jquery.lightbox-0.4.$.fn.lightBox (cognitive 51) · ×1
  • jquery.lightbox-0.4.$.fn.lightBox (cognitive 51) JS/Lightbox/jquery.lightbox-0.4.js:21 — jquery.lightbox-0.4.$.fn.lightBox has cognitive complexity 51 (threshold 15). Drivers by points: if/else 35 (40 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 6). None of this is in the body itself: all 51 points belong to 9 function items inside it that branch (___getPageSize, _keyboard_action, _start, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · EditProperty.Page_Load (cognitive 48) · ×1
  • EditProperty.Page_Load (cognitive 48) EditProperty.ascx.vb:1192 — EditProperty.Page_Load has cognitive complexity 48 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UploadPhotoStandard.cmdUploadPhoto_Click (cognitive 47) · ×1
  • UploadPhotoStandard.cmdUploadPhoto_Click (cognitive 47) Controls/UploadPhotoStandard.ascx.vb:66 — UploadPhotoStandard.cmdUploadPhoto_Click has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ReminderJob.SendReminders (cognitive 47) · ×1
  • ReminderJob.SendReminders (cognitive 47) Entities/Reminders/ReminderJob.vb:53 — ReminderJob.SendReminders has cognitive complexity 47 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CommentForm.CommentFormFields.Get (cognitive 46) · ×1
  • CommentForm.CommentFormFields.Get (cognitive 46) CommentForm.ascx.vb:33 — CommentForm.CommentFormFields.Get has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SWFUploader.CheckLimit (cognitive 45) · ×1
  • SWFUploader.CheckLimit (cognitive 45) Controls/SWFUploader.ashx.vb:63 — SWFUploader.CheckLimit has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.GetTypeLink (cognitive 45) · ×1
  • LayoutController.GetTypeLink (cognitive 45) Entities/Layout/LayoutController.vb:7137 — LayoutController.GetTypeLink has cognitive complexity 45 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmallOptions.LoadSettings (cognitive 42) · ×1
  • SearchSmallOptions.LoadSettings (cognitive 42) SearchSmallOptions.ascx.vb:201 — SearchSmallOptions.LoadSettings has cognitive complexity 42 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LatestOptions.cmdAddCustomField_Click (cognitive 39) · ×1
  • LatestOptions.cmdAddCustomField_Click (cognitive 39) LatestOptions.ascx.vb:427 — LatestOptions.cmdAddCustomField_Click has cognitive complexity 39 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ContactForm.MailTo.Get (cognitive 37) · ×1
  • ContactForm.MailTo.Get (cognitive 37) ContactForm.ascx.vb:93 — ContactForm.MailTo.Get has cognitive complexity 37 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CurrencyConverter.ConvertCurrency (cognitive 36) · ×1
  • CurrencyConverter.ConvertCurrency (cognitive 36) CurrencyConverter.ascx.vb:42 — CurrencyConverter.ConvertCurrency has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditLayoutSettings.BindSortBy (cognitive 36) · ×1
  • EditLayoutSettings.BindSortBy (cognitive 36) EditLayoutSettings.ascx.vb:218 — EditLayoutSettings.BindSortBy has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessHeaderFooter (cognitive 36) · ×1
  • LayoutController.ProcessHeaderFooter (cognitive 36) Entities/Layout/LayoutController.vb:3385 — LayoutController.ProcessHeaderFooter has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessPhoto (cognitive 36) · ×1
  • LayoutController.ProcessPhoto (cognitive 36) Entities/Layout/LayoutController.vb:7010 — LayoutController.ProcessPhoto has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.ProcessHeaderFooter (cognitive 36) · ×1
  • SearchSmall.ProcessHeaderFooter (cognitive 36) SearchSmall.ascx.vb:315 — SearchSmall.ProcessHeaderFooter has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Types.ProcessHeaderFooter (cognitive 36) · ×1
  • Types.ProcessHeaderFooter (cognitive 36) Types.ascx.vb:118 — Types.ProcessHeaderFooter has cognitive complexity 36 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditPropertyPhotos.dlPhotos_OnItemDataBound (cognitive 35) · ×1
  • EditPropertyPhotos.dlPhotos_OnItemDataBound (cognitive 35) Controls/EditPropertyPhotos.ascx.vb:132 — EditPropertyPhotos.dlPhotos_OnItemDataBound has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SendToFriendForm.rptDetails_OnItemDataBound (cognitive 35) · ×1
  • SendToFriendForm.rptDetails_OnItemDataBound (cognitive 35) SendToFriendForm.ascx.vb:263 — SendToFriendForm.rptDetails_OnItemDataBound has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Print.ManageStyleSheets (cognitive 35) · ×1
  • Print.ManageStyleSheets (cognitive 35) Print.aspx.vb:32 — Print.ManageStyleSheets has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.GetPropertyLink (cognitive 34) · ×1
  • LayoutController.GetPropertyLink (cognitive 34) Entities/Layout/LayoutController.vb:376 — LayoutController.GetPropertyLink has cognitive complexity 34 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditPropertyTypes.BindPropertyTypes (cognitive 33) · ×1
  • EditPropertyTypes.BindPropertyTypes (cognitive 33) EditPropertyTypes.ascx.vb:88 — EditPropertyTypes.BindPropertyTypes has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PropertyAgentBase.GetLimit (cognitive 32) · ×1
  • PropertyAgentBase.GetLimit (cognitive 32) Entities/PropertyAgentBase.vb:96 — PropertyAgentBase.GetLimit has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Latest.GetLimit (cognitive 32) · ×1
  • Latest.GetLimit (cognitive 32) Latest.ascx.vb:107 — Latest.GetLimit has cognitive complexity 32 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperties.BindSortBy (cognitive 31) · ×1
  • EditProperties.BindSortBy (cognitive 31) EditProperties.ascx.vb:160 — EditProperties.BindSortBy has cognitive complexity 31 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SWFUploader.ProcessRequest (cognitive 30) · ×1
  • SWFUploader.ProcessRequest (cognitive 30) Controls/SWFUploader.ashx.vb:150 — SWFUploader.ProcessRequest has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Search.BindDetails (cognitive 29) · ×1
  • Search.BindDetails (cognitive 29) Search.ascx.vb:49 — Search.BindDetails has cognitive complexity 29 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditPropertyPhotos.dlPhotos_OnItemCommand (cognitive 27) · ×1
  • EditPropertyPhotos.dlPhotos_OnItemCommand (cognitive 27) Controls/EditPropertyPhotos.ascx.vb:212 — EditPropertyPhotos.dlPhotos_OnItemCommand has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditCustomFields.grdCustomFields_ItemDataBound (cognitive 27) · ×1
  • EditCustomFields.grdCustomFields_ItemDataBound (cognitive 27) EditCustomFields.ascx.vb:222 — EditCustomFields.grdCustomFields_ItemDataBound has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditCustomFields.grdCustomFields_ItemCommand (cognitive 27) · ×1
  • EditCustomFields.grdCustomFields_ItemCommand (cognitive 27) EditCustomFields.ascx.vb:296 — EditCustomFields.grdCustomFields_ItemCommand has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LatestOptions.UpdateSettings (cognitive 27) · ×1
  • LatestOptions.UpdateSettings (cognitive 27) LatestOptions.ascx.vb:687 — LatestOptions.UpdateSettings has cognitive complexity 27 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AgentController.AddUsersToList (cognitive 26) · ×1
  • AgentController.AddUsersToList (cognitive 26) Entities/AgentController.vb:163 — AgentController.AddUsersToList has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LatestOptions.BindSortBy (cognitive 26) · ×1
  • LatestOptions.BindSortBy (cognitive 26) LatestOptions.ascx.vb:111 — LatestOptions.BindSortBy has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewType.GetAdditionalParams (cognitive 26) · ×1
  • ViewType.GetAdditionalParams (cognitive 26) ViewType.ascx.vb:1072 — ViewType.GetAdditionalParams has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ContactForm.ContactFormFields.Get (cognitive 25) · ×1
  • ContactForm.ContactFormFields.Get (cognitive 25) ContactForm.ascx.vb:21 — ContactForm.ContactFormFields.Get has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PagingControl.CreateURL (cognitive 25) · ×1
  • PagingControl.CreateURL (cognitive 25) Entities/WebControls/PagingControl.vb:264 — PagingControl.CreateURL has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.SiblingSearchProperties.Get (cognitive 25) · ×1
  • LayoutController.SiblingSearchProperties.Get (cognitive 25) Entities/Layout/LayoutController.vb:197 — LayoutController.SiblingSearchProperties.Get has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ImportTemplateDefinition.ImportTemplate (cognitive 23) · ×1
  • ImportTemplateDefinition.ImportTemplate (cognitive 23) ImportTemplateDefinition.ascx.vb:56 — ImportTemplateDefinition.ImportTemplate has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LandingPage.GetTypeLink (cognitive 23) · ×1
  • LandingPage.GetTypeLink (cognitive 23) LandingPage.ascx.vb:325 — LandingPage.GetTypeLink has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Search.GetTypeLink (cognitive 23) · ×1
  • Search.GetTypeLink (cognitive 23) Search.ascx.vb:255 — Search.GetTypeLink has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.GetTypeLink (cognitive 23) · ×1
  • SearchSmall.GetTypeLink (cognitive 23) SearchSmall.ascx.vb:274 — SearchSmall.GetTypeLink has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewType.dlProperty_OnItemDataBound (cognitive 23) · ×1
  • ViewType.dlProperty_OnItemDataBound (cognitive 23) ViewType.ascx.vb:1274 — ViewType.dlProperty_OnItemDataBound has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (ViewType.rptProperty_OnItemDataBound) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · ViewType.rptProperty_OnItemDataBound (cognitive 23) · ×1
  • ViewType.rptProperty_OnItemDataBound (cognitive 23) ViewType.ascx.vb:1329 — ViewType.rptProperty_OnItemDataBound has cognitive complexity 23 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (ViewType.dlProperty_OnItemDataBound) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · NotificationJob.SendReminders (cognitive 22) · ×1
  • NotificationJob.SendReminders (cognitive 22) Entities/Reminders/NotificationJob.vb:53 — NotificationJob.SendReminders has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Types.BindTypes (cognitive 22) · ×1
  • Types.BindTypes (cognitive 22) Types.ascx.vb:20 — Types.BindTypes has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewContactLog.DataGrid1_ItemDataBound (cognitive 21) · ×1
  • ViewContactLog.DataGrid1_ItemDataBound (cognitive 21) ViewContactLog.ascx.vb:186 — ViewContactLog.DataGrid1_ItemDataBound has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PagingControl.BindPageNumbers (cognitive 21) · ×1
  • PagingControl.BindPageNumbers (cognitive 21) Entities/WebControls/PagingControl.vb:211 — PagingControl.BindPageNumbers has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · AgentController.FillUserInfo (cognitive 21) · ×1
  • AgentController.FillUserInfo (cognitive 21) Entities/AgentController.vb:217 — AgentController.FillUserInfo has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.GetPhotoPath (cognitive 21) · ×1
  • LayoutController.GetPhotoPath (cognitive 21) Entities/Layout/LayoutController.vb:872 — LayoutController.GetPhotoPath has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmallOptions.UpdateSettings (cognitive 21) · ×1
  • SearchSmallOptions.UpdateSettings (cognitive 21) SearchSmallOptions.ascx.vb:280 — SearchSmallOptions.UpdateSettings has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TypesOptions.UpdateSettings (cognitive 21) · ×1
  • TypesOptions.UpdateSettings (cognitive 21) TypesOptions.ascx.vb:203 — TypesOptions.UpdateSettings has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TypesOptions.cmdAddAgent_Click (cognitive 21) · ×1
  • TypesOptions.cmdAddAgent_Click (cognitive 21) TypesOptions.ascx.vb:277 — TypesOptions.cmdAddAgent_Click has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditContactField.cmdUpdate_Click (cognitive 20) · ×1
  • EditContactField.cmdUpdate_Click (cognitive 20) EditContactField.ascx.vb:229 — EditContactField.cmdUpdate_Click has cognitive complexity 20 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperties.BindProperties (cognitive 19) · ×1
  • EditProperties.BindProperties (cognitive 19) EditProperties.ascx.vb:282 — EditProperties.BindProperties has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperty.cmdUpdate_Click (cognitive 19) · ×1
  • EditProperty.cmdUpdate_Click (cognitive 19) EditProperty.ascx.vb:1991 — EditProperty.cmdUpdate_Click has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperty.cmdClone_Click (cognitive 19) · ×1
  • EditProperty.cmdClone_Click (cognitive 19) EditProperty.ascx.vb:2085 — EditProperty.cmdClone_Click has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessRSSHeader (cognitive 19) · ×1
  • LayoutController.ProcessRSSHeader (cognitive 19) Entities/Layout/LayoutController.vb:2335 — LayoutController.ProcessRSSHeader has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PropertyController.List (cognitive 19) · ×1
  • PropertyController.List (cognitive 19) Entities/Property/PropertyController.vb:111 — PropertyController.List has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ImageHandler.ProcessRequest (cognitive 19) · ×1
  • ImageHandler.ProcessRequest (cognitive 19) ImageHandler.ashx.vb:71 — ImageHandler.ProcessRequest has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UploadPhotoHTML5.GetImageByUrl (cognitive 18) · ×1
  • UploadPhotoHTML5.GetImageByUrl (cognitive 18) Controls/UploadPhotoHTML5.ascx.vb:113 — UploadPhotoHTML5.GetImageByUrl has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditCustomField.valFieldElementsFrom_ServerValidate (cognitive 18) · ×1
  • EditCustomField.valFieldElementsFrom_ServerValidate (cognitive 18) EditCustomField.ascx.vb:749 — EditCustomField.valFieldElementsFrom_ServerValidate has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (EditCustomField.valFieldElementsTo_ServerValidate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · EditCustomField.valFieldElementsTo_ServerValidate (cognitive 18) · ×1
  • EditCustomField.valFieldElementsTo_ServerValidate (cognitive 18) EditCustomField.ascx.vb:794 — EditCustomField.valFieldElementsTo_ServerValidate has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (EditCustomField.valFieldElementsFrom_ServerValidate) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · EditPermissions.grdPermissions_ItemDataBound (cognitive 18) · ×1
  • EditPermissions.grdPermissions_ItemDataBound (cognitive 18) EditPermissions.ascx.vb:433 — EditPermissions.grdPermissions_ItemDataBound has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UploadPhotoHTML5.cmdAttachPhoto_Click (cognitive 17) · ×1
  • UploadPhotoHTML5.cmdAttachPhoto_Click (cognitive 17) Controls/UploadPhotoHTML5.ascx.vb:40 — UploadPhotoHTML5.cmdAttachPhoto_Click has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UploadPhotoSWF.cmdAttachPhoto_Click (cognitive 17) · ×1
  • UploadPhotoSWF.cmdAttachPhoto_Click (cognitive 17) Controls/UploadPhotoSWF.ascx.vb:232 — UploadPhotoSWF.cmdAttachPhoto_Click has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · CurrencySelector.BindCurrency (cognitive 17) · ×1
  • CurrencySelector.BindCurrency (cognitive 17) CurrencySelector.ascx.vb:14 — CurrencySelector.BindCurrency has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditTemplateDefinition.BindDetails (cognitive 17) · ×1
  • EditTemplateDefinition.BindDetails (cognitive 17) EditTemplateDefinition.ascx.vb:68 — EditTemplateDefinition.BindDetails has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LandingPage.LayoutController.Get (cognitive 17) · ×1
  • LandingPage.LayoutController.Get (cognitive 17) LandingPage.ascx.vb:60 — LandingPage.LayoutController.Get has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Latest.dlLatest_ItemDataBound (cognitive 17) · ×1
  • Latest.dlLatest_ItemDataBound (cognitive 17) Latest.ascx.vb:859 — Latest.dlLatest_ItemDataBound has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (Latest.rptLatest_ItemDataBound) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · Latest.rptLatest_ItemDataBound (cognitive 17) · ×1
  • Latest.rptLatest_ItemDataBound (cognitive 17) Latest.ascx.vb:890 — Latest.rptLatest_ItemDataBound has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function. This shape REPEATS in the file: one other method here (Latest.dlLatest_ItemDataBound) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · TypesOptions.LoadSettings (cognitive 17) · ×1
  • TypesOptions.LoadSettings (cognitive 17) TypesOptions.ascx.vb:136 — TypesOptions.LoadSettings has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · TypesOptions.rptTypesFilter_ItemDataBound (cognitive 17) · ×1
  • TypesOptions.rptTypesFilter_ItemDataBound (cognitive 17) TypesOptions.ascx.vb:307 — TypesOptions.rptTypesFilter_ItemDataBound has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · UploadPhotoSWF.GetImageByUrl (cognitive 16) · ×1
  • UploadPhotoSWF.GetImageByUrl (cognitive 16) Controls/UploadPhotoSWF.ascx.vb:55 — UploadPhotoSWF.GetImageByUrl has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ImageHandlerExt.ProcessRequest (cognitive 16) · ×1
  • ImageHandlerExt.ProcessRequest (cognitive 16) ImageHandlerExt.ashx.vb:122 — ImageHandlerExt.ProcessRequest has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Xml.ReadQueryString (cognitive 16) · ×1
  • Xml.ReadQueryString (cognitive 16) Xml.ascx.vb:74 — Xml.ReadQueryString has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperty.CheckSecurity (cognitive 16) · ×1
  • EditProperty.CheckSecurity (cognitive 16) EditProperty.ascx.vb:83 — EditProperty.CheckSecurity has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · EditProperty.Page_Initialization (cognitive 16) · ×1
  • EditProperty.Page_Initialization (cognitive 16) EditProperty.ascx.vb:1122 — EditProperty.Page_Initialization has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · LayoutController.ProcessExportHeader (cognitive 16) · ×1
  • LayoutController.ProcessExportHeader (cognitive 16) Entities/Layout/LayoutController.vb:1807 — LayoutController.ProcessExportHeader has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Export.ReadQueryString (cognitive 16) · ×1
  • Export.ReadQueryString (cognitive 16) Export.ascx.vb:84 — Export.ReadQueryString has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Latest.ReadQueryStringTotal (cognitive 16) · ×1
  • Latest.ReadQueryStringTotal (cognitive 16) Latest.ascx.vb:426 — Latest.ReadQueryStringTotal has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Rss.ReadQueryString (cognitive 16) · ×1
  • Rss.ReadQueryString (cognitive 16) Rss.ascx.vb:74 — Rss.ReadQueryString has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmall.drpPropertyBrokersCustom_SelectedIndexChanged (cognitive 16) · ×1
  • SearchSmall.drpPropertyBrokersCustom_SelectedIndexChanged (cognitive 16) SearchSmall.ascx.vb:3018 — SearchSmall.drpPropertyBrokersCustom_SelectedIndexChanged has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SearchSmallOptions.BindSortBy (cognitive 16) · ×1
  • SearchSmallOptions.BindSortBy (cognitive 16) SearchSmallOptions.ascx.vb:116 — SearchSmallOptions.BindSortBy has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewType.ReadQueryString (cognitive 16) · ×1
  • ViewType.ReadQueryString (cognitive 16) ViewType.ascx.vb:166 — ViewType.ReadQueryString has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ViewType.Page_Load (cognitive 16) · ×1
  • ViewType.Page_Load (cognitive 16) ViewType.ascx.vb:1234 — ViewType.Page_Load has cognitive complexity 16 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D3 · God Classes · FunctionTooLong · ×1
  • FunctionTooLong: jquery.lightbox-0.4.$.fn.lightBox JS/Lightbox/jquery.lightbox-0.4.js:21 — FunctionTooLong — $.fn.lightBox runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Near-duplicate member pair (240 shared lines) · ×1
  • Near-duplicate member pair (240 shared lines) LandingPage.ascx.vb:1720 — LandingPage.ascx.vb:1720-1977 | SearchSmall.ascx.vb:1504-1764 — These two members are variants of one another: 240 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (43 shared lines) · ×1
  • Near-duplicate member pair (43 shared lines) ContactForm.ascx.vb:238 — ContactForm.ascx.vb:238-419 | SendToFriendForm.ascx.vb:146-259 — These two members are variants of one another: 43 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×1
  • Edited copy of a member (33 corresponding lines) SearchSmall.ascx.vb:317 — SearchSmall.ascx.vb:317-349 | Types.ascx.vb:120-152 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (26 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (26 members, 50+ identical tokens) AccessDenied.ascx.vb:20 — AccessDenied.ascx.vb:20-48 | ApproveReviews.ascx.vb:15-43 | ChangeTemplate.ascx.vb:26-54 | EditBrokers.ascx.vb:29-57 | EditContactField.ascx.vb:76-113 | EditContactFields.ascx.vb:52-80 | EditCustomField.ascx.vb:36-73 | EditCustomFields.ascx.vb:52-80 | EditEmailFiles.ascx.vb:14-42 | EditExpiryNotifications.ascx.vb:23-51 | EditLayoutFiles.ascx.vb:14-42 | EditLayoutSettings.ascx.vb:750-778 | EditPermissions.ascx.vb:15-43 | EditProperties.ascx.vb:250-278 | EditProperty.ascx.vb:142-397 | EditPropertyNotifications.ascx.vb:23-51 | EditPropertyType.ascx.vb:38-75 | EditPropertyTypes.ascx.vb:56-84 | EditReviewField.ascx.vb:76-113 | EditReviewFields.ascx.vb:52-80 | EditTemplateDefinition.ascx.vb:31-64 | EditTemplateDefinitions.ascx.vb:15-43 | ExportTemplateDefinition.ascx.vb:14-47 | ImportTemplateDefinition.ascx.vb:19-52 | ViewContactLog.ascx.vb:120-148 | ViewType.ascx.vb:424-703 — These 26 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 26 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 26 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Export.ascx.vb:86 — Export.ascx.vb:86-133 | Latest.ascx.vb:428-485 | Latest.ascx.vb:624-645 | Rss.ascx.vb:76-123 | ViewType.ascx.vb:168-225 | Xml.ascx.vb:76-123 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Edited copy of a member (97 corresponding lines) · ×1
  • Edited copy of a member (97 corresponding lines) Entities/Reminders/NotificationJob.vb:55 — Entities/Reminders/NotificationJob.vb:55-151 | Entities/Reminders/ReminderJob.vb:55-205 — These two members are one piece of code written twice and then edited apart: 97 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (82 corresponding lines) · ×1
  • Edited copy of a member (82 corresponding lines) Entities/Layout/LayoutController.vb:377 — Entities/Layout/LayoutController.vb:377-458 | Entities/Layout/LayoutController.vb:7139-7233 — These two members are one piece of code written twice and then edited apart: 82 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) EditPermissions.ascx.vb:525 — EditPermissions.ascx.vb:525-574 | EditPermissions.ascx.vb:580-616 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (56 corresponding lines) · ×1
  • Edited copy of a member (56 corresponding lines) EditContactField.ascx.vb:231 — EditContactField.ascx.vb:231-293 | EditReviewField.ascx.vb:206-261 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) Xml.ascx.vb:129 — Xml.ascx.vb:129-159 | Rss.ascx.vb:129-150 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 49+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 49+ corresponding lines) EditContactFields.ascx.vb:86 — EditContactFields.ascx.vb:86-134 | EditCustomFields.ascx.vb:86-134 | EditReviewFields.ascx.vb:86-134 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 49 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) Search.ascx.vb:175 — Search.ascx.vb:175-213 | SearchSmall.ascx.vb:221-248 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×1
  • Edited copy of a member (40 corresponding lines) EditCustomField.ascx.vb:751 — EditCustomField.ascx.vb:751-790 | EditCustomField.ascx.vb:796-835 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) Latest.ascx.vb:157 — Latest.ascx.vb:157-190 | Types.ascx.vb:85-114 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 46+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 46+ corresponding lines) EditContactFields.ascx.vb:255 — EditContactFields.ascx.vb:255-300 | EditPropertyTypes.ascx.vb:342-397 | EditReviewFields.ascx.vb:255-300 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 46 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) Controls/UploadPhotoSWF.ascx.vb:57 — Controls/UploadPhotoSWF.ascx.vb:57-105 | ImageHandlerExt.ashx.vb:28-74 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) EditContactField.ascx.vb:150 — EditContactField.ascx.vb:150-183 | EditReviewField.ascx.vb:130-160 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×1
  • Edited copy of a member (25 corresponding lines) ImageHandlerExt.ashx.vb:80 — ImageHandlerExt.ashx.vb:80-104 | ImageHandler.ashx.vb:29-53 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) Entities/Social/Journal.vb:15 — Entities/Social/Journal.vb:15-43 | Entities/Social/Journal.vb:47-69 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×1
  • Edited copy of a member (20 corresponding lines) Entities/Layout/LayoutController.vb:310 — Entities/Layout/LayoutController.vb:310-329 | ViewType.ascx.vb:123-142 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) EditPropertyNotifications.ascx.vb:78 — EditPropertyNotifications.ascx.vb:78-104 | EditExpiryNotifications.ascx.vb:85-111 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) Entities/AgentController.vb:64 — Entities/AgentController.vb:64-77 | Entities/AgentController.vb:121-135 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) EditProperties.ascx.vb:122 — EditProperties.ascx.vb:122-133 | EditProperty.ascx.vb:119-136 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) Entities/Property/PropertySettings.vb:1795 — Entities/Property/PropertySettings.vb:1795-1809 | Entities/Property/PropertySettings.vb:1815-1830 | Entities/Property/PropertySettings.vb:1836-1850 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (179 corresponding lines) · ×1
  • Edited copy of a member (179 corresponding lines) Entities/Reminders/NotificationJob.vb:177 — Entities/Reminders/NotificationJob.vb:177-355 | Entities/Reminders/ReminderJob.vb:211-389 — These two members are one piece of code written twice and then edited apart: 179 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 5+ corresponding lines) Entities/WebControls/PagingControl.vb:342 — Entities/WebControls/PagingControl.vb:342-346 | Entities/WebControls/PagingControl.vb:360-364 | Entities/WebControls/PagingControl.vb:378-382 | Entities/WebControls/PagingControl.vb:396-400 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 4+ corresponding lines) LandingPage.ascx.vb:2015 — LandingPage.ascx.vb:2015-2018 | LandingPage.ascx.vb:2024-2027 | ViewType.ascx.vb:1410-1413 | ViewType.ascx.vb:1419-1422 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 2+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 2+ corresponding lines) Entities/ContactFields/ContactFieldController.vb:39 — Entities/ContactFields/ContactFieldController.vb:39-40 | Entities/ContactFields/ContactFieldController.vb:46-47 | Entities/ReviewFields/ReviewFieldController.vb:34-35 | Entities/ReviewFields/ReviewFieldController.vb:41-42 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 9+ corresponding lines) EditContactFields.ascx.vb:186 — EditContactFields.ascx.vb:186-194 | EditCustomFields.ascx.vb:186-194 | EditReviewFields.ascx.vb:186-194 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) Controls/UploadPhotoStandard.ascx.vb:287 — Controls/UploadPhotoStandard.ascx.vb:287-299 | ImportTemplateDefinition.ascx.vb:197-209 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 15+ corresponding lines) EditContactFields.ascx.vb:166 — EditContactFields.ascx.vb:166-180 | EditCustomFields.ascx.vb:166-180 | EditPropertyTypes.ascx.vb:233-247 | EditReviewFields.ascx.vb:166-180 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (2 corresponding lines) · ×1
  • Edited copy of a member (2 corresponding lines) Entities/Templates/TemplateWriter.vb:198 — Entities/Templates/TemplateWriter.vb:198-199 | ImportTemplateDefinition.ascx.vb:144-145 — These two members are one piece of code written twice and then edited apart: 2 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 6+ corresponding lines) Entities/PropertyAgentLatestBase.vb:49 — Entities/PropertyAgentLatestBase.vb:49-54 | Entities/PropertyAgentSearchBase.vb:46-51 | Entities/PropertyAgentTypesBase.vb:34-39 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (156 lines × 2) · ×1
  • Duplicated block (156 lines × 2) LandingPage.ascx.vb:1822 — LandingPage.ascx.vb:1822-1977 | SearchSmall.ascx.vb:1609-1764 — before extracting anything, compare `LandingPage.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 345 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (50 lines × 2) · ×1
  • Duplicated block (50 lines × 2) ViewType.ascx.vb:1276 — ViewType.ascx.vb:1276-1325 | ViewType.ascx.vb:1331-1380 — 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.
D4 · Code Duplication · Duplicated block (49 lines × 2) · ×1
  • Duplicated block (49 lines × 2) Latest.ascx.vb:437 — Latest.ascx.vb:437-485 | ViewType.ascx.vb:177-225 — before extracting anything, compare `Latest.ascx.vb` and `ViewType.ascx.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (46 lines × 2) · ×1
  • Duplicated block (46 lines × 2) LandingPage.ascx.vb:1770 — LandingPage.ascx.vb:1770-1815 | SearchSmall.ascx.vb:1557-1602 — before extracting anything, compare `LandingPage.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 345 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (23–45 lines × 3) · ×1
  • Duplicated block (23–45 lines × 3) EditPermissions.ascx.vb:227 — EditPermissions.ascx.vb:227-249 | EditPermissions.ascx.vb:282-306 | EditPermissions.ascx.vb:335-379 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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.
D4 · Code Duplication · Duplicated block (43 lines × 3) · ×1
  • Duplicated block (43 lines × 3) LatestOptions.ascx.vb:66 — LatestOptions.ascx.vb:66-108 | SearchSmallOptions.ascx.vb:38-80 | TypesOptions.ascx.vb:87-129 — before extracting anything, compare `LatestOptions.ascx.vb` and `TypesOptions.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 71 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) Controls/UploadPhotoSWF.ascx.vb:57 — Controls/UploadPhotoSWF.ascx.vb:57-90 | ImageHandlerExt.ashx.vb:28-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.
D4 · Code Duplication · Duplicated block (33 lines × 3) · ×1
  • Duplicated block (33 lines × 3) Export.ascx.vb:95 — Export.ascx.vb:95-127 | Rss.ascx.vb:85-117 | Xml.ascx.vb:85-117 — before extracting anything, compare `Export.ascx.vb` and `Rss.ascx.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (32–33 lines × 2) · ×1
  • Duplicated block (32–33 lines × 2) LandingPage.ascx.vb:1727 — LandingPage.ascx.vb:1727-1758 | SearchSmall.ascx.vb:1513-1545 — before extracting anything, compare `LandingPage.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 345 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) Entities/Layout/LayoutController.vb:3393 — Entities/Layout/LayoutController.vb:3393-3419 | SearchSmall.ascx.vb:323-349 | Types.ascx.vb:126-152 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) EditExpiryNotifications.ascx.vb:89 — EditExpiryNotifications.ascx.vb:89-111 | EditPropertyNotifications.ascx.vb:82-104 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×1
  • Duplicated block (24 lines × 2) EditCustomField.ascx.vb:767 — EditCustomField.ascx.vb:767-790 | EditCustomField.ascx.vb:812-835 — 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.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) Latest.ascx.vb:861 — Latest.ascx.vb:861-885 | Latest.ascx.vb:892-916 — 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.
D4 · Code Duplication · Duplicated block (20 lines × 3) · ×1
  • Duplicated block (20 lines × 3) EditTemplateDefinition.ascx.vb:34 — EditTemplateDefinition.ascx.vb:34-53 | ExportTemplateDefinition.ascx.vb:17-36 | ImportTemplateDefinition.ascx.vb:22-41 — before extracting anything, compare `EditTemplateDefinition.ascx.vb` and `ExportTemplateDefinition.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) ContactForm.ascx.vb:390 — ContactForm.ascx.vb:390-409 | SendToFriendForm.ascx.vb:234-253 — before extracting anything, compare `ContactForm.ascx.vb` and `SendToFriendForm.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×1
  • Duplicated block (19 lines × 3) EditPermissions.ascx.vb:251 — EditPermissions.ascx.vb:251-270 | EditPermissions.ascx.vb:304-322 | EditPermissions.ascx.vb:365-383 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (17 lines × 26) · ×1
  • Duplicated block (17 lines × 26) AccessDenied.ascx.vb:32 — AccessDenied.ascx.vb:32-48 | ApproveReviews.ascx.vb:27-43 | ChangeTemplate.ascx.vb:38-54 | EditBrokers.ascx.vb:41-57 | EditContactField.ascx.vb:97-113 | EditContactFields.ascx.vb:64-80 | EditCustomField.ascx.vb:57-73 | EditCustomFields.ascx.vb:64-80 | EditEmailFiles.ascx.vb:26-42 | EditExpiryNotifications.ascx.vb:35-51 | EditLayoutFiles.ascx.vb:26-42 | EditLayoutSettings.ascx.vb:762-778 | EditPermissions.ascx.vb:27-43 | EditProperties.ascx.vb:262-278 | EditProperty.ascx.vb:378-394 | EditPropertyNotifications.ascx.vb:35-51 | EditPropertyType.ascx.vb:59-75 | EditPropertyTypes.ascx.vb:68-84 | EditReviewField.ascx.vb:97-113 | EditReviewFields.ascx.vb:64-80 | EditTemplateDefinition.ascx.vb:48-64 | EditTemplateDefinitions.ascx.vb:27-43 | ExportTemplateDefinition.ascx.vb:31-47 | ImportTemplateDefinition.ascx.vb:36-52 | ViewContactLog.ascx.vb:132-148 | ViewType.ascx.vb:556-572 — before extracting anything, compare `AccessDenied.ascx.vb` and `EditEmailFiles.ascx.vb` as WHOLE FILES: 84% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17 lines × 5) · ×1
  • Duplicated block (17 lines × 5) Export.ascx.vb:117 — Export.ascx.vb:117-133 | Latest.ascx.vb:467-483 | Rss.ascx.vb:107-123 | ViewType.ascx.vb:207-223 | Xml.ascx.vb:107-123 — before extracting anything, compare `Export.ascx.vb` and `Latest.ascx.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14–17 lines × 3) · ×1
  • Duplicated block (14–17 lines × 3) Entities/AgentController.vb:36 — Entities/AgentController.vb:36-52 | Entities/AgentController.vb:100-115 | Entities/AgentController.vb:142-155 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1
  • Duplicated block (17 lines × 3) LandingPage.ascx.vb:289 — LandingPage.ascx.vb:289-305 | Search.ascx.vb:219-235 | SearchSmall.ascx.vb:1424-1440 — before extracting anything, compare `LandingPage.ascx.vb` and `Search.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16–17 lines × 3) · ×1
  • Duplicated block (16–17 lines × 3) LandingPage.ascx.vb:878 — LandingPage.ascx.vb:878-893 | Search.ascx.vb:305-321 | SearchSmall.ascx.vb:38-54 — before extracting anything, compare `LandingPage.ascx.vb` and `Search.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (14 lines × 8) · ×1
  • Duplicated block (14 lines × 8) LandingPage.ascx.vb:1860 — LandingPage.ascx.vb:1860-1873 | LandingPage.ascx.vb:1886-1899 | LandingPage.ascx.vb:1924-1937 | LandingPage.ascx.vb:1944-1957 | SearchSmall.ascx.vb:1647-1660 | SearchSmall.ascx.vb:1673-1686 | SearchSmall.ascx.vb:1711-1724 | SearchSmall.ascx.vb:1731-1744 — before extracting anything, compare `LandingPage.ascx.vb` and `SearchSmall.ascx.vb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 345 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (22–23 lines × 3) · ×1
  • Duplicated block (22–23 lines × 3) EditProperty.ascx.vb:718 — EditProperty.ascx.vb:718-740 | EditProperty.ascx.vb:776-798 | EditProperty.ascx.vb:808-829 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) Latest.ascx.vb:46 — Latest.ascx.vb:46-57 | ViewType.ascx.vb:66-78 — before extracting anything, compare `Latest.ascx.vb` and `ViewType.ascx.vb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) EditTemplateDefinition.ascx.vb:31 — EditTemplateDefinition.ascx.vb:31-41 | EditTemplateDefinitions.ascx.vb:15-25 | ExportTemplateDefinition.ascx.vb:14-24 | ImportTemplateDefinition.ascx.vb:19-29 — before extracting anything, compare `EditTemplateDefinition.ascx.vb` and `ExportTemplateDefinition.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 55 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) EditPropertyType.ascx.vb:229 — EditPropertyType.ascx.vb:229-238 | EditPropertyType.ascx.vb:275-285 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `EditPropertyType.ascx.vb:274` calls `Delete` and `EditPropertyType.ascx.vb:228` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) Export.ascx.vb:94 — Export.ascx.vb:94-103 | Latest.ascx.vb:436-445 | Latest.ascx.vb:624-633 | Rss.ascx.vb:84-93 | ViewType.ascx.vb:176-185 | Xml.ascx.vb:84-93 — before extracting anything, compare `Export.ascx.vb` and `Latest.ascx.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8–9 lines × 4) · ×1
  • Duplicated block (8–9 lines × 4) ContactForm.ascx.vb:254 — ContactForm.ascx.vb:254-262 | ContactForm.ascx.vb:395-402 | SendToFriendForm.ascx.vb:159-167 | SendToFriendForm.ascx.vb:239-246 — before extracting anything, compare `ContactForm.ascx.vb` and `SendToFriendForm.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×1
  • Duplicated block (7 lines × 4) EditProperty.ascx.vb:733 — EditProperty.ascx.vb:733-739 | EditProperty.ascx.vb:756-762 | EditProperty.ascx.vb:790-797 | EditProperty.ascx.vb:822-828 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×1
  • Duplicated block (6 lines × 5) EditContactFields.ascx.vb:224 — EditContactFields.ascx.vb:224-229 | EditCustomFields.ascx.vb:224-229 | EditLayoutSettings.ascx.vb:1148-1153 | EditPropertyTypes.ascx.vb:297-302 | EditReviewFields.ascx.vb:224-229 — before extracting anything, compare `EditContactFields.ascx.vb` and `EditCustomFields.ascx.vb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (36 lines × 2) · ×1
  • Duplicated block (36 lines × 2) EditContactFields.ascx.vb:265 — EditContactFields.ascx.vb:265-300 | EditReviewFields.ascx.vb:265-300 — before extracting anything, compare `EditContactFields.ascx.vb` and `EditReviewFields.ascx.vb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7 lines × 9) · ×1
  • Duplicated block (7 lines × 9) CommentForm.ascx.vb:198 — CommentForm.ascx.vb:198-204 | ContactForm.ascx.vb:184-190 | EditProperty.ascx.vb:73-79 | Export.ascx.vb:171-177 | PdfRender.ascx.vb:122-128 | ReviewForm.ascx.vb:45-51 | Rss.ascx.vb:156-162 | SendToFriendForm.ascx.vb:101-107 | Xml.ascx.vb:165-171 — before extracting anything, compare `ContactForm.ascx.vb` and `SendToFriendForm.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `PdfRender.ascx.vb:137` calls `Page_Init` and `Export.ascx.vb:185` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) Export.ascx.vb:64 — Export.ascx.vb:64-68 | Rss.ascx.vb:62-66 | Xml.ascx.vb:62-66 — before extracting anything, compare `Export.ascx.vb` and `Rss.ascx.vb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 108 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (36 lines × 3) · ×1
  • Duplicated block (36 lines × 3) LandingPage.ascx.vb:327 — LandingPage.ascx.vb:327-362 | Search.ascx.vb:257-292 | SearchSmall.ascx.vb:276-311 — before extracting anything, compare `LandingPage.ascx.vb` and `Search.ascx.vb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: UploadPhotoHTML5 (LCOM4 4) Controls/UploadPhotoHTML5.ascx.vb:23 — UploadPhotoHTML5's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity Includes/plaxo_cb.html:1 — `https://www.plaxo.com/ab_chooser/abc_comm.jsdyn` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 5 such include(s) across the repository's markup.
Minor — 118 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×87
  • Orphaned file LandingPage.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file EditProperty.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Search.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ViewType.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file EditLayoutSettings.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Entities/Constants.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Latest.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file EditCustomField.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file LatestOptions.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ContactForm.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file CommentForm.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Providers/DataProviders/SqlDataProvider/SqlDataProvider.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Default.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file EditLayoutFiles.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file EditPermissions.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file EditProperties.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Controls/UploadPhotoHTML5.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ReviewForm.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Entities/Property/PropertyController.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ChangeTemplate.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file ViewProperty.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file SendToFriendForm.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Entities/WebControls/PagingControl.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file SearchSmallOptions.ascx.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Entities/Reminders/ReminderJob.vb:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 62 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D24 · Comment Value · redundant comment · ×9
  • redundant comment ChangeTemplate.ascx.vb:110 — "- Delete Custom Fields" repeats the code it sits on: 3 of its 3 words (delete, custom, fields) are already in `Dim objCustomFieldsToDelete As List(Of CustomFieldInfo) = objCustomFieldController.List(Me.ModuleId, False)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment ChangeTemplate.ascx.vb:116 — "- Delete Property Types" repeats the code it sits on: 3 of its 3 words (delete, property, types) are already in `Dim objPropertyTypesToDelete As List(Of PropertyTypeInfo) = objPropertyTypeController.List(Me.ModuleId, False)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Entities/Layout/LayoutController.vb:4870 — "field.EndsWith("link") Then" repeats the code it sits on: 3 of its 3 words (field, ends, link) are already in `If fieldNameEndsWithLink = True Then 'field.EndsWith("link") Then`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Entities/Layout/LayoutController.vb:5028 — "field.EndsWith("link") Then" repeats the code it sits on: 3 of its 3 words (field, ends, link) are already in `If fieldNameEndsWithLink = True Then 'field.EndsWith("link") Then`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Entities/Layout/LayoutController.vb:5262 — "field.EndsWith("link") Then" repeats the code it sits on: 3 of its 3 words (field, ends, link) are already in `If fieldNameEndsWithLink = True Then 'field.EndsWith("link") Then`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Entities/Templates/TemplateWriter.vb:59 — "Create Manifest Document" repeats the code it sits on: 3 of its 3 words (create, manifest, document) are already in `Dim xmlManifest As New XmlDocument`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Entities/Templates/TemplateWriter.vb:71 — "Custom Fields Element" repeats the code it sits on: 3 of its 3 words (custom, fields, element) are already in `Dim nodeCustomFields As XmlNode = xmlManifest.CreateElement("CustomFields")`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Entities/Templates/TemplateWriter.vb:206 — "Open File Stream" repeats the code it sits on: 3 of its 3 words (open, file, stream) are already in `Dim fs As FileStream = File.OpenRead(filePath)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment Entities/Templates/TemplateWriter.vb:214 — "Create Zip Entry" repeats the code it sits on: 3 of its 3 words (create, zip, entry) are already in `Dim entry As ZipEntry = New ZipEntry(folder & fileName)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file Entities/Layout/LayoutController.vb:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file SearchSmall.ascx.vb:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file Entities/Property/PropertySettings.vb:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 90 of 90 significant files have no living knowledge — the codebase as a whole is dormant, not 90 separate risks. Counted over 90 of the 158 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
M1 · Documentation (README) · Thin README · ×1
  • Thin README README.md:1 — The root README is 32 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers.
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
M3 · Folder & project structure · No src/ separation · ×1
  • No src/ separation — Production code is mixed at the repository root with everything else the repository holds, so nothing marks which files are the product.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4bbf5b12ca944a4d81fb507c02b7ed0c/history.json --exit-code 0 --source .1artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4bbf5b12ca944a4d81fb507c02b7ed0c/tree.json --exit-code 0 --source .1artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .37artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a1dd20-f05f-7707-af1b-78dc105b95d3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md