Public report of dependabot/dependabot-core, published 25 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 report Measured 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, 25 October 2026, 21:06 UTC · Survey ID cd_182eed1bdd34417f8df10adc0790a8de

dependabot/dependabot-core

Measured 25 October 2026, 20:45 UTC, at code version 7c06280

Regression: 4 dimensions fell since the last survey Code coverage: not measuredTest reliability: not measuredBoundary Type-Coupling: not measured

A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.

Code coverage is not measured: .NET suite (CouldNotMeasureNoCollector).

Test reliability is not measured: No runner for the .rb half of a polyglot repository.

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

CAI score 44out of 100 At risk Down 12 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.

Maturity 72 Strong Architecture 70 Adequate Production Readiness 61 Adequate Performance 60 Adequate Code Health 51 Adequate Security and Compliance 29 Weak

A large codebase: 172,562 lines of product code in 71 projects, tests not counted · Estimated rebuild effort: about 4.0 person-years · Weakest lens: Security and Compliance, 29

Findings by how serious they are

189 critical 1114 serious 108 minor

6 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
25 October 2026, 20:45 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 ▸

80of 80 dimensions measured by tools.
1383of 1411 findings point to an exact file and line, so you can open each one in the code. The other 28 concern the repository as a whole, such as missing documentation.
80dimensions across 6 lenses, read from 172,562 lines of product code in 71 projects.
Chapters

Executive summary

dependabot/dependabot-core is rated At risk because critical security findings are open. Its score is held back because it has passwords or keys in the code's history and automatic dependency updates that take new releases at once. It scores 44 out of 100, which the At risk rating leaves unchanged.

Security and Compliance, at 29, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the four runtimes or frameworks that no longer get security updates, worth about 5 points. Replacing the 18 passwords or keys found in the code's history would lift Security and Compliance itself, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 58.

Fifty-four automatic updates take new releases before a bad one can be spotted. Thirty-four known security holes in the packages the code depends on can be used by attackers, and eighteen passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Setting a waiting period for automatic updates, updating the vulnerable packages and replacing each exposed password or key would close these risks. The 14 unsafe settings in infrastructure or container files need changing to safe values. The nine places where the code runs text as code or as a command need a direct call instead. The 25 sets of compiler warnings switched off in projects need turning back on in the build file.

The product code is 172,562 lines, about €590,000 to rebuild.

Code Health 51 Adequate, capped by Explicit Debt Architecture 70 Adequate, capped by Import Boundaries Maturity 72 Strong Production Readiness 61 Adequate Security and Compliance 29 Weak, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities, IaC & Container Security and Platform End-of-Life Performance 60 Adequate

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

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

If Security and Compliance rose from 29 to 70, the lowest score rated Strong, the score would rise from 44 to about 58.

Code composition: what the lines of code are
Business logic 3%Supporting code 2%Tests 95%
New since the last survey: 117 findings

