Public report — CodeIgniter, published 5 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
246findings with an exact file:lineof 253 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
24/94dimensions across the health lenses56737 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
bcit-ci/CodeIgniter carries serious gaps (49%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.
It is strongest in Architecture (100%) — the structure is clean and changes stay contained.
The area that most needs attention is Maturity (45%) — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent. Readiness (46%) is the next concern — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade.
Leadership focus, highest impact first: Record significant decisions one document per decision (Architecture documentation); SAST step to CI running what this repository's stack ships (Security & performance tooling); Stamp a version in your build/package manifest (e.g. csproj <Version> (Release Hygiene).
For scale: Medium (~56,737 production lines); rebuilding it from scratch would take roughly ~0.4 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Architecture foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
AC6 · Low contrast colour pair in CSS (1.5:1) user_guide_src/source/_themes/sphinx_rtd_theme/static/css/theme.css
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.7× (at 49% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.4 person-years of build effort (about ~€61,000 to rebuild). Its weakest lens is Maturity at 45% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.0) — standard service × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with DB_query_builder.php, Email.php, DB_driver.php.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Value concentrated against a weak lens · High · Value at risk
This is a Medium asset (~0.4 person-years to rebuild), and its weakest lens is Maturity at 45%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Maturity first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form). The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
A velocity tax on every change · Medium · Economics
The code-quality signals (complexity, duplication, cohesion) average 6.2/10, which acts as a tax on every change in the weaker areas: modifications there plausibly cost on the order of 5–10% more than in clean code, and the tax compounds as the codebase grows. (A modelled estimate, not a measured fact.)
Evidence: D1/D2/D4 code quality: averaging 6.2/10 across the code-quality signals actually measured
→ Pay it down where churn is highest — the hotspots — not everywhere; that's where the tax is actually paid.
At a glance — Code Health · 70% · Adequate · gated by D2
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2021 — Injection
37
Medium
Roadmap
First, establish a central repository for architectural decisions to capture context and consequences, and immediately introduce static analysis in your CI pipeline to prevent security regressions. Next, enforce release hygiene by stamping versions in your build manifests to ensure all builds are traceable. Then, improve the root README with a clear quick-start section to help newcomers. Finally, address the three largest orphaned files to improve knowledge freshness.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with DB_query_builder.php, Email.php, DB_driver.php.
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Add an explicit build/compile step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is compiled before merge.
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 23 of 24 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 1 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.4 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 24 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 246 of 253 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A clean result is "no unlabelled native control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (2): D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
+ 38 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 CI_Form_validation._execute (cyclomatic 47) finding(s) in Cyclomatic Complexity — start with Form_validation.php. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CI_Pagination.create_links (cyclomatic 47) finding(s) in Cyclomatic Complexity — start with Pagination.php. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CI_Image_lib.initialize (cyclomatic 34) finding(s) in Cyclomatic Complexity — start with Image_lib.php. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 83 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 CI_Form_validation._execute (cognitive 111) finding(s) in Cognitive Complexity — start with Form_validation.php. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CI_Pagination.create_links (cognitive 70) finding(s) in Cognitive Complexity — start with Pagination.php. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 CI_Input.ip_address (cognitive 68) finding(s) in Cognitive Complexity — start with Input.php. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.5 / 10Exemplary✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
Medium: tainted-filename · ×35system/core/Output.php:588detected by semgrep finding
Low: plaintext-http-link · ×2user_guide_src/source/_themes/sphinx_rtd_theme/footer.html:31detected by semgrep finding
What to do
Resolve the 35 Medium finding(s) in Static Analysis (SAST) — start with layout_old.html (10), Output.php (9), layout.html (6). — One of this dimension's main actionable groups (35 warning-level).
Resolve the 2 Low finding(s) in Static Analysis (SAST) — start with footer.html, layout_old.html. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
164 of 164 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is system/database/DB_query_builder.php.
Largest orphaned file · ×3system/database/DB_query_builder.php
Dormant codebase
What to do
Resolve the 3 Largest orphaned file finding(s) in Knowledge Freshness — start with DB_query_builder.php, Email.php, DB_driver.php. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.
No strong hidden change-coupling between production files.
✓ On the Gold path — maintain.
Detailed fixes: d35_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Do you agree with this assessment?
AC2 · Forms & labels6.3 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — searchbox.html:4
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Do you agree with this assessment?
AC3 · Page structure4.3 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×25) — index.html:2, index.html:2, index.html:2, …
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
`.rst-versions .rst-current-version.rst-out-of-date` sets color: #fff on background-color: #E74C3C — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — badge_only.css:1
`select[disabled],textarea[disabled],input[readonly],select[readonly],textarea[readonly]` sets color: #cad2d3 on background-color: #fff — 1.5:1, below the 4.5:1 WCAG AA minimum for normal text. This is a MINIFIED, build-generated sheet — editing the literal here is undone by the next vendor drop or rebuild, so override the rule in your own stylesheet (or fix it upstream / in the source the bundle is built from). — theme.css:4
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Do you agree with this assessment?
AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge.
What to do
Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Add a 'Testing' section to the root README — how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no `NNNN-title.md` documents and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/PlantUML/Mermaid diagram or architecture.md — the high-level shape isn't documented.
What to do
Record significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Do you agree with this assessment?
P1 · CI/CD gates8.0 / 10Strong✓ 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.
A CI pipeline exists but no build/compile step was matched — changes may merge without being compiled. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
Add an explicit build/compile step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is compiled before merge.
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 phpstan or psalm (or `semgrep --config=auto`, which runs on any language) as a CI step.
What to do
Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — 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.
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.
What to do
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 70 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~8747 lines of test source are present (.php) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (composer.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D19 Documentation Quality — LLM evaluation failed
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.php, .py) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
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 (composer.json — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
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.
D38 OSV Dependency Vulnerabilities — No supported non-.NET dependency lockfile found outside build output (npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven pom.xml, Gradle lockfiles, Python requirements.txt/poetry.lock/Pipfile.lock/pdm.lock, PHP composer.lock, Ruby Gemfile.lock, Elixir mix.lock, Dart pubspec.lock, Swift Package.resolved); nothing for OSV to scan. A NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .php, .py, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.php) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this check looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
GD1 Unfinished & placeholder code — no source files
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
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
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — `vendor/bin/phpunit --coverage-clover coverage.xml`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
Appendix A — Findings (grouped)
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.
Medium: tainted-filename system/core/Output.php:588— File name based on user input risks server-side request forgery.
Medium: tainted-filename system/core/Output.php:637— File name based on user input risks server-side request forgery.
Medium: tainted-filename system/core/Output.php:642— File name based on user input risks server-side request forgery.
Medium: tainted-filename system/core/Output.php:682— File name based on user input risks server-side request forgery.
Medium: tainted-filename system/core/Output.php:689— File name based on user input risks server-side request forgery.
Medium: tainted-filename system/core/Output.php:703— File name based on user input risks server-side request forgery.
Medium: tainted-filename system/core/Output.php:709— File name based on user input risks server-side request forgery.
Medium: tainted-filename system/core/Output.php:771— File name based on user input risks server-side request forgery.
Medium: tainted-sql-string system/core/Output.php:773— User data flows into this manually-constructed SQL string. User data can be safely inserted into SQL strings using prepared statements or an object-relational mapper (ORM). Manually-constructed SQL strings is a possible indicator of SQL injection, which could let an attacker steal or manipulate data from the database. Instead, use prepared statements (`$mysqli->prepare("INSERT INTO test(id, label) VALUES (?, ?)");`) or a safe library.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/breadcrumbs.html:3— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/breadcrumbs.html:5— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/breadcrumbs.html:14— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/footer.html:5— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/footer.html:8— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/footer.html:19— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/layout.html:88— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/layout.html:112— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-script-tag user_guide_src/source/_themes/sphinx_rtd_theme/layout.html:136— Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the rendered page, consider placing it in the HTML portion (outside of a script tag). Alternatively, emit the value into a data attribute or a JSON block in the HTML and read it from script by element id, so the value is never parsed as JavaScript source. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-script-tag user_guide_src/source/_themes/sphinx_rtd_theme/layout.html:137— Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the rendered page, consider placing it in the HTML portion (outside of a script tag). Alternatively, emit the value into a data attribute or a JSON block in the HTML and read it from script by element id, so the value is never parsed as JavaScript source. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-script-tag user_guide_src/source/_themes/sphinx_rtd_theme/layout.html:139— Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the rendered page, consider placing it in the HTML portion (outside of a script tag). Alternatively, emit the value into a data attribute or a JSON block in the HTML and read it from script by element id, so the value is never parsed as JavaScript source. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-script-tag user_guide_src/source/_themes/sphinx_rtd_theme/layout.html:140— Detected a template variable used in a script tag. Although template variables are HTML escaped, HTML escaping does not always prevent cross-site scripting (XSS) attacks when used directly in JavaScript. If you need this data on the rendered page, consider placing it in the HTML portion (outside of a script tag). Alternatively, emit the value into a data attribute or a JSON block in the HTML and read it from script by element id, so the value is never parsed as JavaScript source. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/layout_old.html:33— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: unquoted-attribute-var user_guide_src/source/_themes/sphinx_rtd_theme/layout_old.html:34— Detected a unquoted template variable as an attribute. If unquoted, a malicious actor could inject custom JavaScript handlers. To fix this, add quotes around the template expression, like this: "{{ expr }}". This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/layout_old.html:38— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Medium: var-in-href user_guide_src/source/_themes/sphinx_rtd_theme/layout_old.html:41— Detected a template variable used in an anchor tag with the 'href' attribute. This allows a malicious actor to input the 'javascript:' URI and is subject to cross- site scripting (XSS) attacks. Emit the link through your template layer's URL construction: a helper that percent-encodes the value and rejects any scheme other than http/https, rather than interpolating it raw. Where the template engine is a third-party generator you do not control, validate the value before it reaches the template. You may also consider setting the Content Security Policy (CSP) header. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Duplicated block (13 lines × 2) system/database/DB_query_builder.php:1577— system/database/DB_query_builder.php:1577-1589 | system/database/DB_query_builder.php:1994-2006 — 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) system/database/DB_query_builder.php:2124— system/database/DB_query_builder.php:2124-2136 | system/database/DB_query_builder.php:2157-2169 — 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 `system/database/DB_query_builder.php:2124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) system/database/drivers/pdo/subdrivers/pdo_ibm_driver.php:84— system/database/drivers/pdo/subdrivers/pdo_ibm_driver.php:84-96 | system/database/drivers/pdo/subdrivers/pdo_odbc_driver.php:116-129 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_ibm_driver.php:84` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) system/database/drivers/pdo/subdrivers/pdo_sqlite_driver.php:158— system/database/drivers/pdo/subdrivers/pdo_sqlite_driver.php:158-170 | system/database/drivers/sqlite3/sqlite3_driver.php:260-272 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_sqlite_driver.php:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) system/libraries/Image_lib.php:1079— system/libraries/Image_lib.php:1079-1091 | system/libraries/Image_lib.php:1099-1111 — 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 `system/libraries/Image_lib.php:1079` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) system/libraries/Profiler.php:488— system/libraries/Profiler.php:488-500 | system/libraries/Profiler.php:526-538 — 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) system/libraries/Xmlrpc.php:972— system/libraries/Xmlrpc.php:972-984 | system/libraries/Xmlrpc.php:1611-1623 — 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 `system/libraries/Xmlrpc.php:972` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) system/database/DB_query_builder.php:482— system/database/DB_query_builder.php:482-492 | system/database/DB_query_builder.php:499-509 — 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 `system/database/DB_query_builder.php:482` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) system/database/DB_result.php:133— system/database/DB_result.php:133-143 | system/database/drivers/pdo/pdo_result.php:61-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/DB_result.php:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) system/database/drivers/ibase/ibase_forge.php:151— system/database/drivers/ibase/ibase_forge.php:151-161 | system/database/drivers/pdo/subdrivers/pdo_firebird_forge.php:137-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/ibase/ibase_forge.php:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:332— system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:332-342 | system/database/drivers/postgre/postgre_driver.php:540-550 — 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 (11 lines × 2) system/database/drivers/pdo/subdrivers/pdo_sqlite_forge.php:133— system/database/drivers/pdo/subdrivers/pdo_sqlite_forge.php:133-143 | system/database/drivers/sqlite3/sqlite3_forge.php:119-129 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_sqlite_forge.php:133` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) system/libraries/Email.php:1018— system/libraries/Email.php:1018-1028 | system/libraries/Form_validation.php:1243-1253 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `system/libraries/Email.php:1018` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) system/libraries/Encryption.php:248— system/libraries/Encryption.php:248-258 | system/libraries/Encryption.php:299-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. Read the line range as the matched WINDOW rather than a finished unit: at `system/libraries/Encryption.php:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) system/core/Log.php:223— system/core/Log.php:223-232 | system/core/Output.php:624-633 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Duplicated block (10 lines × 2) system/database/drivers/cubrid/cubrid_forge.php:114— system/database/drivers/cubrid/cubrid_forge.php:114-123 | system/database/drivers/pdo/subdrivers/pdo_cubrid_forge.php:114-123 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/cubrid/cubrid_forge.php:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:139— system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:139-148 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:163-172 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:139` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:123— system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:123-132 | system/database/drivers/postgre/postgre_forge.php:111-120 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:123` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) system/database/drivers/pdo/subdrivers/pdo_sqlite_driver.php:134— system/database/drivers/pdo/subdrivers/pdo_sqlite_driver.php:134-143 | system/database/drivers/sqlite3/sqlite3_driver.php:236-245 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_sqlite_driver.php:134` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) system/libraries/Xmlrpc.php:988— system/libraries/Xmlrpc.php:988-997 | system/libraries/Xmlrpc.php:1628-1637 — 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 `system/libraries/Xmlrpc.php:988` 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 (10 lines × 2) system/libraries/Zip.php:210— system/libraries/Zip.php:210-219 | system/libraries/Zip.php:292-301 — 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 `system/libraries/Zip.php:210` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) system/database/drivers/oci8/oci8_driver.php:447— system/database/drivers/oci8/oci8_driver.php:447-458 | system/database/drivers/pdo/subdrivers/pdo_oci_driver.php:242-253 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 2) system/database/drivers/oci8/oci8_forge.php:104— system/database/drivers/oci8/oci8_forge.php:104-115 | system/database/drivers/pdo/subdrivers/pdo_oci_forge.php:97-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:272— system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:272-283 | system/database/drivers/postgre/postgre_driver.php:430-441 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:301— system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:301-312 | system/database/drivers/sqlsrv/sqlsrv_driver.php:463-474 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) system/libraries/Profiler.php:320— system/libraries/Profiler.php:320-331 | system/libraries/Profiler.php:372-383 — 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 `system/libraries/Profiler.php:320` 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) system/core/Loader.php:420— system/core/Loader.php:420-429 | system/core/Loader.php:452-460 — 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 (9 lines × 2) system/core/Output.php:574— system/core/Output.php:574-582 | system/core/Output.php:756-764 — 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 `system/core/Output.php:574` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) system/database/DB_forge.php:575— system/database/DB_forge.php:575-583 | system/database/DB_forge.php:637-645 — 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 `system/database/DB_forge.php:575` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:156— system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:156-164 | system/database/drivers/postgre/postgre_forge.php:144-152 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:156` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) system/libraries/Form_validation.php:765— system/libraries/Form_validation.php:765-773 | system/libraries/Form_validation.php:784-792 — 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 `system/libraries/Form_validation.php:765` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
TooManyMethods: CI_DB_query_builder system/database/DB_query_builder.php:53— TooManyMethods — 84 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CI_Email system/libraries/Email.php:52— TooManyMethods — 61 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CI_DB_driver system/database/DB_driver.php:54— TooManyMethods — 56 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CI_Form_validation system/libraries/Form_validation.php:50— TooManyMethods — 53 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: database/DB_query_builder.php system/database/DB_query_builder.php:0— FileTooLong — 798 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: CI_DB_query_builder (53-2881). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: libraries/Email.php system/libraries/Email.php:0— FileTooLong — 781 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: CI_Email (52-2418). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: libraries/Xmlrpc.php system/libraries/Xmlrpc.php:0— FileTooLong — 642 significant lines (blank, comment-only and punctuation-only lines excluded). To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: libraries/Image_lib.php system/libraries/Image_lib.php:0— FileTooLong — 624 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: CI_Image_lib (50-1879). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Duplicated block (8 lines × 2) system/database/drivers/ibase/ibase_forge.php:167— system/database/drivers/ibase/ibase_forge.php:167-174 | system/database/drivers/pdo/subdrivers/pdo_firebird_forge.php:153-160 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/ibase/ibase_forge.php:167` 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 (8 lines × 2) system/database/drivers/pdo/subdrivers/pdo_sqlite_forge.php:229— system/database/drivers/pdo/subdrivers/pdo_sqlite_forge.php:229-236 | system/database/drivers/sqlite3/sqlite3_forge.php:216-223 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_sqlite_forge.php:229` 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 (8 lines × 2) system/libraries/Email.php:1290— system/libraries/Email.php:1290-1297 | system/libraries/Email.php:1379-1386 — 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 `system/libraries/Email.php:1290` 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 (8 lines × 2) system/libraries/Image_lib.php:1379— system/libraries/Image_lib.php:1379-1386 | system/libraries/Image_lib.php:1399-1406 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) system/database/drivers/oci8/oci8_driver.php:418— system/database/drivers/oci8/oci8_driver.php:418-432 | system/database/drivers/pdo/subdrivers/pdo_oci_driver.php:213-227 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) system/database/drivers/oci8/oci8_forge.php:200— system/database/drivers/oci8/oci8_forge.php:200-214 | system/database/drivers/pdo/subdrivers/pdo_oci_forge.php:191-205 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/oci8/oci8_forge.php:200` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) system/libraries/Email.php:491— system/libraries/Email.php:491-505 | system/libraries/Email.php:534-548 — 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 (7 lines × 3) system/database/DB_query_builder.php:2052— system/database/DB_query_builder.php:2052-2058 | system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:345-351 | system/database/drivers/postgre/postgre_driver.php:553-559 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/DB_query_builder.php:2052` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 3) system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:163— system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:163-169 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:187-193 | system/database/drivers/sqlsrv/sqlsrv_driver.php:293-299 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:163` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) system/database/drivers/pdo/subdrivers/pdo_firebird_forge.php:147— system/database/drivers/pdo/subdrivers/pdo_firebird_forge.php:147-153 | system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:134-140 | system/database/drivers/postgre/postgre_forge.php:122-128 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_firebird_forge.php:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) system/database/DB_driver.php:937— system/database/DB_driver.php:937-955 | system/database/drivers/odbc/odbc_driver.php:158-176 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/DB_driver.php:937` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) system/libraries/Form_validation.php:966— system/libraries/Form_validation.php:966-984 | system/libraries/Form_validation.php:1009-1027 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 3) system/database/drivers/ibase/ibase_forge.php:221— system/database/drivers/ibase/ibase_forge.php:221-234 | system/database/drivers/pdo/subdrivers/pdo_4d_forge.php:157-170 | system/database/drivers/pdo/subdrivers/pdo_firebird_forge.php:207-220 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 3) system/database/drivers/mysql/mysql_forge.php:151— system/database/drivers/mysql/mysql_forge.php:151-164 | system/database/drivers/mysqli/mysqli_forge.php:153-166 | system/database/drivers/pdo/subdrivers/pdo_mysql_forge.php:165-178 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/mysql/mysql_forge.php:151` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:182— system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:182-195 | system/database/drivers/postgre/postgre_forge.php:170-183 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:182` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 2) system/libraries/Session/drivers/Session_memcached_driver.php:370— system/libraries/Session/drivers/Session_memcached_driver.php:370-383 | system/libraries/Session/drivers/Session_redis_driver.php:453-466 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `system/libraries/Session/drivers/Session_memcached_driver.php:370` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 4) system/database/drivers/ibase/ibase_forge.php:123— system/database/drivers/ibase/ibase_forge.php:123-130 | system/database/drivers/pdo/subdrivers/pdo_firebird_forge.php:109-116 | system/database/drivers/pdo/subdrivers/pdo_sqlite_forge.php:133-140 | system/database/drivers/sqlite3/sqlite3_forge.php:119-126 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/ibase/ibase_forge.php:123` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 4) system/database/drivers/mssql/mssql_forge.php:90— system/database/drivers/mssql/mssql_forge.php:90-97 | system/database/drivers/pdo/subdrivers/pdo_dblib_forge.php:88-95 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_forge.php:88-95 | system/database/drivers/sqlsrv/sqlsrv_forge.php:88-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
CI_Form_validation._execute (cyclomatic 47) system/libraries/Form_validation.php:627— CI_Form_validation._execute has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Pagination.create_links (cyclomatic 47) system/libraries/Pagination.php:395— CI_Pagination.create_links has cyclomatic complexity 47 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Image_lib.initialize (cyclomatic 34) system/libraries/Image_lib.php:461— CI_Image_lib.initialize has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Upload.do_upload (cyclomatic 34) system/libraries/Upload.php:375— CI_Upload.do_upload has cyclomatic complexity 34 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
XML_RPC_Message.closing_tag (cyclomatic 34) system/libraries/Xmlrpc.php:1381— XML_RPC_Message.closing_tag has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_driver.protect_identifiers (cyclomatic 32) system/database/DB_driver.php:1763— CI_DB_driver.protect_identifiers has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_mysqli_driver.db_connect (cyclomatic 31) system/database/drivers/mysqli/mysqli_driver.php:118— CI_DB_mysqli_driver.db_connect has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DB.DB (cyclomatic 30) system/database/DB.php:50— DB.DB has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Input.set_cookie (cyclomatic 28) system/core/Input.php:307— CI_Input.set_cookie has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Calendar.generate (cyclomatic 28) system/libraries/Calendar.php:180— CI_Calendar.generate has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XML_RPC_Message.open_tag (cyclomatic 27) system/libraries/Xmlrpc.php:1280— XML_RPC_Message.open_tag has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
CI_DB_driver.query (cyclomatic 26) system/database/DB_driver.php:575— CI_DB_driver.query has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Table.generate (cyclomatic 25) system/libraries/Table.php:292— CI_Table.generate has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Loader.model (cyclomatic 24) system/core/Loader.php:242— CI_Loader.model has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Session.__construct (cyclomatic 24) system/libraries/Session/Session.php:71— CI_Session.__construct has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_forge._process_fields (cyclomatic 23) system/database/DB_forge.php:696— CI_DB_forge._process_fields has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Input.ip_address (cyclomatic 22) system/core/Input.php:405— CI_Input.ip_address has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Lang.load (cyclomatic 21) system/core/Lang.php:89— CI_Lang.load has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Output._display (cyclomatic 21) system/core/Output.php:420— CI_Output._display has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Email._build_message (cyclomatic 21) system/libraries/Email.php:1246— CI_Email._build_message has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_pdo_mysql_driver.db_connect (cyclomatic 20) system/database/drivers/pdo/subdrivers/pdo_mysql_driver.php:124— CI_DB_pdo_mysql_driver.db_connect has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Image_lib.image_reproportion (cyclomatic 20) system/libraries/Image_lib.php:1623— CI_Image_lib.image_reproportion has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Migration.version (cyclomatic 20) system/libraries/Migration.php:197— CI_Migration.version has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Xmlrpcs._execute (cyclomatic 20) system/libraries/Xmlrpcs.php:317— CI_Xmlrpcs._execute has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Hooks._run_hook (cyclomatic 19) system/core/Hooks.php:166— CI_Hooks._run_hook has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_utility.backup (cyclomatic 19) system/database/DB_utility.php:313— CI_DB_utility.backup has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_oci8_driver.__construct (cyclomatic 19) system/database/drivers/oci8/oci8_driver.php:145— CI_DB_oci8_driver.__construct has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Form_validation.set_rules (cyclomatic 19) system/libraries/Form_validation.php:161— CI_Form_validation.set_rules has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Image_lib.text_watermark (cyclomatic 19) system/libraries/Image_lib.php:1267— CI_Image_lib.text_watermark has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CI_Upload._file_mime_type (cyclomatic 19) system/libraries/Upload.php:1215— CI_Upload._file_mime_type has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Loader._ci_load (cyclomatic 18) system/core/Loader.php:888— CI_Loader._ci_load has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Session._configure (cyclomatic 18) system/libraries/Session/Session.php:280— CI_Session._configure has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CI_Typography.auto_typography (cyclomatic 18) system/libraries/Typography.php:109— CI_Typography.auto_typography has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_mysql_utility._backup (cyclomatic 17) system/database/drivers/mysql/mysql_utility.php:79— CI_DB_mysql_utility._backup has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_mysqli_utility._backup (cyclomatic 17) system/database/drivers/mysqli/mysqli_utility.php:81— CI_DB_mysqli_utility._backup has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_pdo_sqlsrv_driver.__construct (cyclomatic 17) system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:92— CI_DB_pdo_sqlsrv_driver.__construct has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Form_validation.run (cyclomatic 17) system/libraries/Form_validation.php:415— CI_Form_validation.run has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_Session._ci_load_classes (cyclomatic 17) system/libraries/Session/Session.php:206— CI_Session._ci_load_classes has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XML_RPC_Message.parseResponse (cyclomatic 17) system/libraries/Xmlrpc.php:1120— XML_RPC_Message.parseResponse has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CI_Loader._ci_autoloader (cyclomatic 16) system/core/Loader.php:1317— CI_Loader._ci_autoloader has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CI_DB_driver.escape_identifiers (cyclomatic 16) system/database/DB_driver.php:1335— CI_DB_driver.escape_identifiers has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CI_DB_pdo_ibm_driver.__construct (cyclomatic 16) system/database/drivers/pdo/subdrivers/pdo_ibm_driver.php:73— CI_DB_pdo_ibm_driver.__construct has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CI_DB_pdo_odbc_driver.__construct (cyclomatic 16) system/database/drivers/pdo/subdrivers/pdo_odbc_driver.php:105— CI_DB_pdo_odbc_driver.__construct has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
dormant codebase — no living knowledge left to concentrate — All 158 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[0].suggestion | LineNumber: 0 | BytePositionInLine: 1262.
CI_Form_validation._execute (cognitive 111) system/libraries/Form_validation.php:627— CI_Form_validation._execute has cognitive complexity 111 (threshold 15). Drivers by points: if/else 61, ternaries 34, boolean chains 13, loops 3 (nesting depth added 60). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Pagination.create_links (cognitive 70) system/libraries/Pagination.php:395— CI_Pagination.create_links has cognitive complexity 70 (threshold 15). Drivers by points: if/else 46, ternaries 13, boolean chains 9, loops 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Input.ip_address (cognitive 68) system/core/Input.php:405— CI_Input.ip_address has cognitive complexity 68 (threshold 15). Drivers by points: if/else 46, loops 16, ternaries 4, boolean chains 2 (nesting depth added 44). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_driver.protect_identifiers (cognitive 55) system/database/DB_driver.php:1763— CI_DB_driver.protect_identifiers has cognitive complexity 55 (threshold 15). Drivers by points: if/else 35, boolean chains 7, ternaries 7, loops 6 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_mysqli_driver.db_connect (cognitive 54) system/database/drivers/mysqli/mysqli_driver.php:118— CI_DB_mysqli_driver.db_connect has cognitive complexity 54 (threshold 15). Drivers by points: ternaries 26, if/else 20, boolean chains 8 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DB.DB (cognitive 53) system/database/DB.php:50— DB.DB has cognitive complexity 53 (threshold 15). Drivers by points: if/else 33, ternaries 10, loops 6, boolean chains 4 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Table.generate (cognitive 52) system/libraries/Table.php:292— CI_Table.generate has cognitive complexity 52 (threshold 15). Drivers by points: if/else 25, loops 14, ternaries 10, boolean chains 3 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Image_lib.initialize (cognitive 50) system/libraries/Image_lib.php:461— CI_Image_lib.initialize has cognitive complexity 50 (threshold 15). Drivers by points: if/else 32, boolean chains 10, ternaries 6, loops 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Calendar.generate (cognitive 49) system/libraries/Calendar.php:180— CI_Calendar.generate has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 20, if/else 18, boolean chains 6, loops 5 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Upload._file_mime_type (cognitive 41) system/libraries/Upload.php:1215— CI_Upload._file_mime_type has cognitive complexity 41 (threshold 15). Drivers by points: if/else 38, boolean chains 3 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_forge._process_fields (cognitive 40) system/database/DB_forge.php:696— CI_DB_forge._process_fields has cognitive complexity 40 (threshold 15). Drivers by points: if/else 19, ternaries 12, boolean chains 5, match/switch 3, loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Input.set_cookie (cognitive 38) system/core/Input.php:307— CI_Input.set_cookie has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15, ternaries 12, boolean chains 9, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Loader.model (cognitive 37) system/core/Loader.php:242— CI_Loader.model has cognitive complexity 37 (threshold 15). Drivers by points: if/else 29, loops 4, ternaries 3, boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_mysql_utility._backup (cognitive 36) system/database/drivers/mysql/mysql_utility.php:79— CI_DB_mysql_utility._backup has cognitive complexity 36 (threshold 15). Drivers by points: if/else 21, loops 10, ternaries 5 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_mysqli_utility._backup (cognitive 36) system/database/drivers/mysqli/mysqli_utility.php:81— CI_DB_mysqli_utility._backup has cognitive complexity 36 (threshold 15). Drivers by points: if/else 21, loops 10, ternaries 5 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_driver.query (cognitive 35) system/database/DB_driver.php:575— CI_DB_driver.query has cognitive complexity 35 (threshold 15). Drivers by points: if/else 23, boolean chains 7, loops 3, ternaries 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Upload.do_upload (cognitive 35) system/libraries/Upload.php:375— CI_Upload.do_upload has cognitive complexity 35 (threshold 15). Drivers by points: if/else 26, boolean chains 3, loops 2, match/switch 2, ternaries 2 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CI_Email._build_message (cognitive 33) system/libraries/Email.php:1246— CI_Email._build_message has cognitive complexity 33 (threshold 15). Drivers by points: if/else 28, boolean chains 2, ternaries 2, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Xmlrpcs._execute (cognitive 33) system/libraries/Xmlrpcs.php:317— CI_Xmlrpcs._execute has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17, loops 6, boolean chains 5, ternaries 5 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Profiler._compile_queries (cognitive 31) system/libraries/Profiler.php:198— CI_Profiler._compile_queries has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16, loops 13, ternaries 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Session.__construct (cognitive 29) system/libraries/Session/Session.php:71— CI_Session.__construct has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12, ternaries 11, boolean chains 6 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Lang.load (cognitive 28) system/core/Lang.php:89— CI_Lang.load has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17, boolean chains 5, loops 4, ternaries 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Output._display (cognitive 28) system/core/Output.php:420— CI_Output._display has cognitive complexity 28 (threshold 15). Drivers by points: if/else 20, boolean chains 6, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_query_builder._compile_wh (cognitive 28) system/database/DB_query_builder.php:2463— CI_DB_query_builder._compile_wh has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12, ternaries 9, loops 5, boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_utility.backup (cognitive 28) system/database/DB_utility.php:313— CI_DB_utility.backup has cognitive complexity 28 (threshold 15). Drivers by points: if/else 20, boolean chains 3, ternaries 3, loops 2 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Config.load (cognitive 27) system/core/Config.php:127— CI_Config.load has cognitive complexity 27 (threshold 15). Drivers by points: if/else 18, ternaries 5, loops 3, boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Hooks._run_hook (cognitive 27) system/core/Hooks.php:166— CI_Hooks._run_hook has cognitive complexity 27 (threshold 15). Drivers by points: if/else 19, ternaries 5, boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Loader._ci_load (cognitive 27) system/core/Loader.php:888— CI_Loader._ci_load has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15, boolean chains 4, loops 4, ternaries 4 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_mysql_driver.db_connect (cognitive 27) system/database/drivers/pdo/subdrivers/pdo_mysql_driver.php:124— CI_DB_pdo_mysql_driver.db_connect has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15, boolean chains 10, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Form_validation.set_rules (cognitive 27) system/libraries/Form_validation.php:161— CI_Form_validation.set_rules has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12, ternaries 7, boolean chains 4, loops 4 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Migration.version (cognitive 27) system/libraries/Migration.php:197— CI_Migration.version has cognitive complexity 27 (threshold 15). Drivers by points: if/else 22, boolean chains 3, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Upload.initialize (cognitive 27) system/libraries/Upload.php:312— CI_Upload.initialize has cognitive complexity 27 (threshold 15). Drivers by points: if/else 22, loops 4, boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Loader._ci_init_library (cognitive 26) system/core/Loader.php:1217— CI_Loader._ci_init_library has cognitive complexity 26 (threshold 15). Drivers by points: if/else 22, loops 3, ternaries 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Driver_Library.load_driver (cognitive 26) system/libraries/Driver.php:92— CI_Driver_Library.load_driver has cognitive complexity 26 (threshold 15). Drivers by points: if/else 21, loops 5 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Typography.auto_typography (cognitive 26) system/libraries/Typography.php:109— CI_Typography.auto_typography has cognitive complexity 26 (threshold 15). Drivers by points: if/else 21, loops 4, boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Image_lib.image_reproportion (cognitive 25) system/libraries/Image_lib.php:1623— CI_Image_lib.image_reproportion has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, if/else 7, ternaries 6 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_query_builder.update_batch (cognitive 24) system/database/DB_query_builder.php:1967— CI_DB_query_builder.update_batch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12, ternaries 11, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_oci8_driver.__construct (cognitive 24) system/database/drivers/oci8/oci8_driver.php:145— CI_DB_oci8_driver.__construct has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10, boolean chains 7, ternaries 4, loops 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Image_lib.text_watermark (cognitive 24) system/libraries/Image_lib.php:1267— CI_Image_lib.text_watermark has cognitive complexity 24 (threshold 15). Drivers by points: if/else 23, boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CI_Loader.helper (cognitive 23) system/core/Loader.php:598— CI_Loader.helper has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15, loops 5, ternaries 2, boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Router._set_routing (cognitive 23) system/core/Router.php:156— CI_Router._set_routing has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17, boolean chains 3, ternaries 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_ibm_driver.__construct (cognitive 23) system/database/drivers/pdo/subdrivers/pdo_ibm_driver.php:73— CI_DB_pdo_ibm_driver.__construct has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13, ternaries 7, boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_odbc_driver.__construct (cognitive 23) system/database/drivers/pdo/subdrivers/pdo_odbc_driver.php:105— CI_DB_pdo_odbc_driver.__construct has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13, ternaries 7, boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Session._configure (cognitive 23) system/libraries/Session/Session.php:280— CI_Session._configure has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11, boolean chains 9, ternaries 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
XML_RPC_Message.closing_tag (cognitive 23) system/libraries/Xmlrpc.php:1381— XML_RPC_Message.closing_tag has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13, ternaries 8, boolean chains 1, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Form_validation.run (cognitive 22) system/libraries/Form_validation.php:415— CI_Form_validation.run has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13, ternaries 5, boolean chains 2, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Form_validation._reset_data_array (cognitive 22) system/libraries/Form_validation.php:583— CI_Form_validation._reset_data_array has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11, loops 6, ternaries 4, boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Session._ci_load_classes (cognitive 22) system/libraries/Session/Session.php:206— CI_Session._ci_load_classes has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14, boolean chains 5, ternaries 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XML_RPC_Message.parseResponse (cognitive 22) system/libraries/Xmlrpc.php:1120— XML_RPC_Message.parseResponse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16, loops 5, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_query_builder.insert_batch (cognitive 21) system/database/DB_query_builder.php:1558— CI_DB_query_builder.insert_batch has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, ternaries 9, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_informix_driver.__construct (cognitive 21) system/database/drivers/pdo/subdrivers/pdo_informix_driver.php:82— CI_DB_pdo_informix_driver.__construct has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 5, ternaries 5 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_sqlsrv_driver.__construct (cognitive 21) system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:92— CI_DB_pdo_sqlsrv_driver.__construct has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 8, ternaries 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Session_redis_driver.__construct (cognitive 21) system/libraries/Session/drivers/Session_redis_driver.php:115— CI_Session_redis_driver.__construct has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11, if/else 9, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Loader._ci_load_stock_library (cognitive 20) system/core/Loader.php:1130— CI_Loader._ci_load_stock_library has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17, loops 2, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_query_builder._wh (cognitive 20) system/database/DB_query_builder.php:655— CI_DB_query_builder._wh has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, ternaries 6, boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Email.word_wrap (cognitive 20) system/libraries/Email.php:1102— CI_Email.word_wrap has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11, loops 7, ternaries 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Loader._ci_autoloader (cognitive 19) system/core/Loader.php:1317— CI_Loader._ci_autoloader has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12, loops 5, boolean chains 2 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
CI_DB_query_builder.join (cognitive 19) system/database/DB_query_builder.php:527— CI_DB_query_builder.join has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7, loops 5, ternaries 5, boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_mysql_driver.db_connect (cognitive 19) system/database/drivers/mysql/mysql_driver.php:125— CI_DB_mysql_driver.db_connect has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11, ternaries 7, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Security.xss_clean (cognitive 18) system/core/Security.php:377— CI_Security.xss_clean has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, loops 7 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_driver.initialize (cognitive 18) system/database/DB_driver.php:387— CI_DB_driver.initialize has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, loops 7, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_query_builder._compile_select (cognitive 18) system/database/DB_query_builder.php:2390— CI_DB_query_builder._compile_select has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, ternaries 6, loops 3, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_pgsql_forge._alter_table (cognitive 18) system/database/drivers/pdo/subdrivers/pdo_pgsql_forge.php:116— CI_DB_pdo_pgsql_forge._alter_table has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, ternaries 3, boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_sqlsrv_driver._limit (cognitive 18) system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:298— CI_DB_pdo_sqlsrv_driver._limit has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7, if/else 5, boolean chains 3, loops 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_postgre_forge._alter_table (cognitive 18) system/database/drivers/postgre/postgre_forge.php:104— CI_DB_postgre_forge._alter_table has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13, ternaries 3, boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_sqlsrv_driver._limit (cognitive 18) system/database/drivers/sqlsrv/sqlsrv_driver.php:460— CI_DB_sqlsrv_driver._limit has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 7, if/else 5, boolean chains 3, loops 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Encryption._get_params (cognitive 18) system/libraries/Encryption.php:658— CI_Encryption._get_params has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12, ternaries 4, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Trackback.convert_ascii (cognitive 18) system/libraries/Trackback.php:490— CI_Trackback.convert_ascii has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, ternaries 8, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Xmlrpc.values_parsing (cognitive 18) system/libraries/Xmlrpc.php:452— CI_Xmlrpc.values_parsing has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, loops 4, boolean chains 3, ternaries 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Output._write_cache (cognitive 17) system/core/Output.php:558— CI_Output._write_cache has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 2, loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CI_DB_driver.escape_identifiers (cognitive 17) system/database/DB_driver.php:1335— CI_DB_driver.escape_identifiers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, boolean chains 6, loops 3, ternaries 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_forge.create_table (cognitive 17) system/database/DB_forge.php:323— CI_DB_forge.create_table has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, loops 3, ternaries 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_query_builder.delete (cognitive 17) system/database/DB_query_builder.php:2224— CI_DB_query_builder.delete has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8, ternaries 6, loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_mssql_driver._limit (cognitive 17) system/database/drivers/mssql/mssql_driver.php:431— CI_DB_mssql_driver._limit has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7, if/else 4, boolean chains 3, loops 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_dblib_driver._limit (cognitive 17) system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:274— CI_DB_pdo_dblib_driver._limit has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7, if/else 4, boolean chains 3, loops 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Email._send_with_smtp (cognitive 17) system/libraries/Email.php:1924— CI_Email._send_with_smtp has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 3, loops 3 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Image_lib.image_process_gd (cognitive 17) system/libraries/Image_lib.php:753— CI_Image_lib.image_process_gd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CI_Image_lib.image_save_gd (cognitive 17) system/libraries/Image_lib.php:1505— CI_Image_lib.image_save_gd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 16, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CI_Profiler._compile_post (cognitive 17) system/libraries/Profiler.php:341— CI_Profiler._compile_post has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6, boolean chains 5, loops 4, if/else 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Input._fetch_from_array (cognitive 16) system/core/Input.php:125— CI_Input._fetch_from_array has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, loops 4, boolean chains 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_URI._uri_to_assoc (cognitive 16) system/core/URI.php:447— CI_URI._uri_to_assoc has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, loops 3, ternaries 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_mysql_forge._alter_table (cognitive 16) system/database/drivers/mysql/mysql_forge.php:137— CI_DB_mysql_forge._alter_table has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, ternaries 7, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_mysqli_forge._alter_table (cognitive 16) system/database/drivers/mysqli/mysqli_forge.php:139— CI_DB_mysqli_forge._alter_table has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, ternaries 7, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_DB_pdo_mysql_forge._alter_table (cognitive 16) system/database/drivers/pdo/subdrivers/pdo_mysql_forge.php:151— CI_DB_pdo_mysql_forge._alter_table has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8, ternaries 7, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Email._prep_quoted_printable (cognitive 16) system/libraries/Email.php:1476— CI_Email._prep_quoted_printable has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, loops 3, boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Encryption._mcrypt_initialize (cognitive 16) system/libraries/Encryption.php:228— CI_Encryption._mcrypt_initialize has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14, boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Session_files_driver.write (cognitive 16) system/libraries/Session/drivers/Session_files_driver.php:242— CI_Session_files_driver.write has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 3, loops 2, ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CI_Trackback.send (cognitive 16) system/libraries/Trackback.php:118— CI_Trackback.send has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, loops 3, match/switch 2, boolean chains 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Duplicated block (25 lines × 2) system/database/drivers/mysql/mysql_utility.php:83— system/database/drivers/mysql/mysql_utility.php:83-107 | system/database/drivers/mysqli/mysqli_utility.php:85-109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/mysql/mysql_utility.php:83` 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 (23 lines × 2) system/database/drivers/mysql/mysql_utility.php:163— system/database/drivers/mysql/mysql_utility.php:163-185 | system/database/drivers/mysqli/mysqli_utility.php:163-185 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/mysql/mysql_utility.php:163` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:203— system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:203-218 | system/database/drivers/postgre/postgre_driver.php:485-500 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:203` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (14 lines × 4) system/database/drivers/mssql/mssql_forge.php:119— system/database/drivers/mssql/mssql_forge.php:119-132 | system/database/drivers/pdo/subdrivers/pdo_dblib_forge.php:117-130 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_forge.php:117-130 | system/database/drivers/sqlsrv/sqlsrv_forge.php:117-130 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/mssql/mssql_forge.php:119` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (13 lines × 5) system/database/drivers/cubrid/cubrid_forge.php:172— system/database/drivers/cubrid/cubrid_forge.php:172-184 | system/database/drivers/ibase/ibase_forge.php:218-230 | system/database/drivers/pdo/subdrivers/pdo_4d_forge.php:154-166 | system/database/drivers/pdo/subdrivers/pdo_cubrid_forge.php:172-184 | system/database/drivers/pdo/subdrivers/pdo_firebird_forge.php:204-216 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/cubrid/cubrid_forge.php:172` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12 lines × 6) system/database/DB_forge.php:1003— system/database/DB_forge.php:1003-1014 | system/database/drivers/cubrid/cubrid_forge.php:209-220 | system/database/drivers/mysql/mysql_forge.php:221-232 | system/database/drivers/mysqli/mysqli_forge.php:223-234 | system/database/drivers/pdo/subdrivers/pdo_cubrid_forge.php:209-220 | system/database/drivers/pdo/subdrivers/pdo_mysql_forge.php:235-246 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/DB_forge.php:1003` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 4) system/database/drivers/mssql/mssql_driver.php:315— system/database/drivers/mssql/mssql_driver.php:315-326 | system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:203-214 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:227-238 | system/database/drivers/sqlsrv/sqlsrv_driver.php:333-344 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times.
Duplicated block (11 lines × 4) system/database/drivers/mssql/mssql_driver.php:442— system/database/drivers/mssql/mssql_driver.php:442-452 | system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:285-295 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:317-327 | system/database/drivers/sqlsrv/sqlsrv_driver.php:479-489 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/mssql/mssql_driver.php:442` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) system/database/drivers/mysql/mysql_forge.php:104— system/database/drivers/mysql/mysql_forge.php:104-114 | system/database/drivers/mysqli/mysqli_forge.php:106-116 | system/database/drivers/pdo/subdrivers/pdo_mysql_forge.php:118-128 — 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) system/database/DB_query_builder.php:2034— system/database/DB_query_builder.php:2034-2043 | system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:327-336 | system/database/drivers/postgre/postgre_driver.php:535-544 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/DB_query_builder.php:2034` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 13) system/database/drivers/cubrid/cubrid_driver.php:337— system/database/drivers/cubrid/cubrid_driver.php:337-345 | system/database/drivers/mssql/mssql_driver.php:321-329 | system/database/drivers/mysql/mysql_driver.php:423-431 | system/database/drivers/mysqli/mysqli_driver.php:471-479 | system/database/drivers/oci8/oci8_driver.php:434-442 | system/database/drivers/pdo/subdrivers/pdo_cubrid_driver.php:150-158 | system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:209-217 | system/database/drivers/pdo/subdrivers/pdo_mysql_driver.php:320-328 | system/database/drivers/pdo/subdrivers/pdo_oci_driver.php:229-237 | system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:278-286 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:233-241 | system/database/drivers/postgre/postgre_driver.php:436-444 | system/database/drivers/sqlsrv/sqlsrv_driver.php:339-347 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 13 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 13 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/cubrid/cubrid_driver.php:337` 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 × 5) system/database/drivers/cubrid/cubrid_forge.php:141— system/database/drivers/cubrid/cubrid_forge.php:141-149 | system/database/drivers/mysql/mysql_forge.php:181-189 | system/database/drivers/mysqli/mysqli_forge.php:183-191 | system/database/drivers/pdo/subdrivers/pdo_cubrid_forge.php:141-149 | system/database/drivers/pdo/subdrivers/pdo_mysql_forge.php:195-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 5) system/database/drivers/pdo/subdrivers/pdo_4d_driver.php:82— system/database/drivers/pdo/subdrivers/pdo_4d_driver.php:82-89 | system/database/drivers/pdo/subdrivers/pdo_cubrid_driver.php:89-96 | system/database/drivers/pdo/subdrivers/pdo_mysql_driver.php:100-107 | system/database/drivers/pdo/subdrivers/pdo_pgsql_driver.php:91-98 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:94-101 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/pdo/subdrivers/pdo_4d_driver.php:82` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) system/database/drivers/mysql/mysql_forge.php:191— system/database/drivers/mysql/mysql_forge.php:191-198 | system/database/drivers/mysqli/mysqli_forge.php:193-200 | system/database/drivers/pdo/subdrivers/pdo_mysql_forge.php:205-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/mysql/mysql_forge.php:191` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 5) system/database/drivers/cubrid/cubrid_forge.php:199— system/database/drivers/cubrid/cubrid_forge.php:199-205 | system/database/drivers/mysql/mysql_forge.php:211-217 | system/database/drivers/mysqli/mysqli_forge.php:213-219 | system/database/drivers/pdo/subdrivers/pdo_cubrid_forge.php:199-205 | system/database/drivers/pdo/subdrivers/pdo_mysql_forge.php:225-231 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 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 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `system/database/drivers/cubrid/cubrid_forge.php:199` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) system/core/Loader.php:462— system/core/Loader.php:462-468 | system/database/DB.php:164-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `system/core/Loader.php:462` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (6 lines × 3) system/database/drivers/mssql/mssql_driver.php:135— system/database/drivers/mssql/mssql_driver.php:135-140 | system/database/drivers/pdo/subdrivers/pdo_dblib_driver.php:143-148 | system/database/drivers/pdo/subdrivers/pdo_sqlsrv_driver.php:167-172 — 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) system/libraries/Email.php:1124— system/libraries/Email.php:1124-1129 | system/libraries/Typography.php:133-138 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `system/libraries/Email.php:1124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Recommendation — 8 finding(s)
D34 · Knowledge Freshness· Largest orphaned file · ×3
Largest orphaned file system/database/DB_query_builder.php— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file system/libraries/Email.php— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Largest orphaned file system/database/DB_driver.php— One of the largest files with no living knowledge remaining — a reasonable place to start a read-through before the aggregate risk above bites.
Low: plaintext-http-link user_guide_src/source/_themes/sphinx_rtd_theme/footer.html:31— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
Low: plaintext-http-link user_guide_src/source/_themes/sphinx_rtd_theme/layout_old.html:198— This link points to a plaintext HTTP URL. Prefer an encrypted HTTPS URL if possible.
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.php) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
Dormant codebase — 164 of 164 significant files have no living knowledge — the codebase as a whole is dormant, not 164 separate risks. Re-engage owners or document before change.
Coverage not included — suite not readable by the collector — Coverage NOT READ here — but this repository measures it: a coverage step in CI (`phpunit --coverage`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.php), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (Clover XML — `vendor/bin/phpunit --coverage-clover coverage.xml`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 2 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifest (composer.json) was found, but this pass cannot parse it for hygiene, 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 D38 wherever the manifest is OSV-readable.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Terraform, Kubernetes/Helm, CloudFormation); nothing to scan.
trivy: not applicable — No JS/npm manifest or lockfile found outside build output (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
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.
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.
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.
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
—
Run 019fd06f-62f6-7d4c-988b-a6a9a369a1ab · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Warnings: 243 · Recommendations: 8 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 05-08-2026 @ 05:39 UTC.
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.