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

shivammathur/homebrew-php

Measured 17 November 2026, 23:27 UTC, at code version 7c48211

CAI score 61.9out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 1.1 since the last survey

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

A medium codebase: 26,616 lines of product code in 2 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Security and Compliance, 53.7

Findings by how serious they are

36 critical 47 serious 6 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 23:27 UTC

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

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

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

Executive summary

shivammathur/homebrew-php falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 61.9 out of 100 and is rated Adequate, and all 36 of its critical findings are security problems in the build pipeline.

Security and Compliance, at 53.7, is the weakest lens and counts most in the score. The best first step is fixing the eight pipeline tools referenced by a changeable name, worth about 5.5 points. Stopping the three pipeline steps that hand secrets to unpinned tools comes next, worth about 2.7 points. Raising Security and Compliance to 70 would lift the score to about 67.5.

Thirty-three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three secrets can leak from the build pipeline. Pinning each tool to an exact version and limiting each secret to its own step would close both risks.

The product code is 26,616 lines, about €30,000 to rebuild.

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

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

If Security and Compliance rose from 53.7 to 70, the lowest score rated Strong, the score would rise from 61.9 to about 67.5.

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

These 2 critical or serious findings were in the previous survey, on 5 November 2026, and are gone from this one.

  • Code Duplication · Duplicated block (20 lines × 4) Formula/php@5.6-debug-zts.rb
  • Code Duplication · Duplicated block (19 lines × 12) Formula/php@7.4-debug.rb
Rebuild cost: about €30,000 · Estimate
Cost to rebuild€9,800 to €49,000, for 164 to 519 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 26,616 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED.
Raises the score by about 5.5 points · Low effort · Static Analysis (SAST)
2
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 2.7 points · Low effort · Static Analysis (SAST)
3
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED.
Raises the score by about 2.0 points · Low effort · Supply-chain Provenance & Signing

Diagnosis: what the measurements show together

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

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

Architecture: which parts of the code depend on which

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

2 modules, with 1 dependency between them. Every module uses only modules listed above it, so there are no loops.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 (global)2 Scripts
1 (global)
2 Scripts1
Uses a module listed above itPart of a loopThe module itself
1 (global)2 Scripts(global)1Scripts21

At a glance — Code Health · 62.6 · Adequate · gated by D4, X5 ·

At a glance — Architecture · 100.0 · Exemplary ·

At a glance — Maturity · 65.7 · Adequate · gated by M2 ·

At a glance — Readiness · 80.8 · Strong ·

At a glance — Security · 53.7 · Adequate · gated by D29, D36 ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection36High / Critical
A03:2025 — Software Supply Chain Failures6Medium

Roadmap

Top priorities: Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED; Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

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

Do thisHelpsEffortDimension
Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED.+5.5 ptsLowStatic Analysis (SAST)
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED.+2.7 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED.+2.0 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED.+2.0 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+2.0 ptsLowSupply-chain Provenance & Signing
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.+3.6 ptsMediumNullable reference types
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+2.8 ptsMediumArchitecture documentation
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.+1.2 ptsMediumDocumentation (README)

File quality

Per-file score 0–10 — a quality signature. Of 26 files carrying findings, judged against the Production bar: 4% slop · 73% mixed · 23% near-clean.

FileScoreBandWorst signal
REDACTED2.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
Formula/php-debug-zts.rb7.0MixedCyclomatic Complexity: PhpDebugZts.install (cyclomatic 20)
Formula/php@5.6-debug-zts.rb7.0MixedCode Duplication: Near-duplicate member family (52 members, 41 shared lines)
Formula/php@7.4-debug.rb7.2MixedCode Duplication: Duplicated block (122–125 lines × 12)
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED
Formula/php-debug.rb7.4MixedCyclomatic Complexity: PhpDebug.install (cyclomatic 20)
Formula/php@7.0-debug-zts.rb7.4MixedCode Duplication: Duplicated block (99–106 lines × 16)
Formula/php@7.4-debug-zts.rb7.4MixedCode Duplication: Duplicated block (95–97 lines × 6)
Formula/php@8.2-debug-zts.rb7.4MixedCode Duplication: Duplicated block (93–95 lines × 4)
Formula/php-zts.rb7.8MixedCyclomatic Complexity: PhpZts.install (cyclomatic 20)
Formula/php.rb7.8MixedCyclomatic Complexity: Php.install (cyclomatic 20)
Formula/php@7.3-debug-zts.rb7.8MixedCode Duplication: Duplicated block (32 lines × 4)
REDACTED7.9MixedSupply-chain Provenance & Signing: REDACTED

How the grades work

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

Critical — 36

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

Serious — 47

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

Minor — 6

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

Could not be resolved — 6

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

Methodology & how to trust this report

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

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 30 dimensions across the health lenses
D1D2D3D4D5D13D15D17D28D29D34D35D36D37AX10AX3AX4GD1IC1M1M2M3M4P1P3P4X12X19X27X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 83 of 89 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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

Every finding is locatable in findings.md. Run 01a1ebd6-89fd-74fa-9944-88247b5841c1.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rb) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rb) 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.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (11 contributor(s) across 13364 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 10 hold 0.9% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. This repository is a Homebrew tap: it publishes formulae (Formula/autoconf@2.69.rb) — build recipes that `brew install` resolves by name. No consumer links against a formula, so the tap exposes no code API and there is no surface for API consistency to be judged over.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `Scripts/pgo_script.php` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file or a .NET image on a Dockerfile FROM line, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile on a non-.NET image) is simply not read here yet.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes Homebrew formulae (build recipes for software other people install and run) and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.

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

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • 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.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".

Dimensions

D1 · Cyclomatic Complexity9.4 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

4 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was PhpDebugZts.install at 20.

PhpDebugZts.install (cyclomatic 20)Formula/php-debug-zts.rb:90
PhpDebug.install (cyclomatic 20)Formula/php-debug.rb:90
PhpZts.install (cyclomatic 20)Formula/php-zts.rb:90
Php.install (cyclomatic 20)Formula/php.rb:91

What to do

  1. Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with PhpDebugZts.install (cyclomatic 20), PhpDebug.install (cyclomatic 20), PhpZts.install (cyclomatic 20). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D2 · Cognitive Complexity8.8 / 10Strong✓ Tool-verified

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

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

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

4 method(s) exceeded the cognitive complexity threshold of 15; the worst was PhpDebugZts.install at 35.

PhpDebugZts.install (cognitive 35)Formula/php-debug-zts.rb:90
PhpDebug.install (cognitive 35)Formula/php-debug.rb:90
PhpZts.install (cognitive 35)Formula/php-zts.rb:90
Php.install (cognitive 35)Formula/php.rb:91