These 117 critical or serious findings weren't in the previous survey, on 11 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.

  • God Classes · TooManyMethods: PackageManagerHelper npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb
  • God Classes · TooManyMethods: PackageLatestVersionFinder npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb
  • Code Duplication · Edited copy of a member (23 corresponding lines) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Edited copy of a member (12 corresponding lines) bun/lib/dependabot/bun/package/registry_finder.rb
  • Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) bun/lib/dependabot/bun/requirement.rb
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) updater/lib/dependabot/api_client.rb
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) common/lib/dependabot/package/npm_package_json.rb
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) bundler/lib/dependabot/bundler/file_parser.rb
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) common/lib/dependabot/pull_request_creator.rb
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) bun/lib/dependabot/bun/package/registry_finder.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) common/lib/dependabot/update_checkers/vulnerability_audit.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb
  • Code Duplication · Duplicated block (23 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Duplicated block (21 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Duplicated block (15 lines × 2) bun/lib/dependabot/bun/metadata_finder.rb
  • Code Duplication · Duplicated block (8 lines × 2) apm/lib/dependabot/apm/version.rb
  • Code Duplication · Duplicated block (7 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Duplicated block (5 lines × 2) bundler/lib/dependabot/bundler/update_checker/cooldown_options_builder.rb
  • Code Duplication · Duplicated block (12 lines × 3) apm/lib/dependabot/apm/native_helpers.rb
  • Churn × Complexity Hotspots · Hotspot: composer/lib/dependabot/composer/file_updater/lockfile_updater.rb composer/lib/dependabot/composer/file_updater/lockfile_updater.rb
  • Churn × Complexity Hotspots · Hotspot: nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs
  • Explicit Debt · EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs
  • Explicit Debt · EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs
  • Explicit Debt · EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs
  • Explicit Debt · NoWarnInCsproj repeated across 10 files nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Build.Tasks/NuGet.Build.Tasks.csproj
  • Explicit Debt · NoWarnInCsproj repeated across 10 files nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Common/NuGet.Common.csproj
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Secrets (history) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Static Analysis (SAST) · REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • Dependency Vulnerabilities · REDACTED
  • IaC & Container Security · REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Platform End-of-Life · End-of-life runtime: Node.js 16 npm_and_yarn/spec/fixtures/projects/pnpm/peer_disambiguation_v6/package.json
  • Platform End-of-Life · End-of-life runtime: Node.js 18 npm_and_yarn/spec/fixtures/projects/yarn/submodule_dependency/package.json
  • Platform End-of-Life · End-of-life runtime: Node.js 20 npm_and_yarn/spec/fixtures/projects/pnpm/unsupported_engine_pnpm/package.json
  • Platform End-of-Life · End-of-life runtime: Node.js 23 npm_and_yarn/spec/fixtures/projects/pnpm/unmet_peer_deps/package.json
  • Code Duplication · Duplicated block (19 lines × 2 locations) REDACTED
  • Cyclomatic Complexity · Complex function findConflictingParentDependencies (cyclomatic 11, cognitive 15) REDACTED
  • Async correctness · Sync-over-async (deadlock risk) through `.Result` nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs
  • Cancellation propagation · Async method without CancellationToken: RunGitCommandAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Clone/ShellGitCommandHandler.cs
  • Cancellation propagation · Async method without CancellationToken: SolveAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/DependencySolver/MSBuildDependencySolver.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs
  • Cancellation propagation · Async local function without CancellationToken: EnsurePackagesForFileAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs
  • Cancellation propagation · Async method without CancellationToken: SaveAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Files/BuildFile.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Graph/GraphWorker.cs
  • Cancellation propagation · Async method without CancellationToken: GetIndexEOLsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/GitEOLMetadataProvider.cs
  • Cancellation propagation · Async method without CancellationToken: SendAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/HttpApiHandler.cs
  • Cancellation propagation · Async local function without CancellationToken: TrackOriginalContentsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ModifiedFilesTracker.cs
  • Exception handling · Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs
  • Exception handling · Swallowed exception (caught, then discarded) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs
  • Exception handling · Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs
  • Exception handling · Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/npm6/subdependency-updater.js
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/npm6/subdependency-updater.js
  • Async & latency hygiene · Sync-over-async blocking REDACTED
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/yarn/conflicting-dependency-parser.js
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/yarn/lockfile-parser.js
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/yarn/subdependency-updater.js
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/yarn/subdependency-updater.js
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/yarn/updater.js
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/yarn/updater.js
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/yarn/updater.js
  • Async & latency hygiene · Sync-over-async blocking bun/helpers/lib/yarn/updater.js
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs
  • Async & latency hygiene · Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs

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: 102 findings

These 102 critical or serious findings were in the previous survey, on 11 October 2026, and are gone from this one. The first 100 are listed here.

  • Cognitive Complexity · AnalyzeWorker.FindFirstCompatibleVersion (cognitive 18) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs
  • God Classes · FileTooLong: npm_and_yarn/file_parser.rb npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb
  • Code Duplication · Edited copy of a member (23 corresponding lines) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Edited copy of a member (12 corresponding lines) bun/lib/dependabot/bun/package/registry_finder.rb
  • Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) bun/lib/dependabot/bun/requirement.rb
  • Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) updater/lib/dependabot/api_client.rb
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) common/lib/dependabot/package/npm_package_json.rb
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) bundler/lib/dependabot/bundler/file_parser.rb
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) common/lib/dependabot/pull_request_creator.rb
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) bun/lib/dependabot/bun/package/registry_finder.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) common/lib/dependabot/update_checkers/vulnerability_audit.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb
  • Code Duplication · Duplicated block (30 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Duplicated block (27 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Duplicated block (25 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Duplicated block (15 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Duplicated block (8 lines × 2) bundler/lib/dependabot/bundler/update_checker/cooldown_options_builder.rb
  • Code Duplication · Duplicated block (12 lines × 2) go_modules/lib/dependabot/go_modules/native_helpers.rb
  • Code Duplication · Duplicated block (20 lines × 2) bun/lib/dependabot/bun/file_updater/package_json_updater.rb
  • Code Duplication · Duplicated block (13 lines × 2) bun/lib/dependabot/bun/update_checker.rb
  • Code Duplication · Duplicated block (9 lines × 2) bun/lib/dependabot/bun/update_checker.rb
  • Code Duplication · Duplicated block (12 lines × 2) bun/lib/dependabot/bun/update_checker.rb
  • Code Duplication · Duplicated block (11 lines × 2) bun/lib/dependabot/bun/update_checker/latest_version_finder.rb
  • Code Duplication · Duplicated block (9 lines × 2) bun/lib/dependabot/bun/update_checker/latest_version_finder.rb
  • Code Duplication · Duplicated block (10 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Code Duplication · Duplicated block (10 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb
  • Churn × Complexity Hotspots · Repeated repair: julia/lib/dependabot/julia/update_checker.rb julia/lib/dependabot/julia/update_checker.rb
  • Churn × Complexity Hotspots · Repeated repair: julia/lib/dependabot/julia/requirement.rb julia/lib/dependabot/julia/requirement.rb
  • Churn × Complexity Hotspots · Repeated repair: julia/lib/dependabot/julia/version.rb julia/lib/dependabot/julia/version.rb
  • Churn × Complexity Hotspots · Repeated repair: updater/lib/dependabot/fetched_files.rb updater/lib/dependabot/fetched_files.rb
  • Explicit Debt · NoWarnInCsproj repeated across 10 files nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Versioning/NuGet.Versioning.csproj
  • Explicit Debt · NoWarnInCsproj repeated across 10 files nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Resolver/NuGet.Resolver.csproj
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · High CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
  • Supply-chain Provenance & Signing · REDACTED
  • Code Duplication · Duplicated block (23 lines × 2 locations) REDACTED
  • Import Boundaries · Boundary violation [package:third-party-deep-import] npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts
  • Import Boundaries · Boundary violation [package:third-party-deep-import] npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts
  • Import Boundaries · Boundary violation [package:third-party-deep-import] npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts
  • Import Boundaries · Boundary violation [package:third-party-deep-import] npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts
  • Import Boundaries · Boundary violation [package:third-party-deep-import] npm_and_yarn/helpers/lib/yarn/updater.ts
  • Import Boundaries · Boundary violation [package:third-party-deep-import] npm_and_yarn/helpers/lib/yarn/updater.ts
  • Import Boundaries · Boundary violation [package:third-party-deep-import] npm_and_yarn/helpers/lib/yarn/updater.ts
  • Cancellation propagation · Async method without CancellationToken: StopTrackingAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ModifiedFilesTracker.cs
  • Cancellation propagation · Async method without CancellationToken: GetJsonElementAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/IHttpFetcher.cs
  • Cancellation propagation · Async method without CancellationToken: GetPullRequestBodyAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestTextGenerator.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs
  • Cancellation propagation · Async method without CancellationToken: ResolveRootDirectoriesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs
  • Cancellation propagation · Async method without CancellationToken: RunScenarioHandlersWithErrorHandlingAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs
  • Cancellation propagation · Async method without CancellationToken: PatchNuGetConfigFilesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs
  • Cancellation propagation · Async method without CancellationToken: RunGroupedDependencyUpdates nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs
  • Cancellation propagation · Async method without CancellationToken: RunEffectiveGroupUpdate nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs
  • Cancellation propagation · Async method without CancellationToken: RunUngroupedDependencyUpdates nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateBindingRedirectsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/BindingRedirectManager.cs
  • Cancellation propagation · Async method without CancellationToken: TryGetRuntimeConfigurationFile nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/BindingRedirectManager.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateDependencyAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/DotNetToolsJsonUpdater.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: ProcessNonProjectUpdatesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: ProcessPackagesConfigUpdatesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: ProcessPackageReferenceUpdatesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: GetOriginalFileContentsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: RestoreOriginalFileContentsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: TryPerformFileWritesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: ReadFileContentsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs
  • Cancellation propagation · Async method without CancellationToken: WriteFileContentsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateDependencyAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/GlobalJsonUpdater.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateLockFileAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/LockFileUpdater.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateDependencyAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackagesConfigUpdater.cs
  • Cancellation propagation · Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/UpdaterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: RunWithErrorHandlingAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/UpdaterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: WriteResultFile nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/UpdaterWorker.cs
  • Cancellation propagation · Async method without CancellationToken: GetDependenciesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs
  • Cancellation propagation · Async method without CancellationToken: PopulatePackageDependenciesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateVersion nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs
  • Cancellation propagation · Async method without CancellationToken: IsCompatibleAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs
  • Cancellation propagation · Async method without CancellationToken: FindCompatibleVersionAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs
  • Cancellation propagation · Async method without CancellationToken: AreAllParentsCompatibleAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs
  • Cancellation propagation · Async method without CancellationToken: HandleGlobalJsonAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: ResolveDependencyConflicts nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: CreateTempProjectAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetTargetFrameworkValuesFromProject nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetAllPackageDependenciesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetProjectTargetsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetProjectPropertiesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetProjectPropertyAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetProjectTargetFrameworksAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetProjectPropertyUsingCompatibilityTargetAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs
  • Cancellation propagation · Async method without CancellationToken: DownloadNuGetPackagesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/NuGetHelper.cs
  • Cancellation propagation · Async method without CancellationToken: GetCredentialProvidersAsync nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/Command.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateSelfAsync nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/UpdateCommand.cs
  • Cancellation propagation · Async method without CancellationToken: UpdateAllPackages nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/UpdateCommand.cs
  • Cancellation propagation · Async method without CancellationToken: UpdatePackagesAsync nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/UpdateCommand.cs
  • Exception handling · Swallowed exception (caught, then discarded) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs
  • Exception handling · Swallowed exception (caught, then discarded) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/IHttpFetcher.cs
  • Exception handling · Swallowed exception (caught, then discarded) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs
Rebuild cost: about €590,000 · Estimate
Cost to rebuild€190,000 to €980,000, for 3,224 to 10,286 hours of work, about 4.0 person-years for 2 to 8 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 44. 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.
SizeLarge: 172,562 lines of product code
Comment linesThe estimate prices 171,449 lines. Comment lines count towards the size of 172,562 lines but aren't priced as work.

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.

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 4 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (4).
Raises the score by about 5 points · Low effort · Platform End-of-Life
2
Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with SdkProjectDiscovery.cs (3), Program.cs (2), MSBuildHelper.cs.
Raises the score by about 3 points · Low effort · Explicit Debt
3
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with UpdaterWorker.cs, DependencyConflictResolver.cs.
Raises the score by about 3 points · Low effort · Explicit Debt

Diagnosis: what the measurements show together

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

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

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

arch dependabot-apm dependabot-apm dependabot-common dependabot-common dependabot-apm->dependabot-common dependabot-bazel dependabot-bazel dependabot-bazel->dependabot-common dependabot-bun dependabot-bun dependabot-bun->dependabot-common dependabot-bundler dependabot-bundler dependabot-bundler->dependabot-common dependabot-cargo dependabot-cargo dependabot-cargo->dependabot-common dependabot-composer dependabot-composer dependabot-composer->dependabot-common dependabot-conda dependabot-conda dependabot-conda->dependabot-common dependabot-python dependabot-python dependabot-conda->dependabot-python dependabot-docker dependabot-docker dependabot-docker->dependabot-common dependabot-docker_compose dependabot-docker_compose dependabot-docker_compose->dependabot-common dependabot-docker_compose->dependabot-docker dependabot-go_modules dependabot-go_modules dependabot-go_modules->dependabot-common dependabot-gradle dependabot-gradle dependabot-gradle->dependabot-common dependabot-maven dependabot-maven dependabot-gradle->dependabot-maven dependabot-helm dependabot-helm dependabot-helm->dependabot-common dependabot-helm->dependabot-docker dependabot-maven->dependabot-common dependabot-npm_and_yarn dependabot-npm_and_yarn dependabot-npm_and_yarn->dependabot-common dependabot-omnibus dependabot-omnibus dependabot-omnibus->dependabot-apm dependabot-omnibus->dependabot-bazel dependabot-omnibus->dependabot-bun dependabot-omnibus->dependabot-bundler dependabot-omnibus->dependabot-cargo dependabot-omnibus->dependabot-common dependabot-omnibus->dependabot-composer dependabot-omnibus->dependabot-conda dependabot-omnibus->dependabot-docker dependabot-omnibus->dependabot-docker_compose dependabot-omnibus->dependabot-go_modules dependabot-omnibus->dependabot-gradle dependabot-omnibus->dependabot-helm dependabot-omnibus->dependabot-maven dependabot-omnibus->dependabot-npm_and_yarn dependabot-pre_commit dependabot-pre_commit dependabot-omnibus->dependabot-pre_commit dependabot-omnibus->dependabot-python dependabot-sbt dependabot-sbt dependabot-omnibus->dependabot-sbt dependabot-uv dependabot-uv dependabot-omnibus->dependabot-uv dependabot-pre_commit->dependabot-bundler dependabot-pre_commit->dependabot-cargo dependabot-pre_commit->dependabot-common dependabot-pre_commit->dependabot-go_modules dependabot-pre_commit->dependabot-npm_and_yarn dependabot-pre_commit->dependabot-python dependabot-python->dependabot-common dependabot-sbt->dependabot-common dependabot-sbt->dependabot-maven dependabot-uv->dependabot-common dependabot-uv->dependabot-python __more__ +51 more projects

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.

342 modules, with 348 dependencies between them. 2 loops run through 7 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 302 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.
uses →1 Dependabot2 Dependabot.Ecosystem3 Dependabot.FileFetchers4 Dependabot.FileParsers5 Dependabot.FileUpdaters6 Dependabot.MetadataFinders7 Dependabot.Package8 Dependabot.UpdateCheckers9 Dependabot.Apm10 Dependabot.Bazel11 Dependabot.Bun12 Dependabot.Bundler13 Dependabot.Cargo14 Dependabot.Conda15 Dependabot.Devcontainers16 Dependabot.DotnetSdk17 Dependabot.Elm18 Dependabot.GitSubmodules19 Dependabot.GithubActions20 Dependabot.GoModules21 Dependabot.Hex22 Dependabot.Julia23 Dependabot.Maven.Shared24 Dependabot.Nix25 Dependabot.NpmAndYarn26 Dependabot.Opentofu27 Dependabot.PreCommit28 Dependabot.Pub29 Dependabot.Python30 Dependabot.RustToolchain31 Dependabot.Swift32 Dependabot.Terraform33 Dependabot.Vcpkg34 NuGetUpdater.Core.Run.ApiModel35 Dependabot.Gradle36 Dependabot.Maven37 NuGetUpdater.Core.Discover38 Dependabot.Sbt39 NuGetUpdater.Core40 NuGetUpdater.Core.Run
1 Dependabot
2 Dependabot.Ecosystem
3 Dependabot.FileFetchers
4 Dependabot.FileParsers
5 Dependabot.FileUpdaters
6 Dependabot.MetadataFinders
7 Dependabot.Package
8 Dependabot.UpdateCheckers
9 Dependabot.Apm3111111
10 Dependabot.Bazel2211111
11 Dependabot.Bun2311111
12 Dependabot.Bundler2211111
13 Dependabot.Cargo2221111
14 Dependabot.Conda2111111
15 Dependabot.Devcontainers2211111
16 Dependabot.DotnetSdk2211111
17 Dependabot.Elm2211111
18 Dependabot.GitSubmodules2111111
19 Dependabot.GithubActions2111111
20 Dependabot.GoModules2211111
21 Dependabot.Hex2211111
22 Dependabot.Julia3211111
23 Dependabot.Maven.Shared111
24 Dependabot.Nix2111111
25 Dependabot.NpmAndYarn2411111
26 Dependabot.Opentofu2111111
27 Dependabot.PreCommit2111111
28 Dependabot.Pub2211111
29 Dependabot.Python2511111
30 Dependabot.RustToolchain2111111
31 Dependabot.Swift2211111
32 Dependabot.Terraform2111111
33 Dependabot.Vcpkg2211111
34 NuGetUpdater.Core.Run.ApiModel3
35 Dependabot.Gradle1211112
36 Dependabot.Maven1211112
37 NuGetUpdater.Core.Discover116
38 Dependabot.Sbt2111121
39 NuGetUpdater.Core23
40 NuGetUpdater.Core.Run15310
Uses a module listed above itPart of a loopThe module itself
1 Dependabot2 Dependabot.Ecosystem3 Dependabot.FileFetchers4 Dependabot.FileParsers5 Dependabot.FileUpdaters6 Dependabot.MetadataFinders7 Dependabot.Package8 Dependabot.UpdateCheckers9 Dependabot.Apm10 Dependabot.Bazel11 Dependabot.Bun12 Dependabot.Bundler13 Dependabot.Cargo14 Dependabot.Conda15 Dependabot.Devcontainers16 Dependabot.DotnetSdk17 Dependabot.Elm18 Dependabot.GitSubmodules19 Dependabot.GithubActions20 Dependabot.GoModules21 Dependabot.Hex22 Dependabot.Julia23 Dependabot.Maven.Shared24 Dependabot.Nix25 Dependabot.NpmAndYarn26 Dependabot.Opentofu27 Dependabot.PreCommit28 Dependabot.Pub29 Dependabot.Python30 Dependabot.RustToolchain31 Dependabot.Swift32 Dependabot.Terraform33 Dependabot.Vcpkg34 NuGetUpdater.Core.Run.ApiModel35 Dependabot.Gradle36 Dependabot.Maven37 NuGetUpdater.Core.Discover38 Dependabot.Sbt39 NuGetUpdater.Core40 NuGetUpdater.Core.RunDependabot1Dependabot.Ecosystem2Dependabot.FileFetchers3Dependabot.FileParsers4Dependabot.FileUpdaters5Dependabot.MetadataFinders6Dependabot.Package7Dependabot.UpdateCheckers8Dependabot.Apm9Dependabot.Bazel10Dependabot.Bun11Dependabot.Bundler12Dependabot.Cargo13Dependabot.Conda14Dependabot.Devcontainers15Dependabot.DotnetSdk16Dependabot.Elm17Dependabot.GitSubmodules18Dependabot.GithubActions19Dependabot.GoModules20Dependabot.Hex21Dependabot.Julia22Dependabot.Maven.Shared23Dependabot.Nix24Dependabot.NpmAndYarn25Dependabot.Opentofu26Dependabot.PreCommit27Dependabot.Pub28Dependabot.Python29Dependabot.RustToolchain30Dependabot.Swift31Dependabot.Terraform32Dependabot.Vcpkg33NuGetUpdater.Core.Run.ApiModel34Dependabot.Gradle35Dependabot.Maven36NuGetUpdater.Core.Discover37Dependabot.Sbt38NuGetUpdater.Core39NuGetUpdater.Core.Run4031111112211111231111122111112221111211111122111112211111221111121111112111111221111122111113211111111211111124111112111111211111122111112511111211111122111112111111221111131211112121111211621111212315310+302 more modules (most-connected shown)

At a glance — Code Health · 51% · Adequate · gated by D17 ·

The Good
D3 · Ruby God Classes 7.7 D4 · Ruby Code Duplication 8.6 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 8.0 R10 · React / TS Code Duplication 7.5 R2 · React / TS Cyclomatic Complexity 10.0 R3 · React / TS Large Files 9.1 R7 · React / TS Dead Code 10.0 X1 · Repo Async correctness 7.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X32 · Repo Type resolved by simple name across every loaded assembly 10.0
The Bad
D1 · Ruby Cyclomatic Complexity 6.4 R1 · React / TS Type Safety 5.2 X18 · Repo Disposal-pattern correctness 5.1 X2 · Repo Cancellation propagation 5.2 X3 · Repo Exception handling 5.5 X4 · Repo Structured logging 6.6 X5 · Repo Nullable reference types 5.0
The Ugly
D2 · Ruby Cognitive Complexity 4.8 D17 · Ruby Explicit Debt 3.0

At a glance — Architecture · 70% · Adequate · gated by R11 ·

The Good
D5 · Ruby Coupling 9.7 D6 · Ruby Cohesion (LCOM4) 9.9 D26 · Ruby Project Cohesion 9.1 D35 · Ruby Change Coupling 9.9 AX10 · Repo Code composition 10.0 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0 R9 · React / TS Circular Imports 10.0
The Ugly
R11 · React / TS Import Boundaries 0.0

At a glance — Maturity · 72% · Strong ·

The Good
D15 · Ruby Churn × Complexity Hotspots 9.9 D34 · Ruby Knowledge Freshness 9.7 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0
The Bad
D16 · Ruby Bus Factor 5.9 D19 · Ruby Documentation Quality 5.0 D24 · Ruby Comment Value 6.8 M1 · Repo Documentation (README) 6.5 M2 · Repo Architecture documentation 5.0
The Ugly
D20 · Ruby ADR Quality 0.0

At a glance — Readiness · 61% · Adequate ·

The Good
D10 · Ruby Test Quality 10.0 D14 · Ruby License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P2 · Repo Observability 8.7 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 10.0 P6 · Repo Release Hygiene 10.0 R5 · React / TS Dependency Freshness 8.6 R6 · React / TS Tooling 10.0
The Bad
D13 · Ruby Secret Scanning 5.0 P10 · Repo Library API & versioning 6.0 R4 · React / TS Test Coverage 5.5 R8 · React / TS Dependency Hygiene 6.0
The Ugly
P5 · Repo DR & Backup 4.0

At a glance — Security · 29% · Weak · gated by D28, D29, D30, D31, D44 ·

The Good
D36 · Ruby Supply-chain Provenance & Signing 10.0 D43 · Ruby Malicious Dependencies 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Ugly
D28 · Ruby Secrets (history) 0.0 D29 · Ruby Static Analysis (SAST) 0.0 D30 · Ruby Dependency Vulnerabilities 0.0 D31 · Ruby IaC & Container Security 0.0 D44 · Ruby Platform End-of-Life 0.5

At a glance — Performance · 60% · Adequate ·

The Bad
PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection132High / Critical
A02:2025 — Security Misconfiguration99High / Critical
A03:2025 — Software Supply Chain Failures59High / Critical
A07:2025 — Authentication Failures20High / Critical

Roadmap

Begin by addressing the 18 high-severity secrets in history, focusing on REDACTED, REDACTED, and REDACTED, followed by resolving the 84 medium IaC findings in Dockerfiles. Next, update the four end-of-life runtime packages in package.json and clear the 23 explicit debt items in project configuration files. Finally, remediate the 28 high-severity dependency vulnerabilities, prioritizing REDACTED, REDACTED, and REDACTED.

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

Do thisHelpsEffortDimension
Resolve the 4 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (4).+5.0 ptsLowPlatform End-of-Life
Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with SdkProjectDiscovery.cs (3), Program.cs (2), MSBuildHelper.cs.+3.2 ptsLowExplicit Debt
Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with UpdaterWorker.cs, DependencyConflictResolver.cs.+3.2 ptsLowExplicit Debt
Resolve the 18 High secret finding(s) in Secrets (history) — start with REDACTED (8), REDACTED (7), REDACTED (3).+6.3 ptsMediumSecrets (history)
Resolve the 84 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (80), REDACTED (2), REDACTED.+5.6 ptsMediumIaC & Container Security
Resolve the 23 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (6), NuGet.CommandLine.csproj (2), NuGet.Frameworks.csproj (2).+3.6 ptsMediumExplicit Debt
Resolve the 28 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25), REDACTED, REDACTED.+3.4 ptsMediumDependency Vulnerabilities
Resolve the 53 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (53).+2.7 ptsMediumStatic Analysis (SAST)

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.1SlopDependency Vulnerabilities: Critical CVE: REDACTED
nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs1.0SlopExplicit Debt: EmptyCatchBlock
REDACTED2.7SlopIaC & Container Security: Critical IaC: REDACTED
REDACTED3.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.7SlopIaC & Container Security: High IaC: REDACTED
nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs3.8SlopExplicit Debt: EmptyCatchBlock
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.0MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.1MixedIaC & Container Security: Critical IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.1MixedStatic Analysis (SAST): Medium: REDACTED
nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs4.1MixedExplicit Debt: WriteOnlyPrivateField
REDACTED4.2MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.6MixedStatic Analysis (SAST): High: REDACTED
nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs4.6MixedExplicit Debt: EmptyCatchBlock
REDACTED4.8MixedSecrets (history): High secret: REDACTED
REDACTED5.0MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED

How the grades work

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

Critical — 189

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 — 1114

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 — 108

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

Could not be resolved — 6

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

Methodology & how to trust this report

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. 80 of 80 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. 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 — 80 dimensions across the health lenses
D1D2D3D4D5D6D10D13D14D15D16D17D19D20D24D26D28D29D30D31D34D35D36D43D44AX10AX3AX5AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P5P6PF3R1R10R11R2R3R4R5R6R7R8R9X1X12X13X14X15X16X17X18X19X2X20X21X22X23X24X25X26X27X28X29X3X30X32X4X5

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

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

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement—◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a174cf-93fe-7747-8ee5-5f8f521e2e87.

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

Run transparency — what happened this run

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

  • D9 Test Distribution — 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. Test distribution NOT SCORED: this repository's production source spans more than one ecosystem, and the test-pyramid census cannot read the .rb test suite(s) — so the pyramid was not measured for the repository as a whole. The suites we could count came back with 763 test method(s) (763 unit, 0 integration, 0 BDD, 0 e2e), but that is a shape for one part of the product and we do not publish a partial pyramid as if it were complete. This is OUR limitation, not a defect in the repo — test distribution is excluded from the score rather than counted.
  • D10 Test Quality — 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 586 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 891 test source file(s) (.rb, .ts, .js) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — 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. Test reliability NOT SCORED: this repository's production source spans .cs, .rb, and the ruby executor ran against the .rb half and never executed — so reliability was not measured for the repository as a whole. The .NET suite did build and re-run, and came back with 0 flaky across 2 measured tier(s) (other: measured (0 flaky); JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in bun/helpers/ (23 tests); mocha via `npm install --ignore-scripts` (no lockfile) in bun/spec/fixtures/projects/javascript/etag_no_lockfile/; jest via `npm ci --ignore-scripts` in npm_and_yarn/helpers/ (86 tests); jest via `npm install --ignore-scripts` (no lockfile) in npm_and_yarn/spec/fixtures/projects/grapher/npm_no_lockfile/ (0 tests); jest via `npm ci --ignore-scripts` in npm_and_yarn/spec/fixtures/projects/npm5/subdependency_update/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in npm_and_yarn/spec/fixtures/projects/npm5_and_yarn/npm_subdependency_update/ (0 tests); mocha via `npm install --ignore-scripts` (no lockfile) in npm_and_yarn/spec/fixtures/projects/npm6/etag_no_lockfile/; mocha via `npm ci --ignore-scripts` in npm_and_yarn/spec/fixtures/projects/npm6/path_dependency/deps/etag/; jest via `npm ci --ignore-scripts` in npm_and_yarn/spec/fixtures/projects/npm6/subdependency_update/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in npm_and_yarn/spec/fixtures/projects/npm6_and_yarn/npm_subdependency_update/ (0 tests); mocha via `yarn install --frozen-lockfile --ignore-scripts` in npm_and_yarn/spec/fixtures/projects/npm6_and_yarn/path_dependency/deps/etag/; jest via `npm install --ignore-scripts` (no lockfile) in npm_and_yarn/spec/fixtures/projects/npm8/app_no_version/ (0 tests)): measured (0 flaky)) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted. The half was driven by a runner we ship, so this is not a missing-runner gap.
  • 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.
  • D14 License Compliance — 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. This repository declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), but the licence verdict published here was taken over its NuGet package dependencies. Nothing was read about its Bundler dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D17 Explicit Debt — 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 C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Frameworks/NuGet.Frameworks.csproj' with message: Input file "nuget/helpers/lib/NuGetUpdater/NuGetProjects/../../NuGet.Client/build/config.props" cannot be opened. Could not find a part of the ….
  • D17 Explicit Debt — 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 80 deducted marker(s) and the 3.5/KLoC density on this row were taken over this repository's .NET projects ALONE: .rb (143,037 lines, 85% of production source) went unread, because every marker collector on this path is reached through a C# workspace. A read-only sweep of that source finds at least 156 task marker(s) (TODO/FIXME/HACK/XXX) across 106 file(s) that this score does not count — a floor, since only line comments are read there and D17's other eight marker kinds (suppressions, NoWarn, editorconfig severities, empty catches, commented-out code, Obsolete, dead code, preprocessor branches) need a compiler we do not have for that language. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
  • D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D19 Documentation Quality — 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D21 Naming Consistency — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — 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. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
  • D23 Boundary Type-Coupling — 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. Large codebase (169,063 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D31 IaC & Container Security — 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. REDACTED carries no `FROM` instruction, so it declares no build stage and every REDACTED rule this engine owns — the runtime-hardening, key-material, mutable-clone, no-op-shim, build-context, trust-anchor, install-guard, setuid and world-writable-path rules — is outside its own premise there and returned nothing. That silence is deliberate and correct: with no base image there is no image to reason about. It is reported here because it is NOT the same fact as a clean file, and coverage is stated as 247 of 248 Infrastructure-as-Code manifest(s) fully judged rather than as 100%. The vendor scanners (trivy, checkov) do read these files and their findings above stand; only this engine's own stage-keyed rules are absent. No owner action: a build file with no FROM is a legitimate include fragment.
  • D32 Data Compliance (PII/GDPR) — 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. `nuget/helpers/lib/NuGetUpdater/DotNetPackageCorrelation/Correlator.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/CompatibilityChecker.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/PackageVersionsCache.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Clone/CloneWorker.cs`, … (+6 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.
  • D39 IL Efficiency — 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. IL NOT MEASURED: the analyzer's own build of this repository failed for an ENVIRONMENT reason (exit 1) — MSBuild's engine or the CLR gave up, or our image does not carry the SDK band/targeting pack this repository needs. This is OUR limitation, not a defect in the repo, and it is not a statement that this repository fails to build. D18 owns the question of whether this repository builds; it was not answered here.
  • 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 DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
  • 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. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
  • PF3 Async & latency hygiene — 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. 34 further occurrence(s) are not listed individually; the score already reflects all 74.
  • R11 Import Boundaries — 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. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
  • X2 Cancellation propagation — 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. 60 further occurrence(s) are not listed individually; the score already reflects all 100.

Repo exclusion declarations: 5 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — 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.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • 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 (REDACTED, 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.
  • 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".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity6.4 / 10Adequate✓ Tool-verified

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

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

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

44 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was XmlFileWriter.UpdatePackageVersionsAsync at 71. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Dependabot.updater_error_details at 31 — they are counted neither in the figure above nor in this dimension's score. 5 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: common/lib/dependabot/errors.rb (Dependabot.updater_error_details at 31), gradle/lib/dependabot/gradle/file_updater/lockfile_updater.rb (LockfileUpdater.write_properties_file at 17), gradle/lib/dependabot/gradle/file_updater/wrapper_updater.rb (WrapperUpdater.proxy_args at 17), common/lib/dependabot/clients/azure.rb (Azure.post at 16), npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb (NpmrcBuilder.global_registry at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

XmlFileWriter.UpdatePackageVersionsAsync (cyclomatic 71)nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:52
SdkProjectDiscovery.DiscoverAsync (cyclomatic 57)nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:76
NpmLockfileUpdater.handle_npm_updater_error (cyclomatic 52)npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:585
SdkProjectDiscovery.BuildResults (cyclomatic 48)nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:492
PnpmLockfileUpdater.handle_pnpm_lock_updater_error (cyclomatic 44)npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:832

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

What to do

  1. Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with XmlFileWriter.UpdatePackageVersionsAsync (cyclomatic 71). — Refactoring it lifts Cyclomatic Complexity from 6.4 to about 6.5/10.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity4.8 / 10Weak✓ Tool-verified

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

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

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

84 method(s) exceeded the cognitive complexity threshold of 15; the worst was XmlFileWriter.UpdatePackageVersionsAsync at 329.

parser.parse_setup (cognitive 18) · ×2REDACTED:226
parser.parse_requirements (cognitive 17) · ×2REDACTED:174
XmlFileWriter.UpdatePackageVersionsAsync (cognitive 329)nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:52
SdkProjectDiscovery.DiscoverAsync (cognitive 158)nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:76
SdkProjectDiscovery.BuildResults (cognitive 131)nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:492

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

What to do

  1. Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with XmlFileWriter.UpdatePackageVersionsAsync (cognitive 329), SdkProjectDiscovery.DiscoverAsync (cognitive 158), SdkProjectDiscovery.BuildResults (cognitive 131). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 4.8 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes7.7 / 10Strong✓ Tool-verified

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

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

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

107 god class(es) detected.

TooManyMethods: UpdateChecker · ×71docker/lib/dependabot/docker/update_checker.rb:56
FileTooLong: docker/update_checker.rb · ×26docker/lib/dependabot/docker/update_checker.rb
MethodTooLong: XmlFileWriter.UpdatePackageVersionsAsync · ×7nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:52
ClassTooLong: XmlFileWriter · ×2nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs
FunctionTooLong: vulnerability-auditor.findVulnerableDependenciesnpm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts:116

What to do

  1. Resolve the 71 TooManyMethods finding(s) in God Classes — start with REDACTED (9), update_checker.rb (8), lockfile_updater.rb (3). — One of this dimension's main actionable groups (71 warning-level).
  2. Resolve the 26 FileTooLong finding(s) in God Classes — start with update_checker.rb (2), version_resolver.rb (2), npm_lockfile_updater.rb. — One of this dimension's main actionable groups (26 warning-level).
  3. Resolve the 7 MethodTooLong finding(s) in God Classes — start with SdkProjectDiscovery.cs (2), XmlFileWriter.cs, FileWriterWorker.cs. — One of this dimension's main actionable groups (7 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D4 · Code Duplication8.6 / 10Strong✓ Tool-verified

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.

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

492 duplicated block group(s) detected. A further 15 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (6 lines × 2) · ×41nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:354
Duplicated block (8 lines × 2) · ×41nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:300
Duplicated block (7 lines × 2) · ×36nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:965
Duplicated block (5 lines × 2) · ×36nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/DotNetToolsJsonUpdater.cs:24
Duplicated block (9 lines × 2) · ×26nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/NuGetContext.cs:111

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

What to do

  1. Resolve the 41 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with REDACTED (5), REDACTED (4), dependency_files_filterer.rb (4). — One of this dimension's main actionable groups (41 warning-level).
  2. Resolve the 41 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with lockfile_updater.rb (3), REDACTED (3), package_json_preparer.rb (2). — One of this dimension's main actionable groups (41 warning-level).
  3. Resolve the 36 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with update_checker.rb (5), version_resolver.rb (4), REDACTED (3). — One of this dimension's main actionable groups (36 warning-level).
  4. 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.

D5 · Coupling9.7 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

71 production modules (Gradle+Maven+npm+Go+Python+RubyGems+Composer+pub), 0 dependency cycle(s), 1 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 6 of the 71 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Unstable project dependabot-pre_commit
Off the main sequence: dependabot-python

What to do

  1. Resolve the 1 Unstable project dependabot-pre_commit finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 3 serious findings✓ Tool-verified

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

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

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

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

3 of 503 classes have LCOM4 above 3.

Low cohesion: Job (LCOM4 7) · ×3updater/lib/dependabot/job.rb:38

What to do

  1. Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with job.rb, REDACTED, version.rb. — One of this dimension's main actionable groups (3 warning-level).
  2. 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.

D10 · Test Quality10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

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

0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 586 tests. Measured on the C# suite only — at least 891 test source file(s) (.rb, .ts, .js) went unread, so its test quality is unmeasured and is not in these counts.

No assertions: GetAllPackageDependencies_NugetConfigInvalid_DoesNotThrownuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Utilities/MSBuildHelperTests.cs:218

What to do

  1. Resolve the 1 No assertions finding(s) in Test Quality — start with MSBuildHelperTests.cs. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D13 · Secret Scanning5.0 / 10Adequate✓ Tool-verified

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

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

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

1 secret(s) detected.

REDACTED

What to do

  1. Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

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.

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

0 of 166 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 30 direct `PackageReference`(s), and 139 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution. ★ COVERAGE OF THIS VERDICT: it grades this repository's NuGet package dependencies and nothing else. The repository also declares a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 11 serious findings✓ Tool-verified

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

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

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

Top hotspots: npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb (21×44=924); REDACTED (14×15=210); common/lib/dependabot/errors.rb (6×31=186) Repeated repair below the complexity floor: npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb (3 of 4 changes were fixes); nix/lib/dependabot/nix/file_parser.rb (3 of 3 changes were fixes)

Hotspot: npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb · ×9npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:832
Repeated repair: npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb · ×2npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:223

What to do

  1. Resolve the 9 Hotspot finding(s) in Churn × Complexity Hotspots — start with pnpm_lockfile_updater.rb, REDACTED, errors.rb. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with package_details_fetcher.rb, REDACTED. — One of this dimension's main actionable groups (2 warning-level).

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

D16 · Bus Factor5.9 / 10Adequate✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

26 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs. Counted over 63 of the 196 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

D17 · Explicit Debt3.0 / 10Weak✓ Tool-verified

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

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

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

80 deducted debt markers + unmeasured dead symbols across 18315 LoC in the .NET projects (3.5/KLoC) → score 3.0. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .rb (85% of production source) was not read, and carries at least 156 uncounted task marker(s) in 106 file(s).

NoWarnInCsproj — 7 warning codes suppressed in one element · ×23nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Commands/NuGet.Commands.csproj:5
EmptyCatchBlock · ×6nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:325
WriteOnlyPrivateField · ×2nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/UpdaterWorker.cs:20
NoWarnInCsproj repeated across 10 files · ×2nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Build.Tasks/NuGet.Build.Tasks.csproj:5
DisabledAnalyzersnuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/DependencyDiscovery.props:15

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

What to do

  1. Resolve the 23 NoWarnInCsproj finding(s) in Explicit Debt — start with Directory.Build.props (6), NuGet.CommandLine.csproj (2), NuGet.Frameworks.csproj (2). — One of this dimension's main actionable groups (23 issue-level).
  2. Resolve the 6 EmptyCatchBlock finding(s) in Explicit Debt — start with SdkProjectDiscovery.cs (3), Program.cs (2), MSBuildHelper.cs. — One of this dimension's main actionable groups (6 issue-level).
  3. Resolve the 2 WriteOnlyPrivateField finding(s) in Explicit Debt — start with UpdaterWorker.cs, DependencyConflictResolver.cs. — One of this dimension's main actionable groups (2 issue-level).
  4. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D19 · Documentation Quality5.0 / 10Adequate✓ Tool-verified

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

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

1 of 2 documentation facets pass in full; short on: F4 map. 47 document(s) read across 21 unit(s).

Documentation: no map of the repository's partsREADME.md:1

What to do

  1. Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

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

D24 · Comment Value6.8 6.8 / 10Adequate✓ Tool-verified

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

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

Maturity: Documented → Verified → Prevented · effective 6.8 / 10 · rule-coverage 99% · ceiling Documented

32 of 1016 judged comments only repeat the code they sit on (3.1 %). 21 comment(s) in another language or script were not judged.

redundant comment · ×21nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:126
doc comments repeat the names · ×3nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:634

What to do

  1. Resolve the 21 redundant comment finding(s) in Comment Value — start with BindingRedirectManager.cs (4), ProjectFactory.cs (3), ModifiedFilesTrackerTests.cs (2). — One of this dimension's main actionable groups (21 recommendation-level).

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

D26 · Project Cohesion9.1 / 10Exemplary✓ Tool-verified

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

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

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

1 of 23 projects flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

✓ On the Gold path — maintain.

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

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

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

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

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

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

REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

134 finding(s): 0 critical, 75 high, 41 medium, 18 low. semgrep hit a parse error in 107 file(s) — `REDACTED` (line 10), `REDACTED` (line 41), `REDACTED` (line 38), `bun/spec/fixtures/npm_responses/200_with_invalid_json.json`, `REDACTED` (line 10), … (+102 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. In 6 of those file(s) — `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Analyze/AnalyzeWorkerTests.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Analyze/CompatibilityCheckerTests.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Analyze/VersionFinderTests.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Run/ModifiedFilesTrackerTests.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/PackageVersionsCache.cs`, … (+1 more) — the break is a C# primary constructor, which semgrep's grammar cannot parse and which hides the type from every rule scoped to it; those files were re-scanned from a shadow copy with the constructor's parameter list blanked (line and column preserving), which restores the type to the rules, and 0 additional row(s) came from that pass. Only the header's own parameter list is unread in them. In 20 of those file(s) — `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Cli.Test/EntryPointTestHelper.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Cli.Test/EntryPointTests.Graph.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Cli.Test/EntryPointTests.Run.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Analyze/AnalyzeWorkerTestBase.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Analyze/AnalyzeWorkerTests.cs`, … (+15 more) — the break is at a TYPE DECLARATION (a C# primary constructor semgrep's grammar cannot parse), so the loss is wider than the named lines: rules scoped to that type see no type to scope to and are blind over its whole body, while rules matching statements keep working there. Absence of a type-scoped finding in those types is not evidence of anything. Separately, one or more rules could not re-parse an embedded snippet in 5 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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 Gemfile.lock 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.

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

54 finding(s): 6 critical, 28 high, 17 medium, 3 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 28 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25), REDACTED, REDACTED. — One of this dimension's main actionable groups (28 issue-level).
  2. Resolve the 16 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (15), REDACTED. — One of this dimension's main actionable groups (16 warning-level).
  3. Resolve the 6 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).

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

D31 · IaC & Container Security0.0 / 10Critical✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

99 finding(s): 2 critical, 12 high, 84 medium, 1 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 84 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (80), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (84 warning-level).
  2. Resolve the 12 High IaC finding(s) in IaC & Container Security — start with REDACTED (9), REDACTED (3). — One of this dimension's main actionable groups (12 issue-level).
  3. Resolve the 2 Critical IaC finding(s) in IaC & Container Security — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).

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

D34 · Knowledge Freshness9.7 / 10Exemplary✓ Tool-verified

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

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

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

2 of 63 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Files/BuildFile.cs. Counted over 63 of the 196 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×2nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Files/BuildFile.cs:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.9 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: PackageReferenceUpdater.cs↔ProcessExtensions.cs 64%; base_command.rb↔error_handler.rb 57%; PackageReferenceUpdater.cs↔MSBuildHelper.cs 56%

Change coupling: PackageReferenceUpdater.cs ↔ ProcessExtensions.cs · ×4nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackageReferenceUpdater.cs:1

What to do

  1. Resolve the 4 Change coupling finding(s) in Change Coupling — start with PackageReferenceUpdater.cs (2), base_command.rb, lockfile_updater.rb. — One of this dimension's main actionable groups (4 warning-level).

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

D36 · Supply-chain Provenance & Signing10.0 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

Build pipeline generates provenance, signs artifacts and produces an SBOM.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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.

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life0.5 / 10Critical✓ Tool-verified

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.

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

4 end-of-life runtime(s) and 1 end-of-life framework(s), read from 92 platform declaration(s) and 677 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.

End-of-life runtime: Node.js 16 · ×4npm_and_yarn/spec/fixtures/projects/pnpm/peer_disambiguation_v6/package.json:23
End-of-life framework: Rails 5bundler/spec/fixtures/projects/bundler2/transitive_blocking/Gemfile:1

What to do

  1. Resolve the 4 End-of-life runtime finding(s) in Platform End-of-Life — start with package.json (4). — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with Gemfile. — One of this dimension's main actionable groups (1 warning-level).

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

Frontend & cross-cutting dimensions

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

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

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

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.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

  • The namespaces NuGetUpdater.Core ↔ NuGetUpdater.Core.Analyze ↔ NuGetUpdater.Core.Discover ↔ NuGetUpdater.Core.Run.ApiModel ↔ NuGetUpdater.Core.Updater depend on each other. The lightest dependency in the cycle is NuGetUpdater.Core.Discover → NuGetUpdater.Core.Run.ApiModel (NuGetUpdater.Core.Discover.ProjectDiscoveryResult → NuGetUpdater.Core.Run.ApiModel.JobErrorBase, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/ProjectDiscoveryResult.cs:3
  • The namespaces NuGetUpdater.Core.Run ↔ NuGetUpdater.Core.Run.UpdateHandlers depend on each other. The lightest dependency in the cycle is NuGetUpdater.Core.Run → NuGetUpdater.Core.Run.UpdateHandlers (NuGetUpdater.Core.Run.RunWorker → NuGetUpdater.Core.Run.UpdateHandlers.IUpdateHandler, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs:12

What to do

  • Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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.

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

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

  • A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface. (×3) — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:250, nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:255, nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:265

What to do

  • Finish or delete NotImplementedException stubs and replace placeholder literals before shipping.
IC1 · Incompleteness & stubs8.0 / 10Strong✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.

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

  • `ValidateIntegrityAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:250
  • `GetArchiveHashAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:255
  • `GetContentHash` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:265

What to do

  • Finish or delete the unfinished stubs (NotImplementedException / empty / constant-returning bodies) — they are dead surface that looks live.
M1 · Documentation (README)6.5 / 10Adequate✓ Tool-verified

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.

  • 830 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

  • Add a README to the 23 of 23 project(s) that lack one — worth up to 2 pts.
  • Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

Maturity · Maturity — Whether the 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.

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

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.

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

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

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

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

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.

What to do

  • Keep implementation types off the public surface (Go: an unexported name, or move it under `internal/`) — even for a small library, every public type is a stability contract.
P2 · Observability8.7 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 33/37 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `bun/helpers`, `npm_and_yarn/helpers`, `python/helpers`, `uv/helpers`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Add a health-check endpoint (Rails' /up (rails/health#show) or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

  • <NuGetAudit>false</NuGetAudit> in MSBuild suppresses NuGet's vulnerability audit project-wide. — nuget/helpers/lib/NuGetUpdater/Directory.Build.props:8
  • `NoWarn` silences NU1903 — NuGet's vulnerability-audit warnings for high advisories. Suppressed advisories are still shipped; they are only invisible in the build log. Remove these codes from NoWarn and address or explicitly accept each advisory instead. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Build.props:8

What to do

  • Dependabot is configured but does not watch `cargo`, `gradle` — add those `package-ecosystem` entries 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.
P4 · Deployment & Rollback10.0 / 10Exemplary✓ Tool-verified

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

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

P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

  • `fs.readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×6) — bun/helpers/lib/npm6/subdependency-updater.js:12, REDACTED:26, bun/helpers/lib/yarn/lockfile-parser.js:16, …
  • `fs.writeFileSync` in `updateDependencyFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×4) — bun/helpers/lib/npm6/subdependency-updater.js:23, bun/helpers/lib/yarn/subdependency-updater.js:66, bun/helpers/lib/yarn/updater.js:188, …
  • `fs.readFileSync` in `findConflictingDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bun/helpers/lib/yarn/conflicting-dependency-parser.js:21
  • `existsSync` in `mkdirpPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:847
  • `lstatSync` in `preserveTimeSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1103
  • `lutimesSync` in `preserveTimeSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1108
  • `utimesSync` in `preserveTimeSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1110
  • `openSync` in `openPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1915
  • `opendirSync` in `opendirPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1926
  • `readSync` in `readPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1943
  • `writeSync` in `writePromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1959, npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1961
  • `closeSync` in `closePromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1971
  • `realpathSync` in `realpathPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2048
  • `existsSync` in `existsPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2057
  • `accessSync` in `accessPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2077
  • `statSync` in `statPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2089, npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2090
  • `fstatSync` in `fstatPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2106
  • `lstatSync` in `lstatPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2122, npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2123
  • `chmodSync` in `chmodPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2397
  • `chownSync` in `chownPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2415
  • `renameSync` in `renamePromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2421
  • `unlinkSync` in `unlinkPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2542
  • `utimesSync` in `utimesPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2556
  • `lutimesSync` in `lutimesPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2565
  • `mkdirSync` in `mkdirPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2587
  • `rmdirSync` in `rmdirPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2602
  • `linkSync` in `linkPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2631
  • `symlinkSync` in `symlinkPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2637
  • `readdirSync` in `readdirPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2682

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
  • Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
R1 · Type Safety5.2 / 10Adequate✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 32 typed · 29 plain JS — the untyped files are bun/helpers/lib/npm/conflicting-dependency-parser.js, bun/helpers/lib/npm/index.js, bun/helpers/lib/npm/vulnerability-auditor.js, bun/helpers/lib/npm6/helpers.js, bun/helpers/lib/npm6/index.js, bun/helpers/lib/npm6/peer-dependency-checker.js (+23 more).

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication7.5 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • 18 of the duplicated blocks reported below have copies in at least two of the sibling directories bun, npm_and_yarn under the repository root. That concentration is one structural fact, not 18 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — bun/helpers/lib/yarn/conflicting-dependency-parser.js:34
  • bun/helpers/lib/yarn/conflicting-dependency-parser.js:34 · npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts:59 — the two spans are one implementation copied and then locally edited — 446 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — bun/helpers/lib/yarn/conflicting-dependency-parser.js:34
  • bun/helpers/lib/yarn/updater.js:129 · npm_and_yarn/helpers/lib/yarn/updater.ts:148 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — bun/helpers/lib/yarn/updater.js:129
  • bun/helpers/lib/yarn/subdependency-updater.js:29 · npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:44 — the two spans are one implementation copied and then locally edited — 238 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — bun/helpers/lib/yarn/subdependency-updater.js:29
  • bun/helpers/lib/npm6/subdependency-updater.js:16 · npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — bun/helpers/lib/npm6/subdependency-updater.js:16
  • bun/helpers/lib/pnpm/lockfile-parser.js:27 · npm_and_yarn/helpers/lib/pnpm/lockfile-parser.ts:120 — the two spans are one implementation copied and then locally edited — 178 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — bun/helpers/lib/pnpm/lockfile-parser.js:27
  • bun/helpers/lib/yarn/fix-duplicates.js:36 · npm_and_yarn/helpers/lib/yarn/fix-duplicates.ts:55 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — bun/helpers/lib/yarn/fix-duplicates.js:36
  • bun/helpers/run.js:5 · npm_and_yarn/helpers/run.ts:14 — the two spans are one implementation copied and then locally edited — 178 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — bun/helpers/run.js:5
  • bun/helpers/lib/npm6/helpers.js:1 · npm_and_yarn/helpers/lib/npm6/helpers.ts:6 — the two spans are one implementation copied and then locally edited — 93 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — bun/helpers/lib/npm6/helpers.js:1
  • REDACTED:83 · npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:83
  • npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:46 · npm_and_yarn/helpers/lib/yarn/updater.ts:56 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:46
  • bun/helpers/lib/yarn/peer-dependency-checker.js:89 · npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:107 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — bun/helpers/lib/yarn/peer-dependency-checker.js:89
  • bun/helpers/lib/npm6/peer-dependency-checker.js:33 · npm_and_yarn/helpers/lib/npm6/peer-dependency-checker.ts:40 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — bun/helpers/lib/npm6/peer-dependency-checker.js:33
  • bun/helpers/lib/yarn/peer-dependency-checker.js:34 · bun/helpers/lib/yarn/updater.js:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — bun/helpers/lib/yarn/peer-dependency-checker.js:34
  • REDACTED:122 · npm_and_yarn/helpers/lib/yarn/updater.ts:81 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — REDACTED:122
  • bun/helpers/lib/yarn/updater.js:109 · npm_and_yarn/helpers/lib/yarn/updater.ts:128 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — bun/helpers/lib/yarn/updater.js:109
  • bun/helpers/lib/yarn/replace-lockfile-declaration.js:36 · npm_and_yarn/helpers/lib/yarn/replace-lockfile-declaration.ts:43 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — bun/helpers/lib/yarn/replace-lockfile-declaration.js:36
  • npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:20 · npm_and_yarn/helpers/lib/yarn/updater.ts:46 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:20
  • bun/helpers/lib/npm6/remove-dependencies-from-lockfile.js:5 · npm_and_yarn/helpers/lib/npm6/remove-dependencies-from-lockfile.ts:16 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — bun/helpers/lib/npm6/remove-dependencies-from-lockfile.js:5
  • bun/helpers/lib/yarn/peer-dependency-checker.js:60 · npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:77 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — bun/helpers/lib/yarn/peer-dependency-checker.js:60
  • npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:15 · npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:39 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:15
  • bun/helpers/lib/npm6/peer-dependency-checker.js:81 · npm_and_yarn/helpers/lib/npm6/peer-dependency-checker.ts:88 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — bun/helpers/lib/npm6/peer-dependency-checker.js:81
  • bun/helpers/lib/yarn/peer-dependency-checker.js:111 · npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:129 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — bun/helpers/lib/yarn/peer-dependency-checker.js:111
  • bun/helpers/lib/npm/conflicting-dependency-parser.js:23 · npm_and_yarn/helpers/lib/npm/conflicting-dependency-parser.ts:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — bun/helpers/lib/npm/conflicting-dependency-parser.js:23

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries0.0 / 10Critical✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • bun/helpers/lib/npm6/peer-dependency-checker.js:14 imports npm/lib/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/npm6/peer-dependency-checker.js:14
  • bun/helpers/lib/npm6/subdependency-updater.js:4 imports npm/lib/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/npm6/subdependency-updater.js:4
  • REDACTED:20 imports npm/lib/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — REDACTED:20
  • bun/helpers/lib/yarn/fix-duplicates.js:1 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/fix-duplicates.js:1
  • bun/helpers/lib/yarn/fix-duplicates.js:2 imports @dependabot/yarn-lib/lib/lockfile/stringify, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/fix-duplicates.js:2
  • bun/helpers/lib/yarn/helpers.js:1 imports @dependabot/yarn-lib/lib/cli/commands/add, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/helpers.js:1
  • bun/helpers/lib/yarn/helpers.js:2 imports @dependabot/yarn-lib/lib/cli/commands/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/helpers.js:2
  • bun/helpers/lib/yarn/lockfile-parser.js:11 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/lockfile-parser.js:11
  • bun/helpers/lib/yarn/peer-dependency-checker.js:13 imports @dependabot/yarn-lib/lib/cli/commands/add, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/peer-dependency-checker.js:13
  • bun/helpers/lib/yarn/peer-dependency-checker.js:14 imports @dependabot/yarn-lib/lib/config, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/peer-dependency-checker.js:14
  • bun/helpers/lib/yarn/peer-dependency-checker.js:15 imports @dependabot/yarn-lib/lib/reporters, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/peer-dependency-checker.js:15
  • bun/helpers/lib/yarn/peer-dependency-checker.js:16 imports @dependabot/yarn-lib/lib/lockfile, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/peer-dependency-checker.js:16
  • bun/helpers/lib/yarn/peer-dependency-checker.js:18 imports @dependabot/yarn-lib/lib/package-fetcher.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/peer-dependency-checker.js:18
  • bun/helpers/lib/yarn/replace-lockfile-declaration.js:1 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/replace-lockfile-declaration.js:1
  • bun/helpers/lib/yarn/replace-lockfile-declaration.js:2 imports @dependabot/yarn-lib/lib/lockfile/stringify, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/replace-lockfile-declaration.js:2
  • bun/helpers/lib/yarn/subdependency-updater.js:4 imports @dependabot/yarn-lib/lib/config, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/subdependency-updater.js:4
  • bun/helpers/lib/yarn/subdependency-updater.js:5 imports @dependabot/yarn-lib/lib/reporters, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/subdependency-updater.js:5
  • bun/helpers/lib/yarn/subdependency-updater.js:6 imports @dependabot/yarn-lib/lib/lockfile, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/subdependency-updater.js:6
  • bun/helpers/lib/yarn/subdependency-updater.js:11 imports @dependabot/yarn-lib/lib/lockfile/stringify, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/subdependency-updater.js:11
  • bun/helpers/lib/yarn/updater.js:17 imports @dependabot/yarn-lib/lib/cli/commands/add, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/updater.js:17
  • bun/helpers/lib/yarn/updater.js:18 imports @dependabot/yarn-lib/lib/cli/commands/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/updater.js:18
  • bun/helpers/lib/yarn/updater.js:21 imports @dependabot/yarn-lib/lib/cli/commands/upgrade, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/updater.js:21
  • bun/helpers/lib/yarn/updater.js:22 imports @dependabot/yarn-lib/lib/config, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/updater.js:22
  • bun/helpers/lib/yarn/updater.js:23 imports @dependabot/yarn-lib/lib/reporters, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/updater.js:23
  • bun/helpers/lib/yarn/updater.js:24 imports @dependabot/yarn-lib/lib/lockfile, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/updater.js:24
  • bun/helpers/lib/yarn/updater.js:25 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — bun/helpers/lib/yarn/updater.js:25
  • npm_and_yarn/helpers/lib/npm6/peer-dependency-checker.ts:18 imports npm/lib/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/npm6/peer-dependency-checker.ts:18
  • npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:13 imports npm/lib/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:13
  • npm_and_yarn/helpers/lib/yarn/fix-duplicates.ts:5 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/fix-duplicates.ts:5
  • npm_and_yarn/helpers/lib/yarn/fix-duplicates.ts:8 imports @dependabot/yarn-lib/lib/lockfile/stringify, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/fix-duplicates.ts:8
  • npm_and_yarn/helpers/lib/yarn/helpers.ts:2 imports @dependabot/yarn-lib/lib/cli/commands/add, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/helpers.ts:2
  • npm_and_yarn/helpers/lib/yarn/helpers.ts:4 imports @dependabot/yarn-lib/lib/cli/commands/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/helpers.ts:4
  • REDACTED:14 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — REDACTED:14
  • npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:16 imports @dependabot/yarn-lib/lib/cli/commands/add, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:16
  • npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:18 imports @dependabot/yarn-lib/lib/config, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:18
  • npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:20 imports @dependabot/yarn-lib/lib/reporters, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:20
  • npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:22 imports @dependabot/yarn-lib/lib/lockfile, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:22
  • npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:24 imports @dependabot/yarn-lib/lib/package-fetcher.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:24
  • npm_and_yarn/helpers/lib/yarn/replace-lockfile-declaration.ts:3 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/replace-lockfile-declaration.ts:3
  • npm_and_yarn/helpers/lib/yarn/replace-lockfile-declaration.ts:6 imports @dependabot/yarn-lib/lib/lockfile/stringify, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — npm_and_yarn/helpers/lib/yarn/replace-lockfile-declaration.ts:6

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • findConflictingParentDependencies has cyclomatic complexity 12 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts:118
  • nameVerDevFromPkgSnapshot has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — npm_and_yarn/helpers/lib/pnpm/lockfile-parser.ts:113
  • findConflictingParentDependencies has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — bun/helpers/lib/yarn/conflicting-dependency-parser.js:93
  • findConflictingParentDependencies has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:303
R3 · Large Files9.1 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage5.5 / 10Adequate✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×17) — bun/helpers/lib/npm/vulnerability-auditor.js:1, npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:1, bun/helpers/lib/yarn/peer-dependency-checker.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness8.6 / 10Strong✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

What to do

  • Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

R7 · Dead Code10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • 2 file(s) (~19850 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
R8 · Dependency Hygiene6.0 / 10Adequate✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×2) — bun/helpers/lib/npm/vulnerability-auditor.js:237, npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts:35

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

X1 · Async correctness7.0 / 10Strong✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. (×3) — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:34, nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/Command.cs:179, nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:1197
  • Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:951

What to do

  • Sync-over-async (deadlock risk)
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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

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

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.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

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.

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.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. 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 `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

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.

X18 · Disposal-pattern correctness5.1 / 10Adequate✓ Tool-verified

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

  • `_httpFetcher` is never created by `DetailedPullRequestBodyGenerator` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 25). Its declared type `IHttpFetcher` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed. — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/DetailedPullRequestBodyGenerator.cs:25
  • `writer` is a `Utf8JsonWriter`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `UpdateJsonProperty` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var writer = …;`), which releases it at the end of the scope on every path including a throw. — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/JsonHelper.cs:38
  • `referencedProject` is a `ProjectFactory`, which implements `IDisposable`, and it is created here (line 590). Every use of it in `RecursivelyApply` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var referencedProject = …;`), which releases it at the end of the scope on every path including a throw. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:590
  • `projectFactory` is a `ProjectFactory`, which implements `IDisposable`, and it is created here (line 704). Every use of it in `CreateDependencyFromProject` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var projectFactory = …;`), which releases it at the end of the scope on every path including a throw. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:704

What to do

  • Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

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

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

X2 · Cancellation propagation5.2 / 10Adequate✓ Tool-verified

Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 25/124 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
  • No CancellationToken parameter — this work can't be stopped early once started. (×37) — nuget/helpers/lib/NuGetUpdater/DotNetPackageCorrelation/Correlator.cs:24, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:39, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:46, …
  • Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one. (×2) — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:570, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ModifiedFilesTracker.cs:94

What to do

  • Thread a CancellationToken through async methods so work stops promptly on cancellation.
X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `ArgumentNullException` tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

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.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

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.

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.

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

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.

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

Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` 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.

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.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.5 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:433, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:882, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:1093, …
  • `catch (BadImageFormatException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:304

What to do

  • Swallowed exception (empty catch)
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.

X32 · Type resolved by simple name across every loaded assembly10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a plugin lookup names the type it means — searching every assembly loaded into the process for a candidate whose SIMPLE name equals a string supplied at runtime, and taking the first one found, is decided by assembly LOAD ORDER rather than by this source, so the same name can resolve to a different type on the next run.

Method: Roslyn syntax only, no semantic model: every invocation of `First`/`FirstOrDefault`/`Single`/`SingleOrDefault` whose OWN expression subtree contains both a `GetAssemblies()` call and a `GetTypes()`/`GetExportedTypes()` call — a single-element pick out of every type loaded into the process. A nested selector in the same chain sees no `GetAssemblies()` in its own subtree and is outside the population, so one lookup counts once however many links its chain has. A finding additionally needs both remaining halves: the selector must be `First`/`FirstOrDefault` (`Single`/`SingleOrDefault` reports the ambiguity rather than resolving it, and is counted and never reported), and the chain must carry an `==` comparison of `<lambda parameter>.Name` against something that is not a literal. The receiver must be a plain identifier bound by one of the chain’s own lambdas, which places `assembly.GetName().Name == "X"` outside the rule by construction. One exemption: a `.Name` test joined by `&&` to a `FullName`/`AssemblyQualifiedName` test on the same identifier is spared; joined by `||` it is not. Deterministic, provable per finding. Advisory.

X4 · Structured logging6.6 / 10Adequate✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

  • Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/ILogger.cs:41

What to do

  • Interpolated log message defeats structured logging
X5 · Nullable reference types5.0 / 10Adequate✓ Tool-verified

Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.

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

  • This method contradicts itself about `console`: line 134 assigns it with `as IConsole`, which hands back null rather than throwing when the value is not a `IConsole`, but line 139 then dereferences it directly as `console.Verbosity` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `console` once before the first use and handle the null case, or cast with `(IConsole)` so the failure is reported where it happens — rather than leaving the two readings side by side. — nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:139
  • 9/20 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
  • ~1.3 `!` suppressions per 1k syntax nodes — 129 suppression(s) across the 96436 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.

What to do

  • Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
  • Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.

Reference — by lens

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

LensScoreRatingImpact
Code Health51%Adequate — gated by D17Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture70%Adequate — gated by R11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity72%StrongStrongest area.
Readiness61%AdequateAcceptable, with room to improve.
Security29%Weak — gated by D28, D29, D30, D31, D44Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 2 check(s) recorded observations but carry no score

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

  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 24 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 50 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX2 Stateful singletons — no singleton implementations detected
  • AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • 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 — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence 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 — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, 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 the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D11 Test Reliability — Test reliability not scored — polyglot repository, one half's runner produced no measurement
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .dart, .exs, .go, .jl, .php, .py, .rb, .ts, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D21 Naming Consistency — Naming consistency is measured on C# only; Elixir, Go, JavaScript, PHP, Python, Ruby, Rust, TypeScript not measured.
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Ruby, Rust surface was not measured.
  • D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rb), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 11 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • 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 — IL not measured — the analyzer's build of the target did not succeed
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the .NET half could not be measured — the repository wires up no coverage collector for `--collect:"XPlat Code Coverage"` to use; the JavaScript/TypeScript half measured 89.9% (jest via `npm ci --ignore-scripts` in bun/helpers/; jest via `npm ci --ignore-scripts` in npm_and_yarn/helpers/; jest in npm_and_yarn/spec/fixtures/projects/grapher/npm_no_lockfile/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm5/subdependency_update/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm5_and_yarn/npm_subdependency_update/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm6/subdependency_update/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm6_and_yarn/npm_subdependency_update/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm8/app_no_version/: not run). This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
  • D9 Test Distribution — Test distribution not scored — polyglot repository, one half's tests are uncountable
  • DM1 Domain Modelling — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 124 value object(s)
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — 1 mutating command handler(s)/consumer(s) detected and 1 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (SimpleCov — `require "simplecov"` in your `REDACTED`/`test_helper.rb`, which writes `coverage/.resultset.json` (or lcov via `simplecov-lcov`)) 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 — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 189 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 28 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×28
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 3 more in this group — see findings.md.
D17 · Explicit Debt · NoWarnInCsproj · ×23
  • NoWarnInCsproj — 7 warning codes suppressed in one element nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Commands/NuGet.Commands.csproj:5 — A single <NoWarn> suppresses 7 warning codes (CS1591;CS1574;CS1573;CS1584;CS1658;CS1998;RS0041) in one stroke — one team-wide decision, not 7 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj — 6 warning codes suppressed in one element nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.PackageManagement/NuGet.PackageManagement.csproj:5 — A single <NoWarn> suppresses 6 warning codes (CS1591;CS1580;CS1574;CS1573;RS0041;NU1510) in one stroke — one team-wide decision, not 6 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj — 7 warning codes suppressed in one element nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/NuGet.Packaging.csproj:6 — A single <NoWarn> suppresses 7 warning codes (CA1305;CS0414;CS1591;CS1574;CS1573;CS1572;RS0041) in one stroke — one team-wide decision, not 7 independent debts. Review the set centrally rather than code-by-code; each code you can re-enable is one less blanket suppression. (Every code still counts toward the score and metrics.)
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/DotNetPackageCorrelation/DotNetPackageCorrelation.csproj:5 — NU1510 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Build.Tasks/NuGet.Build.Tasks.csproj:5 — NU1510 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/NuGet.CommandLine.csproj:5 — CA1416 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Build.props:12 — CA1416 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/NuGet.CommandLine.csproj:6 — SYSLIB0018 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Common/NuGet.Common.csproj:5 — CS1574 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.DependencyResolver.Core/NuGet.DependencyResolver.Core.csproj:5 — CS1574 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Frameworks/NuGet.Frameworks.csproj:5 — CS1574 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Frameworks/NuGet.Frameworks.csproj:5 — CS1573 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.ProjectModel/NuGet.ProjectModel.csproj:5 — CS1573 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Protocol/NuGet.Protocol.csproj:6 — CS1573 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Resolver/NuGet.Resolver.csproj:5 — CS1573 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Protocol/NuGet.Protocol.csproj:6 — CS0012 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Build.props:6 — CA1305 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Build.props:7 — CA2022 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj — known-vulnerability alert suppressed nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Build.props:8 — NU1903 — this is not a style rule being switched off: it is the dependency audit reporting that a package this project references has a KNOWN, already-published security vulnerability, and the entry deletes that report for the whole project — for this package and for every dependency the project takes from here on, including ones added long after whoever wrote the line has moved on. Nothing in the build will raise it again, so the next reader has no way to learn it was ever accepted. Upgrade the package to a version carrying the fix, or replace it, and drop the code from the list. Where the fix genuinely does not exist yet, keep the report and stop it FAILING the build — demote it to a warning without silencing it — and write down which advisory is being accepted and until when, so it is the acceptance that expires rather than the alert.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Build.props:9 — SYSLIB0014 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Build.props:13 — CS0436 — this warning is switched off for the WHOLE project, in every file it builds, including code written years from now: nothing at the call site records that the rule was ever silenced, so the next reader has no reason to look here. Fix what the rule is reporting and drop the code from the list, or — if some occurrences really are legitimate — narrow the suppression to those sites and give each one its reason, so the rule keeps protecting the rest of the project.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/DependencyDiscoveryTargetingPacks.props:10 — NU1605 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
  • NoWarnInCsproj nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/DependencyDiscoveryTargetingPacks.props:12 — NU1703 — this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself — the packaging, restore or SDK step — about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list.
D28 · Secrets (history) · High secret · ×18
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D11 · Test Reliability · Test suite declares a test script but contains no test files · ×6
  • Test suite declares a test script but contains no test files: npm_and_yarn/spec/fixtures/projects/grapher/npm_no_lockfile/ — The jest suite in npm_and_yarn/spec/fixtures/projects/grapher/npm_no_lockfile/ was installed and launched successfully, and the runner then found no test files to run — No tests found, exiting with code 1. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
  • Test suite declares a test script but contains no test files: npm_and_yarn/spec/fixtures/projects/npm5/subdependency_update/ — The jest suite in npm_and_yarn/spec/fixtures/projects/npm5/subdependency_update/ was installed and launched successfully, and the runner then found no test files to run — No tests found. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
  • Test suite declares a test script but contains no test files: npm_and_yarn/spec/fixtures/projects/npm5_and_yarn/npm_subdependency_update/ — The jest suite in npm_and_yarn/spec/fixtures/projects/npm5_and_yarn/npm_subdependency_update/ was installed and launched successfully, and the runner then found no test files to run — No tests found. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
  • Test suite declares a test script but contains no test files: npm_and_yarn/spec/fixtures/projects/npm6/subdependency_update/ — The jest suite in npm_and_yarn/spec/fixtures/projects/npm6/subdependency_update/ was installed and launched successfully, and the runner then found no test files to run — No tests found. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
  • Test suite declares a test script but contains no test files: npm_and_yarn/spec/fixtures/projects/npm6_and_yarn/npm_subdependency_update/ — The jest suite in npm_and_yarn/spec/fixtures/projects/npm6_and_yarn/npm_subdependency_update/ was installed and launched successfully, and the runner then found no test files to run — No tests found. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
  • Test suite declares a test script but contains no test files: npm_and_yarn/spec/fixtures/projects/npm8/app_no_version/ — The jest suite in npm_and_yarn/spec/fixtures/projects/npm8/app_no_version/ was installed and launched successfully, and the runner then found no test files to run — No tests found. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
D17 · Explicit Debt · EmptyCatchBlock · ×6
  • EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:325 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:446 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:433 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:882 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:1093 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
  • EmptyCatchBlock nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:532 — empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
D30 · Dependency Vulnerabilities · Critical CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX3 · Project dependency cycles · Namespace dependency cycle · ×2
  • Namespace dependency cycle nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/ProjectDiscoveryResult.cs:3 — The namespaces NuGetUpdater.Core ↔ NuGetUpdater.Core.Analyze ↔ NuGetUpdater.Core.Discover ↔ NuGetUpdater.Core.Run.ApiModel ↔ NuGetUpdater.Core.Updater depend on each other. The lightest dependency in the cycle is NuGetUpdater.Core.Discover → NuGetUpdater.Core.Run.ApiModel (NuGetUpdater.Core.Discover.ProjectDiscoveryResult → NuGetUpdater.Core.Run.ApiModel.JobErrorBase, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
  • Namespace dependency cycle nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs:12 — The namespaces NuGetUpdater.Core.Run ↔ NuGetUpdater.Core.Run.UpdateHandlers depend on each other. The lightest dependency in the cycle is NuGetUpdater.Core.Run → NuGetUpdater.Core.Run.UpdateHandlers (NuGetUpdater.Core.Run.RunWorker → NuGetUpdater.Core.Run.UpdateHandlers.IUpdateHandler, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
D17 · Explicit Debt · WriteOnlyPrivateField · ×2
  • WriteOnlyPrivateField nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/UpdaterWorker.cs:20 — private HashSet<string> _processedProjectPaths — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
  • WriteOnlyPrivateField nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:40 — private string repoRoot — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
D17 · Explicit Debt · NoWarnInCsproj repeated across 10 files · ×2
  • NoWarnInCsproj repeated across 10 files nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Build.Tasks/NuGet.Build.Tasks.csproj:5 — The identical NoWarnInCsproj (`CS1591`) appears in 10 files (10 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 10 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
  • NoWarnInCsproj repeated across 10 files nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Common/NuGet.Common.csproj:5 — The identical NoWarnInCsproj (`RS0041`) appears in 10 files (10 occurrences) — a single repo-wide policy (e.g. a Directory.Build.props decision or an idiomatic suppression), not 10 independent debts. Decide it once centrally rather than file-by-file. (Every occurrence still counts toward the score and metrics.)
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · Critical IaC · ×2
  • REDACTED
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'ini' · ×2
  • Unlisted import 'ini' bun/helpers/lib/npm/vulnerability-auditor.js:237 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
  • Unlisted import 'ini' npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts:35 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
D11 · Test Reliability · Test suite cannot be installed from its own lockfile · ×1
  • Test suite cannot be installed from its own lockfile: npm_and_yarn/spec/fixtures/projects/npm6/path_dependency/deps/etag/ — The mocha suite in npm_and_yarn/spec/fixtures/projects/npm6/path_dependency/deps/etag/ was never exercised because its dependency install refused the committed lockfile — the dependency install for npm_and_yarn/spec/fixtures/projects/npm6/path_dependency/deps/etag/ refused the committed lockfile (npm error code EUSAGE), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
D13 · Secret Scanning · Leaked secret · ×1
  • REDACTED
D17 · Explicit Debt · DisabledAnalyzers · ×1
  • DisabledAnalyzers nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/DependencyDiscovery.props:15 — RunAnalyzers — this does not switch a rule off, it stops the analyzers running for the whole project: every rule they ship is silenced at once, including every rule added by a future upgrade, and nothing at the sites they would have reported records that anything was switched off. There is no code here to look up and nothing to weigh, which is what makes it the one suppression that is never revisited. Turn the analyzers back on and deal with what they report — suppressing the handful of rules that are genuinely unwanted, each on its own line with its reason, keeps the rest protecting the project and leaves a record a reader can audit.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
P3 · Security & performance tooling · NuGet vulnerability audit disabled (csproj) · ×1
  • NuGet vulnerability audit disabled (csproj) nuget/helpers/lib/NuGetUpdater/Directory.Build.props:8 — <NuGetAudit>false</NuGetAudit> in MSBuild suppresses NuGet's vulnerability audit project-wide.
P3 · Security & performance tooling · NuGet vulnerability audit suppressed via NoWarn · ×1
  • NuGet vulnerability audit suppressed via NoWarn nuget/helpers/lib/NuGetUpdater/NuGetProjects/Directory.Build.props:8 — `NoWarn` silences NU1903 — NuGet's vulnerability-audit warnings for high advisories. Suppressed advisories are still shipped; they are only invisible in the build log. Remove these codes from NoWarn and address or explicitly accept each advisory instead.
Serious — 1114 finding(s)
D31 · IaC & Container Security · Medium IaC · ×84
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 59 more in this group — see findings.md.
D3 · God Classes · TooManyMethods · ×71
  • TooManyMethods: UpdateChecker docker/lib/dependabot/docker/update_checker.rb:56 — TooManyMethods — 110 methods. The bar is 30 methods; this is 80 over it, 3.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: GitCommitChecker common/lib/dependabot/git_commit_checker.rb:27 — TooManyMethods — 88 methods. The bar is 30 methods; this is 58 over it, 2.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Helpers npm_and_yarn/lib/dependabot/npm_and_yarn/helpers.rb:19 — TooManyMethods — 77 methods. The bar is 30 methods; this is 47 over it, 2.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: NpmLockfileUpdater npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:21 — TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MessageBuilder common/lib/dependabot/pull_request_creator/message_builder.rb:21 — TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LockfileUpdater cargo/lib/dependabot/cargo/file_updater/lockfile_updater.rb:17 — TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FileFetcher npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:20 — TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Base common/lib/dependabot/file_fetchers/base.rb:44 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PrNamePrefixer common/lib/dependabot/pull_request_creator/pr_name_prefixer.rb:17 — TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: LockFileUpdater uv/lib/dependabot/uv/file_updater/lock_file_updater.rb:22 — TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PnpmLockfileUpdater npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:15 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PipCompileFileUpdater python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:21 — TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Dependency common/lib/dependabot/dependency.rb:9 — TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: YarnLockfileUpdater npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/yarn_lockfile_updater.rb:20 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: UpdateChecker python/lib/dependabot/python/update_checker.rb:23 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Labeler common/lib/dependabot/pull_request_creator/labeler.rb:13 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FileParser npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:26 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ProjectFactory nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs — TooManyMethods — 648 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: UpdateChecker npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:14 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Job updater/lib/dependabot/job.rb:38 — TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FileParser gradle/lib/dependabot/gradle/file_parser.rb:24 — TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: VersionResolver cargo/lib/dependabot/cargo/update_checker/version_resolver.rb:15 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: ChangelogFinder common/lib/dependabot/metadata_finders/base/changelog_finder.rb:28 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: VersionResolver bun/lib/dependabot/bun/update_checker/version_resolver.rb:28 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: FileParser python/lib/dependabot/python/file_parser.rb:21 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • + 46 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×41
  • Duplicated block (6 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:354 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:354-359 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:520-525 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:181 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:181-186 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:202-207 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (6 lines × 2) bun/lib/dependabot/bun/constraint_helper.rb:181 — bun/lib/dependabot/bun/constraint_helper.rb:181-186 | npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb:181-186 — before extracting anything, compare `bun/lib/dependabot/bun/constraint_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 138 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 (6 lines × 2) bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:97 — bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:97-102 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb:223-228 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:97` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb:218` calls `must` and `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:91` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:44 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:44-49 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:46-51 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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 (6 lines × 2) bundler/lib/dependabot/bundler/file_fetcher/gemspec_finder.rb:77 — bundler/lib/dependabot/bundler/file_fetcher/gemspec_finder.rb:77-82 | bundler/lib/dependabot/bundler/file_fetcher/path_gemspec_finder.rb:77-82 — 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) cargo/lib/dependabot/cargo/package/package_details_fetcher.rb:169 — cargo/lib/dependabot/cargo/package/package_details_fetcher.rb:169-174 | cargo/lib/dependabot/cargo/update_checker/latest_version_finder.rb:49-54 — 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 (6 lines × 2) docker/lib/dependabot/docker/version.rb:33 — docker/lib/dependabot/docker/version.rb:33-38 | helm/lib/dependabot/helm/version.rb:36-41 — before extracting anything, compare `docker/lib/dependabot/docker/version.rb` and `helm/lib/dependabot/helm/version.rb` as WHOLE FILES: 82% 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 (6 lines × 2) REDACTED:465 — REDACTED:465-470 | REDACTED:300-307 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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:465` 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 (6 lines × 2) bazel/lib/dependabot/bazel/file_updater.rb:67 — bazel/lib/dependabot/bazel/file_updater.rb:67-72 | bazel/lib/dependabot/bazel/file_updater/workspace_file_updater.rb:48-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 (6 lines × 2) bun/lib/dependabot/bun/dependency_files_filterer.rb:42 — bun/lib/dependabot/bun/dependency_files_filterer.rb:42-47 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:42-47 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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 (6 lines × 2) bun/lib/dependabot/bun/dependency_files_filterer.rb:70 — bun/lib/dependabot/bun/dependency_files_filterer.rb:70-75 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:70-75 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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 (6 lines × 2) bun/lib/dependabot/bun/dependency_files_filterer.rb:100 — bun/lib/dependabot/bun/dependency_files_filterer.rb:100-105 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:101-106 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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 (6 lines × 2) bun/lib/dependabot/bun/dependency_files_filterer.rb:110 — bun/lib/dependabot/bun/dependency_files_filterer.rb:110-115 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:111-116 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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 (6 lines × 2) bun/lib/dependabot/bun/file_fetcher.rb:390 — bun/lib/dependabot/bun/file_fetcher.rb:390-395 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:774-779 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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 (6 lines × 2) bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:82 — bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:82-87 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb:82-87 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 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 (6 lines × 2) bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:182 — bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:182-187 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb:182-187 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 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 (6 lines × 2) bun/lib/dependabot/bun/file_parser.rb:54 — bun/lib/dependabot/bun/file_parser.rb:54-59 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:52-57 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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 (6 lines × 2) bun/lib/dependabot/bun/file_parser.rb:336 — bun/lib/dependabot/bun/file_parser.rb:336-341 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:463-468 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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 (6 lines × 2) bun/lib/dependabot/bun/file_updater.rb:141 — bun/lib/dependabot/bun/file_updater.rb:141-146 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:361-366 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb` as WHOLE FILES: this scan already matched 6 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 (6 lines × 2) bun/lib/dependabot/bun/file_updater.rb:187 — bun/lib/dependabot/bun/file_updater.rb:187-192 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:585-590 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb` as WHOLE FILES: this scan already matched 6 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 (6 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:66 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:66-71 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:68-73 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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 (6 lines × 2) bun/lib/dependabot/bun/package/registry_finder.rb:123 — bun/lib/dependabot/bun/package/registry_finder.rb:123-128 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb:125-130 — before extracting anything, compare `bun/lib/dependabot/bun/package/registry_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 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 (6 lines × 2) bun/lib/dependabot/bun/update_checker/library_detector.rb:50 — bun/lib/dependabot/bun/update_checker/library_detector.rb:50-55 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/library_detector.rb:50-55 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/library_detector.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/library_detector.rb` as WHOLE FILES: 89% 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb:124 — bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb:124-129 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb:223-228 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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.
  • + 16 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×41
  • Duplicated block (8 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:300 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:300-307 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:318-325 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:300` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:318` calls `Contains` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:300` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:452 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:452-459 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:472-479 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:452` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8 lines × 2) apm/lib/dependabot/apm/version.rb:214 — apm/lib/dependabot/apm/version.rb:214-221 | vcpkg/lib/dependabot/vcpkg/version.rb:194-201 — 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) bun/lib/dependabot/bun/file_updater/package_json_preparer.rb:88 — bun/lib/dependabot/bun/file_updater/package_json_preparer.rb:88-95 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_preparer.rb:88-95 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_preparer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_preparer.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 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 (8 lines × 2) bun/lib/dependabot/bun/package/registry_finder.rb:45 — bun/lib/dependabot/bun/package/registry_finder.rb:45-52 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb:46-53 — before extracting anything, compare `bun/lib/dependabot/bun/package/registry_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 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 (8 lines × 2) bundler/helpers/v2/lib/functions.rb:41 — bundler/helpers/v2/lib/functions.rb:41-48 | bundler/helpers/v4/lib/functions.rb:41-48 — before extracting anything, compare `bundler/helpers/v2/lib/functions.rb` and `bundler/helpers/v4/lib/functions.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 101 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 (8 lines × 2) bundler/helpers/v2/lib/functions.rb:61 — bundler/helpers/v2/lib/functions.rb:61-68 | bundler/helpers/v4/lib/functions.rb:61-68 — before extracting anything, compare `bundler/helpers/v2/lib/functions.rb` and `bundler/helpers/v4/lib/functions.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 101 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 (8 lines × 2) cargo/lib/dependabot/cargo/file_fetcher.rb:109 — cargo/lib/dependabot/cargo/file_fetcher.rb:109-116 | cargo/lib/dependabot/cargo/file_fetcher.rb:146-153 — 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) cargo/lib/dependabot/cargo/file_updater/lockfile_updater.rb:433 — cargo/lib/dependabot/cargo/file_updater/lockfile_updater.rb:433-440 | cargo/lib/dependabot/cargo/update_checker/version_resolver.rb:333-340 — 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) cargo/lib/dependabot/cargo/file_updater/lockfile_updater.rb:451 — cargo/lib/dependabot/cargo/file_updater/lockfile_updater.rb:451-458 | cargo/lib/dependabot/cargo/update_checker/version_resolver.rb:595-602 — 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) common/lib/dependabot/pull_request_creator/github.rb:309 — common/lib/dependabot/pull_request_creator/github.rb:309-316 | common/lib/dependabot/pull_request_updater/github.rb:169-176 — `common/lib/dependabot/pull_request_creator/github.rb` and `common/lib/dependabot/pull_request_updater/github.rb` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 49 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (8 lines × 2) opentofu/lib/dependabot/opentofu/requirements_updater.rb:65 — opentofu/lib/dependabot/opentofu/requirements_updater.rb:65-72 | terraform/lib/dependabot/terraform/requirements_updater.rb:65-72 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/requirements_updater.rb` and `terraform/lib/dependabot/terraform/requirements_updater.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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 (8 lines × 2) python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:90 — python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:90-97 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:93-100 — before extracting anything, compare `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 186 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 (8 lines × 2) vcpkg/lib/dependabot/vcpkg/update_checker/latest_version_finder.rb:103 — vcpkg/lib/dependabot/vcpkg/update_checker/latest_version_finder.rb:103-110 | vcpkg/lib/dependabot/vcpkg/update_checker/security_fix_resolver.rb:270-277 — 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 (8 lines × 2) bun/lib/dependabot/bun/dependency_files_filterer.rb:30 — bun/lib/dependabot/bun/dependency_files_filterer.rb:30-37 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:30-37 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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 (8 lines × 2) bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:42 — bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:42-49 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb:42-49 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 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 (8 lines × 2) bun/lib/dependabot/bun/file_parser/lockfile_parser.rb:52 — bun/lib/dependabot/bun/file_parser/lockfile_parser.rb:52-59 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser/lockfile_parser.rb:56-63 — 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) bun/lib/dependabot/bun/file_updater/bun_lockfile_updater.rb:300 — bun/lib/dependabot/bun/file_updater/bun_lockfile_updater.rb:300-307 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:1178-1185 — 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) bun/lib/dependabot/bun/file_updater/package_json_preparer.rb:31 — bun/lib/dependabot/bun/file_updater/package_json_preparer.rb:31-38 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_preparer.rb:31-38 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_preparer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_preparer.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 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 `bun/lib/dependabot/bun/file_updater/package_json_preparer.rb:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:318 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:318-325 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:325-332 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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 (8 lines × 2) bun/lib/dependabot/bun/package/registry_finder.rb:274 — bun/lib/dependabot/bun/package/registry_finder.rb:274-281 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb:274-281 — before extracting anything, compare `bun/lib/dependabot/bun/package/registry_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 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 (8 lines × 2) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:142 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:142-149 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:138-145 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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 (8 lines × 2) bundler/helpers/v2/lib/functions/force_updater.rb:179 — bundler/helpers/v2/lib/functions/force_updater.rb:179-186 | bundler/helpers/v4/lib/functions/force_updater.rb:179-186 — before extracting anything, compare `bundler/helpers/v2/lib/functions/force_updater.rb` and `bundler/helpers/v4/lib/functions/force_updater.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 115 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 (8 lines × 2) bundler/helpers/v2/lib/functions/lockfile_updater.rb:112 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:112-119 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:112-119 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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 (8 lines × 2) bundler/helpers/v2/lib/functions/version_resolver.rb:88 — bundler/helpers/v2/lib/functions/version_resolver.rb:88-95 | bundler/helpers/v4/lib/functions/version_resolver.rb:88-95 — before extracting anything, compare `bundler/helpers/v2/lib/functions/version_resolver.rb` and `bundler/helpers/v4/lib/functions/version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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.
  • + 16 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking bun/helpers/lib/npm6/subdependency-updater.js:12 — `fs.readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/npm6/subdependency-updater.js:23 — `fs.writeFileSync` in `updateDependencyFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:26 — `fs.readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/yarn/conflicting-dependency-parser.js:21 — `fs.readFileSync` in `findConflictingDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/yarn/lockfile-parser.js:16 — `fs.readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/yarn/subdependency-updater.js:30 — `fs.readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/yarn/subdependency-updater.js:66 — `fs.writeFileSync` in `updateDependencyFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/yarn/updater.js:105 — `fs.readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/yarn/updater.js:130 — `fs.readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/yarn/updater.js:188 — `fs.writeFileSync` in `updateDependencyFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking bun/helpers/lib/yarn/updater.js:192 — `fs.writeFileSync` in `updateDependencyFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:847 — `existsSync` in `mkdirpPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1103 — `lstatSync` in `preserveTimeSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1108 — `lutimesSync` in `preserveTimeSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1110 — `utimesSync` in `preserveTimeSync` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1915 — `openSync` in `openPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1926 — `opendirSync` in `opendirPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1943 — `readSync` in `readPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1959 — `writeSync` in `writePromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1961 — `writeSync` in `writePromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:1971 — `closeSync` in `closePromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2048 — `realpathSync` in `realpathPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2057 — `existsSync` in `existsPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2077 — `accessSync` in `accessPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:2089 — `statSync` in `statPromise` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • + 15 more in this group — see findings.md.
R11 · Import Boundaries · Boundary violation [package · ×40
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/npm6/peer-dependency-checker.js:14 — bun/helpers/lib/npm6/peer-dependency-checker.js:14 imports npm/lib/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/npm6/subdependency-updater.js:4 — bun/helpers/lib/npm6/subdependency-updater.js:4 imports npm/lib/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] REDACTED:20 — REDACTED:20 imports npm/lib/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/fix-duplicates.js:1 — bun/helpers/lib/yarn/fix-duplicates.js:1 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/fix-duplicates.js:2 — bun/helpers/lib/yarn/fix-duplicates.js:2 imports @dependabot/yarn-lib/lib/lockfile/stringify, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/helpers.js:1 — bun/helpers/lib/yarn/helpers.js:1 imports @dependabot/yarn-lib/lib/cli/commands/add, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/helpers.js:2 — bun/helpers/lib/yarn/helpers.js:2 imports @dependabot/yarn-lib/lib/cli/commands/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/lockfile-parser.js:11 — bun/helpers/lib/yarn/lockfile-parser.js:11 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/peer-dependency-checker.js:13 — bun/helpers/lib/yarn/peer-dependency-checker.js:13 imports @dependabot/yarn-lib/lib/cli/commands/add, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/peer-dependency-checker.js:14 — bun/helpers/lib/yarn/peer-dependency-checker.js:14 imports @dependabot/yarn-lib/lib/config, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/peer-dependency-checker.js:15 — bun/helpers/lib/yarn/peer-dependency-checker.js:15 imports @dependabot/yarn-lib/lib/reporters, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/peer-dependency-checker.js:16 — bun/helpers/lib/yarn/peer-dependency-checker.js:16 imports @dependabot/yarn-lib/lib/lockfile, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/peer-dependency-checker.js:18 — bun/helpers/lib/yarn/peer-dependency-checker.js:18 imports @dependabot/yarn-lib/lib/package-fetcher.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/replace-lockfile-declaration.js:1 — bun/helpers/lib/yarn/replace-lockfile-declaration.js:1 imports @dependabot/yarn-lib/lib/lockfile/parse, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/replace-lockfile-declaration.js:2 — bun/helpers/lib/yarn/replace-lockfile-declaration.js:2 imports @dependabot/yarn-lib/lib/lockfile/stringify, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/subdependency-updater.js:4 — bun/helpers/lib/yarn/subdependency-updater.js:4 imports @dependabot/yarn-lib/lib/config, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/subdependency-updater.js:5 — bun/helpers/lib/yarn/subdependency-updater.js:5 imports @dependabot/yarn-lib/lib/reporters, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/subdependency-updater.js:6 — bun/helpers/lib/yarn/subdependency-updater.js:6 imports @dependabot/yarn-lib/lib/lockfile, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/subdependency-updater.js:11 — bun/helpers/lib/yarn/subdependency-updater.js:11 imports @dependabot/yarn-lib/lib/lockfile/stringify, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/updater.js:17 — bun/helpers/lib/yarn/updater.js:17 imports @dependabot/yarn-lib/lib/cli/commands/add, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/updater.js:18 — bun/helpers/lib/yarn/updater.js:18 imports @dependabot/yarn-lib/lib/cli/commands/install, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/updater.js:21 — bun/helpers/lib/yarn/updater.js:21 imports @dependabot/yarn-lib/lib/cli/commands/upgrade, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/updater.js:22 — bun/helpers/lib/yarn/updater.js:22 imports @dependabot/yarn-lib/lib/config, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/updater.js:23 — bun/helpers/lib/yarn/updater.js:23 imports @dependabot/yarn-lib/lib/reporters, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] bun/helpers/lib/yarn/updater.js:24 — bun/helpers/lib/yarn/updater.js:24 imports @dependabot/yarn-lib/lib/lockfile, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • + 15 more in this group — see findings.md.
X2 · Cancellation propagation · Async method without CancellationToken · ×37
  • Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/DotNetPackageCorrelation/Correlator.cs:24 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:39 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunWithErrorHandlingAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:46 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:70 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DeserializeJsonFileAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:242 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: WriteResultsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:543 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Clone/CloneWorker.cs:26 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Clone/CloneWorker.cs:63 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ReportError nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Clone/CloneWorker.cs:94 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunGitCommandAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Clone/ShellGitCommandHandler.cs:14 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: SolveAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/DependencySolver/MSBuildDependencySolver.cs:20 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:45 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunWithErrorHandlingAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:51 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:71 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: TryRestoreMSBuildSdksAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:189 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunForDirectoryAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:211 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: ExpandEntryPointsIntoProjectsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:284 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: RunForProjectPathsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:427 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: WriteResultsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:636 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: FindRootDirectoriesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/EntryPointFinder.cs:23 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: BuildChildToParentMapAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/EntryPointFinder.cs:106 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetChildrenOfEntryPointAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/EntryPointFinder.cs:128 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: GetChildrenOfSlnxAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/EntryPointFinder.cs:156 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: Discover nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/PackagesConfigDiscovery.cs:9 — No CancellationToken parameter — this work can't be stopped early once started.
  • Async method without CancellationToken: DiscoverAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:76 — No CancellationToken parameter — this work can't be stopped early once started.
  • + 12 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×36
  • Duplicated block (7 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:965 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:965-971 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:993-999 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:965` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:1000` calls `GetChildMetadataValue` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:972` 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 (7 lines × 2) bun/lib/dependabot/bun/file_parser/lockfile_parser.rb:69 — bun/lib/dependabot/bun/file_parser/lockfile_parser.rb:69-75 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser/lockfile_parser.rb:73-79 — 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) bun/lib/dependabot/bun/update_checker/version_resolver.rb:97 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:97-103 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:155-161 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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) bundler/helpers/v2/lib/functions.rb:81 — bundler/helpers/v2/lib/functions.rb:81-87 | bundler/helpers/v4/lib/functions.rb:81-87 — before extracting anything, compare `bundler/helpers/v2/lib/functions.rb` and `bundler/helpers/v4/lib/functions.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 101 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) conda/lib/dependabot/conda/file_updater.rb:166 — conda/lib/dependabot/conda/file_updater.rb:166-172 | conda/lib/dependabot/conda/file_updater.rb:212-218 — 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) python/lib/dependabot/python/update_checker.rb:365 — python/lib/dependabot/python/update_checker.rb:365-371 | uv/lib/dependabot/uv/update_checker.rb:187-193 — 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 (7 lines × 2) bun/lib/dependabot/bun/constraint_helper.rb:356 — bun/lib/dependabot/bun/constraint_helper.rb:356-362 | npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb:466-472 — before extracting anything, compare `bun/lib/dependabot/bun/constraint_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 138 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) bun/lib/dependabot/bun/dependency_files_filterer.rb:120 — bun/lib/dependabot/bun/dependency_files_filterer.rb:120-126 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:121-127 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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) bun/lib/dependabot/bun/file_parser.rb:369 — bun/lib/dependabot/bun/file_parser.rb:369-375 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:496-502 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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) bun/lib/dependabot/bun/file_parser.rb:504 — bun/lib/dependabot/bun/file_parser.rb:504-510 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:637-643 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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) bun/lib/dependabot/bun/update_checker.rb:74 — bun/lib/dependabot/bun/update_checker.rb:74-80 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:84-90 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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) bun/lib/dependabot/bun/update_checker.rb:149 — bun/lib/dependabot/bun/update_checker.rb:149-155 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:159-165 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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) bun/lib/dependabot/bun/update_checker.rb:315 — bun/lib/dependabot/bun/update_checker.rb:315-321 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:381-387 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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) bun/lib/dependabot/bun/update_checker.rb:396 — bun/lib/dependabot/bun/update_checker.rb:396-402 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:462-468 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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) bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:332 — bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:332-338 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb:374-380 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/latest_version_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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) bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb:145 — bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb:145-151 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/subdependency_version_resolver.rb:377-383 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/subdependency_version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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) bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb:156 — bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb:156-162 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/subdependency_version_resolver.rb:388-394 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/subdependency_version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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) bun/lib/dependabot/bun/update_checker/version_resolver.rb:312 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:312-318 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:459-465 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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) bun/lib/dependabot/bun/update_checker/version_resolver.rb:323 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:323-329 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:470-476 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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) bun/lib/dependabot/bun/update_checker/version_resolver.rb:387 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:387-393 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:534-540 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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) bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb:40 — bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb:40-46 | bundler/helpers/v4/lib/functions/conflicting_dependency_resolver.rb:40-46 — before extracting anything, compare `bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb` and `bundler/helpers/v4/lib/functions/conflicting_dependency_resolver.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 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 (7 lines × 2) bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb:50 — bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb:50-56 | bundler/helpers/v4/lib/functions/conflicting_dependency_resolver.rb:50-56 — before extracting anything, compare `bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb` and `bundler/helpers/v4/lib/functions/conflicting_dependency_resolver.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 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 (7 lines × 2) bundler/helpers/v2/lib/functions/file_parser.rb:90 — bundler/helpers/v2/lib/functions/file_parser.rb:90-96 | bundler/helpers/v4/lib/functions/file_parser.rb:90-96 — before extracting anything, compare `bundler/helpers/v2/lib/functions/file_parser.rb` and `bundler/helpers/v4/lib/functions/file_parser.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 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 (7 lines × 2) bundler/helpers/v2/run.rb:16 — bundler/helpers/v2/run.rb:16-22 | bundler/helpers/v4/run.rb:15-21 — `bundler/helpers/v2/run.rb` and `bundler/helpers/v4/run.rb` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 24 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (7 lines × 2) common/lib/dependabot/config/update_config.rb:67 — common/lib/dependabot/config/update_config.rb:67-73 | common/lib/wildcard_matcher.rb:11-17 — 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.
  • + 11 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×36
  • Duplicated block (5 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/DotNetToolsJsonUpdater.cs:24 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/DotNetToolsJsonUpdater.cs:24-28 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/GlobalJsonUpdater.cs:24-28 — 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 (5 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:181 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:181-185 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:80-84 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 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) bun/lib/dependabot/bun/dependency_files_filterer.rb:91 — bun/lib/dependabot/bun/dependency_files_filterer.rb:91-95 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:90-96 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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 `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:90` 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 (5 lines × 2) bun/lib/dependabot/bun/file_parser.rb:494 — bun/lib/dependabot/bun/file_parser.rb:494-498 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:627-631 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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 (5 lines × 2) bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:203 — bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:203-207 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb:404-408 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:203` 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 (5 lines × 2) bundler/lib/dependabot/bundler/update_checker/cooldown_options_builder.rb:58 — bundler/lib/dependabot/bundler/update_checker/cooldown_options_builder.rb:58-66 | npm_and_yarn/lib/dependabot/npm_and_yarn/helpers.rb:263-267 — 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 `bundler/lib/dependabot/bundler/update_checker/cooldown_options_builder.rb:58` 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 (5 lines × 2) gradle/lib/dependabot/gradle/file_updater/lockfile_updater.rb:231 — gradle/lib/dependabot/gradle/file_updater/lockfile_updater.rb:231-235 | gradle/lib/dependabot/gradle/file_updater/wrapper_updater.rb:296-300 — 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) maven/lib/dependabot/maven/version.rb:84 — maven/lib/dependabot/maven/version.rb:84-89 | maven/lib/dependabot/maven/version.rb:101-105 — 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 `maven/lib/dependabot/maven/version.rb:84` 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 (5 lines × 2) updater/lib/dependabot/api_client.rb:41 — updater/lib/dependabot/api_client.rb:41-45 | updater/lib/dependabot/api_client.rb:67-71 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (5 lines × 2) bazel/lib/dependabot/bazel/requirement.rb:42 — bazel/lib/dependabot/bazel/requirement.rb:42-46 | bundler/lib/dependabot/bundler/requirement.rb:66-70 — 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) bun/lib/dependabot/bun/dependency_files_filterer.rb:61 — bun/lib/dependabot/bun/dependency_files_filterer.rb:61-65 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:61-65 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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 (5 lines × 2) bun/lib/dependabot/bun/dependency_files_filterer.rb:80 — bun/lib/dependabot/bun/dependency_files_filterer.rb:80-84 | npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb:80-84 — before extracting anything, compare `bun/lib/dependabot/bun/dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_files_filterer.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 56 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 (5 lines × 2) bun/lib/dependabot/bun/dependency_files_filterer.rb:140 — bun/lib/dependabot/bun/dependency_files_filterer.rb:140-144 | bun/lib/dependabot/bun/sub_dependency_files_filterer.rb:53-57 — 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) bun/lib/dependabot/bun/file_fetcher.rb:407 — bun/lib/dependabot/bun/file_fetcher.rb:407-411 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:885-889 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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 (5 lines × 2) bun/lib/dependabot/bun/file_updater/bun_lockfile_updater.rb:282 — bun/lib/dependabot/bun/file_updater/bun_lockfile_updater.rb:282-286 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:1124-1128 — 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) bun/lib/dependabot/bun/metadata_finder.rb:51 — bun/lib/dependabot/bun/metadata_finder.rb:51-55 | npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb:108-112 — before extracting anything, compare `bun/lib/dependabot/bun/metadata_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 (5 lines × 2) bun/lib/dependabot/bun/metadata_finder.rb:122 — bun/lib/dependabot/bun/metadata_finder.rb:122-126 | npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb:210-214 — before extracting anything, compare `bun/lib/dependabot/bun/metadata_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 (5 lines × 2) bun/lib/dependabot/bun/package_name.rb:43 — bun/lib/dependabot/bun/package_name.rb:43-47 | npm_and_yarn/lib/dependabot/npm_and_yarn/package_name.rb:43-47 — before extracting anything, compare `bun/lib/dependabot/bun/package_name.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package_name.rb` as WHOLE FILES: 98% 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 (5 lines × 2) bun/lib/dependabot/bun/registry_helper.rb:165 — bun/lib/dependabot/bun/registry_helper.rb:165-169 | npm_and_yarn/lib/dependabot/npm_and_yarn/registry_helper.rb:337-341 — before extracting anything, compare `bun/lib/dependabot/bun/registry_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/registry_helper.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 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 (5 lines × 2) bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:230 — bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:230-234 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb:249-253 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/latest_version_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (5 lines × 2) bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb:141 — bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb:141-145 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb:240-244 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 (5 lines × 2) bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb:150 — bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb:150-154 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb:249-253 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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 (5 lines × 2) bun/lib/dependabot/bun/version.rb:47 — bun/lib/dependabot/bun/version.rb:47-51 | npm_and_yarn/lib/dependabot/npm_and_yarn/version.rb:47-51 — before extracting anything, compare `bun/lib/dependabot/bun/version.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/version.rb` as WHOLE FILES: 94% 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. 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 (5 lines × 2) common/lib/dependabot/metadata_finders/base/changelog_finder.rb:615 — common/lib/dependabot/metadata_finders/base/changelog_finder.rb:615-619 | common/lib/dependabot/metadata_finders/base/commits_finder.rb:403-407 — 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) composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:159 — composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:159-163 | composer/lib/dependabot/composer/update_checker/version_resolver.rb:183-187 — before extracting anything, compare `composer/lib/dependabot/composer/file_updater/lockfile_updater.rb` and `composer/lib/dependabot/composer/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 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.
  • + 11 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×26
  • FileTooLong: docker/update_checker.rb docker/lib/dependabot/docker/update_checker.rb — FileTooLong — 1213 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 713 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: file_updater/npm_lockfile_updater.rb npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb — FileTooLong — 994 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 494 over it, 1.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: file_updater/pnpm_lockfile_updater.rb npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb — FileTooLong — 885 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 385 over it, 1.77× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: npm_and_yarn/helpers.rb npm_and_yarn/lib/dependabot/npm_and_yarn/helpers.rb — FileTooLong — 876 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 376 over it, 1.75× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: file_fetchers/base.rb common/lib/dependabot/file_fetchers/base.rb — FileTooLong — 795 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 295 over it, 1.59× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: file_updater/yarn_lockfile_updater.rb npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/yarn_lockfile_updater.rb — FileTooLong — 795 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 295 over it, 1.59× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: pull_request_creator/message_builder.rb common/lib/dependabot/pull_request_creator/message_builder.rb — FileTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 262 over it, 1.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: dependabot/git_commit_checker.rb common/lib/dependabot/git_commit_checker.rb — FileTooLong — 721 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 221 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 714 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 214 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Commands/ProjectFactory.cs nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs — FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 213 over it, 1.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: dependabot/errors.rb common/lib/dependabot/errors.rb — FileTooLong — 705 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 205 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: file_updater/lockfile_updater.rb cargo/lib/dependabot/cargo/file_updater/lockfile_updater.rb — FileTooLong — 681 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 181 over it, 1.36× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: npm_and_yarn/file_fetcher.rb npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb — FileTooLong — 636 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 136 over it, 1.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: file_updater/pip_compile_file_updater.rb python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb — FileTooLong — 630 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 130 over it, 1.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: FileWriters/XmlFileWriter.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs — FileTooLong — 618 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 118 over it, 1.24× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: update_checker/version_resolver.rb bun/lib/dependabot/bun/update_checker/version_resolver.rb — FileTooLong — 613 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 113 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: npm_and_yarn/update_checker.rb npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb — FileTooLong — 609 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 109 over it, 1.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: gradle/file_parser.rb gradle/lib/dependabot/gradle/file_parser.rb — FileTooLong — 607 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 107 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: file_updater/lock_file_updater.rb uv/lib/dependabot/uv/file_updater/lock_file_updater.rb — FileTooLong — 605 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 105 over it, 1.21× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Discover/SdkProjectDiscovery.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs — FileTooLong — 596 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 96 over it, 1.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: update_checker/version_resolver.rb cargo/lib/dependabot/cargo/update_checker/version_resolver.rb — FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: pull_request_creator/pr_name_prefixer.rb common/lib/dependabot/pull_request_creator/pr_name_prefixer.rb — FileTooLong — 533 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 33 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: file_updater/compile_file_updater.rb uv/lib/dependabot/uv/file_updater/compile_file_updater.rb — FileTooLong — 528 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 28 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Utilities/MSBuildHelper.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs — FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 26 over it, 1.05× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: base/changelog_finder.rb common/lib/dependabot/metadata_finders/base/changelog_finder.rb — FileTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 19 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • + 1 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×26
  • Duplicated block (9 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/NuGetContext.cs:111 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/NuGetContext.cs:111-119 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:78-86 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/NuGetContext.cs:111` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:377 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:377-385 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:541-549 — 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) bun/lib/dependabot/bun/update_checker/version_resolver.rb:440 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:440-448 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:606-614 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:808 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:808-816 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:1111-1119 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 (9 lines × 2) bun/lib/dependabot/bun/version.rb:68 — bun/lib/dependabot/bun/version.rb:68-76 | npm_and_yarn/lib/dependabot/npm_and_yarn/version.rb:68-76 — before extracting anything, compare `bun/lib/dependabot/bun/version.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/version.rb` as WHOLE FILES: 94% 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 (9 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:721 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:721-729 | python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:456-464 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 lines × 2) updater/lib/dependabot/updater/operations/refresh_version_update_pull_request.rb:264 — updater/lib/dependabot/updater/operations/refresh_version_update_pull_request.rb:264-272 | updater/lib/dependabot/updater/operations/update_all_versions.rb:247-255 — 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 `updater/lib/dependabot/updater/operations/refresh_version_update_pull_request.rb:264` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:495 — uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:495-503 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:271-279 — before extracting anything, compare `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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 lines × 2) bun/lib/dependabot/bun/file_fetcher.rb:117 — bun/lib/dependabot/bun/file_fetcher.rb:117-125 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:351-359 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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 lines × 2) bun/lib/dependabot/bun/file_fetcher.rb:318 — bun/lib/dependabot/bun/file_fetcher.rb:318-326 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:683-691 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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 lines × 2) bun/lib/dependabot/bun/metadata_finder.rb:35 — bun/lib/dependabot/bun/metadata_finder.rb:35-43 | npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb:42-50 — before extracting anything, compare `bun/lib/dependabot/bun/metadata_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 (9 lines × 2) bun/lib/dependabot/bun/metadata_finder.rb:60 — bun/lib/dependabot/bun/metadata_finder.rb:60-68 | npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb:138-146 — before extracting anything, compare `bun/lib/dependabot/bun/metadata_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 (9 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:184 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:184-192 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:191-199 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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 (9 lines × 2) bun/lib/dependabot/bun/update_checker.rb:241 — bun/lib/dependabot/bun/update_checker.rb:241-249 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:281-289 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 lines × 2) bun/lib/dependabot/bun/update_checker.rb:512 — bun/lib/dependabot/bun/update_checker.rb:512-520 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:581-589 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 (9 lines × 2) bun/lib/dependabot/bun/update_checker.rb:538 — bun/lib/dependabot/bun/update_checker.rb:538-546 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:607-615 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 lines × 2) composer/lib/dependabot/composer/update_checker.rb:204 — composer/lib/dependabot/composer/update_checker.rb:204-212 | nix/lib/dependabot/nix/update_checker.rb:312-320 — 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) github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:291 — github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:291-299 | github_actions/lib/dependabot/github_actions/update_checker/latest_version_finder.rb:420-428 — 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) maven/lib/dependabot/maven/file_parser.rb:458 — maven/lib/dependabot/maven/file_parser.rb:458-466 | maven/lib/dependabot/maven/file_parser/repositories_finder.rb:308-318 — 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 (9 lines × 2) REDACTED:565 — REDACTED:565-573 | REDACTED:451-459 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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 lines × 2) REDACTED:582 — REDACTED:582-590 | REDACTED:423-431 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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 (9 lines × 2) opentofu/lib/dependabot/opentofu/update_checker.rb:254 — opentofu/lib/dependabot/opentofu/update_checker.rb:254-262 | terraform/lib/dependabot/terraform/update_checker.rb:233-241 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/update_checker.rb` and `terraform/lib/dependabot/terraform/update_checker.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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 lines × 2) python/lib/dependabot/python/update_checker.rb:281 — python/lib/dependabot/python/update_checker.rb:281-289 | uv/lib/dependabot/uv/update_checker.rb:110-118 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:583 — uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:583-591 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:473-481 — before extracting anything, compare `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 54 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 lines × 2) dotnet_sdk/lib/dependabot/dotnet_sdk/update_checker.rb:45 — dotnet_sdk/lib/dependabot/dotnet_sdk/update_checker.rb:45-53 | rust_toolchain/lib/dependabot/rust_toolchain/update_checker.rb:34-42 — before extracting anything, compare `dotnet_sdk/lib/dependabot/dotnet_sdk/update_checker.rb` and `rust_toolchain/lib/dependabot/rust_toolchain/update_checker.rb` as WHOLE FILES: 94% 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.
  • + 1 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×18
  • Duplicated block (11 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:67 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:67-77 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:64-74 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 203 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:76` calls `Info` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:79` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (11 lines × 2) bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:84 — bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:84-94 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb:208-218 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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 `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:84` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) bun/lib/dependabot/bun/registry_parser.rb:44 — bun/lib/dependabot/bun/registry_parser.rb:44-54 | npm_and_yarn/lib/dependabot/npm_and_yarn/registry_parser.rb:44-54 — before extracting anything, compare `bun/lib/dependabot/bun/registry_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/registry_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (11 lines × 2) bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb:20 — bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb:20-30 | bundler/helpers/v4/lib/functions/conflicting_dependency_resolver.rb:20-30 — before extracting anything, compare `bundler/helpers/v2/lib/functions/conflicting_dependency_resolver.rb` and `bundler/helpers/v4/lib/functions/conflicting_dependency_resolver.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 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 (11 lines × 2) bundler/helpers/v2/monkey_patches/git_source_patch.rb:20 — bundler/helpers/v2/monkey_patches/git_source_patch.rb:20-30 | bundler/helpers/v4/monkey_patches/git_source_patch.rb:20-30 — before extracting anything, compare `bundler/helpers/v2/monkey_patches/git_source_patch.rb` and `bundler/helpers/v4/monkey_patches/git_source_patch.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `bundler/helpers/v2/monkey_patches/git_source_patch.rb:20` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:268 — composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:268-278 | composer/lib/dependabot/composer/update_checker/version_resolver.rb:429-439 — before extracting anything, compare `composer/lib/dependabot/composer/file_updater/lockfile_updater.rb` and `composer/lib/dependabot/composer/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 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) gradle/lib/dependabot/gradle/update_checker/requirements_updater.rb:63 — gradle/lib/dependabot/gradle/update_checker/requirements_updater.rb:63-73 | sbt/lib/dependabot/sbt/update_checker/requirements_updater.rb:49-59 — 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) REDACTED:123 — REDACTED:123-133 | REDACTED:70-83 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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:401 — REDACTED:401-411 | REDACTED:287-297 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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) opentofu/lib/dependabot/opentofu/requirements_updater.rb:196 — opentofu/lib/dependabot/opentofu/requirements_updater.rb:196-206 | terraform/lib/dependabot/terraform/requirements_updater.rb:178-188 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/requirements_updater.rb` and `terraform/lib/dependabot/terraform/requirements_updater.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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) bundler/helpers/v2/monkey_patches/endpoint_specification_metadata_patch.rb:23 — bundler/helpers/v2/monkey_patches/endpoint_specification_metadata_patch.rb:23-33 | bundler/helpers/v4/monkey_patches/endpoint_specification_metadata_patch.rb:22-32 — before extracting anything, compare `bundler/helpers/v2/monkey_patches/endpoint_specification_metadata_patch.rb` and `bundler/helpers/v4/monkey_patches/endpoint_specification_metadata_patch.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 (11 lines × 2) bun/lib/dependabot/bun/update_checker.rb:497 — bun/lib/dependabot/bun/update_checker.rb:497-507 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:566-576 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 (11 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:516 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:516-526 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:732-742 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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) bundler/helpers/v2/monkey_patches/definition_ruby_version_patch.rb:23 — bundler/helpers/v2/monkey_patches/definition_ruby_version_patch.rb:23-33 | bundler/helpers/v4/monkey_patches/definition_ruby_version_patch.rb:23-33 — before extracting anything, compare `bundler/helpers/v2/monkey_patches/definition_ruby_version_patch.rb` and `bundler/helpers/v4/monkey_patches/definition_ruby_version_patch.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 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 (11 lines × 2) REDACTED:330 — REDACTED:330-340 | REDACTED:248-258 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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) opentofu/lib/dependabot/opentofu/update_checker/latest_version_resolver.rb:155 — opentofu/lib/dependabot/opentofu/update_checker/latest_version_resolver.rb:155-165 | terraform/lib/dependabot/terraform/update_checker/latest_version_resolver.rb:112-122 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/update_checker/latest_version_resolver.rb` and `terraform/lib/dependabot/terraform/update_checker/latest_version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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) opentofu/lib/dependabot/opentofu/update_checker/latest_version_resolver.rb:170 — opentofu/lib/dependabot/opentofu/update_checker/latest_version_resolver.rb:170-180 | terraform/lib/dependabot/terraform/update_checker/latest_version_resolver.rb:127-137 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/update_checker/latest_version_resolver.rb` and `terraform/lib/dependabot/terraform/update_checker/latest_version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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) swift/lib/dependabot/swift/file_parser/package_resolved_parser.rb:69 — swift/lib/dependabot/swift/file_parser/package_resolved_parser.rb:69-79 | swift/lib/dependabot/swift/file_updater/xcode_lockfile_updater.rb:102-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×18
  • Duplicated block (14 lines × 2) bun/lib/dependabot/bun/file_parser.rb:439 — bun/lib/dependabot/bun/file_parser.rb:439-452 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:567-580 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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 (14 lines × 2) bun/lib/dependabot/bun/metadata_finder.rb:147 — bun/lib/dependabot/bun/metadata_finder.rb:147-160 | npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb:240-253 — before extracting anything, compare `bun/lib/dependabot/bun/metadata_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 (14 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:300 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:300-313 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:307-320 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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 (14 lines × 2) bun/lib/dependabot/bun/package_name.rb:76 — bun/lib/dependabot/bun/package_name.rb:76-89 | npm_and_yarn/lib/dependabot/npm_and_yarn/package_name.rb:76-89 — before extracting anything, compare `bun/lib/dependabot/bun/package_name.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package_name.rb` as WHOLE FILES: 98% 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:207 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:207-220 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:203-216 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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) common/lib/dependabot/errors.rb:135 — common/lib/dependabot/errors.rb:135-148 | common/lib/dependabot/errors.rb:416-429 — 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 `common/lib/dependabot/errors.rb:135` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `common/lib/dependabot/errors.rb:152` calls `params`, `returns`, `nilable` and `common/lib/dependabot/errors.rb:439` 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 (14 lines × 2) deno/lib/dependabot/deno/requirement.rb:55 — deno/lib/dependabot/deno/requirement.rb:55-68 | pub/lib/dependabot/pub/requirement.rb:158-171 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (14 lines × 2) REDACTED:285 — REDACTED:285-298 | REDACTED:208-221 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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) opentofu/lib/dependabot/opentofu/file_selector.rb:65 — opentofu/lib/dependabot/opentofu/file_selector.rb:65-78 | terraform/lib/dependabot/terraform/file_selector.rb:58-71 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/file_selector.rb` and `terraform/lib/dependabot/terraform/file_selector.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. 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) opentofu/lib/dependabot/opentofu/update_checker.rb:122 — opentofu/lib/dependabot/opentofu/update_checker.rb:122-135 | terraform/lib/dependabot/terraform/update_checker.rb:133-146 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/update_checker.rb` and `terraform/lib/dependabot/terraform/update_checker.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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 `opentofu/lib/dependabot/opentofu/update_checker.rb:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) python/lib/dependabot/python/file_parser.rb:307 — python/lib/dependabot/python/file_parser.rb:307-320 | uv/lib/dependabot/uv/file_parser.rb:241-254 — before extracting anything, compare `python/lib/dependabot/python/file_parser.rb` and `uv/lib/dependabot/uv/file_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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 `python/lib/dependabot/python/file_parser.rb:307` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) rakelib/support/infrastructure_updaters/gem_infrastructure_updater.rb:39 — rakelib/support/infrastructure_updaters/gem_infrastructure_updater.rb:39-52 | rakelib/support/infrastructure_updaters/script_updater.rb:68-81 — 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 `rakelib/support/infrastructure_updaters/gem_infrastructure_updater.rb:39` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (14 lines × 2) bun/lib/dependabot/bun/file_updater.rb:85 — bun/lib/dependabot/bun/file_updater.rb:85-98 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:205-218 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb` as WHOLE FILES: this scan already matched 6 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 (14 lines × 2) bun/lib/dependabot/bun/helpers.rb:39 — bun/lib/dependabot/bun/helpers.rb:39-52 | npm_and_yarn/lib/dependabot/npm_and_yarn/helpers.rb:776-789 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (14 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:369 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:369-382 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:516-529 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 (14 lines × 2) REDACTED:42 — REDACTED:42-55 | REDACTED:42-55 — 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 (14 lines × 2) common/lib/dependabot/pull_request_creator/gitlab.rb:93 — common/lib/dependabot/pull_request_creator/gitlab.rb:93-106 | common/lib/dependabot/pull_request_creator/message_builder.rb:109-122 — 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 (14 lines × 2) opentofu/lib/dependabot/opentofu/file_fetcher.rb:34 — opentofu/lib/dependabot/opentofu/file_fetcher.rb:34-47 | terraform/lib/dependabot/terraform/file_fetcher.rb:34-47 — 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.
R4 · Test Coverage · No test reaches this file · ×17
  • No test reaches this file bun/helpers/lib/npm/vulnerability-auditor.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file bun/helpers/lib/yarn/peer-dependency-checker.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/npm6/peer-dependency-checker.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file bun/helpers/lib/npm6/peer-dependency-checker.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file bun/helpers/lib/yarn/subdependency-updater.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file bun/helpers/lib/npm6/subdependency-updater.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/run.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file bun/helpers/run.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/npm6/remove-dependencies-from-lockfile.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/npm6/helpers.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file bun/helpers/lib/npm6/remove-dependencies-from-lockfile.js:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/yarn/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/npm/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file npm_and_yarn/helpers/lib/npm6/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
D30 · Dependency Vulnerabilities · Medium CVE · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×16
  • Duplicated block (15 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Cli/Commands/GraphCommand.cs:24 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Cli/Commands/GraphCommand.cs:24-38 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Cli/Commands/RunCommand.cs:24-38 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Cli/Commands/GraphCommand.cs:24` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) bun/lib/dependabot/bun/metadata_finder.rb:216 — bun/lib/dependabot/bun/metadata_finder.rb:216-230 | npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb:306-320 — before extracting anything, compare `bun/lib/dependabot/bun/metadata_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 (15 lines × 2) bun/lib/dependabot/bun/sub_dependency_files_filterer.rb:26 — bun/lib/dependabot/bun/sub_dependency_files_filterer.rb:26-40 | npm_and_yarn/lib/dependabot/npm_and_yarn/sub_dependency_files_filterer.rb:26-40 — before extracting anything, compare `bun/lib/dependabot/bun/sub_dependency_files_filterer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/sub_dependency_files_filterer.rb` as WHOLE FILES: 89% 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 (15 lines × 2) bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:179 — bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:179-193 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb:193-207 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/latest_version_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (15 lines × 2) bun/lib/dependabot/bun/update_checker/library_detector.rb:60 — bun/lib/dependabot/bun/update_checker/library_detector.rb:60-74 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/library_detector.rb:60-74 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/library_detector.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/library_detector.rb` as WHOLE FILES: 89% 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. 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) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:228 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:228-242 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:224-238 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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 (15 lines × 2) bundler/helpers/v2/lib/functions/force_updater.rb:73 — bundler/helpers/v2/lib/functions/force_updater.rb:73-87 | bundler/helpers/v4/lib/functions/force_updater.rb:73-87 — before extracting anything, compare `bundler/helpers/v2/lib/functions/force_updater.rb` and `bundler/helpers/v4/lib/functions/force_updater.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 115 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 (15 lines × 2) common/lib/dependabot/errors.rb:106 — common/lib/dependabot/errors.rb:106-120 | common/lib/dependabot/errors.rb:336-350 — 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 `common/lib/dependabot/errors.rb:106` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) REDACTED:82 — REDACTED:82-96 | REDACTED:85-99 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `REDACTED:97` calls `source_string`, `update_local_variable_declaration` and `REDACTED:100` 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 (15 lines × 2) pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb:97 — pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb:97-111 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/rust.rb:99-113 — before extracting anything, compare `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb` and `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/rust.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 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 (15 lines × 2) bun/lib/dependabot/bun/file_updater/package_json_updater.rb:326 — bun/lib/dependabot/bun/file_updater/package_json_updater.rb:326-340 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb:378-392 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 160 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 `bun/lib/dependabot/bun/file_updater/package_json_updater.rb:326` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (15 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:134 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:134-148 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:141-155 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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 (15 lines × 2) bun/lib/dependabot/bun/package/registry_finder.rb:157 — bun/lib/dependabot/bun/package/registry_finder.rb:157-171 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb:159-173 — before extracting anything, compare `bun/lib/dependabot/bun/package/registry_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 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 (15 lines × 2) cargo/lib/dependabot/cargo/metadata_finder.rb:110 — cargo/lib/dependabot/cargo/metadata_finder.rb:110-124 | cargo/lib/dependabot/cargo/package/package_details_fetcher.rb:150-164 — 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 (15 lines × 2) python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:104 — python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:104-118 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:107-121 — before extracting anything, compare `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 186 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 (15 lines × 2) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:50 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:50-64 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:45-59 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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.
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×16
  • Duplicated block (16 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:107 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:107-122 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:78-93 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 106 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:107` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:162 — bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:162-177 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb:363-378 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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) bun/lib/dependabot/bun/file_updater/package_json_preparer.rb:45 — bun/lib/dependabot/bun/file_updater/package_json_preparer.rb:45-60 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_preparer.rb:45-60 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_preparer.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_preparer.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 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 (16 lines × 2) bun/lib/dependabot/bun/file_updater/package_json_updater.rb:112 — bun/lib/dependabot/bun/file_updater/package_json_updater.rb:112-127 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb:113-128 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 160 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) bun/lib/dependabot/bun/requirement.rb:102 — bun/lib/dependabot/bun/requirement.rb:102-117 | npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:155-170 — before extracting anything, compare `bun/lib/dependabot/bun/requirement.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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) bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb:186 — bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb:186-201 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb:420-435 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/vulnerability_auditor.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 32 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) bundler/helpers/v2/lib/functions/force_updater.rb:91 — bundler/helpers/v2/lib/functions/force_updater.rb:91-106 | bundler/helpers/v4/lib/functions/force_updater.rb:91-106 — before extracting anything, compare `bundler/helpers/v2/lib/functions/force_updater.rb` and `bundler/helpers/v4/lib/functions/force_updater.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 115 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) common/lib/dependabot/errors.rb:75 — common/lib/dependabot/errors.rb:75-90 | common/lib/dependabot/errors.rb:179-197 — 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 `common/lib/dependabot/errors.rb:75` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:230 — github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:230-245 | github_actions/lib/dependabot/github_actions/update_checker.rb:240-255 — 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 `github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:230` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) maven/lib/dependabot/maven/package/package_details_fetcher.rb:53 — maven/lib/dependabot/maven/package/package_details_fetcher.rb:53-68 | sbt/lib/dependabot/sbt/package/package_details_fetcher.rb:49-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (16 lines × 2) python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:116 — python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:116-131 | uv/lib/dependabot/uv/file_parser/pyproject_files_parser.rb:191-206 — before extracting anything, compare `python/lib/dependabot/python/file_parser/pyproject_files_parser.rb` and `uv/lib/dependabot/uv/file_parser/pyproject_files_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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) bun/lib/dependabot/bun/file_parser.rb:349 — bun/lib/dependabot/bun/file_parser.rb:349-364 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:476-491 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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 (16 lines × 2) bun/lib/dependabot/bun/update_checker.rb:100 — bun/lib/dependabot/bun/update_checker.rb:100-115 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:110-125 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 (16 lines × 2) bundler/helpers/v2/lib/functions/lockfile_updater.rb:211 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:211-226 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:211-226 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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) REDACTED:546 — REDACTED:546-561 | REDACTED:387-402 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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:546` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (16 lines × 2) bun/lib/dependabot/bun/update_checker.rb:54 — bun/lib/dependabot/bun/update_checker.rb:54-69 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:57-72 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×16
  • Duplicated block (10 lines × 2) bun/lib/dependabot/bun/constraint_helper.rb:374 — bun/lib/dependabot/bun/constraint_helper.rb:374-383 | npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb:484-493 — before extracting anything, compare `bun/lib/dependabot/bun/constraint_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 138 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 (10 lines × 2) bundler/helpers/v2/lib/functions.rb:92 — bundler/helpers/v2/lib/functions.rb:92-101 | bundler/helpers/v4/lib/functions.rb:92-101 — before extracting anything, compare `bundler/helpers/v2/lib/functions.rb` and `bundler/helpers/v4/lib/functions.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 101 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 (10 lines × 2) cargo/lib/dependabot/cargo/file_parser.rb:135 — cargo/lib/dependabot/cargo/file_parser.rb:135-144 | cargo/lib/dependabot/cargo/file_parser.rb:149-159 — 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) cargo/lib/dependabot/cargo/update_checker/file_preparer.rb:128 — cargo/lib/dependabot/cargo/update_checker/file_preparer.rb:128-137 | cargo/lib/dependabot/cargo/update_checker/file_preparer.rb:198-207 — 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) maven/lib/dependabot/maven/file_parser/property_value_finder.rb:150 — maven/lib/dependabot/maven/file_parser/property_value_finder.rb:150-159 | maven/lib/dependabot/maven/file_parser/repositories_finder.rb:268-277 — 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 (10 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:329 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:329-338 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:288-297 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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 (10 lines × 2) updater/lib/dependabot/updater/operations/refresh_security_update_pull_request.rb:44 — updater/lib/dependabot/updater/operations/refresh_security_update_pull_request.rb:44-53 | updater/lib/dependabot/updater/operations/refresh_version_update_pull_request.rb:45-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. 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) bun/lib/dependabot/bun/package_name.rb:94 — bun/lib/dependabot/bun/package_name.rb:94-103 | npm_and_yarn/lib/dependabot/npm_and_yarn/package_name.rb:94-103 — before extracting anything, compare `bun/lib/dependabot/bun/package_name.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package_name.rb` as WHOLE FILES: 98% 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. 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) bun/lib/dependabot/bun/requirement.rb:49 — bun/lib/dependabot/bun/requirement.rb:49-58 | npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:59-68 — before extracting anything, compare `bun/lib/dependabot/bun/requirement.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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 (10 lines × 2) bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:304 — bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:304-313 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb:344-353 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/latest_version_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (10 lines × 2) pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/go.rb:132 — pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/go.rb:132-141 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/python.rb:140-149 — 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 (10 lines × 2) python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:64 — python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:64-73 | uv/lib/dependabot/uv/file_parser/pyproject_files_parser.rb:70-79 — before extracting anything, compare `python/lib/dependabot/python/file_parser/pyproject_files_parser.rb` and `uv/lib/dependabot/uv/file_parser/pyproject_files_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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 (10 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:179 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:179-188 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:163-172 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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 (10 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:414 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:414-423 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:373-382 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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 (10 lines × 2) updater/lib/dependabot/updater/operations/create_security_update_pull_request.rb:308 — updater/lib/dependabot/updater/operations/create_security_update_pull_request.rb:308-317 | updater/lib/dependabot/updater/operations/refresh_security_update_pull_request.rb:238-247 — 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 (10 lines × 2) bun/lib/dependabot/bun/file_updater.rb:151 — bun/lib/dependabot/bun/file_updater.rb:151-162 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:126-135 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb` as WHOLE FILES: this scan already matched 6 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.
