Public report of collabnix/kubelabs, published 21 October 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 21 October 2026, 02:19 UTC · Survey ID cd_6b7200c0545b4f899ce4d58bfef59f18
collabnix/kubelabs
Measured 21 October 2026, 02:15 UTC, at code version 29d18c3
Code coverage is not measured: Tests deferred to the consumer.
Test distribution is not measured: No automated tests.
CAI scoreAt riskDown 6 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A very small codebase: 44 lines of product code in 3 projects, tests not counted · Weakest lens: Maturity, 37
Findings by how serious they are
120 critical1680 serious488 minor
16 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 02:15 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
56of 60 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
2273of 2288 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
60dimensions across 6 lenses, read from 44 lines of product code in 3 projects.
collabnix/kubelabs scores 43 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged. Watchdog judged it as a template, sample or demo, meant to be read or copied, so the dimensions about building, releasing and running a product don't apply, and its lenses are rated against a lower bar. The score itself is worked out as for any repository.
The weakest lens counts most in the score, and here that is Maturity, which scores 37 and is rated Adequate. Its Documentation accuracy dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 1 No tests found finding(s) in Test Distribution and to reconcile the README with reality: README omits the Kubernetes CRD/CustomResourceDefinition project entirely; README omits the Helm101 Wordpres project; DaemonSet101/README.md changes into `kubelabs/DaemonSet101`, but no such folder exists; Deployment101/README.md changes into `dockerlabs/kubernetes/workshop/Deployment101`, but no such folder exists; Gateway101/README.md documents the environment variable `GATEWAY_IP`, but no code, script or configuration file names it, and if Maturity rose to 70, the score would rise from 43 to about 48.
120 findings are critical: 49 in IaC & Container Security, 34 in Static Analysis (SAST), 19 in Page structure, seven in Forms & labels, six in Dependency Vulnerabilities, three in Text alternatives and two in Secrets (history).
Watchdog couldn't measure 15 dimensions in this code, among them Cyclomatic Complexity, Cognitive Complexity and Dependency Hygiene, so they are left out of the score. The product code is 44 lines.
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 forThe 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.
Visual & motion safety · Focus outline removed in CSS without a :focus replacement .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-markdown/lib/markdown-body.scss
Visual & motion safety · Focus outline removed in CSS without a :focus replacement .bundles_cache/ruby/2.6.0/gems/jekyll-theme-midnight-0.2.0/_sass/jekyll-theme-midnight.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss
Visual & motion safety · Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 7 findings
These 7 critical or serious findings were in the previous survey, on 5 October 2026, and are gone from this one.
Cohesion (LCOM4) · Low cohesion: Multi (LCOM4 5) .bundles_cache/ruby/2.6.0/gems/ethon-0.16.0/lib/ethon/multi/operations.rb
Page structure · Page without a main landmark Slides_Services101/Services101.html
Page structure · Document without a <title> REDACTED
Page structure · <iframe> without a title REDACTED
Rebuild cost: about €38 · Estimate
Cost to rebuild
€13 to €63, for 0 to 1 hours of work, about 0.1 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 43. 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.
Size
Very small: 44 lines of product code
How the estimate is made: Watchdog prices 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 1 No tests found finding(s) in Test Distribution.
Reconcile the README with reality: README omits the Kubernetes CRD/CustomResourceDefinition project entirely; README omits the Helm101 Wordpres project; DaemonSet101/README.md changes into `kubelabs/DaemonSet101`, but no such folder exists; Deployment101/README.md changes into `dockerlabs/kubernetes/workshop/Deployment101`, but no such folder exists; Gateway101/README.md documents the environment variable `GATEWAY_IP`, but no code, script or configuration file names it.
Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.
Raises the score by about 4 points · Medium effort · Observability
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.
If you do one thing first · First action
Resolve the 1 No tests found finding(s) in Test Distribution. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 1 Test Distribution findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
546 modules, with 405 dependencies between them. 8 loops run through 52 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 506 more are left out to keep it readable.
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.
Concurrent.Collection uses Concurrent.Synchronization, so a change to Concurrent.Synchronization can break Concurrent.Collection, while a change to Concurrent.Collection can't break Concurrent.Synchronization.
Position
Below the diagonal: Concurrent.Collection uses a module listed above it, which is the healthy direction.
10→19 Concurrent.Collection uses Concurrentpart of a loop✕
Connections
1 pair of types, where a type in Concurrent.Collection uses a type in Concurrent.
Concurrent.Collection uses Concurrent, so a change to Concurrent can break Concurrent.Collection, while a change to Concurrent.Collection can't break Concurrent.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Concurrent.Promises uses Concurrent.Synchronization, so a change to Concurrent.Synchronization can break Concurrent.Promises, while a change to Concurrent.Promises can't break Concurrent.Synchronization.
Position
Below the diagonal: Concurrent.Promises uses a module listed above it, which is the healthy direction.
11→19 Concurrent.Promises uses Concurrentpart of a loop✕
Connections
6 pairs of types, where a type in Concurrent.Promises uses a type in Concurrent.
Concurrent.Promises uses Concurrent, so a change to Concurrent can break Concurrent.Promises, while a change to Concurrent.Promises can't break Concurrent.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Regexp.Expression.UnicodeProperty uses Regexp.Expression, so a change to Regexp.Expression can break Regexp.Expression.UnicodeProperty, while a change to Regexp.Expression.UnicodeProperty can't break Regexp.Expression.
Position
Below the diagonal: Regexp.Expression.UnicodeProperty uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in Concurrent uses a type in Concurrent.Synchronization. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Concurrent uses Concurrent.Synchronization, so a change to Concurrent.Synchronization can break Concurrent, while a change to Concurrent can't break Concurrent.Synchronization.
Position
Below the diagonal: Concurrent uses a module listed above it, which is the healthy direction.
Concurrent uses Concurrent.Collection, so a change to Concurrent.Collection can break Concurrent, while a change to Concurrent can't break Concurrent.Collection.
Position
Below the diagonal: Concurrent uses a module listed above it, which is the healthy direction.
Concurrent uses Concurrent.Promises, so a change to Concurrent.Promises can break Concurrent, while a change to Concurrent can't break Concurrent.Promises.
Position
Below the diagonal: Concurrent uses a module listed above it, which is the healthy direction.
ActiveSupport.Testing uses Concurrent, so a change to Concurrent can break ActiveSupport.Testing, while a change to ActiveSupport.Testing can't break Concurrent.
Position
Below the diagonal: ActiveSupport.Testing uses a module listed above it, which is the healthy direction.
23→26 ActiveSupport.Testing uses ActiveSupportpart of a loop✕
Connections
2 pairs of types, where a type in ActiveSupport.Testing uses a type in ActiveSupport.
ActiveSupport.Testing uses ActiveSupport, so a change to ActiveSupport can break ActiveSupport.Testing, while a change to ActiveSupport.Testing can't break ActiveSupport.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
ActiveSupport uses ActiveSupport.Testing, so a change to ActiveSupport.Testing can break ActiveSupport, while a change to ActiveSupport can't break ActiveSupport.Testing.
Position
Below the diagonal: ActiveSupport uses a module listed above it, which is the healthy direction.
RuboCop.AST.NodePattern uses Parser.Source, so a change to Parser.Source can break RuboCop.AST.NodePattern, while a change to RuboCop.AST.NodePattern can't break Parser.Source.
Position
Below the diagonal: RuboCop.AST.NodePattern uses a module listed above it, which is the healthy direction.
28→29 RuboCop.AST.NodePattern uses RuboCop.ASTpart of a loop✕
Connections
1 pair of types, where a type in RuboCop.AST.NodePattern uses a type in RuboCop.AST.
RuboCop.AST.NodePattern uses RuboCop.AST, so a change to RuboCop.AST can break RuboCop.AST.NodePattern, while a change to RuboCop.AST.NodePattern can't break RuboCop.AST.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→31 RuboCop.AST.NodePattern uses (global)part of a loop✕
Connections
2 pairs of types, where a type in RuboCop.AST.NodePattern uses a type in (global).
The types involved
RuboCop.AST.NodePattern.Compiler → Forwardable
RuboCop.AST.NodePattern.Node → Forwardable
Direction
RuboCop.AST.NodePattern uses (global), so a change to (global) can break RuboCop.AST.NodePattern, while a change to RuboCop.AST.NodePattern can't break (global).
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
RuboCop.AST uses RuboCop.AST.NodePattern, so a change to RuboCop.AST.NodePattern can break RuboCop.AST, while a change to RuboCop.AST can't break RuboCop.AST.NodePattern.
Position
Below the diagonal: RuboCop.AST uses a module listed above it, which is the healthy direction.
ActiveSupport.Notifications uses Concurrent, so a change to Concurrent can break ActiveSupport.Notifications, while a change to ActiveSupport.Notifications can't break Concurrent.
Position
Below the diagonal: ActiveSupport.Notifications uses a module listed above it, which is the healthy direction.
ActiveSupport.Notifications uses ActiveSupport, so a change to ActiveSupport can break ActiveSupport.Notifications, while a change to ActiveSupport.Notifications can't break ActiveSupport.
Position
Below the diagonal: ActiveSupport.Notifications uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ActiveSupport.Notifications uses a type in (global).
The types involved
ActiveSupport.Notifications.Fanout → Hash
Direction
ActiveSupport.Notifications uses (global), so a change to (global) can break ActiveSupport.Notifications, while a change to ActiveSupport.Notifications can't break (global).
Position
Below the diagonal: ActiveSupport.Notifications uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A02:2025 — Security Misconfiguration
1295
High / Critical
A05:2025 — Injection
395
High / Critical
A03:2025 — Software Supply Chain Failures
9
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
A01:2025 — Broken Access Control
1
Medium
Roadmap
First, resolve the missing test coverage in Test Distribution and reconcile the README with the actual codebase to eliminate significant documentation drift. Next, implement structured JSON logging across all runnable modules to establish basic observability, and begin recording key design decisions in a dedicated ADR folder. Finally, integrate a static analysis security step into the CI pipeline to prevent security regressions from reaching production.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 No tests found finding(s) in Test Distribution.
Reconcile the README with reality: README omits the Kubernetes CRD/CustomResourceDefinition project entirely; README omits the Helm101 Wordpres project; DaemonSet101/README.md changes into `kubelabs/DaemonSet101`, but no such folder exists; Deployment101/README.md changes into `dockerlabs/kubernetes/workshop/Deployment101`, but no such folder exists; Gateway101/README.md documents the environment variable `GATEWAY_IP`, but no code, script or configuration file names it.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
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 — 120
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 — 1680
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 — 488
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
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
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 56 of 60 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 60 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2273 of 2288 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D1 Cyclomatic Complexity — not measured this run — Watchdog 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. Most of this repository's production source (.py) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D2 Cognitive Complexity — not measured this run — Watchdog 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. Most of this repository's production source (.py) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D4 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 206 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .py (44 lines, 100% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
D12 Dependency Hygiene — not measured this run — Watchdog 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. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
D15 Churn × Complexity Hotspots — not measured this run — Watchdog 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. A hotspot is churn × complexity. Churn was measured (1180 line(s) across the 90-day window), but no complexity could be computed for .py, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, 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. All 4 production source file(s) in this repository were read, and every one is under the ~2,400-byte (~100-line) size floor this dimension measures over (or declares itself generated), so there is no significant file to judge and knowledge concentration is not applicable. This is the size of the repository's files, not a file the engine failed to read.
D27 Navigability — not measured this run — Watchdog 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) — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `.bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/DNSKEY.rb`, `.bundles_cache/ruby/2.6.0/gems/execjs-2.8.1/lib/execjs/support/jsc_runner.js`, `.bundles_cache/ruby/2.6.0/gems/execjs-2.8.1/lib/execjs/support/jscript_runner.js`, `.bundles_cache/ruby/2.6.0/gems/execjs-2.8.1/lib/execjs/support/node_runner.js`, `.bundles_cache/ruby/2.6.0/gems/execjs-2.8.1/lib/execjs/support/spidermonkey_runner.js`, … (+5 more) 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.
D34 Knowledge Freshness — 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. All 4 production source file(s) in this repository were read, and every one is under the ~2,400-byte (~100-line) size floor this dimension measures over (or declares itself generated), so there is no significant file to judge and knowledge freshness is not applicable. This is the size of the repository's files, not a file the engine failed to read.
AC3 Page structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
AXR1 Runtime accessibility — not measured this run — Watchdog 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. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/bui…; runtime evidence skipped.
C1 Data Protection — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
GD1 Unfinished & placeholder code — not measured this run — Watchdog 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 reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — Watchdog 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 reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 45 further occurrence(s) are not listed individually; the score already reflects all 85.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X16 Unfloored truncation loop — not measured this run — Watchdog 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 reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X18 Disposal-pattern correctness — not measured this run — Watchdog 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X29 Per-element action decided by a fixed element — not measured this run — Watchdog 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 reads C# syntax, and JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X4 Structured logging — not measured this run — Watchdog 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 reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X5 Nullable reference types — not measured this run — Watchdog 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 reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D40 Network Egress Confinement: Egress confinement is read from committed Kubernetes manifests — a policy applied out-of-band (cluster-default deny, a service mesh, or a cloud firewall/security group off-repo) is invisible, and a present NetworkPolicy is declared config, not proof the cluster admission-controller actually enforces it at runtime.
D41 Kernel & Syscall Confinement: Syscall/MAC confinement is read from committed manifests — a profile applied by a cluster-wide PodSecurity default or a mutating webhook off-repo isn't seen, and a declared seccomp/AppArmor profile is config presence, not proof the node's kernel actually loaded and enforced it.
D42 Runtime Threat Enforcement: Runtime enforcement is read from committed policy files — a Tetragon/Falco/Kyverno stack installed cluster-wide (Helm release, platform add-on) with no in-repo trace can't be credited, and a committed policy is declared intent, not proof the engine is running and blocking in the live cluster.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (4): D19, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
206 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 4 of the 208 are in trees this repository does not ship — vendored, example/demo, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .py (100% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
+ 108 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 11 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with lexer-F0.rb (4), directory.rb (2), links.rb. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 9 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with lexer-F0.rb (2), copy_on_notify_observer_set.rb, KX.rb. — One of this dimension's main actionable groups (9 warning-level).
Resolve the 8 Duplicated block (16 lines × 2) finding(s) in Code Duplication — start with lexer-F0.rb (2), DNSKEY.rb, windows.rb. — One of this dimension's main actionable groups (8 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
3 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, and main-sequence distance (abstractness) is not computed for these modules yet.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 86 Low cohesion finding(s) in Cohesion (LCOM4) — start with node.rb (3), filters.rb (2), REDACTED (2). — One of this dimension's main actionable groups (86 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution0.0 / 10Critical✓ Tool-verified
What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.
Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 97 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 97 gem(s) a consumer installs — this repository's runtime declarations closed transitively over its committed REDACTED. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. This repository publishes itself under CC0-1.0, which is its own choice and is not judged here.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README is an excellent overview of Get Started with Kubernetes and its curated list of labs/tutorials (500+ Docker tutorials, K3s, Helm, Prometheus, best practices, production on GKE), plus a strong community section. The architecture/design docs are well written: the 201/README documents K3s, Helm, Prometheus, and cluster networking with four distinct networking problems solved by pods/localhost, services, external services, and pod-to-pod; DaemonSet101 explains what a DaemonSet is, why use them, how to create one, restrict to nodes, reach a daemonset pod; Deployment101 covers ReplicaSets vs Deployments, rolling updates, scaling, and cleanup; Gateway101 compares Ingress with Gateway API, walks through installing CRDs, creating the GatewayClass/Gateway/HTTPRoute, and advanced routing labs; IOT/README describes five Kubernetes resources for IoT (ReplicaSets, DaemonSets, Jobs) with implementation use cases; Ingress101 explains what an Ingress is vs NodePort/LoadBalancer. All these documents are well written and clearly scoped to their directories. The repository's READMEs are well written for the directories they document: each directory has a focused README explaining what it does and how to use its contents. The labels-and-selectors README is an excellent hands-on tutorial showing exactly how service selectors map pod IPs; the managed-kubernetes README explains why enterprise clusters need managed services versus self-hosted ones, with a clip that clips before the outline sections (Security101) are named; the monitoring pipeline and RBAC docs each have a strong overview plus clear examples. The Services101 README is the longest at 2577 words but ends in a clipped clip marker mid-sentence ('Kubernetes Service Without Pods?'); its outline exists, so it does not suffer from missing content. All documents are well-structured and complete for their scope. (6 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)
What to do
Improve Documentation Quality — currently 8.5/10. — The repository's root README is an excellent overview of Get Started with Kubernetes and its curated list of labs/tutorials (500+ Docker tutorials, K3s, Helm, Prometheus, best practices, production on GKE), plus a strong community section. The architecture/design docs are well written: the 201/README documents K3s, Helm, Prometheus, and cluster networking with four distinct networking problems solved by pods/localhost, services, external services, and pod-to-pod; DaemonSet101 explains what a DaemonSet is, why use them, how to create one, restrict to nodes, reach a daemonset pod; Deployment101 covers ReplicaSets vs Deployments, rolling updates, scaling, and cleanup; Gateway101 compares Ingress with Gateway API, walks through installing CRDs, creating the GatewayClass/Gateway/HTTPRoute, and advanced routing labs; IOT/README describes five Kubernetes resources for IoT (ReplicaSets, DaemonSets, Jobs) with implementation use cases; Ingress101 explains what an Ingress is vs NodePort/LoadBalancer. All these documents are well written and clearly scoped to their directories. The repository's READMEs are well written for the directories they document: each directory has a focused README explaining what it does and how to use its contents. The labels-and-selectors README is an excellent hands-on tutorial showing exactly how service selectors map pod IPs; the managed-kubernetes README explains why enterprise clusters need managed services versus self-hosted ones, with a clip that clips before the outline sections (Security101) are named; the monitoring pipeline and RBAC docs each have a strong overview plus clear examples. The Services101 README is the longest at 2577 words but ends in a clipped clip marker mid-sentence ('Kubernetes Service Without Pods?'); its outline exists, so it does not suffer from missing content. All documents are well-structured and complete for their scope. (6 of 25 sampled documents could not be assessed: 1 of 3 evaluation groups failed.)
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 0 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyStrong◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
5 API inconsistencies across a 400-member sample of 3817 exposed types.
Redundant methods returning the same semantic information (version string).
Duplicate intent across types. While `Array` and `Enumerable` are distinct, `including` is a specific collection manipulation that duplicates the intent of `+` or `concat` but with a different signature/behavior (returning a new array vs modifying or returning self depending on context). More critically, `excluding` and `without` exist on both `Array` and `Enumerable` with identical signatures and intent.
Naming inconsistency with `excluding`. `without` and `excluding` do the same thing (return a new collection without the specified elements). Having both names available on the same types creates confusion for users choosing between them.
Duplicate method signatures with different parameter names. This suggests either an aliasing issue or a copy-paste error in the API definition where the same method is exposed twice with different arity or naming conventions.
Duplicate method signatures with different parameter names, similar to `set_cache_for`.
What to do
Resolve the 1 Redundant methods returning the same semantic information (version… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Duplicate intent across types. While `Array` and `Enumerable` are… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Naming inconsistency with `excluding`. `without` and `excluding` do the… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
406 finding(s): 0 critical, 34 high, 371 medium, 1 low. 6 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 149 file(s) — `.bundles_cache/ruby/2.6.0/gems/coffee-script-source-1.11.1/lib/coffee_script/coffee-script.js`, `.bundles_cache/ruby/2.6.0/gems/commonmarker-0.23.9/ext/commonmarker/blocks.c` (line 67, line 71, line 192, …), `.bundles_cache/ruby/2.6.0/gems/commonmarker-0.23.9/ext/commonmarker/buffer.c` (line 34), `.bundles_cache/ruby/2.6.0/gems/commonmarker-0.23.9/ext/commonmarker/buffer.h` (line 34, line 41, line 44, …), `.bundles_cache/ruby/2.6.0/gems/commonmarker-0.23.9/ext/commonmarker/chunk.h` (line 20, line 29, line 38, …), … (+144 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 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
REDACTED
REDACTED
+ 19 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED, REDACTED. — One of this dimension's main actionable groups (5 issue-level).
No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no REDACTED is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 5 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 982 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (77), REDACTED (50), REDACTED (50). — One of this dimension's main actionable groups (982 warning-level).
Resolve the 264 Low IaC finding(s) in IaC & Container Security — start with REDACTED (18), REDACTED (18), REDACTED (14). — One of this dimension's main actionable groups (264 recommendation-level).
Resolve the 49 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (49 issue-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)9.0 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using Watchdog's own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
1 finding(s): 0 critical, 0 high, 1 medium, 0 low. semgrep could not parse 10 file(s) — `.bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/DNSKEY.rb`, `.bundles_cache/ruby/2.6.0/gems/execjs-2.8.1/lib/execjs/support/jsc_runner.js`, `.bundles_cache/ruby/2.6.0/gems/execjs-2.8.1/lib/execjs/support/jscript_runner.js`, `.bundles_cache/ruby/2.6.0/gems/execjs-2.8.1/lib/execjs/support/node_runner.js`, `.bundles_cache/ruby/2.6.0/gems/execjs-2.8.1/lib/execjs/support/spidermonkey_runner.js`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. 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.
What it measures: Whether Kubernetes workloads restrict network EGRESS with a NetworkPolicy (or Cilium policy), limiting where a compromised pod can send data or reach a command-and-control server. Presence of committed egress-restricting policy, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn — language-agnostic): Kubernetes workloads gate applicability; credits a NetworkPolicy / Cilium policy that restricts egress (policyTypes: [Egress] / egress rules). Reward-leaning (neutral floor climbing to 10, never a deduction — baseline misconfigs stay with D31). Deterministic.
What it measures: Whether Kubernetes workloads confine the kernel boundary — a seccomp profile (RuntimeDefault/Localhost) plus an AppArmor/SELinux mandatory-access-control layer — shrinking the syscall attack surface a container escape would use. Presence of committed confinement config, not runtime enforcement.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a seccomp profile (RuntimeDefault/Localhost) and an AppArmor/SELinux MAC layer. Reward-leaning (neutral floor climbing to 10); NotApplicable without workloads. Deterministic.
Resolve the 72 No seccomp profile finding(s) in Kernel & Syscall Confinement — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (72 recommendation-level).
Resolve the 72 No AppArmor/SELinux confinement finding(s) in Kernel & Syscall Confinement — start with REDACTED (4), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (72 recommendation-level).
Detailed fixes: d41_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the Kubernetes deployment wires runtime threat enforcement — a detection engine (Tetragon/Falco) and/or an admission-control policy gate (Kyverno / OPA Gatekeeper / PodSecurity). Presence of committed policy, not a runtime guarantee.
Method: Deterministic YAML-manifest inspection (no external tool, no Roslyn): on Kubernetes workloads, credits a runtime threat-detection engine (Tetragon TracingPolicy / Falco) and an admission-control policy (Kyverno / OPA Gatekeeper / PodSecurity). Reward-leaning; NotApplicable without workloads. Deterministic.
Resolve the 1 No runtime threat detection finding(s) in Runtime Threat Enforcement. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d42_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 18 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives7.2 / 10Strong✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — REDACTED:46, REDACTED:50, REDACTED:29
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.1 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×7) — Deployment101_slides/Deployment101.html:47, Deployment101_slides/Deployment101.html:48, Pods101_slides/Pods101.html:48, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×18) — REDACTED:2, REDACTED:2, REDACTED:2, …
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×9) — .bundles_cache/ruby/2.6.0/gems/jekyll-swiss-1.0.0/REDACTED:2, REDACTED:2, .bundles_cache/ruby/2.6.0/gems/kramdown-2.3.2/data/kramdown/document.html:2, …
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div>, so there is no content here to wrap — render the <main> from the component mounted into it. — .bundles_cache/ruby/2.6.0/gems/jekyll-swiss-1.0.0/REDACTED:2
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. (×5) — REDACTED:6, REDACTED:10, REDACTED:14, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/assets/output.html.erb:236
An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/assets/output.html.erb:236
An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>. (×5) — Deployment101_slides/Deployment101.html:3, Kubernetes_Intro_slides-1/Kubernetes_Intro_slides-1.html:3, Pods101_slides/Pods101.html:3, …
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.page-header` sets color: #fff on background-color: #159957 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _site/assets/css/style.css:636
`header h2` sets color: #e69b95 on background-color: #7c334f — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-merlot-0.2.0/assets/css/mobile.css:178
`.markdown-body .anchor:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-markdown/lib/markdown-body.scss:56
`section #title` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-midnight-0.2.0/_sass/jekyll-theme-midnight.scss:241
`.anim-fade-up` moves (`animation-name: fade-up`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:49
`.anim-fade-down` moves (`animation-name: fade-down`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:70
`.anim-grow-x` moves (`animation-name: grow-x`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:91
`.anim-shrink-x` moves (`animation-name: shrink-x`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:104
`.anim-scale-in` moves (`animation-name: scale-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:117
`.anim-pulse-in` moves (`animation-name: pulse-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:158
`.hover-grow` moves (`transition: transform 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:178
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 68 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Enforce accessibility in the toolchain your project already uses: assert accessibility in your UI test suite with your toolkit's own matcher (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in CI so a regression blocks the merge.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether 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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`EventableChannel` declares 16 abstract methods: `close`, `getBinding`, `getOutboundDataSize`, `getPeerName`, `getSockName`, `isNotifyReadable`, `isNotifyWritable`, `isWatchOnly`, `readInboundData`, `register`, `scheduleClose`, `scheduleOutboundData`, `scheduleOutboundDatagram`, `setCommInactivityTimeout`, `startTls`, `writeOutboundData`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/java/src/com/rubyeventmachine/EventableChannel.java:36
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no 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.
Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
What to do
Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
README omits the Kubernetes CRD/CustomResourceDefinition project entirely — reported by the model that read the README against this repository; no term search was run for this one, so nothing here has been checked against the tree. Treat it as a reading to confirm, not as a measured contradiction: verify it against the code before acting on it, and if the footprint it describes does exist, this row is wrong. — README.md:1
README omits the Helm101 Wordpres project — reported by the model that read the README against this repository; no term search was run for this one, so nothing here has been checked against the tree. Treat it as a reading to confirm, not as a measured contradiction: verify it against the code before acting on it, and if the footprint it describes does exist, this row is wrong. — README.md:1
DaemonSet101/README.md changes into `kubelabs/DaemonSet101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — DaemonSet101/README.md:41
Deployment101/README.md changes into `dockerlabs/kubernetes/workshop/Deployment101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Deployment101/README.md:20
Gateway101/README.md documents the environment variable `GATEWAY_IP`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Gateway101/README.md:199
Labels-and-Selectors/README.MD changes into `kubelabs/Labels-and-Selectors/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Labels-and-Selectors/README.MD:11
ReplicationController101/readme.md changes into `kubelabs/ReplicationController101/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — ReplicationController101/readme.md:8
Services101/README.md changes into `kubelabs/Services101/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — Services101/README.md:21
ai/README.md changes into `kubeview/charts/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — ai/README.md:38
bluegreen/README.md changes into `kubelabs/bluegreen`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — bluegreen/README.md:14
dockerdesktopformac/README.md documents the environment variable `KOPS_CLUSTER_NAME`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — dockerdesktopformac/README.md:52
intermediate/README.md links to `./compose-on-kubernetes-for-minikube.md`, but `intermediate/compose-on-kubernetes-for-minikube.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — intermediate/README.md:78
intermediate/README.md links to `./bootstrapping-gKE-cluster-docker-desktop-mac.md`, but `intermediate/bootstrapping-gKE-cluster-docker-desktop-mac.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — intermediate/README.md:82
replicaset101/README.md changes into `dockerlabs/kubernetes/workshop/replicaset101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — replicaset101/README.md:44
_site/DaemonSet101/README.md changes into `kubelabs/DaemonSet101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/DaemonSet101/README.md:41
_site/Deployment101/README.md changes into `dockerlabs/kubernetes/workshop/Deployment101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/Deployment101/README.md:20
_site/Labels&Selectors/README.MD changes into `kubelabs/Labels&Selectors/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/Labels&Selectors/README.MD:11
_site/Services101/README.md changes into `kubelabs/Services101/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/Services101/README.md:21
_site/dockerdesktopformac/README.md documents the environment variable `KOPS_CLUSTER_NAME`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/dockerdesktopformac/README.md:52
_site/intermediate/README.md links to `./compose-on-kubernetes-for-minikube.md`, but `_site/intermediate/compose-on-kubernetes-for-minikube.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/intermediate/README.md:78
_site/intermediate/README.md links to `./bootstrapping-gKE-cluster-docker-desktop-mac.md`, but `_site/intermediate/bootstrapping-gKE-cluster-docker-desktop-mac.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/intermediate/README.md:82
_site/replicaset101/README.md changes into `dockerlabs/kubernetes/workshop/replicaset101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/replicaset101/README.md:44
helm/wordpress/README.md documents the environment variable `SERVICE_IP`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — helm/wordpress/README.md:89
_site/helm/wordpress/README.md documents the environment variable `SERVICE_IP`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — _site/helm/wordpress/README.md:89
.bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/README.md links to `docs-source/synchronization.md`, but `.bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/docs-source/synchronization.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/README.md:61
.bundles_cache/ruby/2.6.0/gems/faraday-net_http-3.0.2/README.md links to `rubygems`, but `.bundles_cache/ruby/2.6.0/gems/faraday-net_http-3.0.2/rubygems` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/faraday-net_http-3.0.2/README.md:38
.bundles_cache/ruby/2.6.0/gems/html-pipeline-2.14.3/README.md names `script/changelog`, but no file or folder `script/changelog` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/html-pipeline-2.14.3/README.md:366
.bundles_cache/ruby/2.6.0/gems/jekyll-3.9.3/README.markdown links to `codeclimate`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-3.9.3/codeclimate` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-3.9.3/README.markdown:6
.bundles_cache/ruby/2.6.0/gems/jekyll-3.9.3/README.markdown links to `CODE_OF_CONDUCT.markdown`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-3.9.3/CODE_OF_CONDUCT.markdown` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-3.9.3/README.markdown:42
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-architect-0.2.0/README.md links to `thumbnail.png`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-architect-0.2.0/thumbnail.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-architect-0.2.0/README.md:7
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-architect-0.2.0/README.md links to `docs/CONTRIBUTING.md`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-architect-0.2.0/docs/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-architect-0.2.0/README.md:102
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-cayman-0.2.0/README.md links to `thumbnail.png`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-cayman-0.2.0/thumbnail.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-cayman-0.2.0/README.md:7
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-cayman-0.2.0/README.md links to `docs/CONTRIBUTING.md`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-cayman-0.2.0/docs/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-cayman-0.2.0/README.md:102
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-dinky-0.2.0/README.md links to `thumbnail.png`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-dinky-0.2.0/thumbnail.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-dinky-0.2.0/README.md:7
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-dinky-0.2.0/README.md links to `docs/CONTRIBUTING.md`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-dinky-0.2.0/docs/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-dinky-0.2.0/README.md:102
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-leap-day-0.2.0/README.md links to `thumbnail.png`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-leap-day-0.2.0/thumbnail.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-leap-day-0.2.0/README.md:7
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-leap-day-0.2.0/README.md links to `docs/CONTRIBUTING.md`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-leap-day-0.2.0/docs/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-leap-day-0.2.0/README.md:102
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-merlot-0.2.0/README.md links to `thumbnail.png`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-merlot-0.2.0/thumbnail.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-merlot-0.2.0/README.md:7
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-merlot-0.2.0/README.md links to `docs/CONTRIBUTING.md`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-merlot-0.2.0/docs/CONTRIBUTING.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-merlot-0.2.0/README.md:102
.bundles_cache/ruby/2.6.0/gems/jekyll-theme-midnight-0.2.0/README.md links to `thumbnail.png`, but `.bundles_cache/ruby/2.6.0/gems/jekyll-theme-midnight-0.2.0/thumbnail.png` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — .bundles_cache/ruby/2.6.0/gems/jekyll-theme-midnight-0.2.0/README.md:7
What to do
Reconcile the README with reality: README omits the Kubernetes CRD/CustomResourceDefinition project entirely; README omits the Helm101 Wordpres project; DaemonSet101/README.md changes into `kubelabs/DaemonSet101`, but no such folder exists; Deployment101/README.md changes into `dockerlabs/kubernetes/workshop/Deployment101`, but no such folder exists; Gateway101/README.md documents the environment variable `GATEWAY_IP`, but no code, script or configuration file names it.
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.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability0.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 8 Python production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Log through `logging.getLogger(__name__)` (or structlog) with a JSON formatter at meaningful points in the modules you run.
Consider OpenTelemetry tracing/metrics (opentelemetry-sdk) and a health-check endpoint (a /health route) for operability.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 6322 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: bandit, `semgrep --config=p/python`, or CodeQL's python pack — so a security regression fails the build instead of landing.
Dependabot is configured but does not watch `gitsubmodule` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Add an approval/environment gate (required reviewers / protection rules) before production promotion.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://buttons.github.io/buttons.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 5 such include(s) across the repository's markup. — .bundles_cache/ruby/2.6.0/gems/jekyll-swiss-1.0.0/_includes/head.html:16
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx-custom.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — _site/secerts_configmaps101/nginx-custom.conf:1
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
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.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items 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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 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.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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
Not included — 57 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Python 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.
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
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
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
Install the buildx component to build images with BuildKit:
https://docs.docker.com/go/bui…; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route and starts no server another machine can reach (no Flask/FastAPI/Starlette route, Django urlpatterns or class-based view, Tornado handler). Access control is therefore N/A here — a library or command-line tool is authorized by the application that serves 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 field (email, first_name, date_of_birth, phone, …) or stored credential in a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or MongoEngine model, a migration or a SQL schema — and no database or data-store client (Django ORM, SQLAlchemy, psycopg, PyMongo, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store 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 on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported 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 on a Django, SQLAlchemy, SQLModel, Peewee, Tortoise or mongoengine model, in a migration or in a SQL schema — and no database or data-store client (django.db, sqlalchemy, psycopg2, pymongo, sqlite3, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D1 Cyclomatic Complexity — cyclomatic complexity not measured — .py exposed no member bodies
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Dependency hygiene not measured
D15 Churn × Complexity Hotspots — complexity unreadable for .py — churn × complexity hotspots could not be measured
D16 Bus Factor — every production source file is under the ~100-line size floor — too little code for knowledge concentration to be judged
D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
D2 Cognitive Complexity — cognitive complexity not measured — .py exposed no member bodies
D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
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. 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 reads resolved call sites in the languages it reads only — this repository's production source is .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D3 God Classes — Most of this repository's production source (.py) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
D34 Knowledge Freshness — every production source file is under the ~100-line size floor — too little code for knowledge freshness to be judged
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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 — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 191 value object(s); 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one
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
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — 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'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python 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 — no coverage report found on disk — produce a coverage report in a standard format (`coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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 applicable: Python runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
PF3 Async & latency hygiene — Not applicable: Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X2 Cancellation propagation — no C# was loaded; this repository's Python was read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
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.
X29 Per-element action decided by a fixed element — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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 — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
<html> without a lang .bundles_cache/ruby/2.6.0/gems/jekyll-swiss-1.0.0/REDACTED:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang REDACTED:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang .bundles_cache/ruby/2.6.0/gems/kramdown-2.3.2/data/kramdown/document.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/assets/output.html.erb:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang Deployment101_slides/Deployment101.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang Kubernetes_Intro_slides-1/Kubernetes_Intro_slides-1.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang Pods101_slides/Pods101.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang SlidesReplicaSet101/ReplicaSet101.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang Slides_Services101/Services101.html:3— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels· Link with no accessible name · ×7
Link with no accessible name Deployment101_slides/Deployment101.html:47— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name Deployment101_slides/Deployment101.html:48— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name Pods101_slides/Pods101.html:48— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name Pods101_slides/Pods101.html:49— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name SlidesReplicaSet101/ReplicaSet101.html:39— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name SlidesReplicaSet101/ReplicaSet101.html:40— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name Slides_Services101/Services101.html:31— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Viewport restricts zoom REDACTED:6— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom REDACTED:10— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom REDACTED:14— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom REDACTED:17— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom REDACTED:11— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC3 · Page structure· Document <title> is empty · ×5
Document <title> is empty Deployment101_slides/Deployment101.html:3— An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
Document <title> is empty Kubernetes_Intro_slides-1/Kubernetes_Intro_slides-1.html:3— An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
Document <title> is empty Pods101_slides/Pods101.html:3— An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
Document <title> is empty SlidesReplicaSet101/ReplicaSet101.html:3— An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
Document <title> is empty Slides_Services101/Services101.html:3— An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
AC1 · Text alternatives· <img> without a text alternative · ×3
<img> without a text alternative REDACTED:46— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative REDACTED:50— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative REDACTED:29— An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
Low cohesion: Client (LCOM4 164) .bundles_cache/ruby/2.6.0/gems/octokit-4.25.1/lib/octokit/client.rb:72— Client's methods fall into 164 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 164 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: EvaluationContext (LCOM4 69) REDACTED:492— EvaluationContext's methods fall into 69 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 69 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Filters (LCOM4 35) .bundles_cache/ruby/2.6.0/gems/jekyll-seo-tag-2.8.0/lib/jekyll-seo-tag/filters.rb:5— Filters's methods fall into 35 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 35 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Filters (LCOM4 35) .bundles_cache/ruby/2.6.0/gems/jekyll-titles-from-headings-0.5.3/lib/jekyll-titles-from-headings/filters.rb:4— Filters's methods fall into 35 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 35 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Request (LCOM4 14) REDACTED:25— Request's methods fall into 14 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 14 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NodeSet (LCOM4 13) .bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/xml/node_set.rb:9— NodeSet's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: HtmlRenderer (LCOM4 11) .bundles_cache/ruby/2.6.0/gems/commonmarker-0.23.9/lib/commonmarker/renderer/html_renderer.rb:4— HtmlRenderer's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Module (LCOM4 10) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/module/attr_internal.rb:3— Module's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Chain (LCOM4 10) .bundles_cache/ruby/2.6.0/gems/i18n-1.13.0/lib/i18n/backend/chain.rb:19— Chain's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: EnterpriseManagementConsoleClient (LCOM4 10) .bundles_cache/ruby/2.6.0/gems/octokit-4.25.1/lib/octokit/enterprise_management_console_client.rb:15— EnterpriseManagementConsoleClient's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Node (LCOM4 10) .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/tree/node.rb:30— Node's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Profiler (LCOM4 9) .bundles_cache/ruby/2.6.0/gems/liquid-4.0.4/lib/liquid/profiler.rb:43— Profiler's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TernaryParentheses (LCOM4 9) .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/style/ternary_parentheses.rb:57— TernaryParentheses's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Node (LCOM4 9) .bundles_cache/ruby/2.6.0/gems/rubocop-ast-1.28.1/lib/rubocop/ast/node.rb:21— Node's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: InputStream (LCOM4 9) .bundles_cache/ruby/2.6.0/gems/rubyzip-2.3.2/lib/zip/input_stream.rb:41— InputStream's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Resource (LCOM4 9) .bundles_cache/ruby/2.6.0/gems/sawyer-0.9.2/lib/sawyer/resource.rb:4— Resource's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: CallbackChain (LCOM4 8) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/callbacks.rb:520— CallbackChain's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WatchStack (LCOM4 8) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/dependencies.rb:105— WatchStack's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DescendantsArray (LCOM4 8) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/descendants_tracker.rb:70— DescendantsArray's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Tuple (LCOM4 8) .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/tuple.rb:20— Tuple's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: InputIterator (LCOM4 8) .bundles_cache/ruby/2.6.0/gems/liquid-4.0.4/lib/liquid/standardfilters.rb:457— InputIterator's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TagRegistry (LCOM4 8) .bundles_cache/ruby/2.6.0/gems/liquid-4.0.4/lib/liquid/template.rb:21— TagRegistry's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Reader (LCOM4 8) .bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/xml/reader.rb:32— Reader's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Pathutil (LCOM4 8) .bundles_cache/ruby/2.6.0/gems/pathutil-0.16.2/lib/pathutil.rb:9— Pathutil's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SymbolTable (LCOM4 8) REDACTED:869— SymbolTable's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
AC3 · Page structure· Page without a main landmark · ×19
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .bundles_cache/ruby/2.6.0/gems/jekyll-swiss-1.0.0/REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div>, so there is no content here to wrap — render the <main> from the component mounted into it.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .bundles_cache/ruby/2.6.0/gems/kramdown-2.3.2/data/kramdown/document.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/assets/output.html.erb:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark Deployment101_slides/Deployment101.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark Kubernetes_Intro_slides-1/Kubernetes_Intro_slides-1.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark Pods101_slides/Pods101.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark SlidesReplicaSet101/ReplicaSet101.html:3— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/html-proofer-3.19.4/lib/html-proofer/check/links.rb:156— .bundles_cache/ruby/2.6.0/gems/html-proofer-3.19.4/lib/html-proofer/check/links.rb:156-162 | .bundles_cache/ruby/2.6.0/gems/html-proofer-3.19.4/lib/html-proofer/check/scripts.rb:34-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) REDACTED:32— REDACTED:32-38 | REDACTED:61-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb:63— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb:63-69 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/directory.rb:57-63 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/directory.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb:73— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb:73-79 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/directory.rb:67-73 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/directory.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12662— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12662-12668 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14606-14612 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12678— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12678-12684 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14622-14628 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12761— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12761-12767 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14705-14711 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12761` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12799— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12799-12805 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14743-14749 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/webrick-1.8.1/lib/webrick/cgi.rb:158— .bundles_cache/ruby/2.6.0/gems/webrick-1.8.1/lib/webrick/cgi.rb:158-164 | .bundles_cache/ruby/2.6.0/gems/webrick-1.8.1/lib/webrick/httpservlet/abstract.rb:103-109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/style/negated_if.rb:77— .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/style/negated_if.rb:77-83 | .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/style/negated_unless.rb:67-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/01_eventmachine_echo_server.rb:12— .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/01_eventmachine_echo_server.rb:12-18 | .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/02_eventmachine_echo_server_that_recognizes_exit_command.rb:16-22 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/01_eventmachine_echo_server.rb` and `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/02_eventmachine_echo_server_that_recognizes_exit_command.rb` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/collection/copy_on_notify_observer_set.rb:99— .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/collection/copy_on_notify_observer_set.rb:99-103 | .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/collection/copy_on_write_observer_set.rb:87-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/KX.rb:39— .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/KX.rb:39-43 | .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/RT.rb:40-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/MINFO.rb:43— .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/MINFO.rb:43-47 | .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/RP.rb:48-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) .bundles_cache/ruby/2.6.0/gems/jekyll-commonmark-ghpages-0.4.0/lib/jekyll-commonmark-ghpages.rb:74— .bundles_cache/ruby/2.6.0/gems/jekyll-commonmark-ghpages-0.4.0/lib/jekyll-commonmark-ghpages.rb:74-78 | .bundles_cache/ruby/2.6.0/gems/kramdown-2.3.2/lib/kramdown/converter/base.rb:238-242 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) REDACTED:312— REDACTED:312-316 | .bundles_cache/ruby/2.6.0/gems/kramdown-2.3.2/lib/kramdown/converter/latex.rb:256-260 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12771— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12771-12775 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14715-14719 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12779— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12779-12783 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14723-14727 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/script/tree/interpolation.rb:105— .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/script/tree/interpolation.rb:105-109 | .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/script/tree/string_interpolation.rb:75-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) REDACTED:62— REDACTED:62-66 | REDACTED:60-64 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/DNSKEY.rb:177— .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/DNSKEY.rb:177-192 | REDACTED:205-220 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/windows.rb:54— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/windows.rb:54-69 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/windows.rb:52-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb:21— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb:21-36 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/directory.rb:18-33 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/directory.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/file.rb:16— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/file.rb:16-31 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/file.rb:11-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/listener.rb:45— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/listener.rb:45-60 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/listener.rb:42-57 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) .bundles_cache/ruby/2.6.0/gems/octokit-4.25.1/lib/octokit/enterprise_management_console_client/management_console.rb:107— .bundles_cache/ruby/2.6.0/gems/octokit-4.25.1/lib/octokit/enterprise_management_console_client/management_console.rb:107-122 | .bundles_cache/ruby/2.6.0/gems/octokit-4.25.1/lib/octokit/enterprise_management_console_client/management_console.rb:131-146 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8384— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8384-8399 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8251-8266 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (16 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12727— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12727-12742 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14671-14686 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×7
Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:49— `.anim-fade-up` moves (`animation-name: fade-up`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:70— `.anim-fade-down` moves (`animation-name: fade-down`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:91— `.anim-grow-x` moves (`animation-name: grow-x`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:104— `.anim-shrink-x` moves (`animation-name: shrink-x`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:117— `.anim-scale-in` moves (`animation-name: scale-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:158— `.anim-pulse-in` moves (`animation-name: pulse-in`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-utilities/lib/animations.scss:178— `.hover-grow` moves (`transition: transform 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Duplicated block (13 lines × 2) .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:824— .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:824-836 | .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:2006-2018 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/backend.rb:16— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/backend.rb:16-28 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/backend.rb:12-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9645— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9645-9657 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11875-11887 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10926— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10926-10938 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10097-10109 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12453— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12453-12465 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12773-12785 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/selector/pseudo.rb:252— .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/selector/pseudo.rb:252-264 | .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/selector/pseudo.rb:266-278 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/formatter/offense_count_formatter.rb:49— .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/formatter/offense_count_formatter.rb:49-61 | .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/formatter/worst_offenders_formatter.rb:37-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (25 lines × 2) .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing05.rb:103— .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing05.rb:103-127 | .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing07.rb:125-149 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing05.rb` and `.bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing07.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 75 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 (25 lines × 2) .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb:176— .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb:176-200 | .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/fastfilereader/extconf.rb:59-83 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb` and `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/fastfilereader/extconf.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (25 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9535— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9535-9561 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11117-11141 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (25 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9760— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9760-9784 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10909-10933 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9275— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9275-9299 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10081-10105 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/xml_mini/jdom.rb:121— .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/xml_mini/jdom.rb:121-132 | .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/xml_mini/rexml.rb:104-115 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:612— .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:612-623 | .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:665-676 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/silencer/controller.rb:35— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/silencer/controller.rb:35-46 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/silencer/controller.rb:33-44 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/silencer/controller.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/silencer/controller.rb` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) .bundles_cache/ruby/2.6.0/gems/webrick-1.8.1/lib/webrick/httpauth/htdigest.rb:73— .bundles_cache/ruby/2.6.0/gems/webrick-1.8.1/lib/webrick/httpauth/htdigest.rb:73-84 | .bundles_cache/ruby/2.6.0/gems/webrick-1.8.1/lib/webrick/httpauth/htpasswd.rb:104-115 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/base.rb:17— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/base.rb:17-28 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/base.rb:16-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/date_time/calculations.rb:90— .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/date_time/calculations.rb:90-100 | .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/calculations.rb:195-205 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb:7— .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb:7-17 | .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/fastfilereader/extconf.rb:3-13 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb` and `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/fastfilereader/extconf.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) REDACTED:231— REDACTED:231-241 | REDACTED:244-254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) .bundles_cache/ruby/2.6.0/gems/rexml-3.2.5/lib/rexml/validation/relaxng.rb:377— .bundles_cache/ruby/2.6.0/gems/rexml-3.2.5/lib/rexml/validation/relaxng.rb:377-387 | .bundles_cache/ruby/2.6.0/gems/rexml-3.2.5/lib/rexml/validation/relaxng.rb:451-461 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/scss/parser.rb:830— .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/scss/parser.rb:830-840 | .bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/scss/parser.rb:966-976 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/sass-3.7.4/lib/sass/scss/parser.rb:830` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) REDACTED:213— REDACTED:213-223 | .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/resource/RRSIG.rb:168-177 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:213` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) .bundles_cache/ruby/2.6.0/gems/ffi-1.15.5/lib/ffi/enum.rb:98— .bundles_cache/ruby/2.6.0/gems/ffi-1.15.5/lib/ffi/enum.rb:98-107 | .bundles_cache/ruby/2.6.0/gems/ffi-1.15.5/lib/ffi/enum.rb:194-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/cli.rb:46— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/cli.rb:46-56 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/cli.rb:44-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/silencer/controller.rb:7— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/silencer/controller.rb:7-16 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/silencer/controller.rb:5-14 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/silencer/controller.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/silencer/controller.rb` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/style/trailing_body_on_class.rb:26— .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/style/trailing_body_on_class.rb:26-35 | .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/style/trailing_body_on_module.rb:26-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/date_time/calculations.rb:79— .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/date_time/calculations.rb:79-87 | .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/calculations.rb:184-192 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) REDACTED:652— REDACTED:652-660 | REDACTED:778-786 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9 lines × 2) .bundles_cache/ruby/2.6.0/gems/simpleidn-0.2.1/lib/simpleidn.rb:234— .bundles_cache/ruby/2.6.0/gems/simpleidn-0.2.1/lib/simpleidn.rb:234-242 | .bundles_cache/ruby/2.6.0/gems/simpleidn-0.2.1/lib/simpleidn.rb:258-266 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12696— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12696-12704 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14640-14648 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/bundler/duplicated_gem.rb:64— .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/bundler/duplicated_gem.rb:64-72 | .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/gemspec/duplicated_assignment.rb:91-99 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/java_thread_pool_executor.rb:103— .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/java_thread_pool_executor.rb:103-110 | .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/executor/ruby_thread_pool_executor.rb:119-126 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) .bundles_cache/ruby/2.6.0/gems/kramdown-2.3.2/lib/kramdown/converter/kramdown.rb:131— .bundles_cache/ruby/2.6.0/gems/kramdown-2.3.2/lib/kramdown/converter/kramdown.rb:131-138 | .bundles_cache/ruby/2.6.0/gems/kramdown-2.3.2/lib/kramdown/converter/kramdown.rb:155-162 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/linux.rb:87— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/linux.rb:87-94 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/linux.rb:89-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) REDACTED:33— REDACTED:33-40 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/php.rb:57-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) .bundles_cache/ruby/2.6.0/gems/html-pipeline-2.14.3/lib/html/pipeline/@mention_filter.rb:129— .bundles_cache/ruby/2.6.0/gems/html-pipeline-2.14.3/lib/html/pipeline/@mention_filter.rb:129-136 | .bundles_cache/ruby/2.6.0/gems/html-pipeline-2.14.3/lib/html/pipeline/@team_mention_filter.rb:88-95 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/linux.rb:56— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/linux.rb:56-72 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/linux.rb:59-75 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) REDACTED:70— REDACTED:70-86 | REDACTED:68-84 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9920— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9920-9936 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9394-9410 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (17 lines × 2) .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/formatter/clang_style_formatter.rb:18— .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/formatter/clang_style_formatter.rb:18-34 | .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/formatter/tap_formatter.rb:45-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10942— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10942-10957 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10112-10127 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12972-12987 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (16 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11591— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11591-11606 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11864-11879 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12061-12076 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11621— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11621-11636 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11894-11909 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12116-12131 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (16 lines × 3) .bundles_cache/ruby/2.6.0/gems/yell-2.2.2/examples/003.1-formatting-DefaultFormat.rb:5— .bundles_cache/ruby/2.6.0/gems/yell-2.2.2/examples/003.1-formatting-DefaultFormat.rb:5-21 | .bundles_cache/ruby/2.6.0/gems/yell-2.2.2/examples/003.2-formatting-BasicFormat.rb:5-21 | .bundles_cache/ruby/2.6.0/gems/yell-2.2.2/examples/003.3-formatting-ExtendedFormat.rb:5-20 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (14 lines × 2) .bundles_cache/ruby/2.6.0/gems/ethon-0.16.0/profile/memory_leaks.rb:78— .bundles_cache/ruby/2.6.0/gems/ethon-0.16.0/profile/memory_leaks.rb:78-91 | .bundles_cache/ruby/2.6.0/gems/ethon-0.16.0/profile/memory_leaks.rb:93-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/ethon-0.16.0/profile/memory_leaks.rb:78` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) REDACTED:45— REDACTED:45-58 | REDACTED:43-56 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) .bundles_cache/ruby/2.6.0/gems/octokit-4.25.1/lib/octokit/client/oauth_applications.rb:72— .bundles_cache/ruby/2.6.0/gems/octokit-4.25.1/lib/octokit/client/oauth_applications.rb:72-85 | .bundles_cache/ruby/2.6.0/gems/octokit-4.25.1/lib/octokit/client/oauth_applications.rb:103-116 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12626— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12626-12639 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14570-14583 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) .bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/html5/node.rb:39— .bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/html5/node.rb:39-44 | .bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/xml/node.rb:1257-1262 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `.bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/html5/node.rb:37` calls `super` and `.bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/xml/node.rb:1256` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb:74— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb:74-79 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/bsd.rb:72-78 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/bsd.rb` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) .bundles_cache/ruby/2.6.0/gems/json-2.6.3/lib/json/add/ostruct.rb:18— .bundles_cache/ruby/2.6.0/gems/json-2.6.3/lib/json/add/ostruct.rb:18-23 | .bundles_cache/ruby/2.6.0/gems/json-2.6.3/lib/json/add/struct.rb:17-22 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb:87— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb:87-92 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/bsd.rb:86-91 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/bsd.rb` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (36 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9718— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9718-9753 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11181-11216 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (36 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10805— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10805-10840 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11685-11720 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (36 lines × 2) .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/clojure.rb:18— .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/clojure.rb:18-73 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/hylang.rb:18-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/clojure.rb:18` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (29 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10359— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10359-10387 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9732-9760 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (29 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10867— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10867-10895 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10041-10069 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (29 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11907— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11907-11935 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10741-10769 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (27–28 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9319— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9319-9345 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11201-11228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9319` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (27–28 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9738— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9738-9765 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10098-10124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10098` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (27–28 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9066— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9066-9092 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10664-10691 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (24 lines × 2) .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb:139— .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb:139-162 | .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/fastfilereader/extconf.rb:30-53 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb` and `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/fastfilereader/extconf.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 60 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8992— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8992-9015 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9336-9359 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (24 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9143— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9143-9166 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9656-9680 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (15 lines × 2) .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/update.rb:225— .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/update.rb:225-239 | .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/lib/dnsruby/update.rb:274-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb:56— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb:56-70 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/bsd.rb:54-68 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/bsd.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/bsd.rb` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 3 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8608— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8608-8622 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8464-8478 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×2
Focus outline removed in CSS without a :focus replacement .bundles_cache/ruby/2.6.0/gems/jekyll-theme-primer-0.6.0/_sass/primer-markdown/lib/markdown-body.scss:56— `.markdown-body .anchor:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement .bundles_cache/ruby/2.6.0/gems/jekyll-theme-midnight-0.2.0/_sass/jekyll-theme-midnight.scss:241— `section #title` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Duplicated block (35–36 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9145— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9145-9179 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10074-10109 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (35–36 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9981— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9981-10016 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10599-10633 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (34 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10144— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10144-10177 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11223-11256 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (34 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11471— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11471-11504 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10484-10517 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (32 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8614— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8614-8645 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3403-3434 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8614` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (32 lines × 2) .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/coffeescript.rb:16— .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/coffeescript.rb:16-47 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/haxe.rb:15-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (29 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11999— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11999-12027 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:13198-13226 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:13366-13394 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (29 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12068— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12068-12096 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12142-12171 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12223-12252 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12068` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (26–27 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8990— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8990-9015 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11349-11375 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (26–27 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9451— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9451-9476 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11218-11244 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (27 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10161— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10161-10187 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11276-11302 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11877— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11877-11903 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10712-10738 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (26 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9129— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9129-9154 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11669-11694 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (26 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11363— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11363-11390 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11438-11463 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (24–25 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8678— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8678-8701 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10390-10414 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (24–25 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8807— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8807-8830 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10586-10610 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (22 lines × 5) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11517— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11517-11538 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11926-11947 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10760-10781 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11956-11977 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12506-12527 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (22 lines × 5) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11617— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11617-11638 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11641-11662 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11665-11686 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11689-11710 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11713-11734 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11617` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8468— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8468-8488 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8335-8355 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 × 2) REDACTED:146— REDACTED:146-166 | REDACTED:176-196 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20–21 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11591— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11591-11610 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11863-11883 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (20–21 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11621— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11621-11640 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11893-11913 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19–20 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9191— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9191-9210 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9767-9785 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10916-10934 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19–20 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11946— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11946-11965 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11967-11985 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11988-12006 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) .bundles_cache/ruby/2.6.0/gems/faraday-2.7.4/lib/faraday/encoders/flat_params_encoder.rb:24— .bundles_cache/ruby/2.6.0/gems/faraday-2.7.4/lib/faraday/encoders/flat_params_encoder.rb:24-42 | .bundles_cache/ruby/2.6.0/gems/faraday-2.7.4/lib/faraday/encoders/nested_params_encoder.rb:12-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (19 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10437— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10437-10455 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9763-9781 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (17 lines × 3) .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing03.rb:109— .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing03.rb:109-125 | .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing05.rb:113-129 | .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing07.rb:135-151 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing03.rb` and `.bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing05.rb` as WHOLE FILES: 83% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12109— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12109-12125 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10930-10946 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12676-12692 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (15 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12056— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12056-12070 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10880-10894 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12626-12640 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (15 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12091— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12091-12105 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10913-10927 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12659-12673 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/range/compare_range.rb:17— .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/range/compare_range.rb:17-27 | .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/range/compare_range.rb:42-52 | .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/range/compare_range.rb:67-77 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8549— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8549-8559 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8416-8426 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3341-3351 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–9 lines × 2) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/calculations.rb:75— .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/time/calculations.rb:75-83 | .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/values/time_zone.rb:447-454 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/values/time_zone.rb:447` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 2) REDACTED:96— REDACTED:96-104 | REDACTED:96-103 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:96` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12750— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12750-12757 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:14694-14701 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:5398-5405 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/layout/argument_alignment.rb:72— .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/layout/argument_alignment.rb:72-79 | .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/layout/array_alignment.rb:67-74 | .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/lib/rubocop/cop/layout/parameter_alignment.rb:102-109 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/assets/output.html.erb:236— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Empty <h3> heading .bundles_cache/ruby/2.6.0/gems/rubocop-0.93.1/assets/output.html.erb:236— An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative.
Low contrast colour pair in CSS (3.7:1) _site/assets/css/style.css:636— `.page-header` sets color: #fff on background-color: #159957 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (3.9:1) .bundles_cache/ruby/2.6.0/gems/jekyll-theme-merlot-0.2.0/assets/css/mobile.css:178— `header h2` sets color: #e69b95 on background-color: #7c334f — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — No accessibility enforcement found — no accessibility linting at author time and no automated accessibility check in tests or CI. Add your UI toolkit's own accessibility assertion to the test suite (Flutter `meetsGuideline`, Espresso `AccessibilityChecks`, XCTest `performAccessibilityAudit`), then gate that test in the pipeline. What was searched, so you can tell an absence from a miss: the 68 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
D22 · Internal API Consistency· Redundant methods returning the same semantic information (version string). · ×1
Redundant methods returning the same semantic information (version string). — Deprecate and remove one of them (likely `gem_version` if `version` is the standard Ruby convention, or vice versa depending on internal usage) to provide a single source of truth. (signatures: ActiveSupport.gem_version() | ActiveSupport.version())
D22 · Internal API Consistency· Duplicate intent across types. While `Array` and `Enumerable` are distinct, `including` is a specific collection manipulation that duplicates the intent of `+` or `concat` but with a different signature/behavior (returning a new array vs modifying or returning self depending on context). More critically, `excluding` and `without` exist on both `Array` and `Enumerable` with identical signatures and intent. · ×1
Duplicate intent across types. While `Array` and `Enumerable` are distinct, `including` is a specific collection manipulation that duplicates the intent of `+` or `concat` but with a different signature/behavior (returning a new array vs modifying or returning self depending on context). More critically, `excluding` and `without` exist on both `Array` and `Enumerable` with identical signatures and intent. — Ensure `excluding` and `without` are aliases or that one is deprecated. `excluding` is more descriptive of the operation (removing elements), while `without` is more natural language. Having both on the same type is confusing; having them on both `Array` and `Enumerable` is acceptable if they are aliases, but the API surface suggests they are distinct methods with potentially subtle behavioral differences that are not documented here. If they are identical, alias them. (signatures: Array.including(elements) | Enumerable.including(elements))
D22 · Internal API Consistency· Naming inconsistency with `excluding`. `without` and `excluding` do the same thing (return a new collection without the specified elements). Having both names available on the same types creates confusion for users choosing between them. · ×1
Naming inconsistency with `excluding`. `without` and `excluding` do the same thing (return a new collection without the specified elements). Having both names available on the same types creates confusion for users choosing between them. — Standardize on one name (e.g., `excluding` is more explicit about the action) and deprecate the other, or make them strict aliases. (signatures: Array.without(elements) | Enumerable.without(elements))
D22 · Internal API Consistency· Duplicate method signatures with different parameter names. This suggests either an aliasing issue or a copy-paste error in the API definition where the same method is exposed twice with different arity or naming conventions. · ×1
Duplicate method signatures with different parameter names. This suggests either an aliasing issue or a copy-paste error in the API definition where the same method is exposed twice with different arity or naming conventions. — Remove the duplicate signature. If it's an alias, document it as such. If it's a distinct overload, ensure the parameter names reflect the difference (e.g., one might be a shorthand). Given `l` and `v` are likely just short for `local_cache_key` and `value`, this is likely a redundant alias. (signatures: Cache.Strategy.LocalCache.LocalCacheRegistry.set_cache_for(local_cache_key, value) | Cache.Strategy.LocalCache.LocalCacheRegistry.set_cache_for(l, v))
D22 · Internal API Consistency· Duplicate method signatures with different parameter names, similar to `set_cache_for`. · ×1
Duplicate method signatures with different parameter names, similar to `set_cache_for`. — Remove the duplicate signature. (signatures: Cache.Strategy.LocalCache.LocalCacheRegistry.cache_for(local_cache_key) | Cache.Strategy.LocalCache.LocalCacheRegistry.cache_for(l))
Near-duplicate member pair (60 shared lines) .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb:5— .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/extconf.rb:5-270 | .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/ext/fastfilereader/extconf.rb:3-109 — These two members are variants of one another: 60 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8384— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8384-8411 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8251-8278 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (260 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10765— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10765-11024 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12511-12770 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10765` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (112 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10102— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10102-10213 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12962-13073 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (90–91 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8800— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8800-8890 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8507-8596 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8507` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (61–62 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12567— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12567-12628 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4934-4994 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (58 lines × 9) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3565— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3565-3622 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3774-3831 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3966-4023 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4091-4148 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4150-4207 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4284-4341 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4452-4509 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4553-4610 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4729-4786 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (49 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8416— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8416-8464 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8283-8331 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (43 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8951— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8951-8993 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9443-9485 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10215-10257 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10288-10330 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (43 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8569— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8569-8611 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3358-3400 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (42–43 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12457— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12457-12498 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12833-12875 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (42 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3632— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3632-3673 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3841-3882 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4351-4392 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4620-4661 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (42 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9182— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9182-9223 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9490-9531 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (38–40 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8725— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8725-8764 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8938-8977 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10204-10241 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (40 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:13187— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:13187-13226 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:13355-13394 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (38–39 lines × 9) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8731— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8731-8768 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8944-8981 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9014-9051 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9174-9212 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9436-9473 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9483-9520 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9799-9837 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10208-10245 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10280-10318 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (37–38 lines × 9) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9050— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9050-9087 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9280-9317 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9355-9392 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9557-9594 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9967-10004 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10048-10084 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10478-10515 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11049-11086 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11151-11188 — all 9 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10048` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (37–38 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9286— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9286-9322 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11055-11092 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11157-11193 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12481-12517 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (38 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3700— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3700-3737 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3901-3938 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (36–37 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9433— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9433-9468 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10014-10050 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (35–36 lines × 5) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8952— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8952-8986 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9444-9478 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10216-10250 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10289-10323 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11252-11287 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (34–36 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12138— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12138-12171 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12218-12253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (35 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8544— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8544-8578 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8411-8445 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (34–35 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8821— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8821-8854 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9510-9544 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (24–34 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9512— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9512-9535 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9549-9582 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10470-10503 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11143-11176 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (31–34 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9086— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9086-9119 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10244-10274 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (30–34 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9136— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9136-9169 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9480-9509 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (31–33 lines × 2) .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing05.rb:27— .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing05.rb:27-57 | .bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing07.rb:25-57 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing05.rb` and `.bundles_cache/ruby/2.6.0/gems/em-websocket-0.5.3/lib/em-websocket/framing07.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 75 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 (31–32 lines × 18) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3622— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3622-3653 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3690-3720 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3730-3761 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3831-3862 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3891-3921 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3931-3962 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4023-4054 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4065-4095 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4207-4238 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4241-4271 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4341-4372 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4393-4423 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4425-4456 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4509-4540 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4610-4641 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4670-4700 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4702-4733 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:4786-4817 — all 18 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (32 lines × 10) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9056— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9056-9087 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9286-9317 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9361-9392 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9563-9594 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9973-10004 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10053-10084 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10484-10515 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11055-11086 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11157-11188 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12481-12512 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (32 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9361— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9361-9392 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9843-9876 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10484-10516 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (26–32 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9967— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9967-9992 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11451-11482 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (31 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12353— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12353-12383 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12391-12421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (30 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11011— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11011-11040 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12137-12166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (29 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10405— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10405-10433 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10762-10790 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9954-9982 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11438-11466 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (27–29 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9078— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9078-9106 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9463-9489 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10235-10262 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (28 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12794— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12794-12821 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12884-12911 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12917-12944 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:13082-13109 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (28 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9715— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9715-9742 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11178-11205 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11828-11855 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (25–28 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11730— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11730-11757 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11760-11785 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11813-11837 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (28 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9422— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9422-9449 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11815-11842 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (26–27 lines × 5) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9157— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9157-9182 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9307-9333 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9435-9460 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10016-10042 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10087-10112 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (27 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10176— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10176-10202 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10957-10983 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12703-12729 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:13036-13062 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (23–27 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9686— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9686-9712 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9732-9754 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (25–26 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8833— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8833-8857 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8972-8997 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9256-9281 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10309-10334 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (25–26 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9381— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9381-9405 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11629-11654 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 5) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8971— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8971-8996 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9078-9102 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9463-9488 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10235-10260 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10308-10333 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (23–25 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9744— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9744-9766 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10849-10873 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11195-11217 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (24–25 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10816— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10816-10839 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10890-10914 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11696-11719 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (25 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8832— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8832-8856 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9254-9280 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9522-9546 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (24 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9421— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9421-9444 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11731-11757 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11761-11785 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11814-11837 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23–24 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11850— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11850-11873 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10687-10709 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10687` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 6) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9132— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9132-9154 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9422-9444 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11672-11694 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11732-11757 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11762-11785 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11815-11837 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9144— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9144-9166 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:9657-9680 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:10073-10096 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (23 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11522— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11522-11544 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11931-11953 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11522` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (22 lines × 4) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11761— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11761-11782 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11785-11806 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11809-11830 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11833-11854 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11761` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9769— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9769-9790 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12205-12226 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12202` calls `on_newline` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:9767` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19–20 lines × 7) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10699— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10699-10718 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11612-11630 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11636-11654 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11660-11678 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11684-11702 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11708-11726 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11732-11750 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (19–20 lines × 6) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10728— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10728-10747 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11756-11774 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11780-11798 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11804-11822 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11828-11846 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11852-11870 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (18 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12024— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12024-12041 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10850-10867 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12596-12613 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 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 (17–18 lines × 2) .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/module/attribute_accessors.rb:52— .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/module/attribute_accessors.rb:52-69 | .bundles_cache/ruby/2.6.0/gems/activesupport-6.1.7.3/lib/active_support/core_ext/module/attribute_accessors.rb:116-132 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/base.rb:36— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/adapter/base.rb:36-53 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/adapter/base.rb:34-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12074— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:12074-12087 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:10897-10910 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:12643-12656 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 7) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11588— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11588-11600 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11609-11621 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11633-11645 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11657-11669 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11681-11693 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11705-11717 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11729-11741 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 6) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11618— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:11618-11630 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11753-11765 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11777-11789 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11801-11813 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11825-11837 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:11849-11861 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11–13 lines × 2) .bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/html5/document_fragment.rb:59— .bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/html5/document_fragment.rb:59-71 | .bundles_cache/ruby/2.6.0/gems/nokogiri-1.13.10-x86_64-linux/lib/nokogiri/xml/searchable.rb:252-262 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (12 lines × 3) .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8613— .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb:8613-8624 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb:8469-8480 | .bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-strings.rb:3402-3413 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F0.rb` and `.bundles_cache/ruby/2.6.0/gems/parser-3.2.2.1/lib/parser/lexer-F1.rb` as WHOLE FILES: this scan already matched 38 separate duplicated blocks between them, totalling at least 741 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–12 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb:41— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb:41-50 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/directory.rb:38-49 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/directory.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/directory.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9–10 lines × 2) .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:139— .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:139-148 | .bundles_cache/ruby/2.6.0/gems/addressable-2.8.4/lib/addressable/uri.rb:1276-1284 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (57 lines × 2) .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/fiber_local_var.rb:50— .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/fiber_local_var.rb:50-106 | .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/thread_local_var.rb:52-108 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (20 lines × 2) .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/listener/config.rb:18— .bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/listener/config.rb:18-37 | .bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/listener/config.rb:16-41 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/listen-3.8.0/lib/listen/listener/config.rb` and `.bundles_cache/ruby/2.6.0/gems/sass-listen-4.0.0/lib/sass-listen/listener/config.rb` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31 lines × 6) .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/apex.rb:15— .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/apex.rb:15-45 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/brightscript.rb:17-100 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/ecl.rb:17-92 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/idlang.rb:20-208 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/ocl.rb:12-50 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/yang.rb:17-82 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/ecl.rb` and `.bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/idlang.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (66 lines × 4) .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/brightscript.rb:17— .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/brightscript.rb:17-100 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/ecl.rb:17-92 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/idlang.rb:20-208 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/yang.rb:17-82 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/ecl.rb` and `.bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/idlang.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 567 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 (66 lines × 3) .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/ecl.rb:17— .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/ecl.rb:17-92 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/idlang.rb:20-208 | .bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/yang.rb:17-82 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/ecl.rb` and `.bundles_cache/ruby/2.6.0/gems/rouge-3.26.0/lib/rouge/lexers/idlang.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 567 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/immutable_struct.rb:83— .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/immutable_struct.rb:83-89 | .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/mutable_struct.rb:211-217 | .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/settable_struct.rb:106-112 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (22–23 lines × 2) .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/demo/digdlv.rb:63— .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/demo/digdlv.rb:63-84 | .bundles_cache/ruby/2.6.0/gems/dnsruby-1.70.0/demo/rubydig.rb:68-90 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (123 lines × 2) .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/03_simple_chat_server.rb:19— .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/03_simple_chat_server.rb:19-149 | .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/08_simple_chat_server_step_five.rb:19-141 — before extracting anything, compare `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/03_simple_chat_server.rb` and `.bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/examples/guides/getting_started/08_simple_chat_server_step_five.rb` as WHOLE FILES: 99% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
No structured logging — No logging call was found in the 8 Python production file(s) this check read across 1 module(s). Each was searched for its ecosystem's logging libraries (Python: logging, structlog, loguru) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Third-party script without Subresource Integrity .bundles_cache/ruby/2.6.0/gems/jekyll-swiss-1.0.0/_includes/head.html:16— `https://buttons.github.io/buttons.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 5 such include(s) across the repository's markup.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:5— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:1— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:1— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:4— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No seccomp profile REDACTED:2— Workloads do not set a seccomp profile (RuntimeDefault or a Localhost profile). Seccomp blocks the syscalls a container never needs, shrinking the kernel attack surface a container escape would use.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:5— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:1— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:1— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:4— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
No AppArmor/SELinux confinement REDACTED:2— Workloads declare no AppArmor or SELinux profile. A mandatory-access-control profile confines what a compromised container can touch on the host, complementing seccomp's syscall filter.
README/code drift README.md:1— README omits the Kubernetes CRD/CustomResourceDefinition project entirely — reported by the model that read the README against this repository; no term search was run for this one, so nothing here has been checked against the tree. Treat it as a reading to confirm, not as a measured contradiction: verify it against the code before acting on it, and if the footprint it describes does exist, this row is wrong.
README/code drift README.md:1— README omits the Helm101 Wordpres project — reported by the model that read the README against this repository; no term search was run for this one, so nothing here has been checked against the tree. Treat it as a reading to confirm, not as a measured contradiction: verify it against the code before acting on it, and if the footprint it describes does exist, this row is wrong.
README/code drift DaemonSet101/README.md:41— DaemonSet101/README.md changes into `kubelabs/DaemonSet101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Deployment101/README.md:20— Deployment101/README.md changes into `dockerlabs/kubernetes/workshop/Deployment101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Gateway101/README.md:199— Gateway101/README.md documents the environment variable `GATEWAY_IP`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Labels-and-Selectors/README.MD:11— Labels-and-Selectors/README.MD changes into `kubelabs/Labels-and-Selectors/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift ReplicationController101/readme.md:8— ReplicationController101/readme.md changes into `kubelabs/ReplicationController101/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift Services101/README.md:21— Services101/README.md changes into `kubelabs/Services101/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift ai/README.md:38— ai/README.md changes into `kubeview/charts/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift bluegreen/README.md:14— bluegreen/README.md changes into `kubelabs/bluegreen`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift dockerdesktopformac/README.md:52— dockerdesktopformac/README.md documents the environment variable `KOPS_CLUSTER_NAME`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift intermediate/README.md:78— intermediate/README.md links to `./compose-on-kubernetes-for-minikube.md`, but `intermediate/compose-on-kubernetes-for-minikube.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift intermediate/README.md:82— intermediate/README.md links to `./bootstrapping-gKE-cluster-docker-desktop-mac.md`, but `intermediate/bootstrapping-gKE-cluster-docker-desktop-mac.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift replicaset101/README.md:44— replicaset101/README.md changes into `dockerlabs/kubernetes/workshop/replicaset101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/DaemonSet101/README.md:41— _site/DaemonSet101/README.md changes into `kubelabs/DaemonSet101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/Deployment101/README.md:20— _site/Deployment101/README.md changes into `dockerlabs/kubernetes/workshop/Deployment101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/Labels&Selectors/README.MD:11— _site/Labels&Selectors/README.MD changes into `kubelabs/Labels&Selectors/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/Services101/README.md:21— _site/Services101/README.md changes into `kubelabs/Services101/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/dockerdesktopformac/README.md:52— _site/dockerdesktopformac/README.md documents the environment variable `KOPS_CLUSTER_NAME`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/intermediate/README.md:78— _site/intermediate/README.md links to `./compose-on-kubernetes-for-minikube.md`, but `_site/intermediate/compose-on-kubernetes-for-minikube.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/intermediate/README.md:82— _site/intermediate/README.md links to `./bootstrapping-gKE-cluster-docker-desktop-mac.md`, but `_site/intermediate/bootstrapping-gKE-cluster-docker-desktop-mac.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/replicaset101/README.md:44— _site/replicaset101/README.md changes into `dockerlabs/kubernetes/workshop/replicaset101`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift helm/wordpress/README.md:89— helm/wordpress/README.md documents the environment variable `SERVICE_IP`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift _site/helm/wordpress/README.md:89— _site/helm/wordpress/README.md documents the environment variable `SERVICE_IP`, but no code, script or configuration file names it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/README.md:61— .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/README.md links to `docs-source/synchronization.md`, but `.bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/docs-source/synchronization.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2594— `!(loadFactor > 0.0f) || initialCapacity < 0 || concurrencyLevel <= 0` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:3422— `!collide && q != null && q.hash == p.hash` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:1799— `!onlyIfPresent && (val = mf.apply(k, null)) != null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/Striped64.java:209— `(as = cells) != null && (n = as.length) > 0` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/Striped64.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/Striped64.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/LongAdder.java:63— `(as = cells) != null || !casBase(b = base, b + x)` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/LongAdder.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/LongAdder.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2479— `(b = baseIndex) >= baseLimit || (i = index) < 0 || i >= n` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2482— `(e = tabAt(t, i)) != null && e.hash == MOVED` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2475— `(m = map) != null && (t = tab = m.table) != null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:3211— `(mk = e.getKey()) == null || (mv = e.getValue()) == null || (v = internalGet(mk)) == null || (mv != v && !mv.equals(v))` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:851— `(pk = (RubyObject)p.key) == k || k.equals(pk)` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:860— `(pr = p.right) != null && h >= pr.hash && (r = getTreeNode(h, k, pr)) != null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:1161— `(sl == null || !sl.red) && (sr == null || !sr.red)` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:1123— `(sr == null || !sr.red) && (sl == null || !sl.red)` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2451— `(t = it.tab) == null && (t = it.tab = m.table) != null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:3259— `(v = nextVal) == null && (v = advance()) == null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2224— `bin < 0 || nbuffered >= TRANSFER_BUFFER_SIZE` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:853— `c != (pc = (RubyClass)pk.getMetaClass()) || kNotComparable || (dir = rubyCompare(k, pk)) == 0` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:941— `c != (pc = pk.getMetaClass()) || kNotComparable || (dir = rubyCompare(k, pk)) == 0` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:1946— `entry == null || (k = entry.getKey()) == null || (v = entry.getValue()) == null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2500— `k == null && (advance() == null || (k = nextKey) == null)` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:3007— `key == null || oldValue == null || newValue == null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2889— `key == null || remappingFunction == null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:2968— `key == null || value == null || remappingFunction == null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:1189— `p == replacement && (pp = p.parent) != null` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Duplicated predicate .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java:3206— `v == null || (v != val && !v.equals(val))` appears character-identically in 2 files — .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/ConcurrentHashMapV8.java, .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/ext/concurrent-ruby/com/concurrent_ruby/ext/jsr166e/nounsafe/ConcurrentHashMapV8.java. 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.
Silent fallback default in rescue .bundles_cache/ruby/2.6.0/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/utility/processor_counter.rb:60— `compute_physical_processor_count` rescues every error into `1` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
Silent fallback default in rescue .bundles_cache/ruby/2.6.0/gems/rexml-3.2.5/lib/rexml/source.rb:240— `position` rescues every error into `0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
Silent fallback default in rescue .bundles_cache/ruby/2.6.0/gems/ruby-progressbar-1.13.0/lib/ruby-progressbar/calculators/length.rb:48— `terminal_width` rescues every error into `80` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
Fat interface: EventableChannel (16 abstract methods) .bundles_cache/ruby/2.6.0/gems/eventmachine-1.2.7/java/src/com/rubyeventmachine/EventableChannel.java:36— `EventableChannel` declares 16 abstract methods: `close`, `getBinding`, `getOutboundDataSize`, `getPeerName`, `getSockName`, `isNotifyReadable`, `isNotifyWritable`, `isWatchOnly`, `readInboundData`, `register`, `scheduleClose`, `scheduleOutboundData`, `scheduleOutboundDatagram`, `setCommInactivityTimeout`, `startTls`, `writeOutboundData`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No runtime threat detection — No runtime threat-detection engine (Tetragon TracingPolicy / Falco) is committed. These observe process, file and network activity in-kernel and can alert or kill on malicious behaviour a static scan cannot catch.
No tests — template/sample — This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here.
No tests found — No test suite could be collected — no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (pytest or unittest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here.
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.
No src/ separation — Production code isn't grouped under a src/ folder — it's spread across several top-level directories, so there's no one place that says 'this is the product'.
No SAST — No static application security testing detected. For this repository's stack, add bandit, `semgrep --config=p/python`, or CodeQL's python pack as a CI step. What was searched, so you can tell an absence from a miss: the 6322 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No security response headers detected _site/secerts_configmaps101/nginx-custom.conf:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx-custom.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X7 · Silent fallback defaults· Silent fallback default on lookup miss · ×1
Silent fallback default on lookup miss REDACTED:167— `file_checksum` answers `'_'` when `ENOENT` is raised, with no log or raise — a missing file, record or key silently becomes that value. Log the miss or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the rescue or above the method, and the row stops firing.
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.
provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
Run 01a15c3d-c97e-7415-8352-c42dc48c905b · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 120 · Warnings: 1680 · Recommendations: 488 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 02:15 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.