What to do

  1. Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with PhpDebugZts.install (cognitive 35), PhpDebug.install (cognitive 35), PhpZts.install (cognitive 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes10.0 / 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.

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

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication0.0 / 10Critical✓ Tool-verified

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

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

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

34 duplicated block group(s) detected. 34.0 % of the production lines (9,053 of 26,616) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (21 lines × 10) · ×2Formula/php-debug-zts.rb:316
Near-duplicate member family (52 members, 41 shared lines)Formula/php@5.6-debug-zts.rb:73
Near-duplicate member family (36 members, 98 shared lines)Formula/php-debug-zts.rb:92
Duplicated block (99–106 lines × 16)Formula/php@7.0-debug-zts.rb:141
Duplicated block (125–128 lines × 4)Formula/php@5.6-debug-zts.rb:146

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

What to do

  1. Resolve the 2 Duplicated block (21 lines × 10) finding(s) in Code Duplication — start with php-debug-zts.rb, php@8.2-debug-zts.rb. — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 Near-duplicate member family (52 members, 41 shared lines) finding(s) in Code Duplication — start with php@5.6-debug-zts.rb. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Near-duplicate member family (36 members, 98 shared lines) finding(s) in Code Duplication — start with php-debug-zts.rb. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

2 production modules (source-import), 0 dependency cycle(s), 0 unstable depended-on module(s). No manifest declares this repository's modules, so the modules are its top-level source directories and the edges the imports between them; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

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

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

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

0 deducted task-comment markers across 26616 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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

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

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

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

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

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

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

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

36 finding(s): 0 critical, 36 high, 0 medium, 0 low. 25 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `Scripts/pgo_script.php` (line 41, line 237, line 238, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (8 issue-level).
  2. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  3. No action in Static Analysis (SAST) — all 25 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (25 issue-level, 0 of them charged here).

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

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

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

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

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

Every significant source file has living knowledge — recently and meaningfully worked.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (.github/SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

Frontend & cross-cutting dimensions

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

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

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

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

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

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

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

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

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

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

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

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

Other · Code Health — Unreviewed-generation residue in this repository's Ruby: methods whose whole body still raises NotImplementedError where nothing overrides them, or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Ruby: methods that only raise NotImplementedError or a "not implemented" error where nothing overrides them, methods that take inputs and return a constant or do nothing, dead `if false` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

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

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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.

P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a walk over a `Hash` or `Set` (`each`, `each_pair`, `map`, `for … in` and the other block walks) leaves it alone — Ruby refuses `rehash`, `replace`, `compare_by_identity` and `transform_keys!` on a Hash, and `reset`, `replace`, `compare_by_identity` and `map!` on a Set, while it is being iterated: the call raises `RuntimeError` at once and the remaining entries are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 58 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.

What to do

  • Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.

Reference — by lens

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

LensScoreRatingImpact
Code Health62.6Adequate — gated by D4, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture100.0ExemplaryStrongest area.
Maturity65.7Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness80.8StrongSolid.
Security53.7Adequate — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
  • P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 82 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's Ruby imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads. PHP builds its object graph per request and shares none of it between requests.
  • 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 — no class or module declares an abstract method
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository draws no route and defines no request handler (no Rails routes.draw or controller, no Sinatra, Roda or Grape application, no Hanami action). Access control is therefore N/A here — a gem is authorized by the application that mounts it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (an ActiveRecord model, Sequel, pg, mysql2, Mongo) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (ActiveRecord, Sequel, pg, mysql2, mongo, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — ~0 lines of test source are present (.rb) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — 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 — no .rb test runner
  • D12 Dependency Hygiene — Not applicable — this repository is a Homebrew tap: it publishes formulae (Formula/autoconf@2.69.rb), build recipes that `brew install` resolves by name, and declares no package manifest. A formula's `depends_on` names other formulae that brew installs and upgrades beside it, so there is no dependency this repository pins whose hygiene could be assessed.
  • D14 License Compliance — N/A — this repository is a Homebrew tap: it publishes formulae (Formula/autoconf@2.69.rb), build recipes that `brew install` resolves by name, and declares no package manifest. A formula's `depends_on` names other formulae that brew installs beside it, each under its own licence, so nothing is linked into a work of this repository's and there is no dependency closure whose licences could be graded. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
  • D16 Bus Factor — single-maintainer repository — bus factor is not applicable
  • 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 — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D21 Naming Consistency — Naming consistency does not read PHP yet; not measured.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .php, .rb, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — This repository is one build unit, `(repository root)` (26616 LoC, 67 module-visible types across 2 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 58 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (2 with fewer than two methods, 56 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is 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
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens 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 lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P2 Observability — This repository's Ruby source (1 module(s), 58 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Ruby source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a Gemfile or gemspec, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • PF3 Async & latency hygiene — Not applicable: PHP and Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
  • S1 Web-Security Posture — No web surface: 58 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no `config.ru`, no web framework, Rack or server gem among its gemspec run-time dependencies or its Gemfile's production gems, and no Rails, Rack, Sinatra, Grape, Hanami, WEBrick, Puma or Falcon server defined or booted in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Ruby was read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 36 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
Serious — 47 finding(s)
D4 · Code Duplication · Duplicated block (21 lines × 10) · ×2
  • Duplicated block (21 lines × 10) Formula/php-debug-zts.rb:316 — Formula/php-debug-zts.rb:316-336 | Formula/php-zts.rb:315-335 | Formula/php@8.3-debug-zts.rb:233-253 | Formula/php@8.3-zts.rb:232-252 | Formula/php@8.4-debug-zts.rb:227-247 | Formula/php@8.4-zts.rb:226-246 | Formula/php@8.6-debug-zts.rb:225-245 | Formula/php@8.6-zts.rb:224-244 | Formula/php@8.7-debug-zts.rb:225-245 | Formula/php@8.7-zts.rb:224-244 — before extracting anything, compare `Formula/php-debug-zts.rb` and `Formula/php-zts.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 306 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (21 lines × 10) Formula/php@8.2-debug-zts.rb:226 — Formula/php@8.2-debug-zts.rb:226-246 | Formula/php@8.2-zts.rb:225-245 | Formula/php@8.3-debug-zts.rb:222-242 | Formula/php@8.3-zts.rb:221-241 | Formula/php@8.4-debug-zts.rb:216-236 | Formula/php@8.4-zts.rb:215-235 | Formula/php@8.6-debug-zts.rb:214-234 | Formula/php@8.6-zts.rb:213-233 | Formula/php@8.7-debug-zts.rb:214-234 | Formula/php@8.7-zts.rb:213-233 — before extracting anything, compare `Formula/php@8.2-debug-zts.rb` and `Formula/php@8.2-zts.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 411 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D1 · Cyclomatic Complexity · PhpDebugZts.install (cyclomatic 20) · ×1
  • PhpDebugZts.install (cyclomatic 20) Formula/php-debug-zts.rb:90 — PhpDebugZts.install 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.
D1 · Cyclomatic Complexity · PhpDebug.install (cyclomatic 20) · ×1
  • PhpDebug.install (cyclomatic 20) Formula/php-debug.rb:90 — PhpDebug.install 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.
D1 · Cyclomatic Complexity · PhpZts.install (cyclomatic 20) · ×1
  • PhpZts.install (cyclomatic 20) Formula/php-zts.rb:90 — PhpZts.install 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.
D1 · Cyclomatic Complexity · Php.install (cyclomatic 20) · ×1
  • Php.install (cyclomatic 20) Formula/php.rb:91 — Php.install 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.
D2 · Cognitive Complexity · PhpDebugZts.install (cognitive 35) · ×1
  • PhpDebugZts.install (cognitive 35) Formula/php-debug-zts.rb:90 — PhpDebugZts.install has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 2, ternaries 2 (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.
D2 · Cognitive Complexity · PhpDebug.install (cognitive 35) · ×1
  • PhpDebug.install (cognitive 35) Formula/php-debug.rb:90 — PhpDebug.install has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 2, ternaries 2 (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.
D2 · Cognitive Complexity · PhpZts.install (cognitive 35) · ×1
  • PhpZts.install (cognitive 35) Formula/php-zts.rb:90 — PhpZts.install has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 2, ternaries 2 (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.
D2 · Cognitive Complexity · Php.install (cognitive 35) · ×1
  • Php.install (cognitive 35) Formula/php.rb:91 — Php.install has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21 (31 pts), boolean chains 2, ternaries 2 (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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (52 members, 41 shared lines) · ×1
  • Near-duplicate member family (52 members, 41 shared lines) Formula/php@5.6-debug-zts.rb:73 — Formula/php@5.6-debug-zts.rb:73-273 | Formula/php@5.6-debug.rb:73-265 | Formula/php@5.6-zts.rb:73-266 | Formula/php@5.6.rb:74-265 | Formula/php@7.0-debug-zts.rb:75-272 | Formula/php@7.0-debug.rb:75-270 | Formula/php@7.0-zts.rb:75-271 | Formula/php@7.0.rb:76-270 | Formula/php@7.1-debug-zts.rb:74-265 | Formula/php@7.1-debug.rb:74-263 | Formula/php@7.1-zts.rb:74-264 | Formula/php@7.1.rb:75-263 | Formula/php@7.2-debug-zts.rb:80-274 | Formula/php@7.2-debug.rb:75-267 | Formula/php@7.2-zts.rb:80-273 | Formula/php@7.2.rb:76-267 | Formula/php@7.3-debug-zts.rb:82-277 | Formula/php@7.3-debug.rb:77-270 | Formula/php@7.3-zts.rb:82-276 | Formula/php@7.3.rb:78-270 | Formula/php@7.4-debug-zts.rb:74-253 | Formula/php@7.4-debug.rb:82-272 | Formula/php@7.4-zts.rb:74-252 | Formula/php@7.4.rb:83-275 | Formula/php@8.0-debug-zts.rb:73-254 | Formula/php@8.0-debug.rb:81-273 | Formula/php@8.0-zts.rb:73-253 | Formula/php@8.0.rb:82-273 | Formula/php@8.1-debug-zts.rb:90-266 | Formula/php@8.1-debug.rb:97-281 | Formula/php@8.1-zts.rb:90-265 | Formula/php@8.1.rb:98-278 | Formula/php@8.2-debug-zts.rb:98-289 | Formula/php@8.2-debug.rb:100-277 | Formula/php@8.2-zts.rb:98-288 | Formula/php@8.2.rb:101-277 | Formula/php@8.3-debug-zts.rb:93-277 | Formula/php@8.3-debug.rb:96-275 | Formula/php@8.3-zts.rb:93-276 | Formula/php@8.3.rb:97-274 | Formula/php@8.4-debug-zts.rb:92-271 | Formula/php@8.4-debug.rb:96-271 | Formula/php@8.4-zts.rb:92-270 | Formula/php@8.4.rb:97-271 | Formula/php@8.6-debug-zts.rb:90-270 | Formula/php@8.6-debug.rb:90-254 | Formula/php@8.6-zts.rb:90-269 | Formula/php@8.6.rb:92-255 | Formula/php@8.7-debug-zts.rb:90-270 | Formula/php@8.7-debug.rb:90-254 | Formula/php@8.7-zts.rb:90-269 | Formula/php@8.7.rb:90-253 — These 52 members are variants of one another: a block of 41 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 52 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 52 times.
D4 · Code Duplication · Near-duplicate member family (36 members, 98 shared lines) · ×1
  • Near-duplicate member family (36 members, 98 shared lines) Formula/php-debug-zts.rb:92 — Formula/php-debug-zts.rb:92-361 | Formula/php-debug.rb:92-347 | Formula/php-zts.rb:92-360 | Formula/php.rb:93-347 | Formula/php@7.4-debug-zts.rb:74-253 | Formula/php@7.4-debug.rb:82-272 | Formula/php@7.4-zts.rb:74-252 | Formula/php@7.4.rb:83-275 | Formula/php@8.0-debug-zts.rb:73-254 | Formula/php@8.0-debug.rb:81-273 | Formula/php@8.0-zts.rb:73-253 | Formula/php@8.0.rb:82-273 | Formula/php@8.1-debug-zts.rb:90-266 | Formula/php@8.1-debug.rb:97-281 | Formula/php@8.1-zts.rb:90-265 | Formula/php@8.1.rb:98-278 | Formula/php@8.2-debug-zts.rb:98-289 | Formula/php@8.2-debug.rb:100-277 | Formula/php@8.2-zts.rb:98-288 | Formula/php@8.2.rb:101-277 | Formula/php@8.3-debug-zts.rb:93-277 | Formula/php@8.3-debug.rb:96-275 | Formula/php@8.3-zts.rb:93-276 | Formula/php@8.3.rb:97-274 | Formula/php@8.4-debug-zts.rb:92-271 | Formula/php@8.4-debug.rb:96-271 | Formula/php@8.4-zts.rb:92-270 | Formula/php@8.4.rb:97-271 | Formula/php@8.6-debug-zts.rb:90-270 | Formula/php@8.6-debug.rb:90-254 | Formula/php@8.6-zts.rb:90-269 | Formula/php@8.6.rb:92-255 | Formula/php@8.7-debug-zts.rb:90-270 | Formula/php@8.7-debug.rb:90-254 | Formula/php@8.7-zts.rb:90-269 | Formula/php@8.7.rb:90-253 — These 36 members are variants of one another: a block of 98 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 36 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 36 times.
D4 · Code Duplication · Duplicated block (99–106 lines × 16) · ×1
  • Duplicated block (99–106 lines × 16) Formula/php@7.0-debug-zts.rb:141 — Formula/php@7.0-debug-zts.rb:141-242 | Formula/php@7.0-debug.rb:141-240 | Formula/php@7.0-zts.rb:141-241 | Formula/php@7.0.rb:142-240 | Formula/php@7.1-debug-zts.rb:134-235 | Formula/php@7.1-debug.rb:134-233 | Formula/php@7.1-zts.rb:134-234 | Formula/php@7.1.rb:135-233 | Formula/php@7.2-debug-zts.rb:140-244 | Formula/php@7.2-debug.rb:135-237 | Formula/php@7.2-zts.rb:140-243 | Formula/php@7.2.rb:136-237 | Formula/php@7.3-debug-zts.rb:137-242 | Formula/php@7.3-debug.rb:132-235 | Formula/php@7.3-zts.rb:137-241 | Formula/php@7.3.rb:133-235 — before extracting anything, compare `Formula/php@7.0-debug-zts.rb` and `Formula/php@7.0-debug.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 369 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (125–128 lines × 4) · ×1
  • Duplicated block (125–128 lines × 4) Formula/php@5.6-debug-zts.rb:146 — Formula/php@5.6-debug-zts.rb:146-273 | Formula/php@5.6-debug.rb:140-265 | Formula/php@5.6-zts.rb:140-266 | Formula/php@5.6.rb:141-265 — before extracting anything, compare `Formula/php@5.6-debug-zts.rb` and `Formula/php@5.6-debug.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 353 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (97–98 lines × 2) · ×1
  • Duplicated block (97–98 lines × 2) Formula/php-debug.rb:147 — Formula/php-debug.rb:147-244 | Formula/php.rb:148-244 — before extracting anything, compare `Formula/php-debug.rb` and `Formula/php.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 289 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (95–97 lines × 6) · ×1
  • Duplicated block (95–97 lines × 6) Formula/php@7.4-debug-zts.rb:131 — Formula/php@7.4-debug-zts.rb:131-227 | Formula/php@7.4-zts.rb:131-226 | Formula/php@8.0-debug-zts.rb:133-228 | Formula/php@8.0-zts.rb:133-227 | Formula/php@8.1-debug-zts.rb:144-240 | Formula/php@8.1-zts.rb:144-239 — before extracting anything, compare `Formula/php@7.4-debug-zts.rb` and `Formula/php@7.4-zts.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 385 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Formula/php@7.4-debug-zts.rb:131` 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.
D4 · Code Duplication · Duplicated block (89–96 lines × 20) · ×1
  • Duplicated block (89–96 lines × 20) Formula/php@5.6-debug-zts.rb:139 — Formula/php@5.6-debug-zts.rb:139-230 | Formula/php@5.6-debug.rb:133-222 | Formula/php@5.6-zts.rb:133-223 | Formula/php@5.6.rb:134-222 | Formula/php@7.0-debug-zts.rb:134-226 | Formula/php@7.0-debug.rb:134-224 | Formula/php@7.0-zts.rb:134-225 | Formula/php@7.0.rb:135-224 | Formula/php@7.1-debug-zts.rb:127-219 | Formula/php@7.1-debug.rb:127-217 | Formula/php@7.1-zts.rb:127-218 | Formula/php@7.1.rb:128-217 | Formula/php@7.2-debug-zts.rb:133-228 | Formula/php@7.2-debug.rb:128-221 | Formula/php@7.2-zts.rb:133-227 | Formula/php@7.2.rb:129-221 | Formula/php@7.3-debug-zts.rb:130-225 | Formula/php@7.3-debug.rb:125-218 | Formula/php@7.3-zts.rb:130-224 | Formula/php@7.3.rb:126-218 — before extracting anything, compare `Formula/php@5.6-debug-zts.rb` and `Formula/php@5.6-debug.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 353 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (93–95 lines × 4) · ×1
  • Duplicated block (93–95 lines × 4) Formula/php@8.2-debug-zts.rb:146 — Formula/php@8.2-debug-zts.rb:146-239 | Formula/php@8.2-zts.rb:146-238 | Formula/php@8.3-debug-zts.rb:141-235 | Formula/php@8.3-zts.rb:141-234 — before extracting anything, compare `Formula/php@8.2-debug-zts.rb` and `Formula/php@8.2-zts.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 411 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Formula/php@8.2-debug-zts.rb:146` 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.
D4 · Code Duplication · Duplicated block (122–125 lines × 12) · ×1
  • Duplicated block (122–125 lines × 12) Formula/php@7.4-debug.rb:143 — Formula/php@7.4-debug.rb:143-267 | Formula/php@7.4.rb:147-270 | Formula/php@8.0-debug.rb:145-268 | Formula/php@8.0.rb:146-268 | Formula/php@8.1-debug.rb:153-276 | Formula/php@8.1.rb:151-273 | Formula/php@8.2-debug.rb:148-270 | Formula/php@8.2.rb:149-270 | Formula/php@8.3-debug.rb:144-268 | Formula/php@8.3.rb:145-267 | Formula/php@8.4-debug.rb:142-264 | Formula/php@8.4.rb:143-264 — before extracting anything, compare `Formula/php@7.4-debug.rb` and `Formula/php@7.4.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 447 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Formula/php@7.4-debug.rb:143` 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.
D4 · Code Duplication · Duplicated block (88–94 lines × 10) · ×1
  • Duplicated block (88–94 lines × 10) Formula/php@7.4-debug-zts.rb:126 — Formula/php@7.4-debug-zts.rb:126-219 | Formula/php@7.4-zts.rb:126-218 | Formula/php@8.0-debug-zts.rb:128-220 | Formula/php@8.0-zts.rb:128-219 | Formula/php@8.1-debug-zts.rb:139-232 | Formula/php@8.1-zts.rb:139-231 | Formula/php@8.2-debug-zts.rb:141-229 | Formula/php@8.2-zts.rb:141-228 | Formula/php@8.3-debug-zts.rb:136-225 | Formula/php@8.3-zts.rb:136-224 — before extracting anything, compare `Formula/php@7.4-debug-zts.rb` and `Formula/php@7.4-zts.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 385 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (93–94 lines × 4) · ×1
  • Duplicated block (93–94 lines × 4) Formula/php@8.6-debug.rb:135 — Formula/php@8.6-debug.rb:135-228 | Formula/php@8.6.rb:137-229 | Formula/php@8.7-debug.rb:135-228 | Formula/php@8.7.rb:135-227 — before extracting anything, compare `Formula/php@8.6-debug.rb` and `Formula/php@8.6.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 274 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (93–94 lines × 2) · ×1
  • Duplicated block (93–94 lines × 2) Formula/php-debug-zts.rb:155 — Formula/php-debug-zts.rb:155-248 | Formula/php-zts.rb:155-247 — before extracting anything, compare `Formula/php-debug-zts.rb` and `Formula/php-zts.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 306 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (91–92 lines × 2) · ×1
  • Duplicated block (91–92 lines × 2) Formula/php@8.4-debug-zts.rb:138 — Formula/php@8.4-debug-zts.rb:138-229 | Formula/php@8.4-zts.rb:138-228 — before extracting anything, compare `Formula/php@8.4-debug-zts.rb` and `Formula/php@8.4-zts.rb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 454 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `Formula/php@8.4-debug-zts.rb:138` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (86–91 lines × 14) · ×1
  • Duplicated block (86–91 lines × 14) Formula/php@7.4-debug.rb:138 — Formula/php@7.4-debug.rb:138-228 | Formula/php@7.4.rb:142-231 | Formula/php@8.0-debug.rb:140-229 | Formula/php@8.0.rb:141-229 | Formula/php@8.1-debug.rb:148-237 | Formula/php@8.1.rb:146-234 | Formula/php@8.2-debug.rb:143-231 | Formula/php@8.2.rb:144-231 | Formula/php@8.3-debug.rb:139-229 | Formula/php@8.3.rb:140-228 | Formula/php@8.4-debug-zts.rb:133-219 | Formula/php@8.4-debug.rb:137-225 | Formula/php@8.4-zts.rb:133-218 | Formula/php@8.4.rb:138-225 — before extracting anything, compare `Formula/php@7.4-debug.rb` and `Formula/php@7.4.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 447 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (90–91 lines × 4) · ×1
  • Duplicated block (90–91 lines × 4) Formula/php@8.6-debug-zts.rb:143 — Formula/php@8.6-debug-zts.rb:143-233 | Formula/php@8.6-zts.rb:143-232 | Formula/php@8.7-debug-zts.rb:143-233 | Formula/php@8.7-zts.rb:143-232 — before extracting anything, compare `Formula/php@8.6-debug-zts.rb` and `Formula/php@8.6-zts.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 341 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (82–89 lines × 36) · ×1
  • Duplicated block (82–89 lines × 36) Formula/php-debug-zts.rb:141 — Formula/php-debug-zts.rb:141-224 | Formula/php-debug.rb:141-226 | Formula/php-zts.rb:141-223 | Formula/php.rb:142-226 | Formula/php@7.4-debug-zts.rb:123-211 | Formula/php@7.4-debug.rb:135-221 | Formula/php@7.4-zts.rb:123-210 | Formula/php@7.4.rb:139-224 | Formula/php@8.0-debug-zts.rb:125-212 | Formula/php@8.0-debug.rb:137-222 | Formula/php@8.0-zts.rb:125-211 | Formula/php@8.0.rb:138-222 | Formula/php@8.1-debug-zts.rb:136-224 | Formula/php@8.1-debug.rb:145-230 | Formula/php@8.1-zts.rb:136-223 | Formula/php@8.1.rb:143-227 | Formula/php@8.2-debug-zts.rb:138-221 | Formula/php@8.2-debug.rb:140-224 | Formula/php@8.2-zts.rb:138-220 | Formula/php@8.2.rb:141-224 | Formula/php@8.3-debug-zts.rb:133-217 | Formula/php@8.3-debug.rb:136-222 | Formula/php@8.3-zts.rb:133-216 | Formula/php@8.3.rb:137-221 | Formula/php@8.4-debug-zts.rb:130-212 | Formula/php@8.4-debug.rb:134-218 | Formula/php@8.4-zts.rb:130-211 | Formula/php@8.4.rb:135-218 | Formula/php@8.6-debug-zts.rb:129-212 | Formula/php@8.6-debug.rb:129-214 | Formula/php@8.6-zts.rb:129-211 | Formula/php@8.6.rb:131-215 | Formula/php@8.7-debug-zts.rb:129-212 | Formula/php@8.7-debug.rb:129-214 | Formula/php@8.7-zts.rb:129-211 | Formula/php@8.7.rb:129-213 — before extracting anything, compare `Formula/php-debug-zts.rb` and `Formula/php-debug.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (67 lines × 4) · ×1
  • Duplicated block (67 lines × 4) Formula/php-debug-zts.rb:237 — Formula/php-debug-zts.rb:237-303 | Formula/php-debug.rb:233-299 | Formula/php-zts.rb:236-302 | Formula/php.rb:233-299 — before extracting anything, compare `Formula/php-debug-zts.rb` and `Formula/php-debug.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (44 lines × 8) · ×1
  • Duplicated block (44 lines × 8) Formula/php@5.6-debug-zts.rb:88 — Formula/php@5.6-debug-zts.rb:88-131 | Formula/php@5.6-debug.rb:88-131 | Formula/php@5.6-zts.rb:88-131 | Formula/php@5.6.rb:89-132 | Formula/php@7.0-debug-zts.rb:89-132 | Formula/php@7.0-debug.rb:89-132 | Formula/php@7.0-zts.rb:89-132 | Formula/php@7.0.rb:90-133 — before extracting anything, compare `Formula/php@5.6-debug-zts.rb` and `Formula/php@5.6-debug.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 353 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (32 lines × 4) · ×1
  • Duplicated block (32 lines × 4) Formula/php@7.3-debug-zts.rb:82 — Formula/php@7.3-debug-zts.rb:82-113 | Formula/php@7.3-debug.rb:77-108 | Formula/php@7.3-zts.rb:82-113 | Formula/php@7.3.rb:78-109 — before extracting anything, compare `Formula/php@7.3-debug-zts.rb` and `Formula/php@7.3-debug.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 394 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (31 lines × 44) · ×1
  • Duplicated block (31 lines × 44) Formula/php@7.1-debug-zts.rb:102 — Formula/php@7.1-debug-zts.rb:102-132 | Formula/php@7.1-debug.rb:102-132 | Formula/php@7.1-zts.rb:102-132 | Formula/php@7.1.rb:103-133 | Formula/php@7.2-debug-zts.rb:108-138 | Formula/php@7.2-debug.rb:103-133 | Formula/php@7.2-zts.rb:108-138 | Formula/php@7.2.rb:104-134 | Formula/php@7.3-debug-zts.rb:105-135 | Formula/php@7.3-debug.rb:100-130 | Formula/php@7.3-zts.rb:105-135 | Formula/php@7.3.rb:101-131 | Formula/php@7.4-debug-zts.rb:89-119 | Formula/php@7.4-debug.rb:101-131 | Formula/php@7.4-zts.rb:89-119 | Formula/php@7.4.rb:105-135 | Formula/php@8.0-debug-zts.rb:88-118 | Formula/php@8.0-debug.rb:100-130 | Formula/php@8.0-zts.rb:88-118 | Formula/php@8.0.rb:101-131 | Formula/php@8.1-debug-zts.rb:99-129 | Formula/php@8.1-debug.rb:108-138 | Formula/php@8.1-zts.rb:99-129 | Formula/php@8.1.rb:106-136 | Formula/php@8.2-debug-zts.rb:101-131 | Formula/php@8.2-debug.rb:103-133 | Formula/php@8.2-zts.rb:101-131 | Formula/php@8.2.rb:104-134 | Formula/php@8.3-debug-zts.rb:96-126 | Formula/php@8.3-debug.rb:99-129 | Formula/php@8.3-zts.rb:96-126 | Formula/php@8.3.rb:100-130 | Formula/php@8.4-debug-zts.rb:95-125 | Formula/php@8.4-debug.rb:99-129 | Formula/php@8.4-zts.rb:95-125 | Formula/php@8.4.rb:100-130 | Formula/php@8.6-debug-zts.rb:93-123 | Formula/php@8.6-debug.rb:93-123 | Formula/php@8.6-zts.rb:93-123 | Formula/php@8.6.rb:95-125 | Formula/php@8.7-debug-zts.rb:93-123 | Formula/php@8.7-debug.rb:93-123 | Formula/php@8.7-zts.rb:93-123 | Formula/php@8.7.rb:93-123 — before extracting anything, compare `Formula/php@7.1-debug-zts.rb` and `Formula/php@7.1-debug.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 356 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (28 lines × 8) · ×1
  • Duplicated block (28 lines × 8) Formula/php@8.3-debug-zts.rb:223 — Formula/php@8.3-debug-zts.rb:223-250 | Formula/php@8.3-zts.rb:222-249 | Formula/php@8.4-debug-zts.rb:217-244 | Formula/php@8.4-zts.rb:216-243 | Formula/php@8.6-debug-zts.rb:215-242 | Formula/php@8.6-zts.rb:214-241 | Formula/php@8.7-debug-zts.rb:215-242 | Formula/php@8.7-zts.rb:214-241 — before extracting anything, compare `Formula/php@8.3-debug-zts.rb` and `Formula/php@8.3-zts.rb` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 460 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (28 lines × 4) · ×1
  • Duplicated block (28 lines × 4) Formula/php@7.3-debug-zts.rb:248 — Formula/php@7.3-debug-zts.rb:248-275 | Formula/php@7.3-debug.rb:241-268 | Formula/php@7.3-zts.rb:247-274 | Formula/php@7.3.rb:241-268 — before extracting anything, compare `Formula/php@7.3-debug-zts.rb` and `Formula/php@7.3-debug.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 394 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (26 lines × 20) · ×1
  • Duplicated block (26 lines × 20) Formula/php@5.6-debug-zts.rb:98 — Formula/php@5.6-debug-zts.rb:98-123 | Formula/php@5.6-debug.rb:98-123 | Formula/php@5.6-zts.rb:98-123 | Formula/php@5.6.rb:99-124 | Formula/php@7.0-debug-zts.rb:99-124 | Formula/php@7.0-debug.rb:99-124 | Formula/php@7.0-zts.rb:99-124 | Formula/php@7.0.rb:100-125 | Formula/php@7.1-debug-zts.rb:95-120 | Formula/php@7.1-debug.rb:95-120 | Formula/php@7.1-zts.rb:95-120 | Formula/php@7.1.rb:96-121 | Formula/php@7.2-debug-zts.rb:101-126 | Formula/php@7.2-debug.rb:96-121 | Formula/php@7.2-zts.rb:101-126 | Formula/php@7.2.rb:97-122 | Formula/php@7.3-debug-zts.rb:98-123 | Formula/php@7.3-debug.rb:93-118 | Formula/php@7.3-zts.rb:98-123 | Formula/php@7.3.rb:94-119 — before extracting anything, compare `Formula/php@5.6-debug-zts.rb` and `Formula/php@5.6-debug.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 353 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (25 lines × 52) · ×1
  • Duplicated block (25 lines × 52) Formula/php@5.6-debug-zts.rb:104 — Formula/php@5.6-debug-zts.rb:104-128 | Formula/php@5.6-debug.rb:104-128 | Formula/php@5.6-zts.rb:104-128 | Formula/php@5.6.rb:105-129 | Formula/php@7.0-debug-zts.rb:105-129 | Formula/php@7.0-debug.rb:105-129 | Formula/php@7.0-zts.rb:105-129 | Formula/php@7.0.rb:106-130 | Formula/php@7.1-debug-zts.rb:101-125 | Formula/php@7.1-debug.rb:101-125 | Formula/php@7.1-zts.rb:101-125 | Formula/php@7.1.rb:102-126 | Formula/php@7.2-debug-zts.rb:107-131 | Formula/php@7.2-debug.rb:102-126 | Formula/php@7.2-zts.rb:107-131 | Formula/php@7.2.rb:103-127 | Formula/php@7.3-debug-zts.rb:104-128 | Formula/php@7.3-debug.rb:99-123 | Formula/php@7.3-zts.rb:104-128 | Formula/php@7.3.rb:100-124 | Formula/php@7.4-debug-zts.rb:88-112 | Formula/php@7.4-debug.rb:100-124 | Formula/php@7.4-zts.rb:88-112 | Formula/php@7.4.rb:104-128 | Formula/php@8.0-debug-zts.rb:87-111 | Formula/php@8.0-debug.rb:99-123 | Formula/php@8.0-zts.rb:87-111 | Formula/php@8.0.rb:100-124 | Formula/php@8.1-debug-zts.rb:98-122 | Formula/php@8.1-debug.rb:107-131 | Formula/php@8.1-zts.rb:98-122 | Formula/php@8.1.rb:105-129 | Formula/php@8.2-debug-zts.rb:100-124 | Formula/php@8.2-debug.rb:102-126 | Formula/php@8.2-zts.rb:100-124 | Formula/php@8.2.rb:103-127 | Formula/php@8.3-debug-zts.rb:95-119 | Formula/php@8.3-debug.rb:98-122 | Formula/php@8.3-zts.rb:95-119 | Formula/php@8.3.rb:99-123 | Formula/php@8.4-debug-zts.rb:94-118 | Formula/php@8.4-debug.rb:98-122 | Formula/php@8.4-zts.rb:94-118 | Formula/php@8.4.rb:99-123 | Formula/php@8.6-debug-zts.rb:92-116 | Formula/php@8.6-debug.rb:92-116 | Formula/php@8.6-zts.rb:92-116 | Formula/php@8.6.rb:94-118 | Formula/php@8.7-debug-zts.rb:92-116 | Formula/php@8.7-debug.rb:92-116 | Formula/php@8.7-zts.rb:92-116 | Formula/php@8.7.rb:92-116 — before extracting anything, compare `Formula/php@5.6-debug-zts.rb` and `Formula/php@5.6-debug.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 353 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (24 lines × 6) · ×1
  • Duplicated block (24 lines × 6) Formula/php@8.2-debug-zts.rb:222 — Formula/php@8.2-debug-zts.rb:222-245 | Formula/php@8.2-zts.rb:221-244 | Formula/php@8.3-debug-zts.rb:218-241 | Formula/php@8.3-zts.rb:217-240 | Formula/php@8.4-debug-zts.rb:212-235 | Formula/php@8.4-zts.rb:211-234 — before extracting anything, compare `Formula/php@8.2-debug-zts.rb` and `Formula/php@8.2-zts.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 411 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (22 lines × 12) · ×1
  • Duplicated block (22 lines × 12) Formula/php@7.0-debug-zts.rb:75 — Formula/php@7.0-debug-zts.rb:75-96 | Formula/php@7.0-debug.rb:75-96 | Formula/php@7.0-zts.rb:75-96 | Formula/php@7.0.rb:76-97 | Formula/php@7.1-debug-zts.rb:74-95 | Formula/php@7.1-debug.rb:74-95 | Formula/php@7.1-zts.rb:74-95 | Formula/php@7.1.rb:75-96 | Formula/php@7.2-debug-zts.rb:80-101 | Formula/php@7.2-debug.rb:75-96 | Formula/php@7.2-zts.rb:80-101 | Formula/php@7.2.rb:76-97 — before extracting anything, compare `Formula/php@7.0-debug-zts.rb` and `Formula/php@7.0-debug.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 369 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (22 lines × 6) · ×1
  • Duplicated block (22 lines × 6) Formula/php@8.2-debug.rb:256 — Formula/php@8.2-debug.rb:256-277 | Formula/php@8.2.rb:256-277 | Formula/php@8.3-debug.rb:254-275 | Formula/php@8.3.rb:253-274 | Formula/php@8.4-debug.rb:250-271 | Formula/php@8.4.rb:250-271 — before extracting anything, compare `Formula/php@8.2-debug.rb` and `Formula/php@8.2.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 432 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (20 lines × 6) · ×1
  • Duplicated block (20 lines × 6) Formula/php@7.4-debug.rb:253 — Formula/php@7.4-debug.rb:253-272 | Formula/php@7.4.rb:256-275 | Formula/php@8.0-debug.rb:254-273 | Formula/php@8.0.rb:254-273 | Formula/php@8.1-debug.rb:262-281 | Formula/php@8.1.rb:259-278 — before extracting anything, compare `Formula/php@7.4-debug.rb` and `Formula/php@7.4.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 447 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (19 lines × 12) · ×1
  • Duplicated block (19 lines × 12) Formula/php-debug-zts.rb:343 — Formula/php-debug-zts.rb:343-361 | Formula/php-debug.rb:329-347 | Formula/php-zts.rb:342-360 | Formula/php.rb:329-347 | Formula/php@8.6-debug-zts.rb:252-270 | Formula/php@8.6-debug.rb:236-254 | Formula/php@8.6-zts.rb:251-269 | Formula/php@8.6.rb:237-255 | Formula/php@8.7-debug-zts.rb:252-270 | Formula/php@8.7-debug.rb:236-254 | Formula/php@8.7-zts.rb:251-269 | Formula/php@8.7.rb:235-253 — before extracting anything, compare `Formula/php-debug-zts.rb` and `Formula/php-debug.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Formula/php-debug-zts.rb:366` calls `$PHP` and `Formula/php@8.6-debug-zts.rb:274` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18 lines × 20) · ×1
  • Duplicated block (18 lines × 20) Formula/php@5.6-debug-zts.rb:232 — Formula/php@5.6-debug-zts.rb:232-249 | Formula/php@5.6-debug.rb:224-241 | Formula/php@5.6-zts.rb:225-242 | Formula/php@5.6.rb:224-241 | Formula/php@7.0-debug-zts.rb:230-247 | Formula/php@7.0-debug.rb:228-245 | Formula/php@7.0-zts.rb:229-246 | Formula/php@7.0.rb:228-245 | Formula/php@7.1-debug-zts.rb:223-240 | Formula/php@7.1-debug.rb:221-238 | Formula/php@7.1-zts.rb:222-239 | Formula/php@7.1.rb:221-238 | Formula/php@7.2-debug-zts.rb:232-249 | Formula/php@7.2-debug.rb:225-242 | Formula/php@7.2-zts.rb:231-248 | Formula/php@7.2.rb:225-242 | Formula/php@7.3-debug-zts.rb:230-247 | Formula/php@7.3-debug.rb:223-240 | Formula/php@7.3-zts.rb:229-246 | Formula/php@7.3.rb:223-240 — before extracting anything, compare `Formula/php@5.6-debug-zts.rb` and `Formula/php@5.6-debug.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 353 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17 lines × 18) · ×1
  • Duplicated block (17 lines × 18) Formula/php@7.4-debug-zts.rb:212 — Formula/php@7.4-debug-zts.rb:212-228 | Formula/php@7.4-debug.rb:221-237 | Formula/php@7.4-zts.rb:211-227 | Formula/php@7.4.rb:224-240 | Formula/php@8.0-debug-zts.rb:213-229 | Formula/php@8.0-debug.rb:222-238 | Formula/php@8.0-zts.rb:212-228 | Formula/php@8.0.rb:222-238 | Formula/php@8.1-debug-zts.rb:225-241 | Formula/php@8.1-debug.rb:230-246 | Formula/php@8.1-zts.rb:224-240 | Formula/php@8.1.rb:227-243 | Formula/php@8.2-debug.rb:224-240 | Formula/php@8.2.rb:224-240 | Formula/php@8.3-debug.rb:222-238 | Formula/php@8.3.rb:221-237 | Formula/php@8.4-debug.rb:218-234 | Formula/php@8.4.rb:218-234 — before extracting anything, compare `Formula/php@7.4-debug-zts.rb` and `Formula/php@7.4-debug.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 194 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (17 lines × 4) · ×1
  • Duplicated block (17 lines × 4) Formula/php@7.4-debug.rb:82 — Formula/php@7.4-debug.rb:82-98 | Formula/php@7.4.rb:83-99 | Formula/php@8.0-debug.rb:81-97 | Formula/php@8.0.rb:82-98 — before extracting anything, compare `Formula/php@7.4-debug.rb` and `Formula/php@7.4.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 447 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16 lines × 56) · ×1
  • Duplicated block (16 lines × 56) Formula/php-debug-zts.rb:328 — Formula/php-debug-zts.rb:328-343 | Formula/php-debug.rb:314-329 | Formula/php-zts.rb:327-342 | Formula/php.rb:314-329 | Formula/php@5.6-debug-zts.rb:242-257 | Formula/php@5.6-debug.rb:234-249 | Formula/php@5.6-zts.rb:235-250 | Formula/php@5.6.rb:234-249 | Formula/php@7.0-debug-zts.rb:240-255 | Formula/php@7.0-debug.rb:238-253 | Formula/php@7.0-zts.rb:239-254 | Formula/php@7.0.rb:238-253 | Formula/php@7.1-debug-zts.rb:233-248 | Formula/php@7.1-debug.rb:231-246 | Formula/php@7.1-zts.rb:232-247 | Formula/php@7.1.rb:231-246 | Formula/php@7.2-debug-zts.rb:242-257 | Formula/php@7.2-debug.rb:235-250 | Formula/php@7.2-zts.rb:241-256 | Formula/php@7.2.rb:235-250 | Formula/php@7.3-debug-zts.rb:240-255 | Formula/php@7.3-debug.rb:233-248 | Formula/php@7.3-zts.rb:239-254 | Formula/php@7.3.rb:233-248 | Formula/php@7.4-debug-zts.rb:221-236 | Formula/php@7.4-debug.rb:230-245 | Formula/php@7.4-zts.rb:220-235 | Formula/php@7.4.rb:233-248 | Formula/php@8.0-debug-zts.rb:222-237 | Formula/php@8.0-debug.rb:231-246 | Formula/php@8.0-zts.rb:221-236 | Formula/php@8.0.rb:231-246 | Formula/php@8.1-debug-zts.rb:234-249 | Formula/php@8.1-debug.rb:239-254 | Formula/php@8.1-zts.rb:233-248 | Formula/php@8.1.rb:236-251 | Formula/php@8.2-debug-zts.rb:257-272 | Formula/php@8.2-debug.rb:233-248 | Formula/php@8.2-zts.rb:256-271 | Formula/php@8.2.rb:233-248 | Formula/php@8.3-debug-zts.rb:245-260 | Formula/php@8.3-debug.rb:231-246 | Formula/php@8.3-zts.rb:244-259 | Formula/php@8.3.rb:230-245 | Formula/php@8.4-debug-zts.rb:239-254 | Formula/php@8.4-debug.rb:227-242 | Formula/php@8.4-zts.rb:238-253 | Formula/php@8.4.rb:227-242 | Formula/php@8.6-debug-zts.rb:237-252 | Formula/php@8.6-debug.rb:221-236 | Formula/php@8.6-zts.rb:236-251 | Formula/php@8.6.rb:222-237 | Formula/php@8.7-debug-zts.rb:237-252 | Formula/php@8.7-debug.rb:221-236 | Formula/php@8.7-zts.rb:236-251 | Formula/php@8.7.rb:220-235 — before extracting anything, compare `Formula/php-debug-zts.rb` and `Formula/php-debug.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 191 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16 lines × 40) · ×1
  • Duplicated block (16 lines × 40) Formula/php@7.0-debug-zts.rb:257 — Formula/php@7.0-debug-zts.rb:257-272 | Formula/php@7.0-debug.rb:255-270 | Formula/php@7.0-zts.rb:256-271 | Formula/php@7.0.rb:255-270 | Formula/php@7.1-debug-zts.rb:250-265 | Formula/php@7.1-debug.rb:248-263 | Formula/php@7.1-zts.rb:249-264 | Formula/php@7.1.rb:248-263 | Formula/php@7.2-debug-zts.rb:259-274 | Formula/php@7.2-debug.rb:252-267 | Formula/php@7.2-zts.rb:258-273 | Formula/php@7.2.rb:252-267 | Formula/php@7.3-debug-zts.rb:262-277 | Formula/php@7.3-debug.rb:255-270 | Formula/php@7.3-zts.rb:261-276 | Formula/php@7.3.rb:255-270 | Formula/php@7.4-debug-zts.rb:238-253 | Formula/php@7.4-debug.rb:247-262 | Formula/php@7.4-zts.rb:237-252 | Formula/php@7.4.rb:250-265 | Formula/php@8.0-debug-zts.rb:239-254 | Formula/php@8.0-debug.rb:248-263 | Formula/php@8.0-zts.rb:238-253 | Formula/php@8.0.rb:248-263 | Formula/php@8.1-debug-zts.rb:251-266 | Formula/php@8.1-debug.rb:256-271 | Formula/php@8.1-zts.rb:250-265 | Formula/php@8.1.rb:253-268 | Formula/php@8.2-debug-zts.rb:274-289 | Formula/php@8.2-debug.rb:250-265 | Formula/php@8.2-zts.rb:273-288 | Formula/php@8.2.rb:250-265 | Formula/php@8.3-debug-zts.rb:262-277 | Formula/php@8.3-debug.rb:248-263 | Formula/php@8.3-zts.rb:261-276 | Formula/php@8.3.rb:247-262 | Formula/php@8.4-debug-zts.rb:256-271 | Formula/php@8.4-debug.rb:244-259 | Formula/php@8.4-zts.rb:255-270 | Formula/php@8.4.rb:244-259 — before extracting anything, compare `Formula/php@7.0-debug-zts.rb` and `Formula/php@7.0-debug.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 369 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Minor — 6 finding(s)
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
X10 · Duplicated predicate · Duplicated predicate · ×1
  • Duplicated predicate Formula/php@7.4-debug.rb:90 — `OS.mac? && ENV.compiler.to_s.start_with?("gcc")` appears character-identically in 4 files — Formula/php@7.4-debug.rb, Formula/php@7.4.rb, Formula/php@8.0-debug.rb, Formula/php@8.0.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
X5 · Nullable reference types · Ruby's type checker does not check nil everywhere · ×1
  • Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 58 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-23f8c7a7daeb4a3bb9b86a764ee32455/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-23f8c7a7daeb4a3bb9b86a764ee32455/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-23f8c7a7daeb4a3bb9b86a764ee32455/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=9164" --report-format json --report-path /tmp/watchdog-gitleaks-23f8c7a7daeb4a3bb9b86a764ee32455/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-23f8c7a7daeb4a3bb9b86a764ee32455/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .36artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `Scripts/pgo_script.php` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a1ebd6-89fd-74fa-9944-88247b5841c1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

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