D29 · Static Analysis (SAST) · REDACTED · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×15
  • Duplicated block (13 lines × 2) bun/lib/dependabot/bun/file_fetcher.rb:333 — bun/lib/dependabot/bun/file_fetcher.rb:333-345 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:698-710 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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 `bun/lib/dependabot/bun/file_fetcher.rb:333` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) bun/lib/dependabot/bun/file_fetcher.rb:360 — bun/lib/dependabot/bun/file_fetcher.rb:360-372 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:729-741 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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 (13 lines × 2) bun/lib/dependabot/bun/metadata_finder.rb:80 — bun/lib/dependabot/bun/metadata_finder.rb:80-92 | npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb:158-170 — before extracting anything, compare `bun/lib/dependabot/bun/metadata_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/metadata_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 (13 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:162 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:162-174 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:169-181 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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 (13 lines × 2) bundler/lib/dependabot/bundler/file_fetcher/gemspec_finder.rb:87 — bundler/lib/dependabot/bundler/file_fetcher/gemspec_finder.rb:87-99 | bundler/lib/dependabot/bundler/file_fetcher/path_gemspec_finder.rb:87-99 — 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 (13 lines × 2) cargo/lib/dependabot/cargo/requirement.rb:148 — cargo/lib/dependabot/cargo/requirement.rb:148-160 | composer/lib/dependabot/composer/requirement.rb:85-97 — 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) npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb:285 — npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb:285-297 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/vulnerability_auditor.rb:382-394 — 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) opentofu/lib/dependabot/opentofu.rb:19 — opentofu/lib/dependabot/opentofu.rb:19-31 | terraform/lib/dependabot/terraform.rb:19-31 — 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) REDACTED:122 — REDACTED:122-134 | REDACTED:119-131 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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:122` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) opentofu/lib/dependabot/opentofu/update_checker.rb:77 — opentofu/lib/dependabot/opentofu/update_checker.rb:77-89 | terraform/lib/dependabot/terraform/update_checker.rb:76-88 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/update_checker.rb` and `terraform/lib/dependabot/terraform/update_checker.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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 `opentofu/lib/dependabot/opentofu/update_checker.rb:77` 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 (13 lines × 2) python/lib/dependabot/python/file_parser.rb:349 — python/lib/dependabot/python/file_parser.rb:349-361 | uv/lib/dependabot/uv/file_parser.rb:282-294 — before extracting anything, compare `python/lib/dependabot/python/file_parser.rb` and `uv/lib/dependabot/uv/file_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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 (13 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:694 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:694-706 | python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:429-441 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:694` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (13 lines × 2) python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:346 — python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:346-358 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:385-397 — before extracting anything, compare `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 186 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 (13 lines × 2) bun/lib/dependabot/bun/file_updater/package_json_updater.rb:295 — bun/lib/dependabot/bun/file_updater/package_json_updater.rb:295-307 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb:347-359 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 160 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 `bun/lib/dependabot/bun/file_updater/package_json_updater.rb:295` 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 (13 lines × 2) bun/lib/dependabot/bun/version_selector.rb:28 — bun/lib/dependabot/bun/version_selector.rb:28-40 | npm_and_yarn/lib/dependabot/npm_and_yarn/version_selector.rb:28-40 — before extracting anything, compare `bun/lib/dependabot/bun/version_selector.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/version_selector.rb` as WHOLE FILES: 91% 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×13
  • Duplicated block (17 lines × 2) bun/lib/dependabot/bun/file_fetcher.rb:179 — bun/lib/dependabot/bun/file_fetcher.rb:179-195 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:490-506 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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) bun/lib/dependabot/bun/file_parser.rb:69 — bun/lib/dependabot/bun/file_parser.rb:69-85 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:67-83 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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) bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:182 — bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:182-198 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb:383-399 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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) bun/lib/dependabot/bun/file_updater/package_json_updater.rb:227 — bun/lib/dependabot/bun/file_updater/package_json_updater.rb:227-243 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb:279-295 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 160 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 (17 lines × 2) bun/lib/dependabot/bun/package_manager.rb:175 — bun/lib/dependabot/bun/package_manager.rb:175-191 | npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb:359-375 — before extracting anything, compare `bun/lib/dependabot/bun/package_manager.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 (17 lines × 2) bun/lib/dependabot/bun/registry_parser.rb:67 — bun/lib/dependabot/bun/registry_parser.rb:67-83 | npm_and_yarn/lib/dependabot/npm_and_yarn/registry_parser.rb:67-83 — before extracting anything, compare `bun/lib/dependabot/bun/registry_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/registry_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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 (17 lines × 2) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:186 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:186-202 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:182-198 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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) bundler/helpers/v2/lib/functions/lockfile_updater.rb:149 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:149-165 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:149-165 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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) bundler/helpers/v2/run.rb:32 — bundler/helpers/v2/run.rb:32-48 | bundler/helpers/v4/run.rb:31-47 — `bundler/helpers/v2/run.rb` and `bundler/helpers/v4/run.rb` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 2 separate duplicated blocks between them, totalling at least 24 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
  • Duplicated block (17 lines × 2) REDACTED:450 — REDACTED:450-466 | REDACTED:336-352 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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:450` 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 (17 lines × 2) REDACTED:34 — REDACTED:34-50 | REDACTED:35-51 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:118 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:118-134 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:102-118 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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) updater/lib/dependabot/updater/operations/refresh_version_update_pull_request.rb:301 — updater/lib/dependabot/updater/operations/refresh_version_update_pull_request.rb:301-317 | updater/lib/dependabot/updater/operations/update_all_versions.rb:345-361 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×12
  • Duplicated block (21 lines × 2) bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:125 — bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:125-145 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb:125-145 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 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 (21 lines × 2) bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:217 — bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:217-237 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb:443-463 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb:440` calls `credential_scopes_for` and `bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:216` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 2) bun/lib/dependabot/bun/registry_helper.rb:38 — bun/lib/dependabot/bun/registry_helper.rb:38-58 | npm_and_yarn/lib/dependabot/npm_and_yarn/registry_helper.rb:196-216 — before extracting anything, compare `bun/lib/dependabot/bun/registry_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/registry_helper.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 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 (21 lines × 2) bun/lib/dependabot/bun/registry_helper.rb:138 — bun/lib/dependabot/bun/registry_helper.rb:138-158 | npm_and_yarn/lib/dependabot/npm_and_yarn/registry_helper.rb:310-330 — before extracting anything, compare `bun/lib/dependabot/bun/registry_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/registry_helper.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 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 (21 lines × 2) bun/lib/dependabot/bun/update_checker.rb:330 — bun/lib/dependabot/bun/update_checker.rb:330-350 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:396-416 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 (21 lines × 2) bun/lib/dependabot/bun/update_checker.rb:371 — bun/lib/dependabot/bun/update_checker.rb:371-391 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:437-457 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 (21 lines × 2) bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb:70 — bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb:70-90 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/subdependency_version_resolver.rb:78-98 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/subdependency_version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/subdependency_version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 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 (21 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:489 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:489-509 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:705-725 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 (21 lines × 2) bundler/helpers/v2/lib/functions/version_resolver.rb:29 — bundler/helpers/v2/lib/functions/version_resolver.rb:29-49 | bundler/helpers/v4/lib/functions/version_resolver.rb:29-49 — before extracting anything, compare `bundler/helpers/v2/lib/functions/version_resolver.rb` and `bundler/helpers/v4/lib/functions/version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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 (21 lines × 2) bundler/helpers/v2/monkey_patches/git_source_patch.rb:43 — bundler/helpers/v2/monkey_patches/git_source_patch.rb:43-63 | bundler/helpers/v4/monkey_patches/git_source_patch.rb:43-63 — before extracting anything, compare `bundler/helpers/v2/monkey_patches/git_source_patch.rb` and `bundler/helpers/v4/monkey_patches/git_source_patch.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 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 (21 lines × 2) python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:272 — python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:272-292 | uv/lib/dependabot/uv/file_parser/pyproject_files_parser.rb:277-297 — before extracting anything, compare `python/lib/dependabot/python/file_parser/pyproject_files_parser.rb` and `uv/lib/dependabot/uv/file_parser/pyproject_files_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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 (21 lines × 2) python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:305 — python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:305-325 | uv/lib/dependabot/uv/file_parser/pyproject_files_parser.rb:310-330 — before extracting anything, compare `python/lib/dependabot/python/file_parser/pyproject_files_parser.rb` and `uv/lib/dependabot/uv/file_parser/pyproject_files_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 68 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×12
  • Duplicated block (12 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:206 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:206-217 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:350-361 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:206` 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 (12 lines × 2) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:126 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:126-137 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:122-133 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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 (12 lines × 2) bundler/helpers/v2/lib/functions/file_parser.rb:51 — bundler/helpers/v2/lib/functions/file_parser.rb:51-62 | bundler/helpers/v4/lib/functions/file_parser.rb:51-62 — before extracting anything, compare `bundler/helpers/v2/lib/functions/file_parser.rb` and `bundler/helpers/v4/lib/functions/file_parser.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 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) bundler/helpers/v2/monkey_patches/definition_ruby_version_patch.rb:8 — bundler/helpers/v2/monkey_patches/definition_ruby_version_patch.rb:8-19 | bundler/helpers/v4/monkey_patches/definition_ruby_version_patch.rb:8-19 — before extracting anything, compare `bundler/helpers/v2/monkey_patches/definition_ruby_version_patch.rb` and `bundler/helpers/v4/monkey_patches/definition_ruby_version_patch.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 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. Read the line range as the matched WINDOW rather than a finished unit: at `bundler/helpers/v2/monkey_patches/definition_ruby_version_patch.rb:8` 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 (12 lines × 2) python/lib/dependabot/python/file_parser/python_requirement_parser.rb:109 — python/lib/dependabot/python/file_parser/python_requirement_parser.rb:109-120 | uv/lib/dependabot/uv/file_parser/python_requirement_parser.rb:87-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `python/lib/dependabot/python/file_parser/python_requirement_parser.rb:109` 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 (12 lines × 2) updater/lib/dependabot/updater/operations/create_security_update_pull_request.rb:281 — updater/lib/dependabot/updater/operations/create_security_update_pull_request.rb:281-292 | updater/lib/dependabot/updater/operations/update_all_versions.rb:299-310 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (12 lines × 2) bun/lib/dependabot/bun/update_checker.rb:355 — bun/lib/dependabot/bun/update_checker.rb:355-366 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:421-432 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 (12 lines × 2) dotnet_sdk/lib/dependabot/dotnet_sdk/update_checker.rb:70 — dotnet_sdk/lib/dependabot/dotnet_sdk/update_checker.rb:70-81 | rust_toolchain/lib/dependabot/rust_toolchain/update_checker.rb:59-70 — before extracting anything, compare `dotnet_sdk/lib/dependabot/dotnet_sdk/update_checker.rb` and `rust_toolchain/lib/dependabot/rust_toolchain/update_checker.rb` as WHOLE FILES: 94% 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) git_submodules/lib/dependabot/git_submodules/update_checker.rb:62 — git_submodules/lib/dependabot/git_submodules/update_checker.rb:62-73 | nix/lib/dependabot/nix/update_checker.rb:257-268 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/base.rb:159 — pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/base.rb:159-170 | pre_commit/lib/dependabot/pre_commit/update_checker.rb:383-394 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:757 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:757-768 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:619-630 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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 (12 lines × 2) python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:487 — python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:487-498 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:504-515 — before extracting anything, compare `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 186 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.
D29 · Static Analysis (SAST) · REDACTED · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D17 · Explicit Debt · TodoComment · ×10
  • TodoComment nuget/helpers/lib/NuGetUpdater/DotNetPackageCorrelation/Model/PackageMapper.cs:60 — // TODO: linear search is slow — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Utilities/DiffUtil.cs:237 — // TODO: Optimization possible: O(ND) time, O(N) space — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:188 — //TODO: At this point we should add the peer dependencies to a queue where — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:847 — // TODO: we don't currently partition dependencies by TFM; this will have to be redone when that's supported — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/ExperimentsManager.cs:45 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/ExperimentsManager.cs:49 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ApiModel/DependencyFile.cs:10 — // TODO: enum — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ApiModel/DependencyFile.cs:16 — // TODO: enum — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ApiModel/DependencyFile.cs:17 — // TODO: what is this? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ApiModel/DependencyGroup.cs:15 — // TODO: make more strongly typed, but currently this seems to be: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D15 · Churn × Complexity Hotspots · Hotspot · ×9
  • Hotspot: npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:832 — npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in PnpmLockfileUpdater.handle_pnpm_lock_updater_error at line 832. 4 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: REDACTED REDACTED:83 — REDACTED changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in GroupUpdateCreation.compile_all_dependency_changes_for at line 83. 2 of those changes were fix/bug commits, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: common/lib/dependabot/errors.rb common/lib/dependabot/errors.rb:243 — common/lib/dependabot/errors.rb changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in Dependabot.updater_error_details at line 243. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- common/lib/dependabot/errors.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: common/lib/dependabot/command_helpers.rb common/lib/dependabot/command_helpers.rb:93 — common/lib/dependabot/command_helpers.rb changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in CommandHelpers.capture3_with_timeout at line 93. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- common/lib/dependabot/command_helpers.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb:293 — npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in PackageManagerHelper.setup at line 293. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: composer/lib/dependabot/composer/file_updater/lockfile_updater.rb composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:176 — composer/lib/dependabot/composer/file_updater/lockfile_updater.rb changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in LockfileUpdater.handle_composer_errors at line 176. 2 of those changes were fix/bug commits, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- composer/lib/dependabot/composer/file_updater/lockfile_updater.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:76 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in SdkProjectDiscovery.DiscoverAsync at line 76. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs:140 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in VersionFinder.GetVersionsAsync at line 140. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:49 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in RefreshGroupUpdatePullRequestHandler.HandleAsync at line 49. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×9
  • Duplicated block (20 lines × 2) bun/lib/dependabot/bun/file_parser.rb:387 — bun/lib/dependabot/bun/file_parser.rb:387-406 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:514-533 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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 (20 lines × 2) bun/lib/dependabot/bun/file_parser.rb:465 — bun/lib/dependabot/bun/file_parser.rb:465-484 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:593-612 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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 `bun/lib/dependabot/bun/file_parser.rb:465` 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 (20 lines × 2) bun/lib/dependabot/bun/package/registry_finder.rb:133 — bun/lib/dependabot/bun/package/registry_finder.rb:133-152 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb:135-154 — before extracting anything, compare `bun/lib/dependabot/bun/package/registry_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 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 `bun/lib/dependabot/bun/package/registry_finder.rb:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (20 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:345 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:345-364 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:492-511 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 (20 lines × 2) bundler/helpers/v2/lib/functions/lockfile_updater.rb:125 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:125-144 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:125-144 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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 (20 lines × 2) common/lib/dependabot/clients/azure.rb:425 — common/lib/dependabot/clients/azure.rb:425-444 | common/lib/dependabot/clients/azure.rb:462-481 — 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 `common/lib/dependabot/clients/azure.rb:425` 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 (20 lines × 2) REDACTED:377 — REDACTED:377-396 | REDACTED:263-282 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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 (20 lines × 2) opentofu/lib/dependabot/opentofu/requirements_updater.rb:136 — opentofu/lib/dependabot/opentofu/requirements_updater.rb:136-155 | terraform/lib/dependabot/terraform/requirements_updater.rb:118-137 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/requirements_updater.rb` and `terraform/lib/dependabot/terraform/requirements_updater.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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 (20 lines × 2) REDACTED:150 — REDACTED:150-169 | REDACTED:122-141 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 278 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:150` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×8
  • Duplicated block (19 lines × 2) bun/lib/dependabot/bun/registry_parser.rb:21 — bun/lib/dependabot/bun/registry_parser.rb:21-39 | npm_and_yarn/lib/dependabot/npm_and_yarn/registry_parser.rb:21-39 — before extracting anything, compare `bun/lib/dependabot/bun/registry_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/registry_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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 (19 lines × 2) bun/lib/dependabot/bun/registry_parser.rb:99 — bun/lib/dependabot/bun/registry_parser.rb:99-117 | npm_and_yarn/lib/dependabot/npm_and_yarn/registry_parser.rb:99-117 — before extracting anything, compare `bun/lib/dependabot/bun/registry_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/registry_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 66 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 (19 lines × 2) bun/lib/dependabot/bun/update_checker.rb:168 — bun/lib/dependabot/bun/update_checker.rb:168-186 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:178-196 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 (19 lines × 2) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:154 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:154-172 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:150-168 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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 (19 lines × 2) bundler/helpers/v2/lib/functions.rb:105 — bundler/helpers/v2/lib/functions.rb:105-123 | bundler/helpers/v4/lib/functions.rb:105-123 — before extracting anything, compare `bundler/helpers/v2/lib/functions.rb` and `bundler/helpers/v4/lib/functions.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 101 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 (19 lines × 2) REDACTED:416 — REDACTED:416-434 | REDACTED:302-320 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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:416` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (19 lines × 2) REDACTED:169 — REDACTED:169-187 | REDACTED:143-161 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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 (19 lines × 2) cargo/lib/dependabot/cargo/file_updater/manifest_updater.rb:132 — cargo/lib/dependabot/cargo/file_updater/manifest_updater.rb:132-153 | python/lib/dependabot/python/file_updater/pipfile_manifest_updater.rb:80-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `cargo/lib/dependabot/cargo/file_updater/manifest_updater.rb:132` 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.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×8
  • Duplicated block (18 lines × 2) bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:159 — bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:159-176 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb:159-176 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 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 (18 lines × 2) bundler/helpers/v2/lib/functions/lockfile_updater.rb:230 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:230-247 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:230-247 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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 (18 lines × 2) composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:184 — composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:184-201 | composer/lib/dependabot/composer/update_checker/version_resolver.rb:337-354 — before extracting anything, compare `composer/lib/dependabot/composer/file_updater/lockfile_updater.rb` and `composer/lib/dependabot/composer/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 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 (18 lines × 2) composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:462 — composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:462-479 | composer/lib/dependabot/composer/update_checker/version_resolver.rb:485-502 — before extracting anything, compare `composer/lib/dependabot/composer/file_updater/lockfile_updater.rb` and `composer/lib/dependabot/composer/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 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 (18 lines × 2) opentofu/lib/dependabot/opentofu/registry_client.rb:58 — opentofu/lib/dependabot/opentofu/registry_client.rb:58-75 | terraform/lib/dependabot/terraform/registry_client.rb:45-62 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/registry_client.rb` and `terraform/lib/dependabot/terraform/registry_client.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 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 `opentofu/lib/dependabot/opentofu/registry_client.rb:58` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (18 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:392 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:392-409 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:351-368 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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 (18 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:428 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:428-445 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:387-404 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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 (18 lines × 2) uv/lib/dependabot/uv/file_fetcher.rb:160 — uv/lib/dependabot/uv/file_fetcher.rb:160-177 | uv/lib/dependabot/uv/file_fetcher/workspace_fetcher.rb:215-232 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×8
  • Duplicated block (8 lines × 3) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:32 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:32-39 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:31-38 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:31-38 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 79 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:32` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:40` calls `Error` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:41` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 3) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:63 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:63-70 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:105-112 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:76-83 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 64 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:63` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (8 lines × 3) go_modules/lib/dependabot/go_modules/requirement.rb:35 — go_modules/lib/dependabot/go_modules/requirement.rb:35-42 | opentofu/lib/dependabot/opentofu/requirement.rb:24-31 | terraform/lib/dependabot/terraform/requirement.rb:25-32 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 3) bun/lib/dependabot/bun/update_checker/version_resolver.rb:756 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:756-763 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/yarn_lockfile_updater.rb:493-500 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:1059-1066 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 (8 lines × 3) common/lib/dependabot/file_fetchers/base.rb:488 — common/lib/dependabot/file_fetchers/base.rb:488-495 | common/lib/dependabot/pull_request_creator/codecommit.rb:155-162 | common/lib/dependabot/pull_request_creator/pr_name_prefixer.rb:656-663 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (8 lines × 3) pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb:161 — pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb:161-168 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb:161-168 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/rust.rb:165-172 — before extracting anything, compare `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb` and `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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 (8 lines × 3) pre_commit/lib/dependabot/pre_commit/package/package_details_fetcher.rb:281 — pre_commit/lib/dependabot/pre_commit/package/package_details_fetcher.rb:281-288 | pre_commit/lib/dependabot/pre_commit/update_checker.rb:284-291 | pre_commit/lib/dependabot/pre_commit/update_checker/latest_version_finder.rb:401-408 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (8 lines × 3) bundler/lib/dependabot/bundler/update_checker/version_details.rb:37 — bundler/lib/dependabot/bundler/update_checker/version_details.rb:37-44 | go_modules/lib/dependabot/go_modules/go_mod_manifest.rb:107-114 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser/json_lock/record.rb:112-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D29 · Static Analysis (SAST) · REDACTED · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · MethodTooLong · ×7
  • MethodTooLong: XmlFileWriter.UpdatePackageVersionsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:52 — MethodTooLong — UpdatePackageVersionsAsync runs 502 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 402 over it, 5.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SdkProjectDiscovery.DiscoverAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:76 — MethodTooLong — DiscoverAsync runs 209 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 109 over it, 2.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SdkProjectDiscovery.BuildResults nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:492 — MethodTooLong — BuildResults runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: FileWriterWorker.ProcessPackageReferenceUpdatesAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs:137 — MethodTooLong — ProcessPackageReferenceUpdatesAsync runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: RefreshSecurityUpdatePullRequestHandler.HandleAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:29 — MethodTooLong — HandleAsync runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: RefreshVersionUpdatePullRequestHandler.HandleAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:29 — MethodTooLong — HandleAsync runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: GroupUpdateAllVersionsHandler.RunEffectiveGroupUpdate nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:165 — MethodTooLong — RunEffectiveGroupUpdate runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×7
  • Duplicated block (6 lines × 3) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:183 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:183-188 | composer/lib/dependabot/composer/update_checker/requirements_updater.rb:267-272 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:179-184 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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 (6 lines × 3) deno/lib/dependabot/deno/requirement.rb:57 — deno/lib/dependabot/deno/requirement.rb:57-62 | pub/lib/dependabot/pub/requirement.rb:160-165 | python/lib/dependabot/python/requirement.rb:140-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (6 lines × 3) devcontainers/lib/dependabot/devcontainers/file_parser.rb:67 — devcontainers/lib/dependabot/devcontainers/file_parser.rb:67-72 | devcontainers/lib/dependabot/devcontainers/file_updater.rb:52-57 | gradle/lib/dependabot/gradle/file_parser.rb:748-753 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (6 lines × 3) swift/lib/dependabot/swift/file_parser.rb:130 — swift/lib/dependabot/swift/file_parser.rb:130-135 | swift/lib/dependabot/swift/file_updater.rb:150-155 | swift/lib/dependabot/swift/file_updater.rb:160-165 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
  • Duplicated block (6 lines × 3) bundler/lib/dependabot/bundler/file_fetcher.rb:76 — bundler/lib/dependabot/bundler/file_fetcher.rb:76-81 | bundler/lib/dependabot/bundler/file_fetcher.rb:86-91 | bundler/lib/dependabot/bundler/file_parser.rb:345-350 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 3) cargo/lib/dependabot/cargo/file_parser.rb:75 — cargo/lib/dependabot/cargo/file_parser.rb:75-80 | pub/lib/dependabot/pub/file_parser.rb:52-57 | swift/lib/dependabot/swift/file_parser.rb:159-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (6 lines × 3) devcontainers/lib/dependabot/devcontainers/update_checker/latest_version_finder.rb:99 — devcontainers/lib/dependabot/devcontainers/update_checker/latest_version_finder.rb:99-104 | REDACTED:91-96 | hex/lib/dependabot/hex/update_checker/latest_version_finder.rb:90-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D29 · Static Analysis (SAST) · REDACTED · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X3 · Exception handling · Swallowed exception (empty catch) · ×6
  • Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:433 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:882 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:1093 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:532 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:325 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:446 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×5
  • Members sharing a duplicated core (4 members, 50+ identical tokens) bun/lib/dependabot/bun/package/registry_finder.rb:176 — bun/lib/dependabot/bun/package/registry_finder.rb:176-186 | common/lib/dependabot/clients/azure.rb:509-519 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_credential_helpers.rb:76-84 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb:178-188 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) common/lib/dependabot/update_checkers/vulnerability_audit.rb:18 — common/lib/dependabot/update_checkers/vulnerability_audit.rb:18-27 | updater/lib/dependabot/api_client.rb:456-465 | updater/lib/dependabot/job.rb:179-189 | updater/lib/dependabot/pull_request.rb:212-221 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb:78 — opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb:78-101 | opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb:105-126 | terraform/lib/dependabot/terraform/package/package_details_fetcher.rb:47-73 | terraform/lib/dependabot/terraform/package/package_details_fetcher.rb:77-101 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:267 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:267-278 | python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:327-338 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:250-261 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:364-375 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
  • Members sharing a duplicated core (4 members, 50+ identical tokens) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:773 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:773-788 | python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:503-520 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:635-652 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:520-537 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×5
  • Duplicated block (29 lines × 2) bun/lib/dependabot/bun/file_updater/package_json_updater.rb:255 — bun/lib/dependabot/bun/file_updater/package_json_updater.rb:255-283 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb:307-335 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 160 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 `bun/lib/dependabot/bun/file_updater/package_json_updater.rb:255` 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 (29 lines × 2) bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:265 — bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:265-293 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb:305-333 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/latest_version_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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 (29 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:230 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:230-258 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:383-411 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 (29 lines × 2) bundler/helpers/v2/lib/functions/lockfile_updater.rb:179 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:179-207 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:179-207 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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 (29 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:487 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:487-515 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:443-471 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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.
D4 · Code Duplication · Duplicated block (7 lines × 5) · ×5
  • Duplicated block (7 lines × 5) github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:228 — github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:228-235 | github_actions/lib/dependabot/github_actions/update_checker.rb:238-245 | github_actions/lib/dependabot/github_actions/update_checker/latest_version_finder.rb:347-353 | pre_commit/lib/dependabot/pre_commit/package/package_details_fetcher.rb:220-227 | pre_commit/lib/dependabot/pre_commit/update_checker/latest_version_finder.rb:247-253 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (7 lines × 5) common/lib/dependabot/file_fetchers/base.rb:439 — common/lib/dependabot/file_fetchers/base.rb:439-446 | common/lib/dependabot/pull_request_creator/github.rb:578-585 | common/lib/dependabot/pull_request_creator/labeler.rb:528-534 | common/lib/dependabot/pull_request_creator/pr_name_prefixer.rb:608-615 | common/lib/dependabot/pull_request_updater/github.rb:122-129 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (7 lines × 5) common/lib/dependabot/file_fetchers/base.rb:451 — common/lib/dependabot/file_fetchers/base.rb:451-458 | common/lib/dependabot/pull_request_creator/gitlab.rb:133-140 | common/lib/dependabot/pull_request_creator/labeler.rb:539-545 | common/lib/dependabot/pull_request_creator/pr_name_prefixer.rb:620-627 | common/lib/dependabot/pull_request_updater/gitlab.rb:100-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
  • Duplicated block (7 lines × 5) devcontainers/lib/dependabot/devcontainers/file_parser.rb:93 — devcontainers/lib/dependabot/devcontainers/file_parser.rb:93-99 | devcontainers/lib/dependabot/devcontainers/file_parser.rb:104-110 | git_submodules/lib/dependabot/git_submodules/file_parser.rb:105-111 | REDACTED:586-592 | REDACTED:472-478 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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 × 5) bun/lib/dependabot/bun/file_fetcher.rb:151 — bun/lib/dependabot/bun/file_fetcher.rb:151-157 | bun/lib/dependabot/bun/file_fetcher.rb:162-168 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:403-409 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:426-432 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:437-443 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×5
  • Duplicated block (5 lines × 3) common/lib/dependabot/file_fetchers/base.rb:477 — common/lib/dependabot/file_fetchers/base.rb:477-483 | common/lib/dependabot/metadata_finders/base/changelog_finder.rb:631-635 | common/lib/dependabot/metadata_finders/base/commits_finder.rb:412-416 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (5 lines × 3) common/lib/dependabot/metadata_finders/base/changelog_finder.rb:597 — common/lib/dependabot/metadata_finders/base/changelog_finder.rb:597-601 | common/lib/dependabot/metadata_finders/base/commits_finder.rb:385-389 | common/lib/dependabot/metadata_finders/base/release_finder.rb:427-431 — 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 (5 lines × 3) common/lib/dependabot/metadata_finders/base/changelog_finder.rb:606 — common/lib/dependabot/metadata_finders/base/changelog_finder.rb:606-610 | common/lib/dependabot/metadata_finders/base/commits_finder.rb:394-398 | common/lib/dependabot/metadata_finders/base/release_finder.rb:436-440 — 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 (5 lines × 3) devcontainers/lib/dependabot/devcontainers/requirement.rb:26 — devcontainers/lib/dependabot/devcontainers/requirement.rb:26-30 | dotnet_sdk/lib/dependabot/dotnet_sdk/requirement.rb:24-28 | rust_toolchain/lib/dependabot/rust_toolchain/requirement.rb:64-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (5 lines × 3) cargo/lib/dependabot/cargo/requirement.rb:88 — cargo/lib/dependabot/cargo/requirement.rb:88-92 | npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:96-100 | pub/lib/dependabot/pub/requirement.rb:82-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D35 · Change Coupling · Change coupling · ×4
  • Change coupling: PackageReferenceUpdater.cs ↔ ProcessExtensions.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackageReferenceUpdater.cs:1 — `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackageReferenceUpdater.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/ProcessExtensions.cs` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `1229994b` use preferred function name; `66b60183` force all invocations of `dotnet msbuild` to ignore response files; `fb9f15ff` always honor global.json sdk version (#12692) — run `git show` on any of them.
  • Change coupling: base_command.rb ↔ error_handler.rb updater/lib/dependabot/base_command.rb:1 — `updater/lib/dependabot/base_command.rb` and `updater/lib/dependabot/updater/error_handler.rb` change together 57% of the time (12 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `978d3dc5` Group Excon EOF errors by call site (#16167); `91890e17` Fix 88 type errors from srb tc Removing T.unsafe exposed attribute a…; `bf965ca3` Remove kwarg splatting T.unsafe and add SentryContext interface Two … — run `git show` on any of them.
  • Change coupling: PackageReferenceUpdater.cs ↔ MSBuildHelper.cs nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackageReferenceUpdater.cs:1 — `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackageReferenceUpdater.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs` change together 56% of the time (30 of the 54 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 30 shared commits counted here, the most recent 3 are `1229994b` use preferred function name; `66b60183` force all invocations of `dotnet msbuild` to ignore response files; `fb9f15ff` always honor global.json sdk version (#12692) — run `git show` on any of them.
  • Change coupling: lockfile_updater.rb ↔ version_resolver.rb cargo/lib/dependabot/cargo/file_updater/lockfile_updater.rb:1 — `cargo/lib/dependabot/cargo/file_updater/lockfile_updater.rb` and `cargo/lib/dependabot/cargo/update_checker/version_resolver.rb` change together 54% of the time (15 of the 28 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `ce406b83` Type Cargo requirement access; `523e474b` Reland "Cargo: handle crates locked at multiple versions" (#15638) (#…; `c2870b35` Revert "Cargo: handle crates locked at multiple versions (#15638)" (#… — run `git show` on any of them.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×4
  • Duplicated block (24 lines × 2) bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:92 — bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:92-115 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb:92-115 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 90 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) bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:131 — bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:131-154 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb:145-168 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/latest_version_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 97 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) composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:350 — composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:350-373 | composer/lib/dependabot/composer/update_checker/version_resolver.rb:245-268 — before extracting anything, compare `composer/lib/dependabot/composer/file_updater/lockfile_updater.rb` and `composer/lib/dependabot/composer/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 76 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) opentofu/lib/dependabot/opentofu/requirements_updater.rb:242 — opentofu/lib/dependabot/opentofu/requirements_updater.rb:242-265 | terraform/lib/dependabot/terraform/requirements_updater.rb:224-247 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/requirements_updater.rb` and `terraform/lib/dependabot/terraform/requirements_updater.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×4
  • Duplicated block (7 lines × 3) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:107 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:107-113 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:79-85 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:78-84 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:107` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:76` calls `Info` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:77` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 3) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:248 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:248-254 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:353-359 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:519-525 — 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 (7 lines × 3) bundler/lib/dependabot/bundler/package/package_details_fetcher.rb:307 — bundler/lib/dependabot/bundler/package/package_details_fetcher.rb:307-313 | cargo/lib/dependabot/cargo/package/package_details_fetcher.rb:226-232 | go_modules/lib/dependabot/go_modules/package/package_details_fetcher.rb:208-214 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (7 lines × 3) swift/lib/dependabot/swift/file_parser.rb:118 — swift/lib/dependabot/swift/file_parser.rb:118-124 | swift/lib/dependabot/swift/file_updater.rb:104-110 | swift/lib/dependabot/swift/update_checker.rb:322-328 — 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.
D44 · Platform End-of-Life · End-of-life runtime · ×4
  • End-of-life runtime: Node.js 16 npm_and_yarn/spec/fixtures/projects/pnpm/peer_disambiguation_v6/package.json:23 — npm_and_yarn/spec/fixtures/projects/pnpm/peer_disambiguation_v6/package.json declares Node.js 16 as this project's engines.node, and Node.js 16, support ended 2023-09-11. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2023-09-11 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: Node.js 18 npm_and_yarn/spec/fixtures/projects/yarn/submodule_dependency/package.json:8 — npm_and_yarn/spec/fixtures/projects/yarn/submodule_dependency/package.json declares Node.js 18 as this project's engines.node, and Node.js 18, support ended 2025-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2025-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: Node.js 20 npm_and_yarn/spec/fixtures/projects/pnpm/unsupported_engine_pnpm/package.json:9 — npm_and_yarn/spec/fixtures/projects/pnpm/unsupported_engine_pnpm/package.json declares Node.js 20 as this project's engines.node, and Node.js 20, support ended 2026-04-30. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2026-04-30 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
  • End-of-life runtime: Node.js 23 npm_and_yarn/spec/fixtures/projects/pnpm/unmet_peer_deps/package.json:17 — npm_and_yarn/spec/fixtures/projects/pnpm/unmet_peer_deps/package.json declares Node.js 23 as this project's engines.node, and Node.js 23, support ended 2025-06-01. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2025-06-01 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×3
  • Members sharing a duplicated core (5 members, 50+ identical tokens) bundler/lib/dependabot/bundler/file_parser.rb:333 — bundler/lib/dependabot/bundler/file_parser.rb:333-340 | bundler/lib/dependabot/bundler/file_parser/file_preparer.rb:56-63 | bundler/lib/dependabot/bundler/file_updater.rb:131-141 | bundler/lib/dependabot/bundler/file_updater/lockfile_updater.rb:414-422 | bundler/lib/dependabot/bundler/update_checker/file_preparer.rb:166-173 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) common/lib/dependabot/pull_request_creator.rb:305 — common/lib/dependabot/pull_request_creator.rb:305-322 | common/lib/dependabot/pull_request_creator.rb:327-342 | common/lib/dependabot/pull_request_creator.rb:347-361 | common/lib/dependabot/pull_request_creator.rb:366-378 | common/lib/dependabot/pull_request_creator.rb:383-395 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
  • Members sharing a duplicated core (5 members, 50+ identical tokens) github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:221 — github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:221-245 | github_actions/lib/dependabot/github_actions/update_checker.rb:231-255 | github_actions/lib/dependabot/github_actions/update_checker/latest_version_finder.rb:346-372 | pre_commit/lib/dependabot/pre_commit/package/package_details_fetcher.rb:213-235 | pre_commit/lib/dependabot/pre_commit/update_checker/latest_version_finder.rb:246-256 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×3
  • Duplicated block (25 lines × 2) bundler/helpers/v2/lib/functions.rb:136 — bundler/helpers/v2/lib/functions.rb:136-160 | bundler/helpers/v4/lib/functions.rb:136-160 — before extracting anything, compare `bundler/helpers/v2/lib/functions.rb` and `bundler/helpers/v4/lib/functions.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 101 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) REDACTED:495 — REDACTED:495-519 | REDACTED:381-405 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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) python/helpers/lib/hasher.py:12 — python/helpers/lib/hasher.py:12-36 | uv/helpers/lib/hasher.py:12-36 — before extracting anything, compare `python/helpers/lib/hasher.py` and `uv/helpers/lib/hasher.py` 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. 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×3
  • Duplicated block (22 lines × 2) bazel/lib/dependabot/bazel/file_updater/lockfile_updater.rb:186 — bazel/lib/dependabot/bazel/file_updater/lockfile_updater.rb:186-207 | bazel/lib/dependabot/bazel/file_updater/lockfile_updater.rb:212-233 — 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 (22 lines × 2) bun/lib/dependabot/bun/update_checker.rb:470 — bun/lib/dependabot/bun/update_checker.rb:470-491 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:539-560 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 (22 lines × 2) REDACTED:242 — REDACTED:242-263 | REDACTED:165-186 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×3
  • Duplicated block (15 lines × 3) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:41 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:41-55 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:41-55 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:40-54 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 79 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:41` 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 (15 lines × 3) github_actions/lib/dependabot/github_actions/containing_branch_finder.rb:19 — github_actions/lib/dependabot/github_actions/containing_branch_finder.rb:19-33 | pre_commit/lib/dependabot/pre_commit/package/package_details_fetcher.rb:240-254 | pre_commit/lib/dependabot/pre_commit/update_checker.rb:296-310 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (15 lines × 3) github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:221 — github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:221-235 | github_actions/lib/dependabot/github_actions/update_checker.rb:231-245 | pre_commit/lib/dependabot/pre_commit/package/package_details_fetcher.rb:213-227 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `github_actions/lib/dependabot/github_actions/package/package_details_fetcher.rb:221` 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×3
  • Duplicated block (14–15 lines × 2) REDACTED:451 — REDACTED:451-464 | REDACTED:283-297 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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:451` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (14–15 lines × 2) REDACTED:471 — REDACTED:471-484 | REDACTED:308-322 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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–15 lines × 2) REDACTED:499 — REDACTED:499-512 | REDACTED:339-353 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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:499` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×3
  • Duplicated block (11–12 lines × 2) bundler/lib/dependabot/bundler/update_checker/file_preparer.rb:275 — bundler/lib/dependabot/bundler/update_checker/file_preparer.rb:275-285 | hex/lib/dependabot/hex/update_checker/file_preparer.rb:126-137 — 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–12 lines × 2) opentofu/lib/dependabot/opentofu/registry_client.rb:208 — opentofu/lib/dependabot/opentofu/registry_client.rb:208-218 | terraform/lib/dependabot/terraform/registry_client.rb:116-127 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/registry_client.rb` and `terraform/lib/dependabot/terraform/registry_client.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 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 `opentofu/lib/dependabot/opentofu/registry_client.rb:208` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (11–12 lines × 2) updater/lib/dependabot/updater/operations/create_security_update_pull_request.rb:239 — updater/lib/dependabot/updater/operations/create_security_update_pull_request.rb:239-250 | updater/lib/dependabot/updater/operations/refresh_security_update_pull_request.rb:252-262 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×3
  • Duplicated block (10 lines × 3) updater/lib/dependabot/api_client.rb:123 — updater/lib/dependabot/api_client.rb:123-132 | updater/lib/dependabot/api_client.rb:158-167 | updater/lib/dependabot/api_client.rb:187-196 — 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 `updater/lib/dependabot/api_client.rb:123` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (10 lines × 3) hex/lib/dependabot/hex/update_checker/file_preparer.rb:208 — hex/lib/dependabot/hex/update_checker/file_preparer.rb:208-217 | opentofu/lib/dependabot/opentofu/update_checker.rb:142-151 | terraform/lib/dependabot/terraform/update_checker.rb:153-162 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/update_checker.rb` and `terraform/lib/dependabot/terraform/update_checker.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 46 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 (10 lines × 3) pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb:58 — pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb:58-67 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/ruby.rb:58-67 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/rust.rb:59-68 — before extracting anything, compare `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb` and `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/ruby.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×3
  • Duplicated block (9 lines × 3) bun/lib/dependabot/bun/requirement.rb:100 — bun/lib/dependabot/bun/requirement.rb:100-108 | helm/lib/dependabot/helm/requirement.rb:164-172 | npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:153-161 — before extracting anything, compare `bun/lib/dependabot/bun/requirement.rb` and `helm/lib/dependabot/helm/requirement.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 lines × 3) bun/lib/dependabot/bun/update_checker/requirements_updater.rb:225 — bun/lib/dependabot/bun/update_checker/requirements_updater.rb:225-233 | helm/lib/dependabot/helm/update_checker/requirements_updater.rb:243-251 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb:221-229 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/requirements_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/requirements_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 115 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 lines × 3) git_submodules/lib/dependabot/git_submodules/file_parser.rb:48 — git_submodules/lib/dependabot/git_submodules/file_parser.rb:48-56 | REDACTED:56-64 | REDACTED:46-54 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 178 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×3
  • Duplicated block (12 lines × 3) apm/lib/dependabot/apm/native_helpers.rb:28 — apm/lib/dependabot/apm/native_helpers.rb:28-50 | go_modules/lib/dependabot/go_modules/native_helpers.rb:13-24 | sbt/lib/dependabot/sbt/native_helpers.rb:13-24 — before extracting anything, compare `go_modules/lib/dependabot/go_modules/native_helpers.rb` and `sbt/lib/dependabot/sbt/native_helpers.rb` as WHOLE FILES: 86% 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 (12 lines × 3) cargo/lib/dependabot/cargo/update_checker.rb:385 — cargo/lib/dependabot/cargo/update_checker.rb:385-396 | github_actions/lib/dependabot/github_actions/update_checker.rb:338-349 | hex/lib/dependabot/hex/update_checker.rb:201-212 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
  • Duplicated block (12 lines × 3) conda/lib/dependabot/conda/update_checker.rb:122 — conda/lib/dependabot/conda/update_checker.rb:122-133 | python/lib/dependabot/python/update_checker.rb:385-396 | uv/lib/dependabot/uv/update_checker.rb:202-213 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D6 · Cohesion (LCOM4) · Low cohesion · ×3
  • Low cohesion: Job (LCOM4 7) updater/lib/dependabot/job.rb:38 — Job's methods fall into 7 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 7 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: FileParser (LCOM4 4) pub/lib/dependabot/pub/file_parser.rb:16 — FileParser's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
  • Low cohesion: Version (LCOM4 4) swift/lib/dependabot/swift/version.rb:13 — Version's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
GD1 · Unfinished & placeholder code · Unfinished stub · ×3
  • Unfinished stub — throws NotImplementedException nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:250 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:255 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:265 — A shipped member still throws NotImplementedException — generated scaffolding that was never completed. Implement it or remove the dead surface.
IC1 · Incompleteness & stubs · Unfinished stub · ×3
  • Unfinished stub — throws NotImplementedException nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:250 — `ValidateIntegrityAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:255 — `GetArchiveHashAsync` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
  • Unfinished stub — throws NotImplementedException nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:265 — `GetContentHash` is a shipped member whose whole body throws NotImplementedException — scaffolding that was never completed. Implement it or remove the dead surface.
X1 · Async correctness · Sync-over-async (deadlock risk) · ×3
  • Sync-over-async (deadlock risk) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:34 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/Command.cs:179 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
  • Sync-over-async (deadlock risk) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:1197 — Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
X18 · Disposal-pattern correctness · Disposable created and abandoned in the method that made it · ×3
  • Disposable created and abandoned in the method that made it nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/JsonHelper.cs:38 — `writer` is a `Utf8JsonWriter`, which implements `IDisposable`, and it is created here (line 38). Every use of it in `UpdateJsonProperty` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var writer = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:590 — `referencedProject` is a `ProjectFactory`, which implements `IDisposable`, and it is created here (line 590). Every use of it in `RecursivelyApply` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var referencedProject = …;`), which releases it at the end of the scope on every path including a throw.
  • Disposable created and abandoned in the method that made it nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:704 — `projectFactory` is a `ProjectFactory`, which implements `IDisposable`, and it is created here (line 704). Every use of it in `CreateDependencyFromProject` reads a member through it — it is never returned, never stored, never handed to anything else, and never disposed — so this method both creates the value and is the last thing that can release it, and does not. Nothing announces the leak: the object holds its resource until finalization if its type has a finalizer, and until the process ends if it does not, so the cost accumulates once per CALL rather than showing up as a failure. Declare it with `using` (`using var projectFactory = …;`), which releases it at the end of the scope on every path including a throw.
D15 · Churn × Complexity Hotspots · Repeated repair · ×2
  • Repeated repair: npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:223 — npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is PackageDetailsFetcher.fetch_npm_response at line 223), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Fix npm registry metadata compatibility”; “Fix RuboCop offenses”; “Fix npm ignoring scoped registry issue (#15692)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Repeated repair: nix/lib/dependabot/nix/file_parser.rb nix/lib/dependabot/nix/file_parser.rb:152 — nix/lib/dependabot/nix/file_parser.rb changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is FileParser.build_url at line 152), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(nix): handle indirect inputs”; “fix(nix): lock selected revision”; “Fix RuboCop offenses”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-27..2026-10-25, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-27 12:54:04 -04:00' --until='2026-10-25 12:54:04 -04:00' --full-history --no-merges -- nix/lib/dependabot/nix/file_parser.rb`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D2 · Cognitive Complexity · parser.parse_setup (cognitive 18) · ×2
  • parser.parse_setup (cognitive 18) REDACTED:226 — parser.parse_setup has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (5 pts), error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • parser.parse_setup (cognitive 18) REDACTED:220 — parser.parse_setup has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (5 pts), error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · parser.parse_requirements (cognitive 17) · ×2
  • parser.parse_requirements (cognitive 17) REDACTED:174 — parser.parse_requirements has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), boolean chains 3, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • parser.parse_requirements (cognitive 17) REDACTED:168 — parser.parse_requirements has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), boolean chains 3, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D3 · God Classes · ClassTooLong · ×2
  • ClassTooLong: XmlFileWriter nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs — ClassTooLong — 611 significant lines (blank, comment-only and punctuation-only lines excluded), 7 methods. The bar is 400 significant lines; this is 211 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SdkProjectDiscovery nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs — ClassTooLong — 586 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 186 over it, 1.47× the bar. The type holds no instance state, so there is no shared data to group its members by. To reduce it, split it by area instead: give each cohesive family of members its own smaller type, so no one type has to be read whole to change one of them.
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×2
  • Duplicated block (37 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:217 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:217-253 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:224-260 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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 (37 lines × 2) bundler/helpers/v2/lib/functions/force_updater.rb:23 — bundler/helpers/v2/lib/functions/force_updater.rb:23-59 | bundler/helpers/v4/lib/functions/force_updater.rb:23-59 — before extracting anything, compare `bundler/helpers/v2/lib/functions/force_updater.rb` and `bundler/helpers/v4/lib/functions/force_updater.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 115 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.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×2
  • Duplicated block (34 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:145 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:145-178 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:217-250 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 (34 lines × 2) python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:125 — python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:125-158 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:128-161 — before extracting anything, compare `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 186 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.
D4 · Code Duplication · Duplicated block (30 lines × 2) · ×2
  • Duplicated block (30 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:37 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:37-66 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitLabPackageDetailFinder.cs:37-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:37` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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 (30 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:258 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:258-287 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:265-294 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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.
D4 · Code Duplication · Duplicated block (33 lines × 2) · ×2
  • Duplicated block (33 lines × 2) bun/lib/dependabot/bun/registry_helper.rb:100 — bun/lib/dependabot/bun/registry_helper.rb:100-132 | npm_and_yarn/lib/dependabot/npm_and_yarn/registry_helper.rb:272-304 — before extracting anything, compare `bun/lib/dependabot/bun/registry_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/registry_helper.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 80 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 (33 lines × 2) common/lib/dependabot/pull_request_creator/github.rb:323 — common/lib/dependabot/pull_request_creator/github.rb:323-355 | common/lib/dependabot/pull_request_updater/github.rb:202-234 — `common/lib/dependabot/pull_request_creator/github.rb` and `common/lib/dependabot/pull_request_updater/github.rb` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 49 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication · Duplicated block (32 lines × 2) · ×2
  • Duplicated block (32 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:98 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:98-129 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitLabPackageDetailFinder.cs:104-135 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:98` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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 (32 lines × 2) bun/lib/dependabot/bun/package/package_details_fetcher.rb:96 — bun/lib/dependabot/bun/package/package_details_fetcher.rb:96-127 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb:103-134 — before extracting anything, compare `bun/lib/dependabot/bun/package/package_details_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/package_details_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 170 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.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×2
  • Duplicated block (28 lines × 2) bun/lib/dependabot/bun/package_manager.rb:138 — bun/lib/dependabot/bun/package_manager.rb:138-165 | npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb:300-327 — before extracting anything, compare `bun/lib/dependabot/bun/package_manager.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb:294` calls `reset_npm_version_selector` and `bun/lib/dependabot/bun/package_manager.rb:133` 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 (28 lines × 2) python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:239 — python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:239-266 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:232-259 — before extracting anything, compare `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 186 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.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×2
  • Duplicated block (26 lines × 2) bun/lib/dependabot/bun/file_updater/package_json_updater.rb:424 — bun/lib/dependabot/bun/file_updater/package_json_updater.rb:424-449 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb:410-435 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 160 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 (26 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:450 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:450-475 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:409-434 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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.
D4 · Code Duplication · Duplicated block (22–24 lines × 2) · ×2
  • Duplicated block (22–24 lines × 2) REDACTED:315 — REDACTED:315-336 | REDACTED:232-255 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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:315` 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–24 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:199 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:199-222 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:185-206 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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 `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:199` 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.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:457 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:457-479 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:671-693 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 (23 lines × 2) bun/lib/dependabot/bun/update_checker/version_resolver.rb:535 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:535-557 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:751-773 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker/version_resolver.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 237 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 `bun/lib/dependabot/bun/update_checker/version_resolver.rb:535` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (19 lines × 3) · ×2
  • Duplicated block (19 lines × 3) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:136 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:136-154 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:117-135 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:107-125 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 70 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 (19 lines × 3) pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb:32 — pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb:32-50 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb:33-51 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/ruby.rb:33-51 — before extracting anything, compare `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb` and `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (16–17 lines × 2) · ×2
  • Duplicated block (16–17 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:239 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:239-255 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:381-396 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:239` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:238` calls `Error` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:380` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16–17 lines × 2) bun/lib/dependabot/bun/file_updater.rb:44 — bun/lib/dependabot/bun/file_updater.rb:44-60 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:57-72 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb` as WHOLE FILES: this scan already matched 6 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.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×2
  • Duplicated block (12 lines × 4) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:135 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:135-146 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:390-401 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:130-141 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:120-131 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:135` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:126` calls `Info` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:386` 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 (12 lines × 4) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:267 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:267-278 | python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:327-338 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:250-261 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:364-375 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×2
  • Duplicated block (11 lines × 3) bundler/lib/dependabot/bundler/update_checker/requirements_updater.rb:173 — bundler/lib/dependabot/bundler/update_checker/requirements_updater.rb:173-183 | opentofu/lib/dependabot/opentofu/requirements_updater.rb:219-229 | terraform/lib/dependabot/terraform/requirements_updater.rb:201-211 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/requirements_updater.rb` and `terraform/lib/dependabot/terraform/requirements_updater.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 84 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 × 3) REDACTED:133 — REDACTED:133-143 | opentofu/lib/dependabot/opentofu/update_checker/latest_version_resolver.rb:132-142 | terraform/lib/dependabot/terraform/update_checker/latest_version_resolver.rb:89-99 — before extracting anything, compare `opentofu/lib/dependabot/opentofu/update_checker/latest_version_resolver.rb` and `terraform/lib/dependabot/terraform/update_checker/latest_version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×2
  • Duplicated block (10 lines × 4) common/lib/dependabot/update_checkers/vulnerability_audit.rb:18 — common/lib/dependabot/update_checkers/vulnerability_audit.rb:18-27 | updater/lib/dependabot/api_client.rb:456-465 | updater/lib/dependabot/job.rb:180-189 | updater/lib/dependabot/pull_request.rb:212-221 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (10 lines × 4) cargo/lib/dependabot/cargo/file_parser.rb:51 — cargo/lib/dependabot/cargo/file_parser.rb:51-60 | devcontainers/lib/dependabot/devcontainers/file_parser.rb:35-44 | REDACTED:72-81 | hex/lib/dependabot/hex/file_parser.rb:56-65 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×2
  • Duplicated block (9 lines × 5) common/lib/dependabot/pull_request_creator.rb:306 — common/lib/dependabot/pull_request_creator.rb:306-314 | common/lib/dependabot/pull_request_creator.rb:328-336 | common/lib/dependabot/pull_request_creator.rb:348-356 | common/lib/dependabot/pull_request_creator.rb:367-375 | common/lib/dependabot/pull_request_creator.rb:384-392 — 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 (9 lines × 5) bun/lib/dependabot/bun/file_updater/package_json_updater.rb:411 — bun/lib/dependabot/bun/file_updater/package_json_updater.rb:411-419 | gradle/lib/dependabot/gradle/file_parser.rb:717-725 | gradle/lib/dependabot/gradle/file_parser/repositories_finder.rb:188-196 | gradle/lib/dependabot/gradle/file_updater.rb:314-322 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb:397-405 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 160 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×2
  • Duplicated block (9 lines × 4) bun/lib/dependabot/bun/package/registry_finder.rb:178 — bun/lib/dependabot/bun/package/registry_finder.rb:178-186 | common/lib/dependabot/clients/azure.rb:511-519 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_credential_helpers.rb:76-84 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb:180-188 — before extracting anything, compare `bun/lib/dependabot/bun/package/registry_finder.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 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 lines × 4) opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb:81 — opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb:81-89 | opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb:108-116 | terraform/lib/dependabot/terraform/package/package_details_fetcher.rb:51-59 | terraform/lib/dependabot/terraform/package/package_details_fetcher.rb:81-89 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `terraform/lib/dependabot/terraform/package/package_details_fetcher.rb:61` calls `fetch` and `opentofu/lib/dependabot/opentofu/package/package_details_fetcher.rb:91` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×2
  • Duplicated block (7 lines × 4) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:34 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:34-40 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:85-91 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:33-39 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:33-39 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 64 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:34` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:40` calls `Error` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:41` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 4) bundler/helpers/v2/lib/functions/lockfile_updater.rb:169 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:169-175 | bundler/helpers/v2/lib/functions/version_resolver.rb:111-117 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:169-175 | bundler/helpers/v4/lib/functions/version_resolver.rb:111-117 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×2
  • Duplicated block (5 lines × 6) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:98 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:98-102 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:213-217 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:357-361 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:119-123 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:100-104 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:90-94 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:98` 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 (5 lines × 6) bun/lib/dependabot/bun/file_updater.rb:117 — bun/lib/dependabot/bun/file_updater.rb:117-121 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:247-251 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:256-260 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:265-269 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:274-278 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb:301-305 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater.rb` as WHOLE FILES: this scan already matched 6 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×2
  • Duplicated block (11 lines × 4) common/lib/dependabot/package/package_release.rb:43 — common/lib/dependabot/package/package_release.rb:43-53 | common/lib/dependabot/pull_request_creator/bitbucket.rb:81-91 | common/lib/dependabot/pull_request_creator/codecommit.rb:77-87 | common/lib/dependabot/update_checkers/base.rb:82-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
  • Duplicated block (11 lines × 4) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:591 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:591-601 | python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:302-312 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:545-555 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:300-310 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
R10 · Code Duplication · Duplicated block (19 lines × 2 locations) · ×2
  • Duplicated block (19 lines × 2 locations) REDACTED:83 — REDACTED:83 · npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (19 lines × 2 locations) npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:46 — npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:46 · npm_and_yarn/helpers/lib/yarn/updater.ts:56 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×2
  • Duplicated block (16 lines × 2 locations) bun/helpers/lib/npm6/peer-dependency-checker.js:33 — bun/helpers/lib/npm6/peer-dependency-checker.js:33 · npm_and_yarn/helpers/lib/npm6/peer-dependency-checker.ts:40 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (16 lines × 2 locations) bun/helpers/lib/yarn/peer-dependency-checker.js:34 — bun/helpers/lib/yarn/peer-dependency-checker.js:34 · bun/helpers/lib/yarn/updater.js:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×2
  • Duplicated block (11 lines × 2 locations) bun/helpers/lib/npm6/remove-dependencies-from-lockfile.js:5 — bun/helpers/lib/npm6/remove-dependencies-from-lockfile.js:5 · npm_and_yarn/helpers/lib/npm6/remove-dependencies-from-lockfile.ts:16 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (11 lines × 2 locations) bun/helpers/lib/yarn/peer-dependency-checker.js:60 — bun/helpers/lib/yarn/peer-dependency-checker.js:60 · npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:77 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (6 lines × 2 locations) · ×2
  • Duplicated block (6 lines × 2 locations) bun/helpers/lib/npm6/peer-dependency-checker.js:81 — bun/helpers/lib/npm6/peer-dependency-checker.js:81 · npm_and_yarn/helpers/lib/npm6/peer-dependency-checker.ts:88 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (6 lines × 2 locations) bun/helpers/lib/yarn/peer-dependency-checker.js:111 — bun/helpers/lib/yarn/peer-dependency-checker.js:111 · npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:129 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
X2 · Cancellation propagation · Async local function without CancellationToken · ×2
  • Async local function without CancellationToken: EnsurePackagesForFileAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:570 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
  • Async local function without CancellationToken: TrackOriginalContentsAsync nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ModifiedFilesTracker.cs:94 — Neither takes a CancellationToken nor reads the one of the function it sits in, while it calls something that takes one — this work can't be stopped early once started. Take the token, or pass on the enclosing one.
D1 · Cyclomatic Complexity · XmlFileWriter.UpdatePackageVersionsAsync (cyclomatic 71) · ×1
  • XmlFileWriter.UpdatePackageVersionsAsync (cyclomatic 71) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:52 — XmlFileWriter.UpdatePackageVersionsAsync has cyclomatic complexity 71 (threshold 15). Of this number, 68 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · SdkProjectDiscovery.DiscoverAsync (cyclomatic 57) · ×1
  • SdkProjectDiscovery.DiscoverAsync (cyclomatic 57) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:76 — SdkProjectDiscovery.DiscoverAsync has cyclomatic complexity 57 (threshold 15). Of this number, 22 points are the body's own statements and 35 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · NpmLockfileUpdater.handle_npm_updater_error (cyclomatic 52) · ×1
  • NpmLockfileUpdater.handle_npm_updater_error (cyclomatic 52) npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:585 — NpmLockfileUpdater.handle_npm_updater_error has cyclomatic complexity 52 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SdkProjectDiscovery.BuildResults (cyclomatic 48) · ×1
  • SdkProjectDiscovery.BuildResults (cyclomatic 48) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:492 — SdkProjectDiscovery.BuildResults has cyclomatic complexity 48 (threshold 15). Of this number, 40 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PnpmLockfileUpdater.handle_pnpm_lock_updater_error (cyclomatic 44) · ×1
  • PnpmLockfileUpdater.handle_pnpm_lock_updater_error (cyclomatic 44) npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:832 — PnpmLockfileUpdater.handle_pnpm_lock_updater_error has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ConstraintHelper.to_ruby_constraint_with_version (cyclomatic 38) · ×1
  • ConstraintHelper.to_ruby_constraint_with_version (cyclomatic 38) npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb:359 — ConstraintHelper.to_ruby_constraint_with_version has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ConstraintHelper.to_ruby_constraint_with_version (cyclomatic 32) · ×1
  • ConstraintHelper.to_ruby_constraint_with_version (cyclomatic 32) bun/lib/dependabot/bun/constraint_helper.rb:269 — ConstraintHelper.to_ruby_constraint_with_version has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VersionResolver.handle_composer_errors (cyclomatic 31) · ×1
  • VersionResolver.handle_composer_errors (cyclomatic 31) composer/lib/dependabot/composer/update_checker/version_resolver.rb:316 — VersionResolver.handle_composer_errors has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CommandHelpers.capture3_with_timeout (cyclomatic 30) · ×1
  • CommandHelpers.capture3_with_timeout (cyclomatic 30) common/lib/dependabot/command_helpers.rb:93 — CommandHelpers.capture3_with_timeout has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PackageManager.UpdateVersion (cyclomatic 29) · ×1
  • PackageManager.UpdateVersion (cyclomatic 29) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:335 — PackageManager.UpdateVersion has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FileWriterWorker.ProcessPackageReferenceUpdatesAsync (cyclomatic 28) · ×1
  • FileWriterWorker.ProcessPackageReferenceUpdatesAsync (cyclomatic 28) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs:137 — FileWriterWorker.ProcessPackageReferenceUpdatesAsync has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VersionFinder.CreateVersionFilter (cyclomatic 27) · ×1
  • VersionFinder.CreateVersionFilter (cyclomatic 27) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs:309 — VersionFinder.CreateVersionFilter has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to one function literal inside it that branches (line 317). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · PackageManager.GetDependenciesAsync (cyclomatic 26) · ×1
  • PackageManager.GetDependenciesAsync (cyclomatic 26) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:144 — PackageManager.GetDependenciesAsync has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JsonHelper.UpdateJsonProperty (cyclomatic 26) · ×1
  • JsonHelper.UpdateJsonProperty (cyclomatic 26) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/JsonHelper.cs:23 — JsonHelper.UpdateJsonProperty has cyclomatic complexity 26 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · SdkProjectDiscovery.ProcessResolvedPackageReference (cyclomatic 25) · ×1
  • SdkProjectDiscovery.ProcessResolvedPackageReference (cyclomatic 25) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:888 — SdkProjectDiscovery.ProcessResolvedPackageReference has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GitLabPackageDetailFinder.GetReleaseDataForVersionsAsync (cyclomatic 24) · ×1
  • GitLabPackageDetailFinder.GetReleaseDataForVersionsAsync (cyclomatic 24) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitLabPackageDetailFinder.cs:31 — GitLabPackageDetailFinder.GetReleaseDataForVersionsAsync has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · JobErrorBase.ErrorFromException (cyclomatic 23) · ×1
  • JobErrorBase.ErrorFromException (cyclomatic 23) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ApiModel/JobErrorBase.cs:34 — JobErrorBase.ErrorFromException has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · DetailedPullRequestBodyGenerator.GeneratePullRequestBodyTextAsync (cyclomatic 22) · ×1
  • DetailedPullRequestBodyGenerator.GeneratePullRequestBodyTextAsync (cyclomatic 22) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/DetailedPullRequestBodyGenerator.cs:28 — DetailedPullRequestBodyGenerator.GeneratePullRequestBodyTextAsync has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · GitHubPackageDetailFinder.GetReleaseDataForVersionsAsync (cyclomatic 21) · ×1
  • GitHubPackageDetailFinder.GetReleaseDataForVersionsAsync (cyclomatic 21) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:31 — GitHubPackageDetailFinder.GetReleaseDataForVersionsAsync has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MessageBuilder.version_commit_message_intro (cyclomatic 21) · ×1
  • MessageBuilder.version_commit_message_intro (cyclomatic 21) common/lib/dependabot/pull_request_creator/message_builder.rb:435 — MessageBuilder.version_commit_message_intro has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RefreshSecurityUpdatePullRequest.check_and_update_pull_request (cyclomatic 20) · ×1
  • RefreshSecurityUpdatePullRequest.check_and_update_pull_request (cyclomatic 20) updater/lib/dependabot/updater/operations/refresh_security_update_pull_request.rb:101 — RefreshSecurityUpdatePullRequest.check_and_update_pull_request has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · RefreshGroupUpdatePullRequestHandler.HandleAsync (cyclomatic 19) · ×1
  • RefreshGroupUpdatePullRequestHandler.HandleAsync (cyclomatic 19) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:49 — RefreshGroupUpdatePullRequestHandler.HandleAsync has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MSBuildHelper.GetProjectPropertiesAsync (cyclomatic 19) · ×1
  • MSBuildHelper.GetProjectPropertiesAsync (cyclomatic 19) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:567 — MSBuildHelper.GetProjectPropertiesAsync has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · ProjectFactory.CreateBuilder (cyclomatic 19) · ×1
  • ProjectFactory.CreateBuilder (cyclomatic 19) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:213 — ProjectFactory.CreateBuilder has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SharedBundlerHelpers.handle_bundler_errors (cyclomatic 19) · ×1
  • SharedBundlerHelpers.handle_bundler_errors (cyclomatic 19) bundler/lib/dependabot/bundler/update_checker/shared_bundler_helpers.rb:121 — SharedBundlerHelpers.handle_bundler_errors has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · LockfileUpdater.handle_composer_errors (cyclomatic 19) · ×1
  • LockfileUpdater.handle_composer_errors (cyclomatic 19) composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:176 — LockfileUpdater.handle_composer_errors has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · VersionFinder.GetVersionsAsync (cyclomatic 18) · ×1
  • VersionFinder.GetVersionsAsync (cyclomatic 18) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs:140 — VersionFinder.GetVersionsAsync has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · CreateSecurityUpdatePullRequestHandler.HandleAsync (cyclomatic 18) · ×1
  • CreateSecurityUpdatePullRequestHandler.HandleAsync (cyclomatic 18) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:30 — CreateSecurityUpdatePullRequestHandler.HandleAsync has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MSBuildHelper.ResolveDependencyConflicts (cyclomatic 18) · ×1
  • MSBuildHelper.ResolveDependencyConflicts (cyclomatic 18) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:91 — MSBuildHelper.ResolveDependencyConflicts has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PathHelper.GetMatchingDirectoriesUnder (cyclomatic 18) · ×1
  • PathHelper.GetMatchingDirectoriesUnder (cyclomatic 18) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/PathHelper.cs:266 — PathHelper.GetMatchingDirectoriesUnder has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · VersionParser.parse_version (cyclomatic 18) · ×1
  • VersionParser.parse_version (cyclomatic 18) maven/lib/dependabot/maven/version_parser.rb:70 — VersionParser.parse_version has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PackageManagerHelper.setup (cyclomatic 18) · ×1
  • PackageManagerHelper.setup (cyclomatic 18) npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb:293 — PackageManagerHelper.setup has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PipenvVersionResolver.handle_pipenv_errors (cyclomatic 18) · ×1
  • PipenvVersionResolver.handle_pipenv_errors (cyclomatic 18) python/lib/dependabot/python/update_checker/pipenv_version_resolver.rb:106 — PipenvVersionResolver.handle_pipenv_errors has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · XmlFileWriter.CreateUpdatedVersionRangeString (cyclomatic 17) · ×1
  • XmlFileWriter.CreateUpdatedVersionRangeString (cyclomatic 17) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:881 — XmlFileWriter.CreateUpdatedVersionRangeString has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · TokenBucket.compare_token_pair (cyclomatic 17) · ×1
  • TokenBucket.compare_token_pair (cyclomatic 17) maven/lib/dependabot/maven/token_bucket.rb:56 — TokenBucket.compare_token_pair has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · FileFetcher.inferred_npmrc (cyclomatic 17) · ×1
  • FileFetcher.inferred_npmrc (cyclomatic 17) npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:167 — FileFetcher.inferred_npmrc has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · lockfile-parser.nameVerDevFromPkgSnapshot (cyclomatic 17) · ×1
  • lockfile-parser.nameVerDevFromPkgSnapshot (cyclomatic 17) npm_and_yarn/helpers/lib/pnpm/lockfile-parser.ts:113 — lockfile-parser.nameVerDevFromPkgSnapshot has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 134). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D1 · Cyclomatic Complexity · DiscoveryWorker.ExpandEntryPointsIntoProjectsAsync (cyclomatic 16) · ×1
  • DiscoveryWorker.ExpandEntryPointsIntoProjectsAsync (cyclomatic 16) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:284 — DiscoveryWorker.ExpandEntryPointsIntoProjectsAsync has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · RefreshSecurityUpdatePullRequestHandler.HandleAsync (cyclomatic 16) · ×1
  • RefreshSecurityUpdatePullRequestHandler.HandleAsync (cyclomatic 16) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:29 — RefreshSecurityUpdatePullRequestHandler.HandleAsync has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · Program.MainCore (cyclomatic 16) · ×1
  • Program.MainCore (cyclomatic 16) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:77 — Program.MainCore has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Version.compare_prerelease (cyclomatic 16) · ×1
  • Version.compare_prerelease (cyclomatic 16) go_modules/lib/dependabot/go_modules/version.rb:94 — Version.compare_prerelease has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · FileParser.source_type (cyclomatic 16) · ×1
  • FileParser.source_type (cyclomatic 16) REDACTED:447 — FileParser.source_type has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · Job.allowed_update? (cyclomatic 16) · ×1
  • Job.allowed_update? (cyclomatic 16) updater/lib/dependabot/job.rb:339 — Job.allowed_update? has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · UpdateChecker.getLatestResolvableVersion (cyclomatic 16) · ×1
  • UpdateChecker.getLatestResolvableVersion (cyclomatic 16) composer/helpers/v2/src/UpdateChecker.php:15 — UpdateChecker.getLatestResolvableVersion has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D10 · Test Quality · No assertions · ×1
  • No assertions: GetAllPackageDependencies_NugetConfigInvalid_DoesNotThrow nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Utilities/MSBuildHelperTests.cs:218 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D17 · Explicit Debt · BareSuppressMessage · ×1
  • BareSuppressMessage nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/UpdateCommand.cs:158 — System.Diagnostics.CodeAnalysis.SuppressMessage — the suppression records no reason: either it carries no justification argument at all, or one that states nothing a reader can weigh ("OK", "By design"). A suppression is a decision somebody made, and without the reason the next reader cannot tell a considered exception from an unexamined one, so it is never revisited. Write what makes this site legitimately different — the invariant that holds, the framework contract that forces the shape — or remove the suppression and fix what it hides.
D2 · Cognitive Complexity · XmlFileWriter.UpdatePackageVersionsAsync (cognitive 329) · ×1
  • XmlFileWriter.UpdatePackageVersionsAsync (cognitive 329) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:52 — XmlFileWriter.UpdatePackageVersionsAsync has cognitive complexity 329 (threshold 15). Of this number, 327 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SdkProjectDiscovery.DiscoverAsync (cognitive 158) · ×1
  • SdkProjectDiscovery.DiscoverAsync (cognitive 158) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:76 — SdkProjectDiscovery.DiscoverAsync has cognitive complexity 158 (threshold 15). Of this number, 35 points are the body's own statements and 123 belong to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · SdkProjectDiscovery.BuildResults (cognitive 131) · ×1
  • SdkProjectDiscovery.BuildResults (cognitive 131) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:492 — SdkProjectDiscovery.BuildResults has cognitive complexity 131 (threshold 15). Of this number, 100 points are the body's own statements and 31 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SdkProjectDiscovery.ProcessResolvedPackageReference (cognitive 91) · ×1
  • SdkProjectDiscovery.ProcessResolvedPackageReference (cognitive 91) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/SdkProjectDiscovery.cs:888 — SdkProjectDiscovery.ProcessResolvedPackageReference has cognitive complexity 91 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · PackageManager.UpdateVersion (cognitive 71) · ×1
  • PackageManager.UpdateVersion (cognitive 71) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:335 — PackageManager.UpdateVersion has cognitive complexity 71 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · DetailedPullRequestBodyGenerator.GeneratePullRequestBodyTextAsync (cognitive 63) · ×1
  • DetailedPullRequestBodyGenerator.GeneratePullRequestBodyTextAsync (cognitive 63) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/DetailedPullRequestBodyGenerator.cs:28 — DetailedPullRequestBodyGenerator.GeneratePullRequestBodyTextAsync has cognitive complexity 63 (threshold 15). Of this number, 62 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · FileWriterWorker.ProcessPackageReferenceUpdatesAsync (cognitive 53) · ×1
  • FileWriterWorker.ProcessPackageReferenceUpdatesAsync (cognitive 53) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs:137 — FileWriterWorker.ProcessPackageReferenceUpdatesAsync has cognitive complexity 53 (threshold 15). Of this number, 46 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CreateSecurityUpdatePullRequestHandler.HandleAsync (cognitive 52) · ×1
  • CreateSecurityUpdatePullRequestHandler.HandleAsync (cognitive 52) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:30 — CreateSecurityUpdatePullRequestHandler.HandleAsync has cognitive complexity 52 (threshold 15). Of this number, 51 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · NpmLockfileUpdater.handle_npm_updater_error (cognitive 51) · ×1
  • NpmLockfileUpdater.handle_npm_updater_error (cognitive 51) npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npm_lockfile_updater.rb:585 — NpmLockfileUpdater.handle_npm_updater_error has cognitive complexity 51 (threshold 15). Drivers by points: if/else 31, boolean chains 20. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · GroupUpdateAllVersionsHandler.RunUngroupedDependencyUpdates (cognitive 48) · ×1
  • GroupUpdateAllVersionsHandler.RunUngroupedDependencyUpdates (cognitive 48) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:317 — GroupUpdateAllVersionsHandler.RunUngroupedDependencyUpdates has cognitive complexity 48 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RefreshSecurityUpdatePullRequestHandler.HandleAsync (cognitive 47) · ×1
  • RefreshSecurityUpdatePullRequestHandler.HandleAsync (cognitive 47) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:29 — RefreshSecurityUpdatePullRequestHandler.HandleAsync has cognitive complexity 47 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · CommandHelpers.capture3_with_timeout (cognitive 47) · ×1
  • CommandHelpers.capture3_with_timeout (cognitive 47) common/lib/dependabot/command_helpers.rb:93 — CommandHelpers.capture3_with_timeout has cognitive complexity 47 (threshold 15). Drivers by points: if/else 17 (33 pts), error handling 5 (9 pts), ternaries 3, boolean chains 1, loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · XmlFileWriter.CreateUpdatedVersionRangeString (cognitive 46) · ×1
  • XmlFileWriter.CreateUpdatedVersionRangeString (cognitive 46) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:881 — XmlFileWriter.CreateUpdatedVersionRangeString has cognitive complexity 46 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · RefreshVersionUpdatePullRequestHandler.HandleAsync (cognitive 44) · ×1
  • RefreshVersionUpdatePullRequestHandler.HandleAsync (cognitive 44) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:29 — RefreshVersionUpdatePullRequestHandler.HandleAsync has cognitive complexity 44 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RefreshGroupUpdatePullRequestHandler.HandleAsync (cognitive 42) · ×1
  • RefreshGroupUpdatePullRequestHandler.HandleAsync (cognitive 42) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:49 — RefreshGroupUpdatePullRequestHandler.HandleAsync has cognitive complexity 42 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PackageManager.GetDependenciesAsync (cognitive 41) · ×1
  • PackageManager.GetDependenciesAsync (cognitive 41) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:144 — PackageManager.GetDependenciesAsync has cognitive complexity 41 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ConstraintHelper.to_ruby_constraint_with_version (cognitive 37) · ×1
  • ConstraintHelper.to_ruby_constraint_with_version (cognitive 37) npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb:359 — ConstraintHelper.to_ruby_constraint_with_version has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (26 pts), boolean chains 5, match/switch 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GroupUpdateAllVersionsHandler.RunEffectiveGroupUpdate (cognitive 36) · ×1
  • GroupUpdateAllVersionsHandler.RunEffectiveGroupUpdate (cognitive 36) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:165 — GroupUpdateAllVersionsHandler.RunEffectiveGroupUpdate has cognitive complexity 36 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GitLabPackageDetailFinder.GetReleaseDataForVersionsAsync (cognitive 35) · ×1
  • GitLabPackageDetailFinder.GetReleaseDataForVersionsAsync (cognitive 35) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitLabPackageDetailFinder.cs:31 — GitLabPackageDetailFinder.GetReleaseDataForVersionsAsync has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GroupUpdateAllVersionsHandler.RunGroupedDependencyUpdates (cognitive 35) · ×1
  • GroupUpdateAllVersionsHandler.RunGroupedDependencyUpdates (cognitive 35) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:63 — GroupUpdateAllVersionsHandler.RunGroupedDependencyUpdates has cognitive complexity 35 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VersionFinder.GetVersionsAsync (cognitive 34) · ×1
  • VersionFinder.GetVersionsAsync (cognitive 34) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs:140 — VersionFinder.GetVersionsAsync has cognitive complexity 34 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Correlator.RunAsync (cognitive 31) · ×1
  • Correlator.RunAsync (cognitive 31) nuget/helpers/lib/NuGetUpdater/DotNetPackageCorrelation/Correlator.cs:24 — Correlator.RunAsync has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DiscoveryWorker.ExpandEntryPointsIntoProjectsAsync (cognitive 31) · ×1
  • DiscoveryWorker.ExpandEntryPointsIntoProjectsAsync (cognitive 31) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:284 — DiscoveryWorker.ExpandEntryPointsIntoProjectsAsync has cognitive complexity 31 (threshold 15). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · GitHubPackageDetailFinder.GetReleaseDataForVersionsAsync (cognitive 31) · ×1
  • GitHubPackageDetailFinder.GetReleaseDataForVersionsAsync (cognitive 31) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:31 — GitHubPackageDetailFinder.GetReleaseDataForVersionsAsync has cognitive complexity 31 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PackagesConfigUpdater.GetPathToPackagesDirectory (cognitive 30) · ×1
  • PackagesConfigUpdater.GetPathToPackagesDirectory (cognitive 30) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackagesConfigUpdater.cs:172 — PackagesConfigUpdater.GetPathToPackagesDirectory has cognitive complexity 30 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · ConstraintHelper.to_ruby_constraint_with_version (cognitive 30) · ×1
  • ConstraintHelper.to_ruby_constraint_with_version (cognitive 30) bun/lib/dependabot/bun/constraint_helper.rb:269 — ConstraintHelper.to_ruby_constraint_with_version has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (23 pts), boolean chains 3, ternaries 1 (3 pts), match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VersionResolver.handle_composer_errors (cognitive 30) · ×1
  • VersionResolver.handle_composer_errors (cognitive 30) composer/lib/dependabot/composer/update_checker/version_resolver.rb:316 — VersionResolver.handle_composer_errors has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 9 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · NuGetContext.FindPackageInfoUrlAsync (cognitive 29) · ×1
  • NuGetContext.FindPackageInfoUrlAsync (cognitive 29) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/NuGetContext.cs:103 — NuGetContext.FindPackageInfoUrlAsync has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · EntryPointFinder.FindRootDirectoriesAsync (cognitive 29) · ×1
  • EntryPointFinder.FindRootDirectoriesAsync (cognitive 29) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/EntryPointFinder.cs:23 — EntryPointFinder.FindRootDirectoriesAsync has cognitive complexity 29 (threshold 15). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · JsonHelper.UpdateJsonProperty (cognitive 29) · ×1
  • JsonHelper.UpdateJsonProperty (cognitive 29) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/JsonHelper.cs:23 — JsonHelper.UpdateJsonProperty has cognitive complexity 29 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PnpmLockfileUpdater.handle_pnpm_lock_updater_error (cognitive 29) · ×1
  • PnpmLockfileUpdater.handle_pnpm_lock_updater_error (cognitive 29) npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:832 — PnpmLockfileUpdater.handle_pnpm_lock_updater_error has cognitive complexity 29 (threshold 15). Drivers by points: if/else 23, boolean chains 4, ternaries 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · ModifiedFilesTracker.StopTrackingAsync (cognitive 27) · ×1
  • ModifiedFilesTracker.StopTrackingAsync (cognitive 27) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ModifiedFilesTracker.cs:139 — ModifiedFilesTracker.StopTrackingAsync has cognitive complexity 27 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Version.compare_prerelease (cognitive 27) · ×1
  • Version.compare_prerelease (cognitive 27) go_modules/lib/dependabot/go_modules/version.rb:94 — Version.compare_prerelease has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (25 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FrameworkCompatibilityService.GetCompatibilityMatrix (cognitive 26) · ×1
  • FrameworkCompatibilityService.GetCompatibilityMatrix (cognitive 26) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/FrameworkChecker/FrameworkCompatibilityService.cs:45 — FrameworkCompatibilityService.GetCompatibilityMatrix has cognitive complexity 26 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Job.IsUpdatePermitted (cognitive 26) · ×1
  • Job.IsUpdatePermitted (cognitive 26) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ApiModel/Job.cs:212 — Job.IsUpdatePermitted has cognitive complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · MSBuildHelper.ResolveDependencyConflicts (cognitive 25) · ×1
  • MSBuildHelper.ResolveDependencyConflicts (cognitive 25) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:91 — MSBuildHelper.ResolveDependencyConflicts has cognitive complexity 25 (threshold 15). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProjectFactory.AddDependencies (cognitive 25) · ×1
  • ProjectFactory.AddDependencies (cognitive 25) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:925 — ProjectFactory.AddDependencies has cognitive complexity 25 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GraphWorker.BuildDependencySubmission (cognitive 24) · ×1
  • GraphWorker.BuildDependencySubmission (cognitive 24) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Graph/GraphWorker.cs:86 — GraphWorker.BuildDependencySubmission has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MSBuildHelper.GetProjectPropertiesAsync (cognitive 24) · ×1
  • MSBuildHelper.GetProjectPropertiesAsync (cognitive 24) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:567 — MSBuildHelper.GetProjectPropertiesAsync has cognitive complexity 24 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UpdateChecker.tags_from_registry (cognitive 24) · ×1
  • UpdateChecker.tags_from_registry (cognitive 24) docker/lib/dependabot/docker/update_checker.rb:729 — UpdateChecker.tags_from_registry has cognitive complexity 24 (threshold 15). Drivers by points: error handling 5 (15 pts), if/else 2 (9 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UpdateGraphProcessor.process_directory (cognitive 24) · ×1
  • UpdateGraphProcessor.process_directory (cognitive 24) updater/lib/dependabot/update_graph_processor.rb:102 — UpdateGraphProcessor.process_directory has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), error handling 3 (6 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Correlator.GetPackagesFromMarkdown (cognitive 23) · ×1
  • Correlator.GetPackagesFromMarkdown (cognitive 23) nuget/helpers/lib/NuGetUpdater/DotNetPackageCorrelation/Correlator.cs:95 — Correlator.GetPackagesFromMarkdown has cognitive complexity 23 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProjectFactory.CreateBuilder (cognitive 23) · ×1
  • ProjectFactory.CreateBuilder (cognitive 23) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:213 — ProjectFactory.CreateBuilder has cognitive complexity 23 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · UpdateChecker.getLatestResolvableVersion (cognitive 23) · ×1
  • UpdateChecker.getLatestResolvableVersion (cognitive 23) composer/helpers/v2/src/UpdateChecker.php:15 — UpdateChecker.getLatestResolvableVersion has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 8 (10 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · BindingRedirectManager.AddBindingRedirects (cognitive 22) · ×1
  • BindingRedirectManager.AddBindingRedirects (cognitive 22) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/BindingRedirectManager.cs:149 — BindingRedirectManager.AddBindingRedirects has cognitive complexity 22 (threshold 15). Of this number, 16 points are the body's own statements and 6 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VersionParser.parse_version (cognitive 22) · ×1
  • VersionParser.parse_version (cognitive 22) maven/lib/dependabot/maven/version_parser.rb:70 — VersionParser.parse_version has cognitive complexity 22 (threshold 15). Drivers by points: if/else 18 (21 pts), loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · parser.parse_pep621_pep735_dependencies (cognitive 22) · ×1
  • parser.parse_pep621_pep735_dependencies (cognitive 22) REDACTED:26 — parser.parse_pep621_pep735_dependencies has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (7 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MSBuildHelper.CreateTempProjectAsync (cognitive 21) · ×1
  • MSBuildHelper.CreateTempProjectAsync (cognitive 21) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MSBuildHelper.cs:296 — MSBuildHelper.CreateTempProjectAsync has cognitive complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Program.MainCore (cognitive 21) · ×1
  • Program.MainCore (cognitive 21) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:77 — Program.MainCore has cognitive complexity 21 (threshold 15). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · vulnerability-auditor.extractBlockingDependencies (cognitive 21) · ×1
  • vulnerability-auditor.extractBlockingDependencies (cognitive 21) npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts:418 — vulnerability-auditor.extractBlockingDependencies has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 3 (6 pts), boolean chains 3, ternaries 1 (3 pts) (nesting depth added 11). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Program.RegisterExtensions (cognitive 20) · ×1
  • Program.RegisterExtensions (cognitive 20) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:345 — Program.RegisterExtensions has cognitive complexity 20 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · UpdateChecker.fetch_digest_of (cognitive 20) · ×1
  • UpdateChecker.fetch_digest_of (cognitive 20) docker/lib/dependabot/docker/update_checker.rb:823 — UpdateChecker.fetch_digest_of has cognitive complexity 20 (threshold 15). Drivers by points: error handling 5 (15 pts), if/else 2 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DiscoveryWorker.RunAsync (cognitive 19) · ×1
  • DiscoveryWorker.RunAsync (cognitive 19) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:71 — DiscoveryWorker.RunAsync has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PackageReferenceUpdater.ComputeUpdateOperations (cognitive 19) · ×1
  • PackageReferenceUpdater.ComputeUpdateOperations (cognitive 19) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackageReferenceUpdater.cs:23 — PackageReferenceUpdater.ComputeUpdateOperations has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MarkdownListBuilder.LinesFromObject (cognitive 19) · ×1
  • MarkdownListBuilder.LinesFromObject (cognitive 19) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/MarkdownListBuilder.cs:10 — MarkdownListBuilder.LinesFromObject has cognitive complexity 19 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ProjectFactory.AddFiles (cognitive 19) · ×1
  • ProjectFactory.AddFiles (cognitive 19) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:1192 — ProjectFactory.AddFiles has cognitive complexity 19 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · FileFetcher.inferred_npmrc (cognitive 19) · ×1
  • FileFetcher.inferred_npmrc (cognitive 19) npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:167 — FileFetcher.inferred_npmrc has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · PipenvVersionResolver.handle_pipenv_errors (cognitive 19) · ×1
  • PipenvVersionResolver.handle_pipenv_errors (cognitive 19) python/lib/dependabot/python/update_checker/pipenv_version_resolver.rb:106 — PipenvVersionResolver.handle_pipenv_errors has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · legacy-conflicting-dependency-parser.findConflictingParentDependencies (cognitive 19) · ×1
  • legacy-conflicting-dependency-parser.findConflictingParentDependencies (cognitive 19) npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts:118 — legacy-conflicting-dependency-parser.findConflictingParentDependencies has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · AnalyzeWorker.RunAsync (cognitive 18) · ×1
  • AnalyzeWorker.RunAsync (cognitive 18) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs:70 — AnalyzeWorker.RunAsync has cognitive complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DiscoveryWorker.RunForProjectPathsAsync (cognitive 18) · ×1
  • DiscoveryWorker.RunForProjectPathsAsync (cognitive 18) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs:427 — DiscoveryWorker.RunForProjectPathsAsync has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PathHelper.GetMatchingDirectoriesUnder (cognitive 18) · ×1
  • PathHelper.GetMatchingDirectoriesUnder (cognitive 18) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/PathHelper.cs:266 — PathHelper.GetMatchingDirectoriesUnder has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProjectFactory.AddProjectReferenceDependencies (cognitive 18) · ×1
  • ProjectFactory.AddProjectReferenceDependencies (cognitive 18) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:647 — ProjectFactory.AddProjectReferenceDependencies has cognitive complexity 18 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Base._clone_repo_contents (cognitive 18) · ×1
  • Base._clone_repo_contents (cognitive 18) common/lib/dependabot/file_fetchers/base.rb:916 — Base._clone_repo_contents has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 4, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LockfileUpdater.handle_composer_errors (cognitive 18) · ×1
  • LockfileUpdater.handle_composer_errors (cognitive 18) composer/lib/dependabot/composer/file_updater/lockfile_updater.rb:176 — LockfileUpdater.handle_composer_errors has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, boolean chains 7. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · TokenBucket.compare_token_pair (cognitive 18) · ×1
  • TokenBucket.compare_token_pair (cognitive 18) maven/lib/dependabot/maven/token_bucket.rb:56 — TokenBucket.compare_token_pair has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, if/else 6, ternaries 2 (4 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · PackageManagerHelper.setup (cognitive 18) · ×1
  • PackageManagerHelper.setup (cognitive 18) npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb:293 — PackageManagerHelper.setup has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · lockfile-parser.nameVerDevFromPkgSnapshot (cognitive 18) · ×1
  • lockfile-parser.nameVerDevFromPkgSnapshot (cognitive 18) npm_and_yarn/helpers/lib/pnpm/lockfile-parser.ts:113 — lockfile-parser.nameVerDevFromPkgSnapshot has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, loops 1 (2 pts), ternaries 1 (nesting depth added 3). Of this number, 11 points are the body's own statements and 7 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · JobErrorBase.ErrorFromException (cognitive 17) · ×1
  • JobErrorBase.ErrorFromException (cognitive 17) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/ApiModel/JobErrorBase.cs:34 — JobErrorBase.ErrorFromException has cognitive complexity 17 (threshold 15). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · RunWorker.GetUpdatedDependencyListFromDiscovery (cognitive 17) · ×1
  • RunWorker.GetUpdatedDependencyListFromDiscovery (cognitive 17) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs:274 — RunWorker.GetUpdatedDependencyListFromDiscovery has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ProjectFactory.FindDependency (cognitive 17) · ×1
  • ProjectFactory.FindDependency (cognitive 17) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:895 — ProjectFactory.FindDependency has cognitive complexity 17 (threshold 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SharedBundlerHelpers.handle_bundler_errors (cognitive 17) · ×1
  • SharedBundlerHelpers.handle_bundler_errors (cognitive 17) bundler/lib/dependabot/bundler/update_checker/shared_bundler_helpers.rb:121 — SharedBundlerHelpers.handle_bundler_errors has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 1, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MessageBuilder.version_commit_message_intro (cognitive 17) · ×1
  • MessageBuilder.version_commit_message_intro (cognitive 17) common/lib/dependabot/pull_request_creator/message_builder.rb:435 — MessageBuilder.version_commit_message_intro has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11, boolean chains 6. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · RefreshSecurityUpdatePullRequest.check_and_update_pull_request (cognitive 17) · ×1
  • RefreshSecurityUpdatePullRequest.check_and_update_pull_request (cognitive 17) updater/lib/dependabot/updater/operations/refresh_security_update_pull_request.rb:101 — RefreshSecurityUpdatePullRequest.check_and_update_pull_request has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 1, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · PipCompileVersionResolver.handle_pip_compile_errors (cognitive 17) · ×1
  • PipCompileVersionResolver.handle_pip_compile_errors (cognitive 17) uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:172 — PipCompileVersionResolver.handle_pip_compile_errors has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · conflicting-dependency-parser.findConflictingParentDependencies (cognitive 17) · ×1
  • conflicting-dependency-parser.findConflictingParentDependencies (cognitive 17) bun/helpers/lib/yarn/conflicting-dependency-parser.js:93 — conflicting-dependency-parser.findConflictingParentDependencies has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · VersionFinder.CreateVersionFilter (cognitive 16) · ×1
  • VersionFinder.CreateVersionFilter (cognitive 16) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/VersionFinder.cs:309 — VersionFinder.CreateVersionFilter has cognitive complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to one function literal inside it that branches (line 317). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · FileUpdater.original_buildfile_declarations (cognitive 16) · ×1
  • FileUpdater.original_buildfile_declarations (cognitive 16) gradle/lib/dependabot/gradle/file_updater.rb:256 — FileUpdater.original_buildfile_declarations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · GemInfrastructureUpdater.update_helpers_gemspecs (cognitive 16) · ×1
  • GemInfrastructureUpdater.update_helpers_gemspecs (cognitive 16) rakelib/support/infrastructure_updaters/gem_infrastructure_updater.rb:123 — GemInfrastructureUpdater.update_helpers_gemspecs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D3 · God Classes · FunctionTooLong · ×1
  • FunctionTooLong: vulnerability-auditor.findVulnerableDependencies npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts:116 — FunctionTooLong — findVulnerableDependencies runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (6 members, 5 shared lines) · ×1
  • Near-duplicate member family (6 members, 5 shared lines) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:31 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:31-179 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:178-315 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:318-432 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:50-228 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:30-205 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:30-195 — These 6 members are variants of one another: a block of 5 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Near-duplicate member pair (103 shared lines) · ×1
  • Near-duplicate member pair (103 shared lines) REDACTED:27 — REDACTED:27-171 | REDACTED:27-165 — These two members are variants of one another: 103 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 (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) bun/lib/dependabot/bun/update_checker/version_resolver.rb:89 — bun/lib/dependabot/bun/update_checker/version_resolver.rb:89-111 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/version_resolver.rb:146-172 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (12 corresponding lines) · ×1
  • Edited copy of a member (12 corresponding lines) bun/lib/dependabot/bun/package/registry_finder.rb:45 — bun/lib/dependabot/bun/package/registry_finder.rb:45-56 | npm_and_yarn/lib/dependabot/npm_and_yarn/package/registry_finder.rb:46-57 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (12 members, 50+ identical tokens) bun/lib/dependabot/bun/requirement.rb:32 — bun/lib/dependabot/bun/requirement.rb:32-42 | cargo/lib/dependabot/cargo/requirement.rb:31-40 | go_modules/lib/dependabot/go_modules/requirement.rb:35-44 | gradle/lib/dependabot/gradle/requirement.rb:34-43 | hex/lib/dependabot/hex/requirement.rb:60-69 | maven/lib/dependabot/maven/requirement.rb:34-43 | npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:42-52 | nuget/lib/dependabot/nuget/requirement.rb:19-28 | opentofu/lib/dependabot/opentofu/requirement.rb:24-33 | pub/lib/dependabot/pub/requirement.rb:34-43 | sbt/lib/dependabot/sbt/requirement.rb:36-45 | terraform/lib/dependabot/terraform/requirement.rb:25-34 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) updater/lib/dependabot/api_client.rb:94 — updater/lib/dependabot/api_client.rb:94-109 | updater/lib/dependabot/api_client.rb:114-136 | updater/lib/dependabot/api_client.rb:147-171 | updater/lib/dependabot/api_client.rb:176-200 | updater/lib/dependabot/api_client.rb:205-220 | updater/lib/dependabot/api_client.rb:225-244 | updater/lib/dependabot/api_client.rb:249-265 | updater/lib/dependabot/api_client.rb:270-284 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
D4 · Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (6 members, 50+ identical tokens) common/lib/dependabot/package/npm_package_json.rb:126 — common/lib/dependabot/package/npm_package_json.rb:126-135 | common/lib/dependabot/package/npm_package_manager_config.rb:49-58 | common/lib/dependabot/package/npm_registry_package.rb:163-172 | julia/lib/dependabot/julia/registry_client/result.rb:20-29 | python/lib/dependabot/python/file_parser/pyproject_document.rb:23-32 | uv/lib/dependabot/uv/file_updater/version_config_parser.rb:72-81 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication · Duplicated block (87 lines × 2) · ×1
  • Duplicated block (87 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:119 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:119-205 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:109-195 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 203 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:119` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (62 lines × 2) · ×1
  • Duplicated block (62 lines × 2) bun/lib/dependabot/bun/constraint_helper.rb:101 — bun/lib/dependabot/bun/constraint_helper.rb:101-162 | npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb:101-162 — before extracting anything, compare `bun/lib/dependabot/bun/constraint_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 138 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.
D4 · Code Duplication · Duplicated block (53 lines × 2) · ×1
  • Duplicated block (53 lines × 2) bun/lib/dependabot/bun/constraint_helper.rb:292 — bun/lib/dependabot/bun/constraint_helper.rb:292-344 | npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb:402-454 — before extracting anything, compare `bun/lib/dependabot/bun/constraint_helper.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 138 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 `bun/lib/dependabot/bun/constraint_helper.rb:292` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (46 lines × 2) · ×1
  • Duplicated block (46 lines × 2) bun/lib/dependabot/bun/file_fetcher.rb:234 — bun/lib/dependabot/bun/file_fetcher.rb:234-279 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:572-617 — before extracting anything, compare `bun/lib/dependabot/bun/file_fetcher.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 130 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.
D4 · Code Duplication · Duplicated block (39 lines × 2) · ×1
  • Duplicated block (39 lines × 2) bundler/helpers/v2/lib/functions/force_updater.rb:110 — bundler/helpers/v2/lib/functions/force_updater.rb:110-148 | bundler/helpers/v4/lib/functions/force_updater.rb:110-148 — before extracting anything, compare `bundler/helpers/v2/lib/functions/force_updater.rb` and `bundler/helpers/v4/lib/functions/force_updater.rb` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 115 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.
D4 · Code Duplication · Duplicated block (38 lines × 2) · ×1
  • Duplicated block (38 lines × 2) bundler/helpers/v2/lib/functions/lockfile_updater.rb:68 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:68-105 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:68-105 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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.
D4 · Code Duplication · Duplicated block (36–37 lines × 2) · ×1
  • Duplicated block (36–37 lines × 2) bun/lib/dependabot/bun/file_parser.rb:235 — bun/lib/dependabot/bun/file_parser.rb:235-270 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:310-346 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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 `bun/lib/dependabot/bun/file_parser.rb:235` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) bun/lib/dependabot/bun/file_updater/package_json_updater.rb:50 — bun/lib/dependabot/bun/file_updater/package_json_updater.rb:50-84 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb:47-81 — before extracting anything, compare `bun/lib/dependabot/bun/file_updater/package_json_updater.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/package_json_updater.rb` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 160 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.
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) bundler/helpers/v2/lib/functions/lockfile_updater.rb:34 — bundler/helpers/v2/lib/functions/lockfile_updater.rb:34-64 | bundler/helpers/v4/lib/functions/lockfile_updater.rb:34-64 — before extracting anything, compare `bundler/helpers/v2/lib/functions/lockfile_updater.rb` and `bundler/helpers/v4/lib/functions/lockfile_updater.rb` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 184 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.
D4 · Code Duplication · Duplicated block (25–30 lines × 2) · ×1
  • Duplicated block (25–30 lines × 2) updater/lib/dependabot/updater/operations/refresh_security_update_pull_request.rb:176 — updater/lib/dependabot/updater/operations/refresh_security_update_pull_request.rb:176-200 | updater/lib/dependabot/updater/operations/refresh_version_update_pull_request.rb:169-198 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (24–29 lines × 2) · ×1
  • Duplicated block (24–29 lines × 2) REDACTED:291 — REDACTED:291-314 | REDACTED:201-229 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 215 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:291` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (27–28 lines × 2) · ×1
  • Duplicated block (27–28 lines × 2) updater/lib/dependabot/update_files_command.rb:120 — updater/lib/dependabot/update_files_command.rb:120-147 | updater/lib/dependabot/update_graph_command.rb:75-101 — 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 `updater/lib/dependabot/update_files_command.rb:120` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) bundler/helpers/v2/lib/functions/version_resolver.rb:56 — bundler/helpers/v2/lib/functions/version_resolver.rb:56-82 | bundler/helpers/v4/lib/functions/version_resolver.rb:56-82 — before extracting anything, compare `bundler/helpers/v2/lib/functions/version_resolver.rb` and `bundler/helpers/v4/lib/functions/version_resolver.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 63 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.
D4 · Code Duplication · Duplicated block (26–27 lines × 2) · ×1
  • Duplicated block (26–27 lines × 2) python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:194 — python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:194-220 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:187-212 — before extracting anything, compare `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` and `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 186 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:213` calls `handle_git_credentials_error` and `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:222` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (22–23 lines × 2) · ×1
  • Duplicated block (22–23 lines × 2) bun/lib/dependabot/bun/update_checker.rb:282 — bun/lib/dependabot/bun/update_checker.rb:282-303 | npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb:322-344 — before extracting anything, compare `bun/lib/dependabot/bun/update_checker.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 216 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 `bun/lib/dependabot/bun/update_checker.rb:282` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (17–21 lines × 2) · ×1
  • Duplicated block (17–21 lines × 2) python/lib/dependabot/python/metadata_finder.rb:133 — python/lib/dependabot/python/metadata_finder.rb:133-153 | python/lib/dependabot/python/metadata_finder.rb:173-189 — 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 `python/lib/dependabot/python/metadata_finder.rb:133` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (18–19 lines × 3) · ×1
  • Duplicated block (18–19 lines × 3) bun/lib/dependabot/bun/requirement.rb:133 — bun/lib/dependabot/bun/requirement.rb:133-151 | helm/lib/dependabot/helm/requirement.rb:200-217 | npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:186-204 — before extracting anything, compare `bun/lib/dependabot/bun/requirement.rb` and `helm/lib/dependabot/helm/requirement.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (11–19 lines × 2) · ×1
  • Duplicated block (11–19 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:189 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:189-199 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:200-218 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:189` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (17–19 lines × 2) · ×1
  • Duplicated block (17–19 lines × 2) bun/lib/dependabot/bun/dependency_grapher.rb:54 — bun/lib/dependabot/bun/dependency_grapher.rb:54-70 | python/lib/dependabot/python/dependency_grapher.rb:221-239 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1
  • Duplicated block (18–19 lines × 2) updater/lib/dependabot/api_client.rb:114 — updater/lib/dependabot/api_client.rb:114-131 | updater/lib/dependabot/api_client.rb:177-195 — 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 `updater/lib/dependabot/api_client.rb:114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:110 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:110-124 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:130-144 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:111-125 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:101-115 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 64 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:110` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:109` calls `RecordUpdateJobError`, `SecurityUpdateNotFound` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:129` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:287 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:287-302 | python/lib/dependabot/python/file_updater/pipfile_file_updater.rb:281-296 | python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:355-370 | python/lib/dependabot/python/update_checker/pipenv_version_resolver.rb:265-280 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
D4 · Code Duplication · Duplicated block (12 lines × 5) · ×1
  • Duplicated block (12 lines × 5) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:35 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:35-46 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:71-82 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:321-332 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:86-97 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:34-45 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:35` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:33` calls `ToHashSet` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:319` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–13 lines × 4) · ×1
  • Duplicated block (12–13 lines × 4) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:776 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:776-788 | python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb:506-517 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:638-649 | uv/lib/dependabot/uv/update_checker/pip_compile_version_resolver.rb:523-534 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `python/lib/dependabot/python/update_checker/pip_compile_version_resolver.rb` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) conda/lib/dependabot/conda.rb:22 — conda/lib/dependabot/conda.rb:22-34 | python/lib/dependabot/python.rb:21-34 | uv/lib/dependabot/uv.rb:34-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `conda/lib/dependabot/conda.rb:22` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:245 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:245-256 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:146-155 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:245` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:145` calls `Info` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:244` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11 lines × 5) · ×1
  • Duplicated block (11 lines × 5) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:98 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:98-108 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:357-367 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:119-129 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:100-110 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:90-100 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:98` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:109` calls `RecordUpdateJobError`, `SecurityUpdateNotFound` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:368` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9–11 lines × 2) · ×1
  • Duplicated block (9–11 lines × 2) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:280 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:280-290 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:407-415 — 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:280` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (8–11 lines × 2) · ×1
  • Duplicated block (8–11 lines × 2) maven/lib/dependabot/maven/file_updater.rb:135 — maven/lib/dependabot/maven/file_updater.rb:135-145 | sbt/lib/dependabot/sbt/file_updater.rb:54-61 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:348 — python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:348-358 | uv/lib/dependabot/uv/file_updater/compile_file_updater.rb:308-317 — before extracting anything, compare `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb` and `uv/lib/dependabot/uv/file_updater/compile_file_updater.rb` as WHOLE FILES: this scan already matched 17 separate duplicated blocks between them, totalling at least 240 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 `python/lib/dependabot/python/file_updater/pip_compile_file_updater.rb:348` 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.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) common/lib/dependabot/package/npm_package_json.rb:126 — common/lib/dependabot/package/npm_package_json.rb:126-135 | common/lib/dependabot/package/npm_package_manager_config.rb:49-58 | common/lib/dependabot/package/npm_registry_package.rb:163-172 | julia/lib/dependabot/julia/registry_client/result.rb:20-29 | python/lib/dependabot/python/file_parser/pyproject_document.rb:23-32 | uv/lib/dependabot/uv/file_updater/version_config_parser.rb:72-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×1
  • Duplicated block (9–10 lines × 3) bun/lib/dependabot/bun/requirement.rb:78 — bun/lib/dependabot/bun/requirement.rb:78-87 | helm/lib/dependabot/helm/requirement.rb:105-113 | npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:131-140 — before extracting anything, compare `bun/lib/dependabot/bun/requirement.rb` and `helm/lib/dependabot/helm/requirement.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:125` calls `strip_jsr_prefix` and `bun/lib/dependabot/bun/requirement.rb:73` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–10 lines × 2) · ×1
  • Duplicated block (8–10 lines × 2) common/lib/dependabot/git_commit_checker.rb:772 — common/lib/dependabot/git_commit_checker.rb:772-781 | common/lib/dependabot/git_cooldown_date_resolver.rb:103-110 — 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 `common/lib/dependabot/git_commit_checker.rb:772` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (9 lines × 8) · ×1
  • Duplicated block (9 lines × 8) updater/lib/dependabot/api_client.rb:101 — updater/lib/dependabot/api_client.rb:101-109 | updater/lib/dependabot/api_client.rb:128-136 | updater/lib/dependabot/api_client.rb:163-171 | updater/lib/dependabot/api_client.rb:192-200 | updater/lib/dependabot/api_client.rb:212-220 | updater/lib/dependabot/api_client.rb:236-244 | updater/lib/dependabot/api_client.rb:257-265 | updater/lib/dependabot/api_client.rb:276-284 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1
  • Duplicated block (8–9 lines × 2) python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:89 — python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:89-96 | python/lib/dependabot/python/file_parser/setup_file_parser.rb:55-63 — 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 `python/lib/dependabot/python/file_parser/pyproject_files_parser.rb:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 12) · ×1
  • Duplicated block (6 lines × 12) bun/lib/dependabot/bun/requirement.rb:35 — bun/lib/dependabot/bun/requirement.rb:35-40 | cargo/lib/dependabot/cargo/requirement.rb:33-38 | go_modules/lib/dependabot/go_modules/requirement.rb:37-42 | gradle/lib/dependabot/gradle/requirement.rb:36-41 | hex/lib/dependabot/hex/requirement.rb:62-67 | maven/lib/dependabot/maven/requirement.rb:36-41 | npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb:45-50 | nuget/lib/dependabot/nuget/requirement.rb:21-26 | opentofu/lib/dependabot/opentofu/requirement.rb:26-31 | pub/lib/dependabot/pub/requirement.rb:36-41 | sbt/lib/dependabot/sbt/requirement.rb:38-43 | terraform/lib/dependabot/terraform/requirement.rb:27-32 — before extracting anything, compare `bun/lib/dependabot/bun/requirement.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/requirement.rb` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (6 lines × 6) · ×1
  • Duplicated block (6 lines × 6) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:248 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:248-253 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:353-358 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:377-382 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:519-524 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:541-546 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:590-595 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×1
  • Duplicated block (6 lines × 5) nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:114 — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:114-119 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:234-239 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshGroupUpdatePullRequestHandler.cs:134-139 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshSecurityUpdatePullRequestHandler.cs:115-120 | nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/RefreshVersionUpdatePullRequestHandler.cs:105-110 — before extracting anything, compare `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 46 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 `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:114` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/CreateSecurityUpdatePullRequestHandler.cs:113` calls `Info` and `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs:232` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×1
  • Duplicated block (5 lines × 5) bundler/lib/dependabot/bundler/file_parser.rb:333 — bundler/lib/dependabot/bundler/file_parser.rb:333-337 | bundler/lib/dependabot/bundler/file_parser/file_preparer.rb:56-60 | bundler/lib/dependabot/bundler/file_updater.rb:132-136 | bundler/lib/dependabot/bundler/file_updater/lockfile_updater.rb:415-419 | bundler/lib/dependabot/bundler/update_checker/file_preparer.rb:166-170 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
D4 · Code Duplication · Duplicated block (5 lines × 15) · ×1
  • Duplicated block (5 lines × 15) bazel/lib/dependabot/bazel.rb:18 — bazel/lib/dependabot/bazel.rb:18-22 | cargo/lib/dependabot/cargo.rb:15-19 | deno/lib/dependabot/deno.rb:17-24 | devcontainers/lib/dependabot/devcontainers.rb:15-20 | docker/lib/dependabot/docker.rb:15-19 | dotnet_sdk/lib/dependabot/dotnet_sdk.rb:15-20 | elm/lib/dependabot/elm.rb:17-21 | git_submodules/lib/dependabot/git_submodules.rb:15-20 | go_modules/lib/dependabot/go_modules.rb:16-21 | nix/lib/dependabot/nix.rb:15-20 | pub/lib/dependabot/pub.rb:15-19 | rust_toolchain/lib/dependabot/rust_toolchain.rb:13-18 | sbt/lib/dependabot/sbt.rb:15-19 | swift/lib/dependabot/swift.rb:15-20 | vcpkg/lib/dependabot/vcpkg.rb:19-76 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 15 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 15 times. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (18 lines × 6) · ×1
  • Duplicated block (18 lines × 6) bun/lib/dependabot/bun/bun_package_manager.rb:32 — bun/lib/dependabot/bun/bun_package_manager.rb:32-49 | bun/lib/dependabot/bun/language.rb:25-42 | bun/lib/dependabot/bun/pnpm_package_manager.rb:38-55 | npm_and_yarn/lib/dependabot/npm_and_yarn/language.rb:25-42 | npm_and_yarn/lib/dependabot/npm_and_yarn/pnpm_package_manager.rb:49-66 | npm_and_yarn/lib/dependabot/npm_and_yarn/yarn_package_manager.rb:46-63 — before extracting anything, compare `bun/lib/dependabot/bun/language.rb` and `bun/lib/dependabot/bun/pnpm_package_manager.rb` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (73 lines × 2) · ×1
  • Duplicated block (73 lines × 2) bundler/helpers/v2/lib/functions/dependency_source.rb:15 — bundler/helpers/v2/lib/functions/dependency_source.rb:15-87 | bundler/helpers/v4/lib/functions/dependency_source.rb:15-87 — before extracting anything, compare `bundler/helpers/v2/lib/functions/dependency_source.rb` and `bundler/helpers/v4/lib/functions/dependency_source.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. 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.
D4 · Code Duplication · Duplicated block (8 lines × 11) · ×1
  • Duplicated block (8 lines × 11) bazel/lib/dependabot/bazel/file_parser.rb:56 — bazel/lib/dependabot/bazel/file_parser.rb:56-63 | bundler/lib/dependabot/bundler/file_parser.rb:42-49 | composer/lib/dependabot/composer/file_parser.rb:51-58 | elm/lib/dependabot/elm/file_parser.rb:34-41 | gradle/lib/dependabot/gradle/file_parser.rb:239-246 | maven/lib/dependabot/maven/file_parser.rb:58-65 | pub/lib/dependabot/pub/file_parser.rb:33-40 | python/lib/dependabot/python/file_parser.rb:74-81 | sbt/lib/dependabot/sbt/file_parser.rb:85-92 | uv/lib/dependabot/uv/file_parser.rb:66-73 | vcpkg/lib/dependabot/vcpkg/file_parser.rb:36-43 — before extracting anything, compare `python/lib/dependabot/python/file_parser.rb` and `uv/lib/dependabot/uv/file_parser.rb` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 41 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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×1
  • Duplicated block (8 lines × 4) common/lib/dependabot/file_fetchers/base.rb:463 — common/lib/dependabot/file_fetchers/base.rb:463-470 | common/lib/dependabot/pull_request_creator/azure.rb:122-129 | common/lib/dependabot/pull_request_creator/pr_name_prefixer.rb:632-639 | common/lib/dependabot/pull_request_updater/azure.rb:80-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
D4 · Code Duplication · Duplicated block (6 lines × 9) · ×1
  • Duplicated block (6 lines × 9) bun/lib/dependabot/bun/file_parser.rb:147 — bun/lib/dependabot/bun/file_parser.rb:147-152 | bun/lib/dependabot/bun/file_parser.rb:157-162 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:167-172 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:177-182 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:187-192 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:197-202 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:207-212 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:217-222 | npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb:227-232 — before extracting anything, compare `bun/lib/dependabot/bun/file_parser.rb` and `npm_and_yarn/lib/dependabot/npm_and_yarn/file_parser.rb` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 161 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.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×1
  • Duplicated block (5 lines × 4) common/lib/dependabot/file_fetchers/base.rb:642 — common/lib/dependabot/file_fetchers/base.rb:642-646 | common/lib/dependabot/file_fetchers/base.rb:651-655 | common/lib/dependabot/pull_request_creator/pr_name_prefixer.rb:562-566 | common/lib/dependabot/pull_request_creator/pr_name_prefixer.rb:571-575 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. 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.
D4 · Code Duplication · Duplicated block (14 lines × 6) · ×1
  • Duplicated block (14 lines × 6) pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb:79 — pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb:79-92 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/go.rb:83-96 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb:80-93 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/python.rb:87-100 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/ruby.rb:80-93 | pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/rust.rb:81-94 — before extracting anything, compare `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/dart.rb` and `pre_commit/lib/dependabot/pre_commit/additional_dependency_checkers/node.rb` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 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.
D4 · Code Duplication · Duplicated block (126 lines × 2) · ×1
  • Duplicated block (126 lines × 2) REDACTED:227 — REDACTED:227-352 | REDACTED:221-346 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 278 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.
D4 · Code Duplication · Duplicated block (76–77 lines × 2) · ×1
  • Duplicated block (76–77 lines × 2) REDACTED:59 — REDACTED:59-135 | REDACTED:35-110 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 278 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:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (48 lines × 2) · ×1
  • Duplicated block (48 lines × 2) REDACTED:176 — REDACTED:176-223 | REDACTED:170-217 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 278 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.
D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) composer/helpers/v2/src/UpdateChecker.php:42 — composer/helpers/v2/src/UpdateChecker.php:42-66 | composer/helpers/v2/src/Updater.php:56-81 — 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 `composer/helpers/v2/src/UpdateChecker.php:42` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `composer/helpers/v2/src/Updater.php:82` calls `setWriteLock` and `composer/helpers/v2/src/UpdateChecker.php:67` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D44 · Platform End-of-Life · End-of-life framework · ×1
  • End-of-life framework: Rails 5 bundler/spec/fixtures/projects/bundler2/transitive_blocking/Gemfile:1 — bundler/spec/fixtures/projects/bundler2/transitive_blocking/Gemfile depends on `rails` at a version that pins Rails 5, and Rails 5, support ended 2022-06-01. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
D5 · Coupling · Unstable project dependabot-pre_commit · ×1
  • Unstable project dependabot-pre_commit — dependabot-pre_commit has instability 0.86 with 1 dependents.
D5 · Coupling · Off the main sequence · ×1
  • Off the main sequence: dependabot-python — dependabot-python: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — .NET suite — Coverage NOT MEASURED: the .NET half could not be measured — the repository wires up no coverage collector for `--collect:"XPlat Code Coverage"` to use; the JavaScript/TypeScript half measured 89.9% (jest via `npm ci --ignore-scripts` in bun/helpers/; jest via `npm ci --ignore-scripts` in npm_and_yarn/helpers/; jest in npm_and_yarn/spec/fixtures/projects/grapher/npm_no_lockfile/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm5/subdependency_update/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm5_and_yarn/npm_subdependency_update/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm6/subdependency_update/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm6_and_yarn/npm_subdependency_update/: not run; jest in npm_and_yarn/spec/fixtures/projects/npm8/app_no_version/: not run). This repository's production source spans both ecosystems, and no partial figure is published as if it were the whole: coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
M1 · Documentation (README) · README may be stale · ×1
  • README may be stale — 830 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 32 typed · 29 plain JS — the untyped files are bun/helpers/lib/npm/conflicting-dependency-parser.js, bun/helpers/lib/npm/index.js, bun/helpers/lib/npm/vulnerability-auditor.js, bun/helpers/lib/npm6/helpers.js, bun/helpers/lib/npm6/index.js, bun/helpers/lib/npm6/peer-dependency-checker.js (+23 more).
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (18 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (18 clone groups) bun/helpers/lib/yarn/conflicting-dependency-parser.js:34 — 18 of the duplicated blocks reported below have copies in at least two of the sibling directories bun, npm_and_yarn under the repository root. That concentration is one structural fact, not 18 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 18 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (101 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (101 matched lines × 2 locations) bun/helpers/lib/yarn/conflicting-dependency-parser.js:34 — bun/helpers/lib/yarn/conflicting-dependency-parser.js:34 · npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts:59 — the two spans are one implementation copied and then locally edited — 446 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (58 lines × 2 locations) · ×1
  • Duplicated block (58 lines × 2 locations) bun/helpers/lib/yarn/updater.js:129 — bun/helpers/lib/yarn/updater.js:129 · npm_and_yarn/helpers/lib/yarn/updater.ts:148 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (38 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (38 matched lines × 2 locations) bun/helpers/lib/yarn/subdependency-updater.js:29 — bun/helpers/lib/yarn/subdependency-updater.js:29 · npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:44 — the two spans are one implementation copied and then locally edited — 238 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) bun/helpers/lib/npm6/subdependency-updater.js:16 — bun/helpers/lib/npm6/subdependency-updater.js:16 · npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (30 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (30 matched lines × 2 locations) bun/helpers/lib/pnpm/lockfile-parser.js:27 — bun/helpers/lib/pnpm/lockfile-parser.js:27 · npm_and_yarn/helpers/lib/pnpm/lockfile-parser.ts:120 — the two spans are one implementation copied and then locally edited — 178 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) bun/helpers/lib/yarn/fix-duplicates.js:36 — bun/helpers/lib/yarn/fix-duplicates.js:36 · npm_and_yarn/helpers/lib/yarn/fix-duplicates.ts:55 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (24 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (24 matched lines × 2 locations) bun/helpers/run.js:5 — bun/helpers/run.js:5 · npm_and_yarn/helpers/run.ts:14 — the two spans are one implementation copied and then locally edited — 178 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (19 matched lines × 2 locations) bun/helpers/lib/npm6/helpers.js:1 — bun/helpers/lib/npm6/helpers.js:1 · npm_and_yarn/helpers/lib/npm6/helpers.ts:6 — the two spans are one implementation copied and then locally edited — 93 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) bun/helpers/lib/yarn/peer-dependency-checker.js:89 — bun/helpers/lib/yarn/peer-dependency-checker.js:89 · npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts:107 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (15 matched lines × 2 locations) REDACTED:122 — REDACTED:122 · npm_and_yarn/helpers/lib/yarn/updater.ts:81 — the two spans are one implementation copied and then locally edited — 59 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1
  • Duplicated block (15 lines × 2 locations) bun/helpers/lib/yarn/updater.js:109 — bun/helpers/lib/yarn/updater.js:109 · npm_and_yarn/helpers/lib/yarn/updater.ts:128 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) bun/helpers/lib/yarn/replace-lockfile-declaration.js:36 — bun/helpers/lib/yarn/replace-lockfile-declaration.js:36 · npm_and_yarn/helpers/lib/yarn/replace-lockfile-declaration.ts:43 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×1
  • Duplicated block (12 lines × 2 locations) npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:20 — npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:20 · npm_and_yarn/helpers/lib/yarn/updater.ts:46 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×1
  • Duplicated block (9 lines × 2 locations) npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:15 — npm_and_yarn/helpers/lib/npm6/subdependency-updater.ts:15 · npm_and_yarn/helpers/lib/yarn/subdependency-updater.ts:39 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication · Duplicated block (5 lines × 2 locations) · ×1
  • Duplicated block (5 lines × 2 locations) bun/helpers/lib/npm/conflicting-dependency-parser.js:23 — bun/helpers/lib/npm/conflicting-dependency-parser.js:23 · npm_and_yarn/helpers/lib/npm/conflicting-dependency-parser.ts:34 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R2 · Cyclomatic Complexity · Complex function findConflictingParentDependencies (cyclomatic 12, cognitive 19) · ×1
  • Complex function findConflictingParentDependencies (cyclomatic 12, cognitive 19) npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts:118 — findConflictingParentDependencies has cyclomatic complexity 12 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function nameVerDevFromPkgSnapshot (cyclomatic 12, cognitive 15) · ×1
  • Complex function nameVerDevFromPkgSnapshot (cyclomatic 12, cognitive 15) npm_and_yarn/helpers/lib/pnpm/lockfile-parser.ts:113 — nameVerDevFromPkgSnapshot has cyclomatic complexity 12 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function findConflictingParentDependencies (cyclomatic 11, cognitive 17) · ×1
  • Complex function findConflictingParentDependencies (cyclomatic 11, cognitive 17) bun/helpers/lib/yarn/conflicting-dependency-parser.js:93 — findConflictingParentDependencies has cyclomatic complexity 11 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function findConflictingParentDependencies (cyclomatic 11, cognitive 15) · ×1
  • Complex function findConflictingParentDependencies (cyclomatic 11, cognitive 15) REDACTED:303 — findConflictingParentDependencies has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts · ×1
  • npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts: 568 lines of code npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts:1 — npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
X1 · Async correctness · Sync-over-async (deadlock risk) through `.Result` · ×1
  • Sync-over-async (deadlock risk) through `.Result` nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:951 — Reading `.Result` of a task that has not completed blocks this thread until it does — the same block as `.Wait()`: under a synchronization context (Blazor, a UI thread, classic ASP.NET) it deadlocks, and on the thread pool it parks a thread for as long as the work runs. `await` the task instead (make the caller `async`); where a synchronous entry point must stay, keep the block in ONE documented bridge with a timeout.
X18 · Disposal-pattern correctness · Disposes a dependency it does not own · ×1
  • Disposes a dependency it does not own nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/DetailedPullRequestBodyGenerator.cs:25 — `_httpFetcher` is never created by `DetailedPullRequestBodyGenerator` — every assignment to it takes a constructor parameter — yet this type disposes it here (line 25). Its declared type `IHttpFetcher` is an interface, so the instance came from whoever resolved it, and that owner decides when it ends. Disposing it from here reaches outside this object's lifetime: a dependency shared with the rest of the process is torn down when THIS instance goes away, and the real owner's later `Dispose()` runs a second time on an object already disposed. Drop the call — a type disposes what it constructed, and only that. If this dependency genuinely is exclusive to this instance, construct it here (or take an owned factory) so the ownership is stated in the code rather than assumed.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Program.cs:304 — `catch (BadImageFormatException)` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
X5 · Nullable reference types · Symbol treated as nullable, then dereferenced unguarded · ×1
  • Symbol treated as nullable, then dereferenced unguarded nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:139 — This method contradicts itself about `console`: line 134 assigns it with `as IConsole`, which hands back null rather than throwing when the value is not a `IConsole`, but line 139 then dereferences it directly as `console.Verbosity` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `console` once before the first use and handle the null case, or cast with `(IConsole)` so the failure is reported where it happens — rather than leaving the two readings side by side.
Minor — 105 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate bun/helpers/lib/yarn/peer-dependency-checker.js:39 — `groups.indexOf("devDependencies") > -1 && groups.indexOf("dependencies") == -1` appears character-identically in 4 files — bun/helpers/lib/yarn/peer-dependency-checker.js, bun/helpers/lib/yarn/updater.js, npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts, npm_and_yarn/helpers/lib/yarn/updater.ts. 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 bun/helpers/lib/yarn/peer-dependency-checker.js:47 — `groups.indexOf("optionalDependencies") > -1 && groups.indexOf("dependencies") == -1` appears character-identically in 4 files — bun/helpers/lib/yarn/peer-dependency-checker.js, bun/helpers/lib/yarn/updater.js, npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts, npm_and_yarn/helpers/lib/yarn/updater.ts. 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 bun/helpers/lib/yarn/peer-dependency-checker.js:124 — `isString(data) && data.match(/(unmet|incorrect) peer dependency/)` appears character-identically in 2 files — bun/helpers/lib/yarn/peer-dependency-checker.js, npm_and_yarn/helpers/lib/yarn/peer-dependency-checker.ts. 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 bun/helpers/lib/npm/vulnerability-auditor.js:228 — `key == "registry" || key.endsWith(":registry")` appears character-identically in 2 files — bun/helpers/lib/npm/vulnerability-auditor.js, npm_and_yarn/helpers/lib/npm/vulnerability-auditor.ts. 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 bun/helpers/lib/yarn/conflicting-dependency-parser.js:65 — `parentSpec.name === parentSpec.topLevelSpec.name && parentSpec.version === parentSpec.topLevelSpec.version` appears character-identically in 2 files — bun/helpers/lib/yarn/conflicting-dependency-parser.js, npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts. 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 bun/helpers/lib/yarn/conflicting-dependency-parser.js:74 — `parentSpec.transitiveSpec.name === parentSpec.topLevelSpec.name && parentSpec.transitiveSpec.version === parentSpec.topLevelSpec.version` appears character-identically in 2 files — bun/helpers/lib/yarn/conflicting-dependency-parser.js, npm_and_yarn/helpers/lib/yarn/legacy-conflicting-dependency-parser.ts. 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 bun/helpers/lib/pnpm/lockfile-parser.js:58 — `projectSnapshot.dependencies?.[name] || projectSnapshot.devDependencies?.[name] || projectSnapshot.optionalDependencies?.[name]` appears character-identically in 2 files — bun/helpers/lib/pnpm/lockfile-parser.js, npm_and_yarn/helpers/lib/pnpm/lockfile-parser.ts. 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 bun/helpers/lib/yarn/fix-duplicates.js:48 — `updatedPackageEntry[0] && updatedPackageEntry[0][1]` appears character-identically in 2 files — bun/helpers/lib/yarn/fix-duplicates.js, npm_and_yarn/helpers/lib/yarn/fix-duplicates.ts. 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 nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/AzurePackageDetailFinder.cs:10 — `oldTag is not null && newTag is not null` appears character-identically in 3 files — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/AzurePackageDetailFinder.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitLabPackageDetailFinder.cs. 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 nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:82 — `packageScopedVersion is null && IPackageDetailFinder.HasPackageScopedVersionForOtherDependency(releaseName, tagName, dependencyName)` appears character-identically in 2 files — nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitLabPackageDetailFinder.cs. 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 REDACTED:199 — `install_req.link is not None and install_req.link.is_file` appears character-identically in 2 files — REDACTED, REDACTED. 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 REDACTED:114 — `isinstance(entry, dict) and "include-group" in entry` appears character-identically in 2 files — REDACTED, REDACTED. 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 bundler/lib/dependabot/bundler/file_fetcher.rb:272 — `!@exclude_paths.empty? && Dependabot::FileFiltering.exclude_path?(path, @exclude_paths)` appears character-identically in 2 files — bundler/lib/dependabot/bundler/file_fetcher.rb, python/lib/dependabot/python/shared_file_fetcher.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate bun/lib/dependabot/bun/update_checker.rb:215 — `!audit.fix_available && audit.explanation` appears character-identically in 2 files — bun/lib/dependabot/bun/update_checker.rb, npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate bun/lib/dependabot/bun/update_checker.rb:136 — `!dependency.top_level? && conflicting_dependencies.any?` appears character-identically in 2 files — bun/lib/dependabot/bun/update_checker.rb, npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate opentofu/lib/dependabot/opentofu/file_filter.rb:15 — `!lockfile?(file_name) && file_name.end_with?(".hcl")` appears character-identically in 2 files — opentofu/lib/dependabot/opentofu/file_filter.rb, terraform/lib/dependabot/terraform/file_filter.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate bun/lib/dependabot/bun/package_manager.rb:146 — `@engines && @manifest_package_manager.nil?` appears character-identically in 2 files — bun/lib/dependabot/bun/package_manager.rb, npm_and_yarn/lib/dependabot/npm_and_yarn/package_manager.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate bun/lib/dependabot/bun/update_checker/latest_version_finder.rb:184 — `@raise_on_ignored && filter_lower_releases(filtered).empty? && filter_lower_releases(releases).any?` appears character-identically in 2 files — bun/lib/dependabot/bun/update_checker/latest_version_finder.rb, npm_and_yarn/lib/dependabot/npm_and_yarn/update_checker/latest_version_finder.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb:553 — `@release_age_days && (@release_age_days * Helpers::MINUTES_PER_DAY)` appears character-identically in 2 files — npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/pnpm_lockfile_updater.rb, npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/yarn_lockfile_updater.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:330 — `@retrying_lock && e.message.match?(MODULE_NOT_INSTALLED_ERROR)` appears character-identically in 2 files — REDACTED, REDACTED. 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 bun/lib/dependabot/bun/file_updater/npmrc_builder.rb:185 — `Base64.decode64(token).ascii_only? && Base64.decode64(token).include?(":")` appears character-identically in 7 files — bun/lib/dependabot/bun/file_updater/npmrc_builder.rb, bun/lib/dependabot/bun/package/registry_finder.rb, common/lib/dependabot/clients/azure.rb, npm_and_yarn/lib/dependabot/npm_and_yarn/file_updater/npmrc_builder.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate bundler/helpers/v2/monkey_patches/git_source_patch.rb:23 — `Bundler.settings[remote.to_s] || Bundler.settings[remote.host]` appears character-identically in 2 files — bundler/helpers/v2/monkey_patches/git_source_patch.rb, bundler/helpers/v4/monkey_patches/git_source_patch.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate bun/lib/dependabot/bun/constraint_helper.rb:306 — `Regexp.last_match && Regexp.last_match(1)` appears character-identically in 2 files — bun/lib/dependabot/bun/constraint_helper.rb, npm_and_yarn/lib/dependabot/npm_and_yarn/constraint_helper.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate swift/lib/dependabot/swift/file_parser.rb:120 — `XcodeFileHelpers.xcode_resolved_path?(f.name) && !f.support_file?` appears character-identically in 3 files — swift/lib/dependabot/swift/file_parser.rb, swift/lib/dependabot/swift/file_updater.rb, swift/lib/dependabot/swift/update_checker.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate bundler/helpers/v2/lib/functions/version_resolver.rb:71 — `attempt > 3 || !e.message.include?("Network error")` appears character-identically in 2 files — bundler/helpers/v2/lib/functions/version_resolver.rb, bundler/helpers/v4/lib/functions/version_resolver.rb. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D24 · Comment Value · redundant comment · ×21
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:126 — "Get the target framework of the project" repeats the code it sits on: 4 of its 4 words (get, target, framework, project) are already in `string targetFrameworkMoniker = _project.GetPropertyValue("TargetFrameworkMoniker");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:306 — "Add output files" repeats the code it sits on: 3 of its 3 words (add, output, files) are already in `ApplyAction(p => p.AddOutputFiles(builder));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:859 — "Add the transform file to the package builder" repeats the code it sits on: 4 of its 5 words (transform, file, package, builder) are already in `ProcessTransformFiles(builder, packages.SelectMany(GetTransformFiles));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/UpdateCommand.cs:427 — "Get the full path to the packages directory" repeats the code it sits on: 4 of its 5 words (get, full, path, packages) are already in `packagesDir = Path.GetFullPath(packagesDir);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Discover/EntryPointFinderTests.cs:15 — "a .sln referencing a .csproj creates a child-to-parent mapping" repeats the code it sits on: 6 of its 7 words (sln, referencing, csproj, creates, child, parent) are already in `using var temp = await TemporaryDirectory.CreateWithContentsAsync(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Run/ModifiedFilesTrackerTests.cs:112 — "Create tracker with initial files" repeats the code it sits on: 4 of its 4 words (create, tracker, initial, files) are already in `var tracker = new ModifiedFilesTracker(repoContentsPath, initialFiles, logger, new TestEOLMetadataProvider([]));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/Run/ModifiedFilesTrackerTests.cs:225 — "Create tracker with initial files" repeats the code it sits on: 4 of its 4 words (create, tracker, initial, files) are already in `var tracker = new ModifiedFilesTracker(repoContentsPath, initialFiles, logger, new TestEOLMetadataProvider([]));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core.Test/TestHttpServer.cs:206 — "FindPackagesById" repeats the code it sits on: 3 of its 3 words (find, packages, id) are already in `if (uri.AbsolutePath.TrimEnd('/').Equals("/FindPackagesById()", StringComparison.OrdinalIgnoreCase) ||`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/PackagesConfigDiscovery.cs:29 — "generate `$(TargetFramework)` via MSBuild" repeats the code it sits on: 4 of its 5 words (target, framework, ms, build) are already in `var tfms = await MSBuildHelper.GetTargetFrameworkValuesFromProject(repoRootPath, projectPath, logger);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Graph/GraphWorker.cs:50 — "Check for discovery errors" repeats the code it sits on: 3 of its 3 words (check, discovery, errors) are already in `if (discoveryResult.Error is not null)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:61 — "get release name" repeats the code it sits on: 3 of its 3 words (get, release, name) are already in `if (!releaseObject.TryGetProperty("name", out var releasenameElement) ||`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitHubPackageDetailFinder.cs:70 — "get tag name" repeats the code it sits on: 3 of its 3 words (get, tag, name) are already in `if (!releaseObject.TryGetProperty("tag_name", out var tagNameElement) ||`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/GitLabPackageDetailFinder.cs:61 — "get release name" repeats the code it sits on: 3 of its 3 words (get, release, name) are already in `if (!responseObject.TryGetProperty("name", out var releaseNameElement) ||`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/RunWorker.cs:147 — "<dependency name, <file path, specific dependencies>>" repeats the code it sits on: 5 of its 6 words (dependency, name, file, path, dependencies) are already in `void CollectDependenciesForFile(string filePath, IEnumerable<Dependency> dependencies)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/BindingRedirectManager.cs:90 — "Check for HintPath as a child element" repeats the code it sits on: 4 of its 5 words (check, hint, path, element) are already in `var hintPathElement = element.Elements.FirstOrDefault(static x => x.Name == "HintPath");`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/BindingRedirectManager.cs:157 — "Get the configuration file" repeats the code it sits on: 3 of its 3 words (get, configuration, file) are already in `var document = GetConfiguration(configFile.Content, configFile.Path);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/BindingRedirectManager.cs:201 — "Get an assembly binding element to use" repeats the code it sits on: 4 of its 5 words (get, assembly, binding, element) are already in `var assemblyBindingElement = GetAssemblyBindingElement(runtime);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/BindingRedirectManager.cs:204 — "Add the binding to that element" repeats the code it sits on: 3 of its 3 words (add, binding, element) are already in `assemblyBindingElement.AddIndented(bindingRedirect.ToXElement());`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs:198 — 5 comments in this file only repeat the code they sit on (lines 198, 202, 280, 289, 342), for example "...prepare a new `<PackageReference>` element...". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/PackagesConfigUpdater.cs:97 — "Update binding redirects" repeats the code it sits on: 3 of its 3 words (update, binding, redirects) are already in `var updatedConfigFiles = await BindingRedirectManager.UpdateBindingRedirectsAsync(repoRootPath, projectBuildFile, depend …`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs:136 — 8 comments in this file only repeat the code they sit on (lines 136, 293, 389, 395, 510, 527, 616, 627), for example "Collect all target frameworks from the dependency set". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
X7 · Silent fallback defaults · Silent fallback default on parse failure · ×20
  • Silent fallback default on parse failure bun/lib/dependabot/bun/file_fetcher/path_dependency_builder.rb:153 — `parsed_package_lock` answers `{}` when `ParserError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure bundler/lib/dependabot/bundler/checksum_mismatch.rb:154 — `describe_api_source` answers `"a registry"` when `InvalidURIError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure conda/lib/dependabot/conda/update_checker/latest_version_finder.rb:156 — `extract_all_channels_from_environment_file` answers `[]` when `SyntaxError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure deno/lib/dependabot/deno/package/package_details_fetcher.rb:65 — `fetch_jsr_releases` answers `[]` when `ParserError | Timeout | Socket` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure deno/lib/dependabot/deno/package/package_details_fetcher.rb:89 — `fetch_npm_releases` answers `[]` when `ParserError | Timeout | Socket` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure github_actions/lib/dependabot/github_actions/file_updater.rb:154 — `self_repository_files` answers `[]` when `SyntaxError | DisallowedClass | BadAlias` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure npm_and_yarn/lib/dependabot/npm_and_yarn/dependency_grapher.rb:115 — `parsed_package_json` answers `{}` when `ParserError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:787 — `parsed_package_lock` answers `{}` when `ParserError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher.rb:796 — `parsed_shrinkwrap` answers `{}` when `ParserError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure npm_and_yarn/lib/dependabot/npm_and_yarn/file_fetcher/path_dependency_builder.rb:153 — `parsed_package_lock` answers `{}` when `ParserError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure python/lib/dependabot/python/poetry_plugin_installer.rb:65 — `required_plugins` answers `{}` when `ParseError | ValueOverwriteError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure python/lib/dependabot/python/update_checker/pip_version_resolver/marker_evaluator.rb:234 — `evaluate_python_version_condition` answers `true` when `ArgumentError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure uv/lib/dependabot/uv/file_fetcher.rb:176 — `extract_license_paths` answers `[]` when `ParseError | ValueOverwriteError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure uv/lib/dependabot/uv/file_fetcher.rb:243 — `extract_version_source_paths` answers `[]` when `ParseError | ValueOverwriteError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure uv/lib/dependabot/uv/file_fetcher/workspace_fetcher.rb:113 — `fetch_readme_files_for` answers `[]` when `ParseError | ValueOverwriteError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure uv/lib/dependabot/uv/file_fetcher/workspace_fetcher.rb:206 — `extract_version_source_paths` answers `[]` when `ParseError | ValueOverwriteError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure uv/lib/dependabot/uv/file_fetcher/workspace_fetcher.rb:231 — `extract_license_paths` answers `[]` when `ParseError | ValueOverwriteError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure uv/lib/dependabot/uv/file_updater/lock_file_updater.rb:528 — `uv_lock_registry_urls` answers `[]` when `ParseError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure uv/lib/dependabot/uv/file_updater/lock_file_updater.rb:573 — `parse_uv_indices` answers `{}` when `ParseError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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 on parse failure uv/lib/dependabot/uv/file_updater/lock_index_credential_matcher.rb:57 — `credential_match_score` answers `-1` when `InvalidURIError` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. 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.
D29 · Static Analysis (SAST) · REDACTED · ×16
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/PullRequestBodyGenerator/IHttpFetcher.cs:25 — `GetJsonElementAsync` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
  • Silent fallback default in catch npm_and_yarn/spec/fixtures/projects/yarn_berry/simple/.pnp.cjs:4340 — `patchFs` swallows every exception into `return false` — 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 handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch npm_and_yarn/spec/fixtures/projects/yarn_berry/subdependency/.pnp.cjs:4340 — `patchFs` swallows every exception into `return false` — 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 handler or in the docstring, and the row stops firing.
D30 · Dependency Vulnerabilities · Low CVE · ×2
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned file · ×2
  • Orphaned file nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Files/BuildFile.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/EOLHandling.cs:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 26 significant file(s) lose their only recent owner: nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/XmlFileWriter.cs, nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/DependencyConflictResolver.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Discover/DiscoveryWorker.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Run/UpdateHandlers/GroupUpdateAllVersionsHandler.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs, nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/UpdateCommand.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/FileWriters/FileWriterWorker.cs (+18 more). Pair on, review, or document these before any departure.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no map of the repository's parts README.md:1 — The repository has 20 units (`DotNetPackageCorrelation`, `DotNetPackageCorrelation.Cli`, `NuGet.Build.Tasks`, `NuGet.Build.Tasks.Pack`, `NuGet.CommandLine`, ...); `README.md` and the documents it links name none of them. Add a short list of the parts and what each does.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 23 project(s) overshoot their size bounds, lowering Project Cohesion to 9.1/10. The most over is `NuGetUpdater.Core` (14920 LoC, 133 public types across 15 namespaces). Review these for cohesion — split a project that spans unrelated responsibilities.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Low vulnerability · ×1
  • REDACTED
D31 · IaC & Container Security · Low IaC · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 2 of 63 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 63 of the 196 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Files/BuildFile.cs, nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/EOLHandling.cs. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 33/37 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `bun/helpers`, `npm_and_yarn/helpers`, `python/helpers`, `uv/helpers`.
X2 · Cancellation propagation · Not all async methods take a CancellationToken · ×1
  • Not all async methods take a CancellationToken — Only 25/124 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
X4 · Structured logging · Interpolated log message defeats structured logging · ×1
  • Interpolated log message defeats structured logging nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Utilities/ILogger.cs:41 — Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 9/20 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
X5 · Nullable reference types · Null-forgiving operator (`!`) suppressions reduce the NRT score · ×1
  • Null-forgiving operator (`!`) suppressions reduce the NRT score — ~1.3 `!` suppressions per 1k syntax nodes — 129 suppression(s) across the 96436 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide.
X7 · Silent fallback defaults · Silent fallback default in rescue · ×1
  • Silent fallback default in rescue terraform/lib/dependabot/terraform/file_updater/provider_cli_config_builder.rb:132 — `parse_hcl_file` rescues every error into `{}` — 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.
Minor — 3 finding(s)
D24 · Comment Value · doc comments repeat the names · ×3
  • doc comments repeat the names nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.CommandLine/Commands/ProjectFactory.cs:634 — 1 of 6 documented parameters and 0 of 9 summaries in `NuGet.CommandLine` only repeat the member or parameter name (e.g. "The name of the project file." for `projectFileFullName`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names nuget/helpers/lib/NuGetUpdater/NuGetProjects/NuGet.Packaging/PackageFolderReader.cs:27 — 0 of 7 documented parameters and 4 of 9 summaries in `NuGet.Packaging` only repeat the member or parameter name (e.g. "Package folder reader" for `PackageFolderReader`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Updater/BindingRedirectManager.cs:32 — 1 of 6 documented parameters and 0 of 38 summaries in `NuGetUpdater.Core` only repeat the member or parameter name (e.g. "The version of the package that was updated" for `updatedPackageVersion`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0219041a5c084d329d4e02b7474a184e/history.json --exit-code 0 --source .17artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-0219041a5c084d329d4e02b7474a184e/tree.json --exit-code 0 --source .8artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude bun/helpers/test/yarn/fixtures/updater/updated --exclude cargo/spec/fixtures/updated_projects --exclude npm_and_yarn/helpers/test/yarn/fixtures/updater/scoped-git-source-updated --exclude npm_and_yarn/helpers/test/yarn/fixtures/updater/updated --exclude npm_and_yarn/spec/fixtures/projects/yarn/bad_content --exclude npm_and_yarn/spec/fixtures/projects/yarn/empty_version --exclude npm_and_yarn/spec/fixtures/projects/yarn/file_path_resolutions --exclude npm_and_yarn/spec/fixtures/projects/yarn/path_dependency_subdeps --exclude npm_and_yarn/spec/fixtures/projects/yarn/unparseable --exclude sorbet/rbi/annotations .134artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet—dotnet list nuget/helpers/lib/NuGetUpdater/NuGetUpdater.slnx package --vulnerable --include-transitive --format json54artifacts/raw/dotnet-vulnerable.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .99artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 11 file(s) — `nuget/helpers/lib/NuGetUpdater/DotNetPackageCorrelation/Correlator.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/AnalyzeWorker.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/CompatibilityChecker.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Analyze/PackageVersionsCache.cs`, `nuget/helpers/lib/NuGetUpdater/NuGetUpdater.Core/Clone/CloneWorker.cs`, … (+6 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a174cf-93fe-7747-8ee5-5f8f521e2e87 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 189 · Warnings: 1114 · Recommendations: 105 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 25-10-2026 @ 20:45 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.

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