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

prefix-dev/pixi

Measured 14 November 2026, 17:16 UTC, at code version 9355b58

CAI score 61out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 3 since the last survey

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

A large codebase: 230,877 lines of product code in 70 projects, tests not counted · Estimated rebuild effort: about 2.2 person-years · Weakest lens: Code Health, 56

Findings by how serious they are

15 critical 834 serious 44 minor

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

This survey was produced by

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

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

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

46of 46 dimensions measured by tools.
825of 893 findings point to an exact file and line, so you can open each one in the code. The other 68 concern the repository as a whole, such as missing documentation.
46dimensions across 8 lenses, read from 230,877 lines of product code in 70 projects.
Chapters

Executive summary

prefix-dev/pixi falls short of our standard for a preview release, held back most by its Code Health lens, the quality of the code itself. It scores 61 out of 100 and is rated Adequate, and three of its 15 critical findings are security problems in the build pipeline.

Code Health, at 56, is the weakest lens and counts most in the score. The best first step is turning on missing-value checks, worth about 5 points. Removing the blocking calls comes next, worth about 3 points. Raising Code Health to 67 would lift the score to about 65.

Three pipeline steps run downloads nobody checks. Checking each download against a checksum would close this risk. The 12 pieces of product code that depend on test code need their reference to the test project removed.

The product code is 230,877 lines, about €320,000 to rebuild.

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

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

If Code Health rose from 56 to 67, the lowest score rated Strong, the score would rise from 61 to about 65.

Code composition: what the lines of code are
Supporting code 0%Tests 100%
New since the last survey: 207 findings

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

  • Cyclomatic Complexity · pixi_api::workspace::run::run (cyclomatic 29) crates/pixi_api/src/workspace/run/mod.rs
  • Cyclomatic Complexity · pixi_cli::workspace::exclude_newer::execute (cyclomatic 20) crates/pixi_cli/src/workspace/exclude_newer.rs
  • Cyclomatic Complexity · TaskGraph::from_cmd_args (cyclomatic 16) crates/pixi_task/src/task_graph.rs
  • Cognitive Complexity · pixi_api::workspace::run::run (cognitive 54) crates/pixi_api/src/workspace/run/mod.rs
  • Cognitive Complexity · pixi_cli::workspace::exclude_newer::execute (cognitive 26) crates/pixi_cli/src/workspace/exclude_newer.rs
  • Cognitive Complexity · pixi_api::global::install::setup_environment (cognitive 17) crates/pixi_api/src/global/install.rs
  • God Classes · MethodTooLong: RattlerBuildBackend.conda_outputs crates/pixi_build_rattler_build/src/protocol.rs
  • God Classes · FunctionTooLong: pixi_api::workspace::run::run crates/pixi_api/src/workspace/run/mod.rs
  • God Classes · MethodTooLong: RattlerBuildBackend.conda_build_v1 crates/pixi_build_rattler_build/src/protocol.rs
  • God Classes · FileTooLong: src/project_model.rs crates/pixi_build_types/src/project_model.rs
  • God Classes · FileTooLong: init/mod.rs crates/pixi_api/src/workspace/init/mod.rs
  • God Classes · FileTooLong: project/manifest.rs crates/pixi_global/src/project/manifest.rs
  • God Classes · FunctionTooLong: pixi_cli::workspace::exclude_newer::execute crates/pixi_cli/src/workspace/exclude_newer.rs
  • God Classes · FileTooLong: src/context.rs crates/pixi_api/src/context.rs
  • God Classes · FunctionTooLong: pixi_api::workspace::shell::shell crates/pixi_api/src/workspace/shell/mod.rs
  • God Classes · ClassTooLong: Manifest crates/pixi_global/src/project/manifest.rs
  • God Classes · MethodTooLong: LockFileDerivedData.prefix crates/pixi_core/src/lock_file/update.rs
  • Code Duplication · Near-duplicate member pair (42 shared lines) crates/pixi_manifest/src/utils/inheritable_package_map.rs
  • Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) crates/pixi_build_backend/src/intermediate_backend.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) crates/pixi_api/src/workspace/shell/mod.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) crates/pixi_build_backend/src/intermediate_backend.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) crates/pixi_build_cmake/src/config.rs
  • Code Duplication · Edited copy of a member (70 corresponding lines) crates/pixi_toml_edit/src/array.rs
  • Code Duplication · Edited copy of a member (58 corresponding lines) crates/pixi_manifest/src/toml/exclude_newer.rs
  • Code Duplication · Edited copy of a member (61 corresponding lines) crates/pixi_core/src/lock_file/install_subset.rs
  • Code Duplication · Edited copy of a member (59 corresponding lines) crates/pixi_manifest/src/manifests/workspace.rs
  • Code Duplication · Edited copy of a member (55 corresponding lines) crates/pixi_uv_conversions/src/conversions.rs
  • Code Duplication · Edited copy of a member (40 corresponding lines) crates/pixi_toml/src/hash_map.rs
  • Code Duplication · Edited copy of a member (46 corresponding lines) crates/pixi_build_frontend/src/backend/json_rpc.rs
  • Code Duplication · Edited copy of a member (50 corresponding lines) crates/pixi_command_dispatcher/src/cache/common.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) crates/pixi_cli/src/global/expose.rs
  • Code Duplication · Edited copy of a member (36 corresponding lines) crates/pixi_manifest/src/manifests/workspace.rs
  • Code Duplication · Edited copy of a member (38 corresponding lines) crates/pixi_core/src/workspace/mod.rs
  • Code Duplication · Edited copy of a member (32 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) crates/pixi_manifest/src/toml/channel.rs
  • Code Duplication · Edited copy of a member (43 corresponding lines) crates/pixi_core/src/workspace/mod.rs
  • Code Duplication · Edited copy of a member (26 corresponding lines) crates/pixi_command_dispatcher/src/backend_source_build/ext.rs
  • Code Duplication · Edited copy of a member (57 corresponding lines) crates/pixi_command_dispatcher/src/build/conversion.rs
  • Code Duplication · Edited copy of a member (36 corresponding lines) crates/pixi_core/src/workspace/mod.rs
  • Code Duplication · Edited copy of a member (33 corresponding lines) crates/pixi_compute_sources/src/git.rs
  • Code Duplication · Edited copy of a member (35 corresponding lines) crates/pixi_manifest/src/toml/pypi_options.rs
  • Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) crates/pixi_url/src/extract.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) crates/pixi_global/src/project/parsed_manifest.rs
  • Code Duplication · Edited copy of a member (27 corresponding lines) crates/pixi_utils/src/executable_utils.rs
  • Code Duplication · Edited copies of one member (3 members, 36+ corresponding lines) crates/pixi_api/src/workspace/workspace/channel.rs
  • Code Duplication · Edited copy of a member (28 corresponding lines) crates/pixi_cli/src/workspace/channel.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) crates/pixi_cli/src/add.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) crates/pixi_uv_conversions/src/git_url.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) crates/pixi_toml/src/btree_set.rs
  • Code Duplication · Edited copy of a member (20 corresponding lines) crates/pixi_utils/src/atomic_write.rs
  • Code Duplication · Edited copy of a member (39 corresponding lines) crates/pixi_command_dispatcher/src/keys/solve_conda.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) crates/pixi_command_dispatcher/src/cache/workspace.rs
  • Code Duplication · Edited copy of a member (19 corresponding lines) crates/pixi_manifest/src/toml/package.rs
  • Code Duplication · Edited copy of a member (19 corresponding lines) crates/pixi_core/src/lock_file/records_by_name.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) crates/pixi_cli/src/workspace/description.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) crates/pixi_command_dispatcher/src/dev_source_metadata/mod.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) crates/pixi_toml_edit/src/entry.rs
  • Code Duplication · Edited copies of one member (7 members, 19+ corresponding lines) crates/pixi_build_rust/src/metadata.rs
  • Code Duplication · Edited copy of a member (20 corresponding lines) crates/pixi_manifest/src/manifests/document.rs
  • Code Duplication · Edited copy of a member (30 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) crates/pixi_core/src/lock_file/satisfiability/legacy/key.rs
  • Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) crates/pixi_toml_edit/src/entry.rs
  • Code Duplication · Edited copy of a member (20 corresponding lines) crates/pixi_compute_sources/src/ext.rs
  • Code Duplication · Edited copy of a member (24 corresponding lines) crates/pixi_uv_conversions/src/workspace_anchor.rs
  • Code Duplication · Edited copy of a member (29 corresponding lines) crates/pixi_build_backend/src/variants.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) crates/pixi_install_pypi/src/utils.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) crates/pixi_manifest/src/pypi/pypi_options.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) crates/pixi_manifest/src/toml/pyproject.rs
  • Code Duplication · Edited copy of a member (16 corresponding lines) crates/pixi_build_python/src/main.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) crates/pixi_manifest/src/pypi/merge.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) crates/pixi_build_mojo/src/config.rs
  • Code Duplication · Edited copy of a member (23 corresponding lines) crates/pixi_cli/src/install.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) crates/pixi_manifest/src/script/conda/error.rs
  • Code Duplication · Edited copy of a member (17 corresponding lines) crates/pixi_toml_edit/src/style.rs
  • Code Duplication · Edited copy of a member (17 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs
  • Code Duplication · Edited copy of a member (19 corresponding lines) crates/pixi_utils/src/executable_utils.rs
  • Code Duplication · Edited copy of a member (16 corresponding lines) crates/pixi_utils/src/reqwest.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) crates/pixi_api/src/workspace/workspace/feature.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) crates/pixi_cli/src/global/exclude_newer.rs
  • Code Duplication · Edited copy of a member (21 corresponding lines) crates/pixi_reporters/src/uv_reporter.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) crates/pixi_compute_engine/src/key_graph.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) crates/pixi_git/src/git.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) crates/pixi_manifest/src/script/conda/manifest.rs
  • Code Duplication · Edited copy of a member (12 corresponding lines) crates/pixi_record/src/lib.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) crates/pixi_config/src/lib.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) crates/pixi_global/src/project/environment.rs
  • Code Duplication · Edited copy of a member (14 corresponding lines) crates/pixi_manifest/src/target.rs
  • Code Duplication · Edited copy of a member (17 corresponding lines) crates/pixi_manifest/src/warning/deprecation.rs
  • Code Duplication · Edited copy of a member (20 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs
  • Code Duplication · Edited copy of a member (8 corresponding lines) crates/pixi_variant/src/lib.rs
  • Code Duplication · Edited copy of a member (25 corresponding lines) crates/pixi_command_dispatcher/src/ephemeral_env/mod.rs
  • Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) crates/pixi_api/src/workspace/workspace/activation.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) crates/pixi_reporters/src/main_progress_bar.rs
  • Code Duplication · Edited copies of one member (6 members, 14+ corresponding lines) crates/pixi_build_cmake/src/main.rs
  • Code Duplication · Edited copy of a member (11 corresponding lines) crates/pixi_manifest/src/target.rs
  • Code Duplication · Edited copy of a member (13 corresponding lines) crates/pixi_build_python/src/metadata.rs
  • Code Duplication · Edited copy of a member (18 corresponding lines) crates/pixi_cli/src/workspace/requires_pixi/set.rs
  • Code Duplication · Edited copy of a member (22 corresponding lines) crates/pixi_global/src/project/manifest.rs
  • Code Duplication · Edited copy of a member (10 corresponding lines) crates/pixi_manifest/src/manifests/document.rs
  • Code Duplication · Edited copy of a member (15 corresponding lines) crates/pixi_api/src/workspace/workspace/platform.rs

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

Fixed since the last survey: 89 findings

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

  • Cognitive Complexity · local_patch.get_current_workspace_dependency_versions (cognitive 30) scripts/local_patch.py
  • Cognitive Complexity · release_backends.bump (cognitive 22) scripts/release_backends.py
  • Cognitive Complexity · pixi_cli::shared::tree::print_dependency_tree (cognitive 21) crates/pixi_cli/src/shared/tree.rs
  • Cognitive Complexity · local_patch.update_workspace_dependency_versions (cognitive 20) scripts/local_patch.py
  • Cognitive Complexity · WorkspaceLocator::locate_script (cognitive 18) crates/pixi_core/src/workspace/discovery.rs
  • Cognitive Complexity · release_backends.reconcile_api_version (cognitive 18) scripts/release_backends.py
  • Cognitive Complexity · pixi_cli::global::install::setup_environment (cognitive 17) crates/pixi_cli/src/global/install.rs
  • God Classes · FunctionTooLong: pixi_cli::exec::create_exec_prefix crates/pixi_cli/src/exec.rs
  • God Classes · FileTooLong: src/run.rs crates/pixi_cli/src/run.rs
  • God Classes · FunctionTooLong: pixi_cli::shell::execute crates/pixi_cli/src/shell.rs
  • God Classes · MethodTooLong: Project.environment_in_sync_internal crates/pixi_global/src/project/mod.rs
  • God Classes · FileTooLong: scripts/release_backends.py scripts/release_backends.py
  • Code Duplication · Near-duplicate member pair (77 shared lines) crates/pixi_build_backend/src/intermediate_backend.rs
  • Code Duplication · Near-duplicate member pair (41 shared lines) crates/pixi_manifest/src/utils/inheritable_package_map.rs
  • Code Duplication · Members sharing a duplicated core (6 members, 50+ identical tokens) crates/pixi_build_rust/src/metadata.rs
  • Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) crates/pixi_cli/src/shell.rs
  • Code Duplication · Duplicated block (29 lines × 2) crates/pixi_toml/src/hash_map.rs
  • Code Duplication · Duplicated block (28 lines × 2) crates/pixi_manifest/src/utils/inheritable_package_map.rs
  • Code Duplication · Duplicated block (25–27 lines × 2) crates/pixi_api/src/workspace/remove/mod.rs
  • Code Duplication · Duplicated block (23–24 lines × 3) crates/pixi_api/src/workspace/workspace/channel.rs
  • Code Duplication · Duplicated block (22–23 lines × 2) crates/pixi_cli/src/global/expose.rs
  • Code Duplication · Duplicated block (21 lines × 2) crates/pixi_cli/src/global/expose.rs
  • Code Duplication · Duplicated block (20 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs
  • Code Duplication · Duplicated block (13–19 lines × 2) crates/pixi_build_mojo/src/config.rs
  • Code Duplication · Duplicated block (18–19 lines × 2) crates/pixi_cli/src/global/install.rs
  • Code Duplication · Duplicated block (18 lines × 2) crates/pixi_api/src/workspace/add/mod.rs
  • Code Duplication · Duplicated block (13–17 lines × 6) crates/pixi_build_rust/src/metadata.rs
  • Code Duplication · Duplicated block (16 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs
  • Code Duplication · Duplicated block (16 lines × 2) crates/pixi_cli/src/update.rs
  • Code Duplication · Duplicated block (14–15 lines × 2) crates/pixi_cli/src/global/tree.rs
  • Code Duplication · Duplicated block (15 lines × 2) crates/pixi_cli/src/shell.rs
  • Code Duplication · Duplicated block (15 lines × 2) crates/pixi_manifest/src/toml/exclude_newer.rs
  • Code Duplication · Duplicated block (14 lines × 2) crates/pixi_api/src/workspace/add/mod.rs
  • Code Duplication · Duplicated block (9–14 lines × 2) crates/pixi_manifest/src/toml/platform.rs
  • Code Duplication · Duplicated block (14 lines × 2) crates/pixi_toml_edit/src/array.rs
  • Code Duplication · Duplicated block (10–13 lines × 3) crates/pixi_cli/src/global/install.rs
  • Code Duplication · Duplicated block (13 lines × 2) crates/pixi_api/src/workspace/list/package.rs
  • Code Duplication · Duplicated block (11–13 lines × 2) crates/pixi_api/src/workspace/list/package.rs
  • Code Duplication · Duplicated block (13 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs
  • Code Duplication · Duplicated block (13 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs
  • Code Duplication · Duplicated block (12–13 lines × 2) crates/pixi_manifest/src/toml/feature.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/pixi_build_backend/src/server.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/pixi_build_cmake/src/main.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/pixi_build_cmake/src/main.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/pixi_manifest/src/toml/feature.rs
  • Code Duplication · Duplicated block (11 lines × 3) crates/pixi_build_backend/src/intermediate_backend.rs
  • Code Duplication · Duplicated block (11 lines × 3) crates/pixi_manifest/src/toml/document.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/pixi_core/src/lock_file/outdated.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/pixi_core/src/lock_file/records_by_name.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/pixi_manifest/src/task.rs
  • Code Duplication · Duplicated block (10–11 lines × 2) crates/pixi_url/src/source.rs
  • Code Duplication · Duplicated block (9–10 lines × 4) crates/pixi_cli/src/shell.rs
  • Code Duplication · Duplicated block (10 lines × 3) crates/pixi_build_cmake/src/main.rs
  • Code Duplication · Duplicated block (10 lines × 2) crates/pixi_core/src/workspace/discovery.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/pixi_api/src/workspace/list/package.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/pixi_build_cmake/src/config.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/pixi_cli/src/shell.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/pixi_cli/src/shell.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/pixi_cli/src/update.rs
  • Code Duplication · Duplicated block (7 lines × 3) crates/pixi_cli/src/shell.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/pixi_cli/src/exec.rs
  • Code Duplication · Duplicated block (7 lines × 2) crates/pixi_cli/src/upgrade.rs
  • Code Duplication · Duplicated block (6 lines × 2) crates/pixi_build_rattler_build/src/protocol.rs
  • Code Duplication · Duplicated block (5 lines × 4) crates/pixi_manifest/src/system_requirements.rs
  • Code Duplication · Duplicated block (7 lines × 4) crates/pixi_build_cmake/src/build_script.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/pixi_core/src/workspace/mod.rs
  • Code Duplication · Duplicated block (9 lines × 2) crates/pixi_global/src/project/manifest.rs
  • Code Duplication · Duplicated block (8 lines × 2) crates/pixi_utils/src/executable_utils.rs
  • Code Duplication · Duplicated block (11 lines × 2) crates/pixi_cli/src/tree.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/pixi_api/src/workspace/workspace/platform.rs
  • Code Duplication · Duplicated block (12 lines × 2) crates/pixi_api/src/workspace/task/mod.rs
  • Code Duplication · Duplicated block (6 lines × 2) crates/pixi_global/src/project/manifest.rs
  • Code Duplication · Duplicated block (5 lines × 2) crates/pixi_url/src/extract.rs
  • Code Duplication · Duplicated block (7 lines × 3) crates/pixi_spec/src/url.rs
  • Code Duplication · Duplicated block (10 lines × 2) crates/pixi_spec/src/toml.rs
  • Coupling · Unstable project pixi_task
  • Churn × Complexity Hotspots · Hotspot: crates/pixi_cli/src/lib.rs crates/pixi_cli/src/lib.rs
  • Churn × Complexity Hotspots · Hotspot: crates/pixi_docs/src/main.rs crates/pixi_docs/src/main.rs
  • Churn × Complexity Hotspots · Hotspot: crates/pixi_cli/src/info.rs crates/pixi_cli/src/info.rs
  • Churn × Complexity Hotspots · Hotspot: crates/pixi_manifest/src/discovery.rs crates/pixi_manifest/src/discovery.rs
  • Churn × Complexity Hotspots · Hotspot: crates/pixi_manifest/src/toml/package.rs crates/pixi_manifest/src/toml/package.rs
  • Churn × Complexity Hotspots · Hotspot: crates/pixi_cli/src/clean.rs crates/pixi_cli/src/clean.rs
  • Churn × Complexity Hotspots · Hotspot: crates/pypi_modifiers/src/pypi_marker_env.rs crates/pypi_modifiers/src/pypi_marker_env.rs
  • Explicit Debt · TodoComment crates/pixi_command_dispatcher/src/environment/spec.rs
  • Explicit Debt · TodoComment crates/pixi_cli/src/shell.rs
  • Dependency Vulnerabilities · Medium advisory (unmaintained): RUSTSEC-2026-0173 REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0367 REDACTED
Rebuild cost: about €320,000 · Estimate
Cost to rebuild€110,000 to €540,000, for 1,781 to 5,650 hours of work, about 2.2 person-years for 1 to 5 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.8 at a score of 61. 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: 230,877 lines of product code
Comment linesThe estimate prices 230,870 lines. Comment lines count towards the size of 230,877 lines but aren't priced as work.
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`.
Raises the score by about 5 points · Medium effort · Nullable reference types
2
Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
Raises the score by about 3 points · Medium effort · Async & latency hygiene
3
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.
Raises the score by about 0.7 points · Low effort · ADR Quality

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 €320,000 to build again, about 2.2 person-years of work. Its weakest lens is Code Health, at 56 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. 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.5 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 97,235 lines over the last 90 days, which is about 394,342 lines a year. At that pace, the extra work comes to an estimated 19.7 to 131.4 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture — module dependency graph

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

arch pixi_api pixi_api pixi_config pixi_config pixi_api->pixi_config pixi_consts pixi_consts pixi_api->pixi_consts pixi_core pixi_core pixi_api->pixi_core pixi_global pixi_global pixi_api->pixi_global pixi_install_pypi pixi_install_pypi pixi_api->pixi_install_pypi pixi_manifest pixi_manifest pixi_api->pixi_manifest pixi_reporters pixi_reporters pixi_api->pixi_reporters pixi_spec pixi_spec pixi_api->pixi_spec pixi_task pixi_task pixi_api->pixi_task pixi_utils pixi_utils pixi_api->pixi_utils pixi_uv_conversions pixi_uv_conversions pixi_api->pixi_uv_conversions pixi_build_discovery pixi_build_discovery pixi_build_types pixi_build_types pixi_build_discovery->pixi_build_types pixi_build_discovery->pixi_config pixi_build_discovery->pixi_consts pixi_build_discovery->pixi_manifest pixi_build_discovery->pixi_spec pixi_cli pixi_cli pixi_cli->pixi_api pixi_cli->pixi_build_types pixi_command_dispatcher pixi_command_dispatcher pixi_cli->pixi_command_dispatcher pixi_cli->pixi_config pixi_cli->pixi_consts pixi_cli->pixi_core pixi_git pixi_git pixi_cli->pixi_git pixi_cli->pixi_global pixi_cli->pixi_manifest pixi_path pixi_path pixi_cli->pixi_path pixi_record pixi_record pixi_cli->pixi_record pixi_cli->pixi_reporters pixi_cli->pixi_spec pixi_cli->pixi_task pixi_cli->pixi_utils pixi_cli->pixi_uv_conversions pixi_command_dispatcher->pixi_build_discovery pixi_command_dispatcher->pixi_build_types pixi_compute_sources pixi_compute_sources pixi_command_dispatcher->pixi_compute_sources pixi_command_dispatcher->pixi_consts pixi_command_dispatcher->pixi_git pixi_command_dispatcher->pixi_manifest pixi_command_dispatcher->pixi_path pixi_command_dispatcher->pixi_record pixi_command_dispatcher->pixi_spec pixi_command_dispatcher->pixi_utils pixi_compute_sources->pixi_consts pixi_compute_sources->pixi_git pixi_compute_sources->pixi_path pixi_compute_sources->pixi_record pixi_compute_sources->pixi_spec pixi_config->pixi_consts pixi_core->pixi_build_discovery pixi_core->pixi_build_types pixi_core->pixi_command_dispatcher pixi_core->pixi_config pixi_core->pixi_consts pixi_core->pixi_git pixi_core->pixi_install_pypi pixi_core->pixi_manifest pixi_core->pixi_path pixi_core->pixi_record pixi_core->pixi_reporters pixi_core->pixi_spec pixi_core->pixi_utils pixi_core->pixi_uv_conversions pixi_git->pixi_utils pixi_global->pixi_build_discovery pixi_global->pixi_command_dispatcher pixi_global->pixi_config pixi_global->pixi_consts pixi_global->pixi_core pixi_global->pixi_manifest pixi_global->pixi_path pixi_global->pixi_reporters pixi_global->pixi_spec pixi_global->pixi_utils pixi_install_pypi->pixi_consts pixi_install_pypi->pixi_git pixi_install_pypi->pixi_manifest pixi_install_pypi->pixi_path pixi_install_pypi->pixi_record pixi_install_pypi->pixi_reporters pixi_install_pypi->pixi_utils pixi_install_pypi->pixi_uv_conversions pixi_manifest->pixi_build_types pixi_manifest->pixi_consts pixi_manifest->pixi_spec pixi_record->pixi_git pixi_record->pixi_path pixi_record->pixi_spec pixi_reporters->pixi_build_discovery pixi_reporters->pixi_command_dispatcher pixi_reporters->pixi_config pixi_reporters->pixi_consts pixi_reporters->pixi_git pixi_spec->pixi_build_types pixi_spec->pixi_consts pixi_spec->pixi_git pixi_spec->pixi_path pixi_task->pixi_consts pixi_task->pixi_core pixi_task->pixi_manifest pixi_task->pixi_utils pixi_utils->pixi_config pixi_utils->pixi_consts pixi_uv_conversions->pixi_git pixi_uv_conversions->pixi_manifest pixi_uv_conversions->pixi_record pixi_uv_conversions->pixi_spec __more__ +50 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.

565 modules, with 1431 dependencies between them. 15 loops run through 60 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 525 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 pixi_build_backend.generated_recipe2 pixi_build_types.procedures.conda_build_v13 pixi_build_types.project_model4 pixi_config5 pixi_git6 pixi_global.project.environment7 pixi_record8 pixi_record.pinned_source9 pixi_build_types.procedures.conda_outputs10 pixi_compute_engine.ctx11 pixi_manifest.workspace12 pixi_compute_engine.key13 pixi_manifest.toml.manifest14 pixi_manifest.toml.package15 pixi_manifest.target16 pixi_manifest.platform17 pixi_manifest.feature18 pixi_manifest.environment19 pixi_install_pypi20 pixi_manifest.task21 pixi_manifest.manifests.document22 pixi_manifest.manifests.workspace23 pixi_build_discovery.discovery24 pixi_core.workspace.environment25 pixi_command_dispatcher.instantiate_backend_key26 pixi_core.host27 pixi_command_dispatcher.build_backend_metadata28 pixi_command_dispatcher.command_dispatcher29 pixi_reporters30 pixi_core.workspace31 pixi_global.project32 pixi_core.lock_file.update33 pixi_core.environment34 pixi_cli.cli_config35 pixi_core.workspace.workspace_mut36 pixi_api.context37 pixi_cli.add38 pixi_cli.clean39 pixi_cli.task40 pixi_cli.workspace.platform
1 pixi_build_backend.generated_recipe
2 pixi_build_types.procedures.conda_build_v1
3 pixi_build_types.project_model
4 pixi_config
5 pixi_git
6 pixi_global.project.environment
7 pixi_record
8 pixi_record.pinned_source
9 pixi_build_types.procedures.conda_outputs2
10 pixi_compute_engine.ctx3
11 pixi_manifest.workspace23
12 pixi_compute_engine.key1
13 pixi_manifest.toml.manifest12111
14 pixi_manifest.toml.package111
15 pixi_manifest.target23
16 pixi_manifest.platform11
17 pixi_manifest.feature2111
18 pixi_manifest.environment1
19 pixi_install_pypi11
20 pixi_manifest.task215
21 pixi_manifest.manifests.document12111
22 pixi_manifest.manifests.workspace11487331
23 pixi_build_discovery.discovery11
24 pixi_core.workspace.environment211111
25 pixi_command_dispatcher.instantiate_backend_key11214
26 pixi_core.host2131
27 pixi_command_dispatcher.build_backend_metadata213221
28 pixi_command_dispatcher.command_dispatcher111
29 pixi_reporters1
30 pixi_core.workspace2212412
31 pixi_global.project141111
32 pixi_core.lock_file.update11615445
33 pixi_core.environment513113
34 pixi_cli.cli_config112231
35 pixi_core.workspace.workspace_mut1112111
36 pixi_api.context114122111111
37 pixi_cli.add2214
38 pixi_cli.clean2111
39 pixi_cli.task1325611111
40 pixi_cli.workspace.platform16321211111
Uses a module listed above itPart of a loopThe module itself
1 pixi_build_backend.generated_recipe2 pixi_build_types.procedures.conda_build_v13 pixi_build_types.project_model4 pixi_config5 pixi_git6 pixi_global.project.environment7 pixi_record8 pixi_record.pinned_source9 pixi_build_types.procedures.conda_outputs10 pixi_compute_engine.ctx11 pixi_manifest.workspace12 pixi_compute_engine.key13 pixi_manifest.toml.manifest14 pixi_manifest.toml.package15 pixi_manifest.target16 pixi_manifest.platform17 pixi_manifest.feature18 pixi_manifest.environment19 pixi_install_pypi20 pixi_manifest.task21 pixi_manifest.manifests.document22 pixi_manifest.manifests.workspace23 pixi_build_discovery.discovery24 pixi_core.workspace.environment25 pixi_command_dispatcher.instantiate_backend_key26 pixi_core.host27 pixi_command_dispatcher.build_backend_metadata28 pixi_command_dispatcher.command_dispatcher29 pixi_reporters30 pixi_core.workspace31 pixi_global.project32 pixi_core.lock_file.update33 pixi_core.environment34 pixi_cli.cli_config35 pixi_core.workspace.workspace_mut36 pixi_api.context37 pixi_cli.add38 pixi_cli.clean39 pixi_cli.task40 pixi_cli.workspace.platformpixi_build_backend.generated_recipe1pixi_build_types.procedures.conda_build_v12pixi_build_types.project_model3pixi_config4pixi_git5pixi_global.project.environment6pixi_record7pixi_record.pinned_source8pixi_build_types.procedures.conda_outputs9pixi_compute_engine.ctx10pixi_manifest.workspace11pixi_compute_engine.key12pixi_manifest.toml.manifest13pixi_manifest.toml.package14pixi_manifest.target15pixi_manifest.platform16pixi_manifest.feature17pixi_manifest.environment18pixi_install_pypi19pixi_manifest.task20pixi_manifest.manifests.document21pixi_manifest.manifests.workspace22pixi_build_discovery.discovery23pixi_core.workspace.environment24pixi_command_dispatcher.instantiate_backend_key25pixi_core.host26pixi_command_dispatcher.build_backend_metadata27pixi_command_dispatcher.command_dispatcher28pixi_reporters29pixi_core.workspace30pixi_global.project31pixi_core.lock_file.update32pixi_core.environment33pixi_cli.cli_config34pixi_core.workspace.workspace_mut35pixi_api.context36pixi_cli.add37pixi_cli.clean38pixi_cli.task39pixi_cli.workspace.platform402323112111111231121111112151211111487331112111111121421312132211111221241214111111615445513113112231111211111412211111122142111132561111116321211111+525 more modules (most-connected shown)

At a glance — Code Health · 56% · Adequate · gated by X5 ·

At a glance — Architecture · 67% · Adequate · gated by AX8 ·

At a glance — Maturity · 76% · Strong ·

At a glance — Readiness · 66% · Adequate · gated by P3 ·

At a glance — Security · 84% · Strong ·

At a glance — Domain Modelling · 100% · Exemplary ·

At a glance — Event Sourcing · 100% · Exemplary ·

At a glance — Performance · 60% · Adequate ·

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
A03:2025 — Software Supply Chain Failures42Medium
A05:2025 — Injection5High / Critical

Roadmap

Top priorities: Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`; Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`; Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.

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

Do thisHelpsEffortDimension
Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — and resolve warnings rather than suppressing with `!`.+4.7 ptsMediumNullable reference types
Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.+3.0 ptsMediumAsync & latency hygiene
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs.+0.7 ptsLowADR Quality
Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.+1.3 ptsMediumTest isolation
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Config::set (cyclomatic 97), pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability (cyclomatic 64).+0.6 ptsMediumCyclomatic Complexity
Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.+1.0 ptsMediumSecurity & performance tooling
Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability (cognitive 172).+0.5 ptsMediumCognitive Complexity
Resolve the 92 TodoComment finding(s) in Explicit Debt — start with mod.rs (13), lib.rs (7), import.rs (4).+0.4 ptsMediumExplicit Debt

File quality

Per-file score 0–10 — a quality signature. Of 259 files carrying findings, judged against the Preview bar: 0% slop · 16% mixed · 84% near-clean.

FileScoreBandWorst signal
crates/pixi_cli/src/run.rs5.1MixedCyclomatic Complexity: pixi_cli::run::execute (cyclomatic 22)
crates/pixi_core/src/lock_file/resolve/pypi.rs5.5MixedCyclomatic Complexity: pixi_core::lock_file::resolve::pypi::resolve_pypi (cyclomatic 21)
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedDependency Vulnerabilities: Medium advisory (unmaintained): REDACTED
crates/pixi_config/src/lib.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_core/src/lock_file/update.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_manifest/src/task.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_core/src/lock_file/satisfiability/pypi.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_api/src/workspace/list/package.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_build_python/src/main.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_cli/src/update.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_global/src/project/mod.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_task/src/task_graph.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_command_dispatcher/src/keys/solve_pixi_environment.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_core/src/environment/mod.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_build_rattler_build/src/protocol.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_cli/src/clean.rs6.0MixedExplicit Debt: TodoComment
crates/pixi_record/src/pinned_source.rs6.0MixedExplicit Debt: TodoComment
schema/model.py6.0MixedExplicit Debt: TodoComment
crates/pixi_build_backend/src/intermediate_backend.rs6.0MixedExplicit Debt: TodoComment

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

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

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

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

Could not be resolved — 8

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

Methodology & how to trust this report

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

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

What we checked — 46 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D16D17D19D20D28D29D30D31D34D35D36D37D43D44AX10AX2AX3AX4AX8AX9DM4DM5ES2GD1M1M2M3M4P1P10P2P3P4P6PF3X5

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, 825 of 893 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1db0f-f83e-72a3-8b62-ca366facb78e.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.py, .rs) and this repository declares a Cargo test suite (repository root, 321 test files), but it was not re-run: its build outgrew the 8 GB scratch ceiling (8.032 GB measured) and was stopped; its suite was not run. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `docs/source_files/conda_scripts/main.cs` 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.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (examples/docker/docker-compose.yml). compose up failed (exit 17 — an image could not be built) — pixi-example Pulling pixi-example Warning Get "http://localhost/v2/": dial tcp [::1]:80: connect: connection refused failed to solve: process "/bin/sh -c pixi install" did not complete successfully: exit code: 1; runtime evidence skipped.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. 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.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's C# was parsed (it ships no .sln or .csproj, so it was read as syntax-only projects), but this check proves its findings from resolved symbols and a reference-free parse resolves none. It abstained rather than report a clean bill it could not earn. That is a gap in this analyzer's reach into build-less repositories — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations: 21 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

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • 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 checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
  • DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • 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.0 / 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.0 / 10 · rule-coverage 100% · ceiling Prevented

63 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Config::set at 97. A further 5 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 pixi_cli::execute_command at 31 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/pixi_cli/src/lib.rs (pixi_cli::execute_command at 31), crates/pypi_modifiers/src/pypi_marker_env.rs (pypi_modifiers::pypi_marker_env::determine_marker_environment at 20), crates/pixi_install_pypi/src/plan/models.rs (NeedReinstall::fmt at 17). 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.

pixi_cli::publish::execute (cyclomatic 45) · ×15crates/pixi_cli/src/publish/mod.rs:562
pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability (cyclomatic 64) · ×9crates/pixi_core/src/lock_file/satisfiability/platform.rs:630
pixi_glob::glob_set::walk::set_ignore_hidden_patterns (cyclomatic 21) · ×2crates/pixi_glob/src/glob_set/walk.rs:345
PackageReachability::collect_reachable_from_non_skipped (cyclomatic 19) · ×2crates/pixi_core/src/lock_file/install_subset.rs:401
pixi_docs::arguments (cyclomatic 18) · ×2crates/pixi_docs/src/main.rs:445

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

What to do

  1. Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Config::set (cyclomatic 97), pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability (cyclomatic 64). — 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 2 together lifts Cyclomatic Complexity from 6.0 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.

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

D2 · Cognitive Complexity5.2 / 10Adequate✓ 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 5.2 / 10 · rule-coverage 100% · ceiling Prevented

134 method(s) exceeded the cognitive complexity threshold of 15; the worst was pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability at 172.

pixi_cli::publish::execute (cognitive 64) · ×33crates/pixi_cli/src/publish/mod.rs:562
pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability (cognitive 172) · ×17crates/pixi_core/src/lock_file/satisfiability/platform.rs:630
pixi_command_dispatcher::keys::solve_pixi_environment::walk_and_resolve (cognitive 28) · ×5crates/pixi_command_dispatcher/src/keys/solve_pixi_environment.rs:482
pixi_manifest::toml::manifest::validate_task_environments (cognitive 26) · ×5crates/pixi_manifest/src/toml/manifest.rs:693
pixi_global::install::create_executable_trampolines (cognitive 27) · ×4crates/pixi_global/src/install.rs:119

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

What to do

  1. Bring the 1 body over 120 down to 120 or less in Cognitive Complexity — start with pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability (cognitive 172). — Refactoring it lifts Cognitive Complexity from 5.3 to about 5.7/10.

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

D3 · God Classes8.3 / 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 8.3 / 10 · rule-coverage 100% · ceiling Prevented

130 god class(es) detected.

FileTooLong: lock_file/update.rs · ×42crates/pixi_core/src/lock_file/update.rs
MethodTooLong: UpdateContext.update · ×36crates/pixi_core/src/lock_file/update.rs:2595
FunctionTooLong: pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability · ×32crates/pixi_core/src/lock_file/satisfiability/platform.rs:630
ClassTooLong: Project · ×14crates/pixi_global/src/project/mod.rs:530
TooManyMethods: Workspace · ×6crates/pixi_core/src/workspace/mod.rs:183

What to do

  1. Resolve the 42 FileTooLong finding(s) in God Classes — start with mod.rs (6), platform.rs (4), lib.rs (3). — One of this dimension's main actionable groups (42 warning-level).
  2. Resolve the 36 MethodTooLong finding(s) in God Classes — start with mod.rs (6), update.rs (4), main.rs (4). — One of this dimension's main actionable groups (36 warning-level).
  3. Resolve the 32 FunctionTooLong finding(s) in God Classes — start with mod.rs (4), pypi.rs (4), platform.rs (2). — One of this dimension's main actionable groups (32 warning-level).

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: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

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

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

182 duplicated block group(s) detected. 3.5 % of the production lines (8,130 of 229,912) are in a reported copy. A further 119 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 25 of the 301 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.

Duplicated block (8 lines × 2) · ×16crates/pixi_api/src/workspace/shell/mod.rs:129
Duplicated block (10 lines × 2) · ×13crates/pixi_build_backend/src/server.rs:128
Duplicated block (9 lines × 2) · ×13crates/pixi_build_backend/src/rattler_build_integration.rs:128
Duplicated block (13 lines × 2) · ×10crates/pixi_api/src/workspace/shell/mod.rs:113
Duplicated block (11 lines × 2) · ×10crates/pixi_build_backend/src/dependencies.rs:117

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

What to do

  1. Resolve the 16 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with mod.rs (2), lib.rs (2), intermediate_backend.rs. — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 13 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with lib.rs (2), errors.rs (2), download_verify_reporter.rs (2). — One of this dimension's main actionable groups (13 warning-level).
  3. Resolve the 13 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with rattler_build_integration.rs, install.rs, resolve_source_record.rs. — One of this dimension's main actionable groups (13 warning-level).

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

D5 · Coupling7.1 / 10Strong✓ 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 7.1 / 10 · rule-coverage 100% · ceiling Prevented

70 production modules (Cargo+Python+CMake), 0 dependency cycle(s), 6 unstable depended-on module(s). Read from the build's own module declarations; 18 module(s) off the main sequence, with abstractness counted on 55 of the 70 (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).

Off the main sequence: barrier_cell · ×18
Unstable project pixi_api
Unstable project pixi_command_dispatcher
Unstable project pixi_compute_sources
Unstable project pixi_core

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

What to do

  1. Resolve the 18 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (18 warning-level).
  2. Resolve the 1 Unstable project pixi_api finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project pixi_command_dispatcher finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

1 of 331 classes have LCOM4 above 3.

Low cohesion: PtyProcess (LCOM4 4)crates/pixi_pty/src/unix/pty_process.rs:28

What to do

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

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

D12 · Dependency Hygiene9.0 8.8 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

20 outdated, 0 yanked direct Cargo dependencies. 176 of 181 direct crates were graded against crates.io (0 not published there, 5 not resolved by a committed REDACTED). Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.

Outdated: mimalloc · ×20

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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 1083 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 1 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under BSD-3-Clause, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), 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.7 / 10Stronggated by 35 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.7 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: crates/pixi_config/src/lib.rs (12×97=1164); crates/pixi_core/src/lock_file/update.rs (22×36=792); crates/pixi_cli/src/publish/mod.rs (13×45=585) Repeated repair below the complexity floor: crates/pixi_command_dispatcher/src/keys/source_build.rs (5 of 7 changes were fixes); crates/pixi_task/src/executable_task.rs (3 of 5 changes were fixes); crates/pixi_command_dispatcher/src/cache/backend_metadata.rs (3 of 3 changes were fixes)

Hotspot: crates/pixi_config/src/lib.rs · ×32crates/pixi_config/src/lib.rs:2516
Repeated repair: crates/pixi_command_dispatcher/src/keys/source_build.rs · ×3crates/pixi_command_dispatcher/src/keys/source_build.rs:239

What to do

  1. Resolve the 32 Hotspot finding(s) in Churn × Complexity Hotspots — start with mod.rs (2), pypi.rs (2), lib.rs. — One of this dimension's main actionable groups (32 warning-level).
  2. Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with source_build.rs, executable_task.rs, backend_metadata.rs. — One of this dimension's main actionable groups (3 warning-level).

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

D16 · Bus Factor9.7 / 10Exemplary✓ 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 9.7 / 10 · rule-coverage 100% · ceiling Documented

14 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is crates/pixi_toml_edit/src/entry.rs. Counted over 450 of the 628 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 · ×3
Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.9 / 10Stronggated by 94 serious findings✓ 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 9.9 / 10 · rule-coverage 100% · ceiling Prevented

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

TodoComment · ×92schema/model.py:1383
XxxCommenttests/integration_python/pixi_global/test_global.py:2816
HackCommentcrates/pixi_config/src/lib.rs:1879

What to do

  1. Resolve the 92 TodoComment finding(s) in Explicit Debt — start with mod.rs (13), lib.rs (7), import.rs (4). — One of this dimension's main actionable groups (92 warning-level).
  2. Resolve the 1 XxxComment finding(s) in Explicit Debt — start with test_global.py. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 HackComment finding(s) in Explicit Debt — start with lib.rs. — One of this dimension's main actionable groups (1 warning-level).

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

D19 · Documentation Quality10.0 / 10Exemplary○ Nothing flagged

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 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 documentation facets pass in full. 87 document(s) read across 1 unit(s).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

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

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

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundtrampoline/src/main.rs:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.rs. — 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.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)5.4 / 10Adequate✓ 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 5.4 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 3 high, 2 medium, 0 low. semgrep hit a parse error in 10 file(s) — `crates/pixi_build_python/src/main.rs` (line 1093), `crates/pixi_command_dispatcher/src/cache/artifact.rs` (line 1153, line 1732, line 1991, …), `crates/pixi_command_dispatcher/src/input_globs.rs` (line 54, line 98), `crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs` (line 580), `crates/pixi_command_dispatcher/src/keys/source_build.rs` (line 542, line 553, line 827), … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED

What to do

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

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

D30 · Dependency Vulnerabilities3.1 / 10Weak✓ 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. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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

38 finding(s): 0 critical, 0 high, 38 medium, 0 low.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 15 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (15). — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 12 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (12). — One of this dimension's main actionable groups (12 warning-level).
  3. Resolve the 9 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).

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

D31 · IaC & Container Security10.0 / 10Exemplary○ Nothing flagged

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

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

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

trivy and checkov found no infrastructure-as-code or container misconfigurations.

✓ On the Gold path — maintain.

Detailed fixes: d31_recommendation.md.

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

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

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

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

1 of 450 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/pixi_reporters/src/release_notes.rs. Counted over 450 of the 628 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned files with no living knowledge
Orphaned filecrates/pixi_reporters/src/release_notes.rs:1

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.8 / 10Stronggated by 7 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.8 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: run.rs↔lib.rs 71%; package_identifier.rs↔mod.rs 53%; table_name.rs↔pyproject.rs 50%

Change coupling: run.rs ↔ lib.rs · ×7crates/pixi_cli/src/run.rs:1

What to do

  1. Resolve the 7 Change coupling finding(s) in Change Coupling — start with run.rs (2), package_identifier.rs, table_name.rs. — One of this dimension's main actionable groups (7 warning-level).

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

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ 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 5.0 / 10 · rule-coverage 100% · ceiling Documented

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

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

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-Life10.0 / 10Exemplary✓ 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 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 3 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.8 / 10Exemplary✓ Tool-verified

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

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

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

AX2 · Stateful singletons10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.

Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.

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

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

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

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

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

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

AX8 · Test isolation0.0 / 10Critical✓ 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.

  • `pixi_api` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_build_discovery` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_build_type_conversions` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_cli` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_command_dispatcher` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_core` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_core` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_global` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_manifest` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_manifest` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_record` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • `pixi_uv_conversions` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.

What to do

  • Remove every production → test project reference: extract any shared test helper into a production support library (which the tests reference), or invert the dependency so the test project depends on production — not the reverse.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

DM4 · Rich vs anemic domain model10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether domain entities own their behaviour (invariant-enforcing commands) rather than being data-only structs driven by a foreign service.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

DM5 · Encapsulated state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether a domain type's identity-bearing field stays immutable — a `pub` mutable field under a hand-rolled Hash/PartialEq breaks the value-identity invariant.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

ES2 · Immutable events10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether domain events stay immutable (private fields, set once) rather than carrying mutable state.

Method: Roslyn scan (event-sourcing gated): persisted events checked for public setters; immutability verified per property/field. Deterministic, hard fact.

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

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

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

M1 · Documentation (README)7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture 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 repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

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

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

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

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

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

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

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code 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.

P2 · Observability6.1 / 10Adequate✓ 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 28/40 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `crates/pixi`, `crates/pixi_build_mojo`, `crates/pixi_build_r`, `crates/pixi_build_rust` and 7 more.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling3.0 / 10Weak✓ 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.

  • `scorecard.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.

What to do

  • Trigger your SAST workflow on pull requests — a scan that only runs on a cron reports history, it does not gate.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

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 each language's code 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.

  • `build_v1` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — crates/pixi_command_dispatcher/src/backend_source_build/mod.rs:159
  • `call_conda_outputs` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — crates/pixi_command_dispatcher/src/build_backend_metadata/mod.rs:529
  • `fetch_matching_output` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — crates/pixi_command_dispatcher/src/keys/source_build.rs:863

What to do

  • Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
X5 · Nullable reference types2.0 / 10Critical✓ 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.

  • 0/1 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.

What to do

  • Put every file in a nullable-enabled context — `#nullable enable` at its top, or commit a project file with <Nullable>enable</Nullable> — 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 Health56%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture67%Adequate — gated by AX8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity76%StrongSolid.
Readiness66%Adequate — gated by P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security84%StrongSolid.
Domain Modelling100%ExemplaryStrongest area.
Event Sourcing100%ExemplarySolid.
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 — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for

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

  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX6 Interface segregation — no public interfaces
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — pixi-example Pulling pixi-example Warning Get "http://localhost/v2/": dial tcp [::1]:80: connect: connection refused failed to solve: process "/bin/sh -c pixi install" did not complete successfully: exit code: 1; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — 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.
  • D10 Test Quality — ~61315 lines of test source are present (.py, .rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
  • D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D21 Naming Consistency — N/A — too few peers to establish a naming convention (18611 declarations, no unit with a dominant convention).
  • D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — 1 of 2 comment blocks were not judged (1 in a language other than English): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not measured — Rust suite
  • DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
  • DM2 Strongly-typed ids — the crate defines newtype typed-ids but declares no domain aggregate that could carry an id — so DM2's adoption ratio has no population to be taken over
  • DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
  • DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
  • 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 — no mutating command handlers or message consumers detected — idempotency check not applicable (this repository commits no MSBuild project, so its C# was read as syntax-only projects — a handler marked ONLY by an interface from a package is not visible without a build)
  • ES1 Fold determinism — not applicable — the code was read and holds no event-replay fold, so there is nothing for this check to judge
  • IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — 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 — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • 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.
  • X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no async method does work a token could cancel
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — This check needs a compiled C# program and this repository commits no project file to compile, so only its syntax could be read. That is a limit of the analyzer, not a finding about your code.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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 — 15 finding(s)
AX8 · Test isolation · Production project references a test project · ×12
  • Production project references a test project: pixi_api → pixi_pypi_spec — `pixi_api` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_build_discovery → pixi_spec_containers — `pixi_build_discovery` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_build_type_conversions → pixi_spec_containers — `pixi_build_type_conversions` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_cli → pixi_pypi_spec — `pixi_cli` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_command_dispatcher → pixi_spec_containers — `pixi_command_dispatcher` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_core → pixi_pypi_spec — `pixi_core` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_core → pixi_spec_containers — `pixi_core` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_global → pixi_spec_containers — `pixi_global` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_manifest → pixi_pypi_spec — `pixi_manifest` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_manifest → pixi_spec_containers — `pixi_manifest` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_record → pixi_spec_containers — `pixi_record` (production) references the test project `pixi_spec_containers`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
  • Production project references a test project: pixi_uv_conversions → pixi_pypi_spec — `pixi_uv_conversions` (production) references the test project `pixi_pypi_spec`. Production must never depend on test code — it pulls a unit-test framework and test fixtures into the shipped product and inverts the only correct direction (tests depend on production, never the reverse). Move any shared helper into a production support library, or invert the reference.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 834 finding(s)
D17 · Explicit Debt · TodoComment · ×92
  • TodoComment schema/model.py:1383 — # TODO: url and git source — 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 examples/rerun_example/nuscenes_dataset/nuscenes_dataset/__main__.py:165 — # TODO(#6889): We don't want the radius for the trajectory line to be the same as the radius of the points.
  • TodoComment crates/pypi_modifiers/src/pypi_tags.rs:57 — /// TODO: Add support for more variants. — 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 crates/pypi_modifiers/src/pypi_tags.rs:301 — // TODO: This might not be entirely correct.. — 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 crates/pypi_modifiers/src/pypi_tags.rs:352 — // TODO: Add more libc families for support of other linux distributions — 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 crates/pixi_uv_conversions/src/requirements.rs:184 — // TODO: we could see if we ever need 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 crates/pixi_utils/src/conda_environment_file.rs:161 — // TODO: should we be applying `config.channel_config` for parsed channels too? — 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 crates/pixi_utils/src/reqwest.rs:38 — /// TODO: At some point we might want to make this configurable. — 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 crates/pixi_task/src/error.rs:63 — // TODO: We should make this error much better — 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 crates/pixi_task/src/task_graph.rs:305 — // TODO: support named arguments from the CLI — 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 crates/pixi_spec/src/exclude_newer.rs:131 — // TODO: After https://github.com/conda/ceps/pull/154 we might need to rethink this
  • TodoComment crates/pixi_spec/src/path.rs:89 — // TODO: Contribute `impl FromStr for Utf8TypedPathBuf` to typed-path — 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 crates/pixi_reporters/src/uv_reporter.rs:229 — // TODO: figure out how to display this nicely — 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 crates/pixi_reporters/src/uv_reporter.rs:285 — // TODO: figure out how to display this nicely — 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 crates/pixi_reporters/src/uv_reporter.rs:320 — // TODO: figure out how to display this nicely — 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 crates/pixi_record/src/pinned_source.rs:486 — // TODO: this is a good place to type the url. — 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 crates/pixi_manifest/src/error.rs:182 — // TODO: Now we only take the first error, but we could make this smarter — 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 crates/pixi_manifest/src/pyproject.rs:206 — // TODO: would be nice to add license, license-file, readme, homepage, — 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 crates/pixi_manifest/src/pyproject.rs:254 — // TODO: implement some comparison or spec merging logic here — 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 crates/pixi_manifest/src/pyproject.rs:332 — // TODO: avoid going through string representation for conversion — 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 crates/pixi_manifest/src/target.rs:37 — /// TODO: While the pixi-build preview flag is not stabilized yet, a workspace — 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 crates/pixi_manifest/src/target.rs:450 — // TODO: would be nice to compare pep508 == PyPiRequirement directly — 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 crates/pixi_manifest/src/task.rs:683 — // TODO: In theory, this should check if no placeholders are left in the string — 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 crates/pixi_manifest/src/pypi/pypi_options.rs:97 — // Todo: would be nice to check if these are actually used at some point — 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 crates/pixi_manifest/src/manifests/document.rs:277 — // TODO: When `[package]` will become a standalone table, this method — 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.
  • + 67 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×42
  • FileTooLong: lock_file/update.rs crates/pixi_core/src/lock_file/update.rs — FileTooLong — 2482 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 1982 over it, 4.96× 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: src/lib.rs crates/pixi_config/src/lib.rs — FileTooLong — 1884 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 33 free functions. The bar is 500 significant lines; this is 1384 over it, 3.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: project/mod.rs crates/pixi_global/src/project/mod.rs — FileTooLong — 1578 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 68% of them inside a single declaration: Project (4 blocks, 530-2463). The bar is 500 significant lines; this is 1078 over it, 3.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: manifests/workspace.rs crates/pixi_manifest/src/manifests/workspace.rs — FileTooLong — 1481 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 68% of them inside a single declaration: WorkspaceManifestMut (2 blocks, 407-2082). The bar is 500 significant lines; this is 981 over it, 2.96× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: publish/mod.rs crates/pixi_cli/src/publish/mod.rs — FileTooLong — 1139 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 639 over it, 2.28× 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: workspace/mod.rs crates/pixi_core/src/workspace/mod.rs — FileTooLong — 1114 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 65% of them inside a single declaration: Workspace (4 blocks, 183-1606). The bar is 500 significant lines; this is 614 over it, 2.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: schema/model.py schema/model.py — FileTooLong — 1083 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 583 over it, 2.17× 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: satisfiability/platform.rs crates/pixi_core/src/lock_file/satisfiability/platform.rs — FileTooLong — 942 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 442 over it, 1.88× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: resolve/pypi.rs crates/pixi_core/src/lock_file/resolve/pypi.rs — FileTooLong — 930 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 430 over it, 1.86× 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: src/lib.rs crates/pixi_install_pypi/src/lib.rs — FileTooLong — 890 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 63% of them inside a single declaration: PyPIEnvironmentUpdater (2 blocks, 475-1344). The bar is 500 significant lines; this is 390 over it, 1.78× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: manifests/document.rs crates/pixi_manifest/src/manifests/document.rs — FileTooLong — 852 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 93% of them inside a single declaration: ManifestDocument (3 blocks, 26-1387). The bar is 500 significant lines; this is 352 over it, 1.70× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/lib.rs crates/pixi_build_backend_passthrough/src/lib.rs — FileTooLong — 836 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 336 over it, 1.67× 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: src/host.rs crates/pixi_core/src/host.rs — FileTooLong — 824 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 324 over it, 1.65× 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: src/intermediate_backend.rs crates/pixi_build_backend/src/intermediate_backend.rs — FileTooLong — 812 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 77% of them inside a single declaration: IntermediateBackend (3 blocks, 95-983). The bar is 500 significant lines; this is 312 over it, 1.62× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: workspace/platform.rs crates/pixi_cli/src/workspace/platform.rs — FileTooLong — 807 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 307 over it, 1.61× 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: toml/manifest.rs crates/pixi_manifest/src/toml/manifest.rs — FileTooLong — 790 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 72% of them inside a single declaration: TomlManifest (3 blocks, 47-1148). The bar is 500 significant lines; this is 290 over it, 1.58× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: build_backend_metadata/mod.rs crates/pixi_command_dispatcher/src/build_backend_metadata/mod.rs — FileTooLong — 767 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 70% of them inside a single declaration: BuildBackendMetadataInner (3 blocks, 189-1188). The bar is 500 significant lines; this is 267 over it, 1.53× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: keys/source_build.rs crates/pixi_command_dispatcher/src/keys/source_build.rs — FileTooLong — 757 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 257 over it, 1.51× 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: src/project_model.rs crates/pixi_build_types/src/project_model.rs — FileTooLong — 713 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). 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: toml/platform.rs crates/pixi_manifest/src/toml/platform.rs — FileTooLong — 708 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 208 over it, 1.42× 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: src/info.rs crates/pixi_cli/src/info.rs — FileTooLong — 669 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 169 over it, 1.34× 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: src/git.rs crates/pixi_git/src/git.rs — FileTooLong — 658 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 158 over it, 1.32× 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: src/config.rs crates/pixi_cli/src/config.rs — FileTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted). The bar is 500 significant lines; this is 144 over it, 1.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: workspace/workspace_mut.rs crates/pixi_core/src/workspace/workspace_mut.rs — FileTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), about 88% of them inside a single declaration: WorkspaceMut (3 blocks, 119-946). The bar is 500 significant lines; this is 123 over it, 1.25× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/platform.rs crates/pixi_manifest/src/platform.rs — FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), declaring 33 free functions. The bar is 500 significant lines; this is 115 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.
  • + 17 more in this group — see findings.md.
D3 · God Classes · MethodTooLong · ×36
  • MethodTooLong: UpdateContext.update crates/pixi_core/src/lock_file/update.rs:2595 — MethodTooLong — update runs 413 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 313 over it, 4.13× 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: TomlManifest.into_workspace_manifest crates/pixi_manifest/src/toml/manifest.rs:155 — MethodTooLong — into_workspace_manifest runs 383 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 283 over it, 3.83× 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: Config.set crates/pixi_config/src/lib.rs:2516 — MethodTooLong — set runs 314 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 214 over it, 3.14× 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: IntermediateBackend.conda_outputs crates/pixi_build_backend/src/intermediate_backend.rs:252 — MethodTooLong — conda_outputs runs 309 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 209 over it, 3.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: TomlPackage.into_manifest crates/pixi_manifest/src/toml/package.rs:350 — MethodTooLong — into_manifest runs 239 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 139 over it, 2.39× 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: RattlerBuildBackend.conda_outputs crates/pixi_build_rattler_build/src/protocol.rs:65 — MethodTooLong — conda_outputs runs 232 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 132 over it, 2.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: IntermediateBackend.conda_build_v1 crates/pixi_build_backend/src/intermediate_backend.rs:669 — MethodTooLong — conda_build_v1 runs 228 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 128 over it, 2.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: WorkspaceMut.update_dependencies crates/pixi_core/src/workspace/workspace_mut.rs:433 — MethodTooLong — update_dependencies runs 226 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: PythonGenerator.generate_recipe crates/pixi_build_python/src/main.rs:214 — MethodTooLong — generate_recipe runs 192 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 92 over it, 1.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: WorkspaceDiscoverer.discover crates/pixi_manifest/src/discovery.rs:361 — MethodTooLong — discover runs 187 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× 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: HostDetector.detect_registrations crates/pixi_core/src/host.rs:622 — MethodTooLong — detect_registrations runs 186 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 86 over it, 1.86× 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: RosGenerator.generate_recipe crates/pixi_build_ros/src/main.rs:46 — MethodTooLong — generate_recipe runs 178 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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: UpdateContextBuilder.finish crates/pixi_core/src/lock_file/update.rs:2298 — MethodTooLong — finish runs 177 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 77 over it, 1.77× 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: Package.new crates/pixi_api/src/workspace/list/package.rs:55 — MethodTooLong — new runs 173 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× 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: LockFileDerivedData.update_prefix crates/pixi_core/src/lock_file/update.rs:1408 — MethodTooLong — update_prefix runs 170 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× 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: CommandDispatcherBuilder.finish crates/pixi_command_dispatcher/src/command_dispatcher/builder.rs:358 — MethodTooLong — finish runs 157 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 57 over it, 1.57× 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: SolveCondaEnvironmentSpec.solve_on_blocking_pool crates/pixi_command_dispatcher/src/solve_conda/mod.rs:121 — MethodTooLong — solve_on_blocking_pool runs 155 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× 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: RattlerBuildBackend.conda_build_v1 crates/pixi_build_rattler_build/src/protocol.rs:366 — MethodTooLong — conda_build_v1 runs 154 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: Project.install_environment_with_options crates/pixi_global/src/project/mod.rs:1122 — MethodTooLong — install_environment_with_options runs 148 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 48 over it, 1.48× 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: BackendSourceBuildSpec.build_v1 crates/pixi_command_dispatcher/src/backend_source_build/mod.rs:159 — MethodTooLong — build_v1 runs 140 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 40 over it, 1.40× 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: Item.from crates/pixi_manifest/src/task.rs:867 — MethodTooLong — from runs 133 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× 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: CachedWheels.is_cached crates/pixi_install_pypi/src/plan/cache.rs:100 — MethodTooLong — is_cached runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: TomlTarget.into_workspace_target crates/pixi_manifest/src/toml/target.rs:54 — MethodTooLong — into_workspace_target runs 125 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× 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: BuildBackendMetadataInner.compute_inner crates/pixi_command_dispatcher/src/build_backend_metadata/mod.rs:1017 — MethodTooLong — compute_inner runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: TomlManifest.deserialize crates/pixi_manifest/src/toml/manifest.rs:984 — MethodTooLong — deserialize runs 124 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • + 11 more in this group — see findings.md.
D2 · Cognitive Complexity · pixi_cli · ×33
  • pixi_cli::publish::execute (cognitive 64) crates/pixi_cli/src/publish/mod.rs:562 — pixi_cli::publish::execute has cognitive complexity 64 (threshold 15). Drivers by points: if/else 25 (39 pts), loops 11 (17 pts), boolean chains 5, match/switch 3 (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.
  • pixi_cli::update::expand_specs_for_shared_git_sources (cognitive 59) crates/pixi_cli/src/update.rs:369 — pixi_cli::update::expand_specs_for_shared_git_sources has cognitive complexity 59 (threshold 15). Drivers by points: if/else 14 (42 pts), loops 7 (13 pts), boolean chains 4 (nesting depth added 34). 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.
  • pixi_cli::upgrade::execute (cognitive 52) crates/pixi_cli/src/upgrade.rs:76 — pixi_cli::upgrade::execute has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (39 pts), boolean chains 6, loops 3 (5 pts), match/switch 1 (2 pts) (nesting depth added 22). 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.
  • pixi_cli::config::alter_config (cognitive 41) crates/pixi_cli/src/config.rs:439 — pixi_cli::config::alter_config has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (31 pts), boolean chains 5, match/switch 4 (5 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_cli::install::execute (cognitive 36) crates/pixi_cli/src/install.rs:114 — pixi_cli::install::execute has cognitive complexity 36 (threshold 15). Drivers by points: if/else 22 (35 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.
  • pixi_cli::info::execute (cognitive 35) crates/pixi_cli/src/info.rs:658 — pixi_cli::info::execute has cognitive complexity 35 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 11 (15 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 17). 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.
  • pixi_cli::publish::discovery::resolve_publish_set (cognitive 32) crates/pixi_cli/src/publish/discovery.rs:67 — pixi_cli::publish::discovery::resolve_publish_set has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 3 (6 pts), match/switch 1 (4 pts) (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.
  • pixi_cli::add::resolve_dependency_path (cognitive 31) crates/pixi_cli/src/add.rs:234 — pixi_cli::add::resolve_dependency_path has cognitive complexity 31 (threshold 15). Drivers by points: if/else 18 (29 pts), boolean chains 1, match/switch 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_cli::run::execute (cognitive 31) crates/pixi_cli/src/run.rs:153 — pixi_cli::run::execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (21 pts), loops 2 (4 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • pixi_cli::command_info::find_external_commands (cognitive 28) crates/pixi_cli/src/command_info.rs:68 — pixi_cli::command_info::find_external_commands has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (22 pts), loops 2 (6 pts) (nesting depth added 21). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • pixi_cli::search::execute_impl (cognitive 28) crates/pixi_cli/src/search.rs:86 — pixi_cli::search::execute_impl has cognitive complexity 28 (threshold 15). Drivers by points: if/else 17 (22 pts), boolean chains 3, loops 1 (2 pts), match/switch 1 (nesting depth added 6). 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.
  • pixi_cli::search::print_package_info (cognitive 28) crates/pixi_cli/src/search.rs:373 — pixi_cli::search::print_package_info has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 6 (11 pts), match/switch 3, boolean chains 1 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • pixi_cli::workspace::activation::list (cognitive 27) crates/pixi_cli/src/workspace/activation.rs:280 — pixi_cli::workspace::activation::list has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (7 pts), match/switch 4 (5 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_cli::config::transplant_config_key (cognitive 26) crates/pixi_cli/src/config.rs:711 — pixi_cli::config::transplant_config_key has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 2, loops 2, match/switch 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_cli::workspace::exclude_newer::execute (cognitive 26) crates/pixi_cli/src/workspace/exclude_newer.rs:386 — pixi_cli::workspace::exclude_newer::execute has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 2 (4 pts), match/switch 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.
  • pixi_cli::workspace::export::conda_environment::build_env_yaml (cognitive 26) crates/pixi_cli/src/workspace/export/conda_environment.rs:149 — pixi_cli::workspace::export::conda_environment::build_env_yaml has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 4 (9 pts), match/switch 1 (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.
  • pixi_cli::search::print_search_results (cognitive 25) crates/pixi_cli/src/search.rs:237 — pixi_cli::search::print_search_results has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (19 pts), loops 3 (4 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.
  • pixi_cli::workspace::dependencies::execute (cognitive 25) crates/pixi_cli/src/workspace/dependencies.rs:112 — pixi_cli::workspace::dependencies::execute has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 4 (8 pts), boolean chains 1, match/switch 1 (nesting depth added 11). 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.
  • pixi_cli::add::execute (cognitive 24) crates/pixi_cli/src/add.rs:406 — pixi_cli::add::execute has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4, match/switch 2 (4 pts), loops 1 (nesting depth added 5). 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.
  • pixi_cli::lock::execute (cognitive 24) crates/pixi_cli/src/lock.rs:46 — pixi_cli::lock::execute has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 3, loops 1 (2 pts), match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
  • pixi_cli::publish::discovery::discover_opted_in_packages (cognitive 23) crates/pixi_cli/src/publish/discovery.rs:289 — pixi_cli::publish::discovery::discover_opted_in_packages has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 2 (4 pts), loops 3, boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_cli::clean::execute (cognitive 21) crates/pixi_cli/src/clean.rs:120 — pixi_cli::clean::execute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_cli::workspace::export::conda_environment::build_env_yaml_from_lock_file (cognitive 21) crates/pixi_cli/src/workspace/export/conda_environment.rs:273 — pixi_cli::workspace::export::conda_environment::build_env_yaml_from_lock_file has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (7 pts), match/switch 2 (6 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_cli::exec::execute (cognitive 19) crates/pixi_cli/src/exec.rs:85 — pixi_cli::exec::execute has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, loops 1, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_cli::clean::remove_dir_recording_size (cognitive 18) crates/pixi_cli/src/clean.rs:380 — pixi_cli::clean::remove_dir_recording_size has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (9 pts), if/else 4 (6 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 8). 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.
  • + 8 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×32
  • Hotspot: crates/pixi_config/src/lib.rs crates/pixi_config/src/lib.rs:2516 — crates/pixi_config/src/lib.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 97 in Config::set at line 2516. 3 of those changes were fix/bug commits, and the other 9 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_config/src/lib.rs`: 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: crates/pixi_core/src/lock_file/update.rs crates/pixi_core/src/lock_file/update.rs:3483 — crates/pixi_core/src/lock_file/update.rs changed 22 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in pixi_core::lock_file::update::spawn_extract_environment_task at line 3483. 5 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_core/src/lock_file/update.rs`: 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: crates/pixi_cli/src/publish/mod.rs crates/pixi_cli/src/publish/mod.rs:562 — crates/pixi_cli/src/publish/mod.rs changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 45 in pixi_cli::publish::execute at line 562. 4 of those changes were fix/bug commits, and the other 9 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_cli/src/publish/mod.rs`: 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: crates/pixi_core/src/lock_file/satisfiability/platform.rs crates/pixi_core/src/lock_file/satisfiability/platform.rs:630 — crates/pixi_core/src/lock_file/satisfiability/platform.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability at line 630. 1 of those changes was a fix/bug commit, and the other 7 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_core/src/lock_file/satisfiability/platform.rs`: 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: crates/pixi_global/src/project/mod.rs crates/pixi_global/src/project/mod.rs:1621 — crates/pixi_global/src/project/mod.rs changed 25 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in Project::environment_in_sync_internal at line 1621. 2 of those changes were fix/bug commits, and the other 23 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_global/src/project/mod.rs`: 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: crates/pixi_core/src/lock_file/satisfiability/pypi.rs crates/pixi_core/src/lock_file/satisfiability/pypi.rs:136 — crates/pixi_core/src/lock_file/satisfiability/pypi.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in pixi_core::lock_file::satisfiability::pypi::pypi_satisfies_requirement at line 136. 2 of those changes were fix/bug commits, and the other 9 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_core/src/lock_file/satisfiability/pypi.rs`: 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: crates/pixi_cli/src/config.rs crates/pixi_cli/src/config.rs:439 — crates/pixi_cli/src/config.rs changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in pixi_cli::config::alter_config at line 439. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_cli/src/config.rs`: 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: crates/pixi_cli/src/run.rs crates/pixi_cli/src/run.rs:153 — crates/pixi_cli/src/run.rs changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 22 in pixi_cli::run::execute at line 153. 3 of those changes were fix/bug commits, and the other 13 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_cli/src/run.rs`: 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: crates/pixi_manifest/src/toml/manifest.rs crates/pixi_manifest/src/toml/manifest.rs:155 — crates/pixi_manifest/src/toml/manifest.rs changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in TomlManifest::into_workspace_manifest at line 155. 4 of those changes were fix/bug commits, and the other 7 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_manifest/src/toml/manifest.rs`: 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: crates/pixi_core/src/workspace/workspace_mut.rs crates/pixi_core/src/workspace/workspace_mut.rs:433 — crates/pixi_core/src/workspace/workspace_mut.rs changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in WorkspaceMut::update_dependencies at line 433. 3 of those changes were fix/bug commits, and the other 9 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_core/src/workspace/workspace_mut.rs`: 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: crates/pixi_core/src/workspace/discovery.rs crates/pixi_core/src/workspace/discovery.rs:362 — crates/pixi_core/src/workspace/discovery.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in WorkspaceLocator::locate at line 362. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_core/src/workspace/discovery.rs`: 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: crates/pixi_core/src/lock_file/resolve/pypi.rs crates/pixi_core/src/lock_file/resolve/pypi.rs:334 — crates/pixi_core/src/lock_file/resolve/pypi.rs changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in pixi_core::lock_file::resolve::pypi::resolve_pypi at line 334. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_core/src/lock_file/resolve/pypi.rs`: 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: crates/pixi_cli/src/upgrade.rs crates/pixi_cli/src/upgrade.rs:76 — crates/pixi_cli/src/upgrade.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in pixi_cli::upgrade::execute 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_cli/src/upgrade.rs`: 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: crates/pixi_cli/src/search.rs crates/pixi_cli/src/search.rs:86 — crates/pixi_cli/src/search.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in pixi_cli::search::execute_impl at line 86. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_cli/src/search.rs`: 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: crates/pixi_cli/src/add.rs crates/pixi_cli/src/add.rs:406 — crates/pixi_cli/src/add.rs changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in pixi_cli::add::execute at line 406. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_cli/src/add.rs`: 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: crates/pixi_cli/src/lock.rs crates/pixi_cli/src/lock.rs:46 — crates/pixi_cli/src/lock.rs changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in pixi_cli::lock::execute at line 46. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_cli/src/lock.rs`: 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: crates/pixi_core/src/lock_file/satisfiability/environment.rs crates/pixi_core/src/lock_file/satisfiability/environment.rs:33 — crates/pixi_core/src/lock_file/satisfiability/environment.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in pixi_core::lock_file::satisfiability::environment::verify_environment_satisfiability at line 33. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_core/src/lock_file/satisfiability/environment.rs`: 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: crates/pixi_cli/src/install.rs crates/pixi_cli/src/install.rs:114 — crates/pixi_cli/src/install.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in pixi_cli::install::execute at line 114. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_cli/src/install.rs`: 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: crates/pixi_task/src/task_graph.rs crates/pixi_task/src/task_graph.rs:226 — crates/pixi_task/src/task_graph.rs changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in TaskGraph::from_cmd_args at line 226. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_task/src/task_graph.rs`: 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: crates/pixi_install_pypi/src/plan/validation.rs crates/pixi_install_pypi/src/plan/validation.rs:47 — crates/pixi_install_pypi/src/plan/validation.rs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 37 in pixi_install_pypi::plan::validation::need_reinstall at line 47. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_install_pypi/src/plan/validation.rs`: 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: crates/pixi_build_python/src/main.rs crates/pixi_build_python/src/main.rs:214 — crates/pixi_build_python/src/main.rs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in PythonGenerator::generate_recipe at line 214. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_build_python/src/main.rs`: 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: crates/pixi_command_dispatcher/src/cache/artifact.rs crates/pixi_command_dispatcher/src/cache/artifact.rs:583 — crates/pixi_command_dispatcher/src/cache/artifact.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in ArtifactCache::lookup at line 583. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_command_dispatcher/src/cache/artifact.rs`: 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: crates/pixi_manifest/src/platform/host.rs crates/pixi_manifest/src/platform/host.rs:141 — crates/pixi_manifest/src/platform/host.rs changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in pixi_manifest::platform::host::apply_conda_overrides at line 141. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_manifest/src/platform/host.rs`: 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: crates/pixi_global/src/common.rs crates/pixi_global/src/common.rs:529 — crates/pixi_global/src/common.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in pixi_global::common::build_report at line 529. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_global/src/common.rs`: 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: crates/pixi_core/src/workspace/errors.rs crates/pixi_core/src/workspace/errors.rs:293 — crates/pixi_core/src/workspace/errors.rs changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in pixi_core::workspace::errors::conda_override_hint 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_core/src/workspace/errors.rs`: 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.
  • + 7 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×32
  • FunctionTooLong: pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability crates/pixi_core/src/lock_file/satisfiability/platform.rs:630 — FunctionTooLong — pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability runs 442 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 342 over it, 4.42× 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.
  • FunctionTooLong: pixi_cli::publish::execute crates/pixi_cli/src/publish/mod.rs:562 — FunctionTooLong — pixi_cli::publish::execute runs 440 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 340 over it, 4.40× 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.
  • FunctionTooLong: pixi_core::lock_file::resolve::pypi::resolve_pypi crates/pixi_core/src/lock_file/resolve/pypi.rs:334 — FunctionTooLong — pixi_core::lock_file::resolve::pypi::resolve_pypi runs 412 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 312 over it, 4.12× 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.
  • FunctionTooLong: pixi_command_dispatcher::keys::source_build::compute_inner crates/pixi_command_dispatcher/src/keys/source_build.rs:239 — FunctionTooLong — pixi_command_dispatcher::keys::source_build::compute_inner runs 355 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 255 over it, 3.55× 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.
  • FunctionTooLong: pixi_command_dispatcher::keys::resolve_source_record::assemble_source_record_inner crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:112 — FunctionTooLong — pixi_command_dispatcher::keys::resolve_source_record::assemble_source_record_inner runs 268 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 168 over it, 2.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: pixi_install_pypi::plan::validation::need_reinstall crates/pixi_install_pypi/src/plan/validation.rs:47 — FunctionTooLong — pixi_install_pypi::plan::validation::need_reinstall runs 218 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× 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.
  • FunctionTooLong: pixi_core::lock_file::resolve::pypi::lock_pypi_packages crates/pixi_core/src/lock_file/resolve/pypi.rs:1082 — FunctionTooLong — pixi_core::lock_file::resolve::pypi::lock_pypi_packages runs 210 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 110 over it, 2.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.
  • FunctionTooLong: pixi_cli::run::execute crates/pixi_cli/src/run.rs:153 — FunctionTooLong — pixi_cli::run::execute runs 194 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 94 over it, 1.94× 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.
  • FunctionTooLong: pixi_api::workspace::run::run crates/pixi_api/src/workspace/run/mod.rs:155 — FunctionTooLong — pixi_api::workspace::run::run runs 193 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 93 over it, 1.93× 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.
  • FunctionTooLong: pixi_core::lock_file::satisfiability::pypi::pypi_satisfies_requirement crates/pixi_core/src/lock_file/satisfiability/pypi.rs:136 — FunctionTooLong — pixi_core::lock_file::satisfiability::pypi::pypi_satisfies_requirement runs 190 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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.
  • FunctionTooLong: pixi_core::lock_file::update::spawn_extract_environment_task crates/pixi_core/src/lock_file/update.rs:3483 — FunctionTooLong — pixi_core::lock_file::update::spawn_extract_environment_task runs 188 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 88 over it, 1.88× 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.
  • FunctionTooLong: pixi_cli::upgrade::execute crates/pixi_cli/src/upgrade.rs:76 — FunctionTooLong — pixi_cli::upgrade::execute runs 180 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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.
  • FunctionTooLong: pixi_cli::info::execute crates/pixi_cli/src/info.rs:658 — FunctionTooLong — pixi_cli::info::execute runs 178 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 78 over it, 1.78× 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.
  • FunctionTooLong: pixi_core::lock_file::satisfiability::pypi::read_local_package_metadata crates/pixi_core/src/lock_file/satisfiability/pypi.rs:605 — FunctionTooLong — pixi_core::lock_file::satisfiability::pypi::read_local_package_metadata runs 175 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: pixi_cli::search::print_package_info crates/pixi_cli/src/search.rs:373 — FunctionTooLong — pixi_cli::search::print_package_info runs 174 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 74 over it, 1.74× 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.
  • FunctionTooLong: pixi_build_backend::rattler_build_integration::get_build_output crates/pixi_build_backend/src/rattler_build_integration.rs:33 — FunctionTooLong — pixi_build_backend::rattler_build_integration::get_build_output runs 165 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× 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.
  • FunctionTooLong: pixi_core::lock_file::outdated::find_unsatisfiable_targets crates/pixi_core/src/lock_file/outdated.rs:240 — FunctionTooLong — pixi_core::lock_file::outdated::find_unsatisfiable_targets runs 164 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× 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.
  • FunctionTooLong: pixi_command_dispatcher::install_pixi::ext::install_inner crates/pixi_command_dispatcher/src/install_pixi/ext.rs:98 — FunctionTooLong — pixi_command_dispatcher::install_pixi::ext::install_inner runs 162 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 62 over it, 1.62× 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.
  • FunctionTooLong: pixi_cli::add::execute crates/pixi_cli/src/add.rs:406 — FunctionTooLong — pixi_cli::add::execute runs 153 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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.
  • FunctionTooLong: pixi_core::lock_file::satisfiability::environment::verify_environment_satisfiability crates/pixi_core/src/lock_file/satisfiability/environment.rs:33 — FunctionTooLong — pixi_core::lock_file::satisfiability::environment::verify_environment_satisfiability runs 145 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× 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.
  • FunctionTooLong: pixi_cli::install::execute crates/pixi_cli/src/install.rs:114 — FunctionTooLong — pixi_cli::install::execute runs 143 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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.
  • FunctionTooLong: pixi_core::lock_file::satisfiability::source_record::verify_locked_run_deps_against_backend crates/pixi_core/src/lock_file/satisfiability/source_record.rs:231 — FunctionTooLong — pixi_core::lock_file::satisfiability::source_record::verify_locked_run_deps_against_backend runs 143 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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.
  • FunctionTooLong: pixi_cli::conda_script::execute_run crates/pixi_cli/src/conda_script.rs:68 — FunctionTooLong — pixi_cli::conda_script::execute_run runs 142 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× 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.
  • FunctionTooLong: pixi_core::lock_file::satisfiability::platform::verify_platform_satisfiability crates/pixi_core/src/lock_file/satisfiability/platform.rs:183 — FunctionTooLong — pixi_core::lock_file::satisfiability::platform::verify_platform_satisfiability runs 132 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: pixi_core::lock_file::update::spawn_solve_conda_environment_task crates/pixi_core/src/lock_file/update.rs:3276 — FunctionTooLong — pixi_core::lock_file::update::spawn_solve_conda_environment_task runs 129 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× 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.
  • + 7 more in this group — see findings.md.
D5 · Coupling · Off the main sequence · ×18
  • Off the main sequence: barrier_cell — barrier_cell: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: pixi_consts — pixi_consts: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 15 project(s), so it's rigid to change.
  • Off the main sequence: pixi_progress — pixi_progress: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
  • Off the main sequence: pixi_pty — pixi_pty: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: pixi_script_shell — pixi_script_shell: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: pixi_toml_edit — pixi_toml_edit: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: pixi_build_types — pixi_build_types: abstractness 0.00, instability 0.05, distance 0.95 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
  • Off the main sequence: pypi_mapping — pypi_mapping: abstractness 0.05, instability 0.00, distance 0.95 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
  • Off the main sequence: pixi_config — pixi_config: abstractness 0.00, instability 0.10, distance 0.90 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
  • Off the main sequence: pixi_path — pixi_path: abstractness 0.14, instability 0.00, distance 0.86 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
  • Off the main sequence: pixi_compute_engine — pixi_compute_engine: abstractness 0.15, instability 0.00, distance 0.85 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
  • Off the main sequence: pixi_git — pixi_git: abstractness 0.05, instability 0.10, distance 0.85 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
  • Off the main sequence: pixi_toml — pixi_toml: abstractness 0.15, instability 0.00, distance 0.85 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: pixi_glob — pixi_glob: 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.
  • Off the main sequence: pixi_variant — pixi_variant: abstractness 0.00, instability 0.25, distance 0.75 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: pixi_spec — pixi_spec: abstractness 0.00, instability 0.28, distance 0.72 — zone of pain — concrete and depended on by 13 project(s), so it's rigid to change.
  • Off the main sequence: pixi_utils — pixi_utils: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 10 project(s), so it's rigid to change.
  • Off the main sequence: pixi_compute_reporters — pixi_compute_reporters: abstractness 0.13, instability 0.17, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
D2 · Cognitive Complexity · pixi_core · ×17
  • pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability (cognitive 172) crates/pixi_core/src/lock_file/satisfiability/platform.rs:630 — pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability has cognitive complexity 172 (threshold 15). Drivers by points: if/else 40 (112 pts), match/switch 13 (40 pts), loops 6 (12 pts), boolean chains 8 (nesting depth added 105). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • pixi_core::lock_file::update::spawn_extract_environment_task (cognitive 96) crates/pixi_core/src/lock_file/update.rs:3483 — pixi_core::lock_file::update::spawn_extract_environment_task has cognitive complexity 96 (threshold 15). Drivers by points: if/else 19 (52 pts), loops 14 (38 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 59). 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.
  • pixi_core::lock_file::satisfiability::pypi::pypi_satisfies_requirement (cognitive 85) crates/pixi_core/src/lock_file/satisfiability/pypi.rs:136 — pixi_core::lock_file::satisfiability::pypi::pypi_satisfies_requirement has cognitive complexity 85 (threshold 15). Drivers by points: if/else 26 (70 pts), match/switch 4 (10 pts), boolean chains 5 (nesting depth added 50). 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.
  • pixi_core::lock_file::outdated::find_unsatisfiable_targets (cognitive 44) crates/pixi_core/src/lock_file/outdated.rs:240 — pixi_core::lock_file::outdated::find_unsatisfiable_targets has cognitive complexity 44 (threshold 15). Drivers by points: loops 10 (19 pts), if/else 7 (17 pts), match/switch 3 (8 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_core::lock_file::outdated::find_inconsistent_solve_groups (cognitive 38) crates/pixi_core/src/lock_file/outdated.rs:556 — pixi_core::lock_file::outdated::find_inconsistent_solve_groups has cognitive complexity 38 (threshold 15). Drivers by points: if/else 6 (17 pts), match/switch 3 (14 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 25). 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.
  • pixi_core::lock_file::satisfiability::platform::verify_platform_satisfiability (cognitive 34) crates/pixi_core/src/lock_file/satisfiability/platform.rs:183 — pixi_core::lock_file::satisfiability::platform::verify_platform_satisfiability has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (14 pts), match/switch 6 (14 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_core::lock_file::update::warn_unknown_requested_extras (cognitive 33) crates/pixi_core/src/lock_file/update.rs:1855 — pixi_core::lock_file::update::warn_unknown_requested_extras has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 5 (11 pts) (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.
  • pixi_core::lock_file::satisfiability::environment::verify_environment_satisfiability (cognitive 32) crates/pixi_core/src/lock_file/satisfiability/environment.rs:33 — pixi_core::lock_file::satisfiability::environment::verify_environment_satisfiability has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (20 pts), loops 3 (6 pts), match/switch 2 (4 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_core::lock_file::resolve::pypi::resolve_pypi (cognitive 31) crates/pixi_core/src/lock_file/resolve/pypi.rs:334 — pixi_core::lock_file::resolve::pypi::resolve_pypi has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (21 pts), match/switch 5, loops 3, 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.
  • pixi_core::lock_file::satisfiability::pypi_metadata::expand_self_extras (cognitive 30) crates/pixi_core/src/lock_file/satisfiability/pypi_metadata.rs:129 — pixi_core::lock_file::satisfiability::pypi_metadata::expand_self_extras has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 3 (8 pts), match/switch 1 (2 pts) (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.
  • pixi_core::lock_file::utils::filter_lock_file (cognitive 28) crates/pixi_core/src/lock_file/utils.rs:65 — pixi_core::lock_file::utils::filter_lock_file has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 3 (6 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_core::environment::extract_git_requirements_from_workspace (cognitive 27) crates/pixi_core/src/environment/mod.rs:720 — pixi_core::environment::extract_git_requirements_from_workspace has cognitive complexity 27 (threshold 15). Drivers by points: loops 6 (17 pts), if/else 2 (10 pts) (nesting depth added 19). 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.
  • pixi_core::lock_file::resolve::pypi::lock_pypi_packages (cognitive 20) crates/pixi_core/src/lock_file/resolve/pypi.rs:1082 — pixi_core::lock_file::resolve::pypi::lock_pypi_packages has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (17 pts), if/else 1 (2 pts), loops 1 (nesting depth added 13). 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.
  • pixi_core::lock_file::platform_rename::rebuild_with_renames (cognitive 17) crates/pixi_core/src/lock_file/platform_rename.rs:175 — pixi_core::lock_file::platform_rename::rebuild_with_renames has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (7 pts), loops 3 (6 pts), match/switch 1 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_core::lock_file::satisfiability::pypi::lock_pypi_packages (cognitive 16) crates/pixi_core/src/lock_file/satisfiability/pypi.rs:470 — pixi_core::lock_file::satisfiability::pypi::lock_pypi_packages has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_core::lock_file::satisfiability::source_record::diff_dep_sequences (cognitive 16) crates/pixi_core/src/lock_file/satisfiability/source_record.rs:561 — pixi_core::lock_file::satisfiability::source_record::diff_dep_sequences has cognitive complexity 16 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 4 (5 pts), boolean chains 2 (nesting depth added 5). 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.
  • pixi_core::workspace::implicit_script_platforms (cognitive 16) crates/pixi_core/src/workspace/mod.rs:335 — pixi_core::workspace::implicit_script_platforms has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×16
  • Duplicated block (8 lines × 2) crates/pixi_api/src/workspace/shell/mod.rs:129 — crates/pixi_api/src/workspace/shell/mod.rs:129-136 | crates/pixi_api/src/workspace/shell/mod.rs:167-174 — 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 `crates/pixi_api/src/workspace/shell/mod.rs:129` 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, `crates/pixi_api/src/workspace/shell/mod.rs:126` calls `arg` and `crates/pixi_api/src/workspace/shell/mod.rs:165` 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 (8 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:673 — crates/pixi_build_backend/src/intermediate_backend.rs:673-680 | crates/pixi_build_rattler_build/src/protocol.rs:370-377 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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 (8 lines × 2) crates/pixi_command_dispatcher/src/cache/artifact.rs:603 — crates/pixi_command_dispatcher/src/cache/artifact.rs:603-610 | crates/pixi_command_dispatcher/src/cache/artifact.rs:768-775 — 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 `crates/pixi_command_dispatcher/src/cache/artifact.rs:603` 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 (8 lines × 2) crates/pixi_core/src/lock_file/satisfiability/source_record.rs:298 — crates/pixi_core/src/lock_file/satisfiability/source_record.rs:298-305 | crates/pixi_core/src/lock_file/satisfiability/source_record.rs:313-320 — 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 `crates/pixi_core/src/lock_file/satisfiability/source_record.rs:298` 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 (8 lines × 2) crates/pixi_global/src/project/parsed_manifest.rs:208 — crates/pixi_global/src/project/parsed_manifest.rs:208-215 | crates/pixi_global/src/project/parsed_manifest.rs:239-246 — 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 `crates/pixi_global/src/project/parsed_manifest.rs:208` 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. 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) crates/pixi_manifest/src/manifests/workspace.rs:838 — crates/pixi_manifest/src/manifests/workspace.rs:838-845 | crates/pixi_manifest/src/manifests/workspace.rs:960-967 — 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 `crates/pixi_manifest/src/manifests/workspace.rs:838` 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 (8 lines × 2) crates/pixi_manifest/src/toml/exclude_newer.rs:128 — crates/pixi_manifest/src/toml/exclude_newer.rs:128-135 | crates/pixi_manifest/src/toml/exclude_newer.rs: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.
  • Duplicated block (8 lines × 2) crates/pixi_record/src/lib.rs:71 — crates/pixi_record/src/lib.rs:71-78 | crates/pixi_record/src/lib.rs:374-381 — 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 `crates/pixi_record/src/lib.rs:71` 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.
  • Duplicated block (8 lines × 2) crates/pixi_utils/src/reqwest.rs:344 — crates/pixi_utils/src/reqwest.rs:344-351 | crates/pixi_utils/src/reqwest.rs:364-371 — 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) crates/pixi_manifest/src/toml/build_backend.rs:319 — crates/pixi_manifest/src/toml/build_backend.rs:319-326 | crates/pixi_manifest/src/toml/build_target.rs:17-24 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (8 lines × 2) crates/pixi_core/src/workspace/mod.rs:1441 — crates/pixi_core/src/workspace/mod.rs:1441-1448 | crates/pixi_global/src/project/mod.rs:2194-2201 — 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) crates/pixi_utils/src/executable_utils.rs:57 — crates/pixi_utils/src/executable_utils.rs:57-64 | trampoline/src/executable_from_path.rs:61-68 — before extracting anything, compare `crates/pixi_utils/src/executable_utils.rs` and `trampoline/src/executable_from_path.rs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) crates/pixi_build_python/src/metadata.rs:290 — crates/pixi_build_python/src/metadata.rs:290-297 | crates/pixi_build_python/src/metadata.rs:308-315 — 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 `crates/pixi_build_python/src/metadata.rs:290` 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, `crates/pixi_build_python/src/metadata.rs:317` calls `or_else`, `get` and `crates/pixi_build_python/src/metadata.rs:299` 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 × 2) crates/pixi_config/src/lib.rs:2602 — crates/pixi_config/src/lib.rs:2602-2609 | crates/pixi_config/src/lib.rs:2630-2637 — 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 `crates/pixi_config/src/lib.rs:2602` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (8 lines × 2) crates/pixi_spec/src/toml.rs:1305 — crates/pixi_spec/src/toml.rs:1305-1312 | crates/pixi_spec/src/toml.rs:1456-1463 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/pixi_spec/src/toml.rs:1316` calls `Some` and `crates/pixi_spec/src/toml.rs:1467` 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 (8 lines × 2) crates/pixi_spec/src/url.rs:110 — crates/pixi_spec/src/url.rs:110-117 | crates/pixi_spec/src/url.rs:213-220 — 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 `crates/pixi_spec/src/url.rs:110` 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.
D1 · Cyclomatic Complexity · pixi_cli · ×15
  • pixi_cli::publish::execute (cyclomatic 45) crates/pixi_cli/src/publish/mod.rs:562 — pixi_cli::publish::execute has cyclomatic complexity 45 (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.
  • pixi_cli::list::get_field_cell (cyclomatic 29) crates/pixi_cli/src/list.rs:284 — pixi_cli::list::get_field_cell has cyclomatic complexity 29 (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.
  • pixi_cli::upgrade::execute (cyclomatic 29) crates/pixi_cli/src/upgrade.rs:76 — pixi_cli::upgrade::execute 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.
  • pixi_cli::config::alter_config (cyclomatic 26) crates/pixi_cli/src/config.rs:439 — pixi_cli::config::alter_config 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.
  • pixi_cli::update::expand_specs_for_shared_git_sources (cyclomatic 26) crates/pixi_cli/src/update.rs:369 — pixi_cli::update::expand_specs_for_shared_git_sources 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.
  • pixi_cli::run::execute (cyclomatic 22) crates/pixi_cli/src/run.rs:153 — pixi_cli::run::execute has cyclomatic complexity 22 (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.
  • pixi_cli::config::transplant_config_key (cyclomatic 20) crates/pixi_cli/src/config.rs:711 — pixi_cli::config::transplant_config_key has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • pixi_cli::search::print_package_info (cyclomatic 20) crates/pixi_cli/src/search.rs:373 — pixi_cli::search::print_package_info has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
  • pixi_cli::workspace::activation::list (cyclomatic 20) crates/pixi_cli/src/workspace/activation.rs:280 — pixi_cli::workspace::activation::list has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
  • pixi_cli::workspace::exclude_newer::execute (cyclomatic 20) crates/pixi_cli/src/workspace/exclude_newer.rs:386 — pixi_cli::workspace::exclude_newer::execute has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • pixi_cli::install::execute (cyclomatic 19) crates/pixi_cli/src/install.rs:114 — pixi_cli::install::execute 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.
  • pixi_cli::search::execute_impl (cyclomatic 18) crates/pixi_cli/src/search.rs:86 — pixi_cli::search::execute_impl 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.
  • pixi_cli::add::execute (cyclomatic 17) crates/pixi_cli/src/add.rs:406 — pixi_cli::add::execute 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.
  • pixi_cli::upgrade::parse_specs (cyclomatic 17) crates/pixi_cli/src/upgrade.rs:461 — pixi_cli::upgrade::parse_specs has cyclomatic complexity 17 (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.
  • pixi_cli::lock::execute (cyclomatic 16) crates/pixi_cli/src/lock.rs:46 — pixi_cli::lock::execute 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.
D30 · Dependency Vulnerabilities · Medium advisory (unsound) · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D3 · God Classes · ClassTooLong · ×14
  • ClassTooLong: Project crates/pixi_global/src/project/mod.rs:530 — ClassTooLong — 1075 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 51 methods, 4 blocks, lines 530-2463. The bar is 400 significant lines; this is 675 over it, 2.69× 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: WorkspaceManifestMut crates/pixi_manifest/src/manifests/workspace.rs:407 — ClassTooLong — 1010 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 46 methods, 2 blocks, lines 407-2082. The bar is 400 significant lines; this is 610 over it, 2.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: Config crates/pixi_config/src/lib.rs:1263 — ClassTooLong — 918 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 45 methods, 8 blocks, lines 850-3113. The bar is 400 significant lines; this is 518 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.
  • ClassTooLong: ManifestDocument crates/pixi_manifest/src/manifests/document.rs:26 — ClassTooLong — 794 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 48 methods, 3 blocks, lines 26-1387. The bar is 400 significant lines; this is 394 over it, 1.99× 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: Workspace crates/pixi_core/src/workspace/mod.rs:183 — ClassTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 72 methods, 4 blocks, lines 183-1606. The bar is 400 significant lines; this is 323 over it, 1.81× 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: IntermediateBackend crates/pixi_build_backend/src/intermediate_backend.rs:95 — ClassTooLong — 623 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 1 methods, 3 blocks, lines 95-983. The bar is 400 significant lines; this is 223 over it, 1.56× 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: TomlManifest crates/pixi_manifest/src/toml/manifest.rs:47 — ClassTooLong — 568 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 4 methods, 3 blocks, lines 47-1148. The bar is 400 significant lines; this is 168 over it, 1.42× 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: PyPIEnvironmentUpdater crates/pixi_install_pypi/src/lib.rs:475 — ClassTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 16 methods, 2 blocks, lines 475-1344. The bar is 400 significant lines; this is 165 over it, 1.41× 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: UpdateContext crates/pixi_core/src/lock_file/update.rs:1928 — ClassTooLong — 552 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 7 methods, 3 blocks, lines 1928-3195. The bar is 400 significant lines; this is 152 over it, 1.38× 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: WorkspaceMut crates/pixi_core/src/workspace/workspace_mut.rs:119 — ClassTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 17 methods, 3 blocks, lines 119-946. The bar is 400 significant lines; this is 149 over it, 1.37× 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: BuildBackendMetadataInner crates/pixi_command_dispatcher/src/build_backend_metadata/mod.rs:189 — ClassTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 9 methods, 3 blocks, lines 189-1188. The bar is 400 significant lines; this is 136 over it, 1.34× 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: LockFileDerivedData crates/pixi_core/src/lock_file/update.rs:910 — ClassTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 19 methods, 2 blocks, lines 910-1764. The bar is 400 significant lines; this is 126 over it, 1.32× 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: WorkspaceContext crates/pixi_api/src/context.rs:107 — ClassTooLong — 449 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 53 methods, 2 blocks, lines 107-707. The bar is 400 significant lines; this is 49 over it, 1.12× 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: Manifest crates/pixi_global/src/project/manifest.rs:119 — ClassTooLong — 409 significant lines (blank, comment-only and punctuation-only lines excluded, and inline test code — #[cfg(test)] modules and bare #[test] functions — not counted), 20 methods, 2 blocks, lines 119-732. The bar is 400 significant lines; this is 9 over it, 1.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×13
  • Duplicated block (10 lines × 2) crates/pixi_build_backend/src/server.rs:128 — crates/pixi_build_backend/src/server.rs:128-137 | crates/pixi_build_backend/src/server.rs:173-182 — 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) crates/pixi_cli/src/publish/mod.rs:1703 — crates/pixi_cli/src/publish/mod.rs:1703-1712 | crates/pixi_cli/src/publish/mod.rs:1787-1796 — 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) crates/pixi_cli/src/update.rs:260 — crates/pixi_cli/src/update.rs:260-269 | crates/pixi_cli/src/upgrade.rs:598-607 — 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 `crates/pixi_cli/src/update.rs:260` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 2) crates/pixi_command_dispatcher/src/cache/artifact.rs:168 — crates/pixi_command_dispatcher/src/cache/artifact.rs:168-177 | crates/pixi_command_dispatcher/src/cache/workspace.rs:72-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.
  • Duplicated block (10 lines × 2) crates/pixi_config/src/lib.rs:1961 — crates/pixi_config/src/lib.rs:1961-1970 | crates/pixi_config/src/lib.rs:2018-2027 — 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) crates/pixi_core/src/lock_file/satisfiability/errors.rs:393 — crates/pixi_core/src/lock_file/satisfiability/errors.rs:393-402 | crates/pixi_core/src/lock_file/satisfiability/platform.rs:1195-1205 — 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 `crates/pixi_core/src/lock_file/satisfiability/errors.rs:393` 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 (10 lines × 2) crates/pixi_reporters/src/download_verify_reporter.rs:130 — crates/pixi_reporters/src/download_verify_reporter.rs:130-139 | crates/pixi_reporters/src/main_progress_bar.rs:144-153 — 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 `crates/pixi_reporters/src/download_verify_reporter.rs:130` 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, `crates/pixi_reporters/src/main_progress_bar.rs:140` calls `clear_progress` and `crates/pixi_reporters/src/download_verify_reporter.rs:127` 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 (10 lines × 2) crates/pixi_reporters/src/download_verify_reporter.rs:408 — crates/pixi_reporters/src/download_verify_reporter.rs:408-417 | crates/pixi_reporters/src/repodata_reporter.rs:714-723 — 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) crates/pixi_command_dispatcher/src/errors.rs:513 — crates/pixi_command_dispatcher/src/errors.rs:513-522 | crates/pixi_core/src/lock_file/satisfiability/legacy/key.rs:102-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (10 lines × 2) crates/pixi_cli/src/tree.rs:74 — crates/pixi_cli/src/tree.rs:74-86 | crates/pixi_cli/src/workspace/export/conda_environment.rs:427-436 — 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 `crates/pixi_cli/src/tree.rs:74` 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.
  • Duplicated block (10 lines × 2) crates/pixi_config/src/lib.rs:1991 — crates/pixi_config/src/lib.rs:1991-2000 | crates/pixi_config/src/lib.rs:2061-2070 — 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 `crates/pixi_config/src/lib.rs:1991` 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, `crates/pixi_config/src/lib.rs:2059` calls `from` and `crates/pixi_config/src/lib.rs:1988` 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 (10 lines × 2) crates/pixi_spec/src/toml.rs:1380 — crates/pixi_spec/src/toml.rs:1380-1389 | crates/pixi_spec/src/toml.rs:1395-1404 — 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) examples/rerun_example/nuscenes_dataset/nuscenes_dataset/__main__.py:188 — examples/rerun_example/nuscenes_dataset/nuscenes_dataset/__main__.py:188-197 | examples/rerun_example/nuscenes_dataset/nuscenes_dataset/__main__.py:205-214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×13
  • Duplicated block (9 lines × 2) crates/pixi_build_backend/src/rattler_build_integration.rs:128 — crates/pixi_build_backend/src/rattler_build_integration.rs:128-136 | crates/pixi_build_rattler_build/src/protocol.rs:176-184 — before extracting anything, compare `crates/pixi_build_backend/src/rattler_build_integration.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `crates/pixi_build_backend/src/rattler_build_integration.rs:128` 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) crates/pixi_cli/src/global/install.rs:147 — crates/pixi_cli/src/global/install.rs:147-157 | crates/pixi_cli/src/global/uninstall.rs:32-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_cli/src/global/install.rs:147` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (9 lines × 2) crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:429 — crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:429-437 | crates/pixi_core/src/lock_file/satisfiability/source_record.rs:924-932 — 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) crates/pixi_core/src/lock_file/outdated.rs:607 — crates/pixi_core/src/lock_file/outdated.rs:607-615 | crates/pixi_core/src/lock_file/outdated.rs:617-625 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) crates/pixi_core/src/workspace/discovery.rs:505 — crates/pixi_core/src/workspace/discovery.rs:505-513 | crates/pixi_core/src/workspace/discovery.rs:546-554 — 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 `crates/pixi_core/src/workspace/discovery.rs:505` 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) crates/pixi_core/src/workspace/environment.rs:532 — crates/pixi_core/src/workspace/environment.rs:532-540 | crates/pixi_manifest/src/platform/host.rs:441-449 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (9 lines × 2) crates/pixi_manifest/src/manifests/document.rs:792 — crates/pixi_manifest/src/manifests/document.rs:792-800 | crates/pixi_manifest/src/manifests/document.rs:816-824 — 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) crates/pixi_manifest/src/toml/package.rs:551 — crates/pixi_manifest/src/toml/package.rs:551-559 | crates/pixi_manifest/src/toml/workspace.rs:156-164 — 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 (9 lines × 2) crates/pixi_manifest/src/warning/deprecation.rs:82 — crates/pixi_manifest/src/warning/deprecation.rs:82-90 | crates/pixi_manifest/src/warning/deprecation.rs:103-111 — 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 `crates/pixi_manifest/src/warning/deprecation.rs:82` 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) crates/pixi_config/src/lib.rs:2691 — crates/pixi_config/src/lib.rs:2691-2699 | crates/pixi_config/src/lib.rs:2882-2890 — 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 `crates/pixi_config/src/lib.rs:2691` 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) crates/pixi_command_dispatcher/src/solve_binary.rs:66 — crates/pixi_command_dispatcher/src/solve_binary.rs:66-74 | crates/pixi_compute_sources/src/git.rs:139-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (9 lines × 2) crates/pixi_spec/src/pin.rs:174 — crates/pixi_spec/src/pin.rs:174-182 | crates/pixi_spec/src/pin.rs:203-211 — 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 `crates/pixi_spec/src/pin.rs:174` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (9 lines × 2) examples/rerun_example/lidar/lidar/download_dataset.py:58 — examples/rerun_example/lidar/lidar/download_dataset.py:58-66 | examples/rerun_example/nuscenes_dataset/nuscenes_dataset/download_dataset.py:58-66 — before extracting anything, compare `examples/rerun_example/lidar/lidar/download_dataset.py` and `examples/rerun_example/nuscenes_dataset/nuscenes_dataset/download_dataset.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×10
  • Duplicated block (13 lines × 2) crates/pixi_api/src/workspace/shell/mod.rs:113 — crates/pixi_api/src/workspace/shell/mod.rs:113-125 | crates/pixi_api/src/workspace/shell/mod.rs:153-165 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/pixi_api/src/workspace/shell/mod.rs:127` calls `arg` and `crates/pixi_api/src/workspace/shell/mod.rs:167` 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 (13 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:894 — crates/pixi_build_backend/src/intermediate_backend.rs:894-906 | crates/pixi_build_rattler_build/src/protocol.rs:491-503 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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 `crates/pixi_build_backend/src/intermediate_backend.rs:894` 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) crates/pixi_build_mojo/src/config.rs:284 — crates/pixi_build_mojo/src/config.rs:284-296 | crates/pixi_build_mojo/src/config.rs:399-411 — 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 `crates/pixi_build_mojo/src/config.rs:284` 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, `crates/pixi_build_mojo/src/config.rs:297` calls `clone` and `crates/pixi_build_mojo/src/config.rs:412` 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 (13 lines × 2) crates/pixi_cli/src/upgrade.rs:471 — crates/pixi_cli/src/upgrade.rs:471-483 | crates/pixi_cli/src/upgrade.rs:546-558 — 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) crates/pixi_manifest/src/manifests/document.rs:602 — crates/pixi_manifest/src/manifests/document.rs:602-614 | crates/pixi_manifest/src/manifests/document.rs:676-688 — 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 `crates/pixi_manifest/src/manifests/document.rs:602` 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, `crates/pixi_manifest/src/manifests/document.rs:601` calls `with_target`, `cloned` and `crates/pixi_manifest/src/manifests/document.rs:675` 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 (13 lines × 2) crates/pixi_reporters/src/download_verify_reporter.rs:481 — crates/pixi_reporters/src/download_verify_reporter.rs:481-493 | crates/pixi_reporters/src/repodata_reporter.rs:766-778 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (13 lines × 2) crates/pixi_toml_edit/src/array.rs:149 — crates/pixi_toml_edit/src/array.rs:149-161 | crates/pixi_toml_edit/src/entry.rs:194-206 — 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 `crates/pixi_toml_edit/src/array.rs:149` 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) crates/pixi_config/src/lib.rs:1976 — crates/pixi_config/src/lib.rs:1976-1988 | crates/pixi_config/src/lib.rs:2045-2057 — 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 `crates/pixi_config/src/lib.rs:1976` 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, `crates/pixi_config/src/lib.rs:2059` calls `from` and `crates/pixi_config/src/lib.rs:1990` 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 (13 lines × 2) crates/pixi_spec/src/toml.rs:1276 — crates/pixi_spec/src/toml.rs:1276-1288 | crates/pixi_spec/src/toml.rs:1444-1456 — 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) examples/rerun_example/lidar/lidar/download_dataset.py:28 — examples/rerun_example/lidar/lidar/download_dataset.py:28-40 | examples/rerun_example/nuscenes_dataset/nuscenes_dataset/download_dataset.py:28-40 — before extracting anything, compare `examples/rerun_example/lidar/lidar/download_dataset.py` and `examples/rerun_example/nuscenes_dataset/nuscenes_dataset/download_dataset.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 × 2) · ×10
  • Duplicated block (11 lines × 2) crates/pixi_build_backend/src/dependencies.rs:117 — crates/pixi_build_backend/src/dependencies.rs:117-127 | crates/pixi_build_backend/src/dependencies.rs:369-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) crates/pixi_build_frontend/src/backend/json_rpc.rs:300 — crates/pixi_build_frontend/src/backend/json_rpc.rs:300-310 | crates/pixi_build_frontend/src/backend/json_rpc.rs:352-362 — 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 `crates/pixi_build_frontend/src/backend/json_rpc.rs:300` 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) crates/pixi_core/src/lock_file/outdated.rs:162 — crates/pixi_core/src/lock_file/outdated.rs:162-172 | crates/pixi_core/src/lock_file/outdated.rs:174-184 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) crates/pixi_core/src/lock_file/records_by_name.rs:158 — crates/pixi_core/src/lock_file/records_by_name.rs:158-168 | crates/pixi_core/src/lock_file/records_by_name.rs:181-191 — 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 `crates/pixi_core/src/lock_file/records_by_name.rs:158` 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) crates/pixi_core/src/workspace/mod.rs:555 — crates/pixi_core/src/workspace/mod.rs:555-565 | crates/pixi_core/src/workspace/mod.rs:698-708 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note first that the copies are not typed on the same thing: the declarations holding them bind `script` to `ScriptManifest` in one and `CondaScriptManifest` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/pixi_core/src/workspace/mod.rs:554` calls `path`, `to_owned` and `crates/pixi_core/src/workspace/mod.rs:697` 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 (11 lines × 2) crates/pixi_toml_edit/src/style.rs:56 — crates/pixi_toml_edit/src/style.rs:56-66 | crates/pixi_toml_edit/src/style.rs:74-84 — 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 `crates/pixi_toml_edit/src/style.rs:56` 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.
  • Duplicated block (11 lines × 2) crates/pixi_manifest/src/toml/package.rs:86 — crates/pixi_manifest/src/toml/package.rs:86-96 | crates/pixi_manifest/src/toml/package.rs:111-121 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (11 lines × 2) crates/pixi_core/src/lock_file/update.rs:2956 — crates/pixi_core/src/lock_file/update.rs:2956-2966 | crates/pixi_core/src/lock_file/update.rs:2993-3003 — 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 `crates/pixi_core/src/lock_file/update.rs:2956` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (11 lines × 2) examples/rerun_example/lidar/lidar/download_dataset.py:44 — examples/rerun_example/lidar/lidar/download_dataset.py:44-54 | examples/rerun_example/nuscenes_dataset/nuscenes_dataset/download_dataset.py:44-54 — before extracting anything, compare `examples/rerun_example/lidar/lidar/download_dataset.py` and `examples/rerun_example/nuscenes_dataset/nuscenes_dataset/download_dataset.py` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 33 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) scripts/local_patch.py:387 — scripts/local_patch.py:387-397 | scripts/local_patch.py:445-455 — 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.
D1 · Cyclomatic Complexity · pixi_core · ×9
  • pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability (cyclomatic 64) crates/pixi_core/src/lock_file/satisfiability/platform.rs:630 — pixi_core::lock_file::satisfiability::platform::verify_package_platform_satisfiability has cyclomatic complexity 64 (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.
  • pixi_core::lock_file::update::spawn_extract_environment_task (cyclomatic 36) crates/pixi_core/src/lock_file/update.rs:3483 — pixi_core::lock_file::update::spawn_extract_environment_task has cyclomatic complexity 36 (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.
  • pixi_core::lock_file::satisfiability::pypi::pypi_satisfies_requirement (cyclomatic 35) crates/pixi_core/src/lock_file/satisfiability/pypi.rs:136 — pixi_core::lock_file::satisfiability::pypi::pypi_satisfies_requirement has cyclomatic complexity 35 (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.
  • pixi_core::lock_file::outdated::find_unsatisfiable_targets (cyclomatic 25) crates/pixi_core/src/lock_file/outdated.rs:240 — pixi_core::lock_file::outdated::find_unsatisfiable_targets has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
  • pixi_core::lock_file::resolve::pypi::resolve_pypi (cyclomatic 21) crates/pixi_core/src/lock_file/resolve/pypi.rs:334 — pixi_core::lock_file::resolve::pypi::resolve_pypi 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.
  • pixi_core::lock_file::satisfiability::environment::verify_environment_satisfiability (cyclomatic 20) crates/pixi_core/src/lock_file/satisfiability/environment.rs:33 — pixi_core::lock_file::satisfiability::environment::verify_environment_satisfiability has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • pixi_core::lock_file::satisfiability::platform::verify_platform_satisfiability (cyclomatic 17) crates/pixi_core/src/lock_file/satisfiability/platform.rs:183 — pixi_core::lock_file::satisfiability::platform::verify_platform_satisfiability has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
  • pixi_core::workspace::errors::conda_override_hint (cyclomatic 17) crates/pixi_core/src/workspace/errors.rs:293 — pixi_core::workspace::errors::conda_override_hint has cyclomatic complexity 17 (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.
  • pixi_core::lock_file::outdated::find_inconsistent_solve_groups (cyclomatic 16) crates/pixi_core/src/lock_file/outdated.rs:556 — pixi_core::lock_file::outdated::find_inconsistent_solve_groups 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.
D30 · Dependency Vulnerabilities · Medium advisory (unmaintained) · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×9
  • Duplicated block (14 lines × 2) crates/pixi_api/src/workspace/add/mod.rs:76 — crates/pixi_api/src/workspace/add/mod.rs:76-89 | crates/pixi_api/src/workspace/add/mod.rs:200-213 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (14 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:296 — crates/pixi_build_backend/src/intermediate_backend.rs:296-309 | crates/pixi_build_backend/src/intermediate_backend.rs:717-730 — 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 `crates/pixi_build_backend/src/intermediate_backend.rs:296` 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 first that the copies are not typed on the same thing: the declarations holding them bind `params` to `CondaOutputsParams` in one and `CondaBuildV1Params` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
  • Duplicated block (14 lines × 2) crates/pixi_build_rattler_build/src/protocol.rs:105 — crates/pixi_build_rattler_build/src/protocol.rs:105-118 | crates/pixi_build_rattler_build/src/protocol.rs:420-433 — 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 `crates/pixi_build_rattler_build/src/protocol.rs:105` 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) crates/pixi_cli/src/upgrade.rs:190 — crates/pixi_cli/src/upgrade.rs:190-203 | crates/pixi_cli/src/upgrade.rs:226-239 — 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 `crates/pixi_cli/src/upgrade.rs:190` 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) crates/pixi_manifest/src/toml/feature.rs:219 — crates/pixi_manifest/src/toml/feature.rs:219-232 | crates/pixi_manifest/src/toml/target.rs:312-325 — 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 `crates/pixi_manifest/src/toml/feature.rs:219` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (14 lines × 2) crates/pixi_toml/src/diagnostic.rs:90 — crates/pixi_toml/src/diagnostic.rs:90-103 | crates/pixi_toml/src/diagnostic.rs:106-119 — 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 `crates/pixi_toml/src/diagnostic.rs: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 (14 lines × 2) crates/pixi_toml_edit/src/array.rs:29 — crates/pixi_toml_edit/src/array.rs:29-42 | crates/pixi_toml_edit/src/entry.rs:137-150 — 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) crates/pixi_manifest/src/target.rs:197 — crates/pixi_manifest/src/target.rs:197-210 | crates/pixi_manifest/src/toml/package_target.rs:43-56 — 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) crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:167 — crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:167-180 | crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:207-220 — 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 `crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:167` 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, `crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:166` calls `global_data`, `gateway`, `clone` and `crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:205` 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 (7 lines × 2) · ×9
  • Duplicated block (7 lines × 2) crates/pixi_core/src/workspace/mod.rs:617 — crates/pixi_core/src/workspace/mod.rs:617-624 | crates/pixi_core/src/workspace/mod.rs:658-664 — 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 `crates/pixi_core/src/workspace/mod.rs:617` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) crates/pixi_manifest/src/manifests/document.rs:591 — crates/pixi_manifest/src/manifests/document.rs:591-597 | crates/pixi_manifest/src/target.rs:534-540 — 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) crates/pixi_manifest/src/script/conda/manifest.rs:325 — crates/pixi_manifest/src/script/conda/manifest.rs:325-331 | crates/pixi_manifest/src/script/pep723.rs:418-424 — 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) crates/pixi_manifest/src/script/pep723.rs:431 — crates/pixi_manifest/src/script/pep723.rs:431-437 | crates/pixi_manifest/src/script/pep723.rs:460-466 — 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) crates/pixi_manifest/src/toml/pypi_options.rs:86 — crates/pixi_manifest/src/toml/pypi_options.rs:86-92 | crates/pixi_manifest/src/toml/pypi_options.rs:124-130 — 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 `crates/pixi_manifest/src/toml/pypi_options.rs:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) crates/pixi_manifest/src/utils/inheritable_package_map.rs:494 — crates/pixi_manifest/src/utils/inheritable_package_map.rs:494-500 | crates/pixi_manifest/src/utils/package_map.rs:314-320 — before extracting anything, compare `crates/pixi_manifest/src/utils/inheritable_package_map.rs` and `crates/pixi_manifest/src/utils/package_map.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/pixi_manifest/src/utils/inheritable_package_map.rs:494` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (7 lines × 2) crates/pixi_command_dispatcher/src/cache/artifact.rs:525 — crates/pixi_command_dispatcher/src/cache/artifact.rs:525-531 | crates/pixi_command_dispatcher/src/cache/workspace.rs:158-164 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (7 lines × 2) crates/pixi_build_types/src/variant.rs:91 — crates/pixi_build_types/src/variant.rs:91-97 | crates/pixi_variant/src/lib.rs:97-103 — before extracting anything, compare `crates/pixi_build_types/src/variant.rs` and `crates/pixi_variant/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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) crates/pixi_cli/src/global/expose.rs:64 — crates/pixi_cli/src/global/expose.rs:64-70 | crates/pixi_cli/src/global/shortcut.rs:49-55 — before extracting anything, compare `crates/pixi_cli/src/global/expose.rs` and `crates/pixi_cli/src/global/shortcut.rs` 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 lines × 2) · ×8
  • Duplicated block (16 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:327 — crates/pixi_build_backend/src/intermediate_backend.rs:327-342 | crates/pixi_build_rattler_build/src/protocol.rs:89-104 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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 `crates/pixi_build_backend/src/intermediate_backend.rs:327` 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 (16 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:496 — crates/pixi_build_backend/src/intermediate_backend.rs:496-511 | crates/pixi_build_rattler_build/src/protocol.rs:194-209 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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 `crates/pixi_build_backend/src/intermediate_backend.rs:496` 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) crates/pixi_build_cmake/src/main.rs:69 — crates/pixi_build_cmake/src/main.rs:69-84 | crates/pixi_build_mojo/src/main.rs:48-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_build_cmake/src/main.rs:69` 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 (16 lines × 2) crates/pixi_cli/src/add.rs:410 — crates/pixi_cli/src/add.rs:410-425 | crates/pixi_cli/src/install.rs:117-132 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/pixi_cli/src/add.rs:408` calls `warn_deprecated_subdir` and `crates/pixi_cli/src/install.rs:115` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16 lines × 2) crates/pixi_cli/src/global/expose.rs:90 — crates/pixi_cli/src/global/expose.rs:90-105 | crates/pixi_cli/src/global/shortcut.rs:74-89 — before extracting anything, compare `crates/pixi_cli/src/global/expose.rs` and `crates/pixi_cli/src/global/shortcut.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_cli/src/global/expose.rs:90` 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, `crates/pixi_cli/src/global/expose.rs:89` calls `save` and `crates/pixi_cli/src/global/shortcut.rs:73` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (16 lines × 2) crates/pixi_cli/src/update.rs:382 — crates/pixi_cli/src/update.rs:382-397 | crates/pixi_cli/src/update.rs:413-428 — 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 `crates/pixi_cli/src/update.rs:382` 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) crates/pixi_manifest/src/toml/environment.rs:183 — crates/pixi_manifest/src/toml/environment.rs:183-198 | crates/pixi_manifest/src/toml/feature.rs:226-241 — before extracting anything, compare `crates/pixi_manifest/src/toml/environment.rs` and `crates/pixi_manifest/src/toml/feature.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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 before the matched lines, `crates/pixi_manifest/src/toml/environment.rs:182` calls `optional` and `crates/pixi_manifest/src/toml/feature.rs:225` 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 lines × 2) crates/pixi_manifest/src/toml/pypi_options.rs:95 — crates/pixi_manifest/src/toml/pypi_options.rs:95-110 | crates/pixi_manifest/src/toml/pypi_options.rs:133-148 — 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 `crates/pixi_manifest/src/toml/pypi_options.rs:95` 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.
D35 · Change Coupling · Change coupling · ×7
  • Change coupling: run.rs ↔ lib.rs crates/pixi_cli/src/run.rs:1 — `crates/pixi_cli/src/run.rs` and `crates/pixi_task/src/lib.rs` change together 71% of the time (15 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 `a5a98dc8` feat: add executable flag to pixi run (#5253); `24dd763f` perf: Experimental environment activation cache (#2367) (at that commit the files were still `src/cli/run.rs` and `src/task/mod.rs`); `1bfdf4a9` feat: add `INIT_CWD` to activation env (#1798) (at that commit the files were still `src/cli/run.rs` and `src/task/mod.rs`) — run `git show` on any of them.
  • Change coupling: package_identifier.rs ↔ mod.rs crates/pixi_core/src/lock_file/package_identifier.rs:1 — `crates/pixi_core/src/lock_file/package_identifier.rs` and `crates/pixi_core/src/lock_file/satisfiability/mod.rs` change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 10 shared commits counted here, the most recent 3 are `2625cf18` fix: No longer panics, when a conda dependency is a PyPI get dependen… (at that commit the files were still `src/lock_file/package_identifier.rs` and `src/lock_file/satisfiability/mod.rs`); `b949adb8` feat: migrate to `uv_distribution_types` for package requirements and… (at that commit the files were still `src/lock_file/package_identifier.rs` and `src/lock_file/satisfiability/mod.rs`); `b4e168ff` fix: pypi panic with path dependencies in lock file (#3690) (at that commit the files were still `src/lock_file/package_identifier.rs` and `src/lock_file/satisfiability/mod.rs`) — run `git show` on any of them.
  • Change coupling: table_name.rs ↔ pyproject.rs crates/pixi_manifest/src/manifests/table_name.rs:1 — `crates/pixi_manifest/src/manifests/table_name.rs` and `crates/pixi_manifest/src/pyproject.rs` change together 50% of the time (12 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 `e72411b6` refactor: reduce difference between default and named feature (#3545); `2a994fde` chore: bump rattler (#2860); `8a67cd69` refactor: renamed some manifest types for clarity (#2704) — run `git show` on any of them.
  • Change coupling: run.rs ↔ task_environment.rs crates/pixi_cli/src/run.rs:1 — `crates/pixi_cli/src/run.rs` and `crates/pixi_task/src/task_environment.rs` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 6 shared commits counted here, the most recent 3 are `7dd06c03` feat(pixi_api): Expose run and shell (#7354); `20ed8307` fix: scope target activation to the platform a run targets (#6822); `8525a02d` feat(task): `--default_environment` flag for specifying the default e… — run `git show` on any of them.
  • Change coupling: mod.rs ↔ conversions.rs crates/pixi_core/src/lock_file/satisfiability/mod.rs:1 — `crates/pixi_core/src/lock_file/satisfiability/mod.rs` and `crates/pixi_install_pypi/src/conversions.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 5 shared commits counted here, the most recent 3 are `06d12818` chore: upgrade uv to 0.9.5 (#4840); `1e11b3d1` feat: upgrade to uv 0.7.19 (#4091) (at that commit the files were still `src/lock_file/satisfiability/mod.rs` and `src/install_pypi/conversions.rs`); `d3c21254` chore: update to Rust 1.86 (#3621) (at that commit the files were still `src/lock_file/satisfiability.rs` and `src/install_pypi/conversions.rs`) — run `git show` on any of them.
  • Change coupling: shell.rs ↔ pty_session.rs crates/pixi_cli/src/shell.rs:1 — `crates/pixi_cli/src/shell.rs` and `crates/pixi_pty/src/unix/pty_session.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 5 shared commits counted here, the most recent 3 are `16d9a978` fix: some more things to get the shell to work in all cases (#3321) (at that commit the file was still `src/cli/shell.rs`); `6b0d7dc1` fix: flush shell activation file after writing and add some debug inf… (at that commit the file was still `src/cli/shell.rs`); `fb85c0ba` feat: hide the sourcing of the activation script when starting shell … (at that commit the file was still `src/cli/shell.rs`) — run `git show` on any of them.
  • Change coupling: pypi.rs ↔ conversions.rs crates/pixi_core/src/lock_file/resolve/pypi.rs:1 — `crates/pixi_core/src/lock_file/resolve/pypi.rs` and `crates/pixi_install_pypi/src/conversions.rs` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 5 shared commits counted here, the most recent 3 are `ca2876a2` fix: verify PyPI lock file hashes during install (#6353); `06d12818` chore: upgrade uv to 0.9.5 (#4840); `908825fe` feat: upgrade to uv 0.8.20 and get rid of non-async build dispatch ca… (at that commit the files were still `src/lock_file/resolve/pypi.rs` and `src/install_pypi/conversions.rs`) — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×7
  • Edited copy of a member (8 corresponding lines) crates/pixi_variant/src/lib.rs:154 — crates/pixi_variant/src/lib.rs:154-161 | crates/pixi_variant/src/lib.rs:195-202 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) crates/pixi_compute_engine/src/ctx.rs:835 — crates/pixi_compute_engine/src/ctx.rs:835-842 | crates/pixi_compute_engine/src/ctx.rs:963-970 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) crates/pixi_global/src/project/parsed_manifest.rs:518 — crates/pixi_global/src/project/parsed_manifest.rs:518-529 | crates/pixi_record/src/dev_source_record.rs:73-80 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) crates/pixi_global/src/project/manifest.rs:491 — crates/pixi_global/src/project/manifest.rs:491-498 | crates/pixi_global/src/project/manifest.rs:601-608 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) crates/pixi_uv_conversions/src/conversions.rs:58 — crates/pixi_uv_conversions/src/conversions.rs:58-65 | crates/pixi_uv_conversions/src/conversions.rs:73-84 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs:514 — crates/pixi_reporters/src/download_verify_reporter.rs:514-521 | crates/pixi_reporters/src/main_progress_bar.rs:299-306 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (8 corresponding lines) crates/pixi_spec/src/pin.rs:414 — crates/pixi_spec/src/pin.rs:414-421 | crates/pixi_spec/src/pin.rs:438-445 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×7
  • Duplicated block (5 lines × 2) crates/pixi_install_pypi/src/utils.rs:22 — crates/pixi_install_pypi/src/utils.rs:22-26 | crates/pixi_install_pypi/src/utils.rs:35-39 — 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) crates/pixi_global/src/project/manifest.rs:813 — crates/pixi_global/src/project/manifest.rs:813-817 | crates/pixi_manifest/src/manifests/document.rs:1392-1396 — 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) crates/pixi_manifest/src/script/conda/manifest.rs:60 — crates/pixi_manifest/src/script/conda/manifest.rs:60-64 | crates/pixi_manifest/src/script/pep723.rs:144-148 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/pixi_manifest/src/script/pep723.rs:141` calls `validate_script_extension`, `script_name` and `crates/pixi_manifest/src/script/conda/manifest.rs:59` 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 (5 lines × 2) crates/pixi_toml/src/index_set.rs:32 — crates/pixi_toml/src/index_set.rs:32-36 | crates/pixi_toml/src/index_set.rs:62-66 — 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 `crates/pixi_toml/src/index_set.rs: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.
  • Duplicated block (5 lines × 2) crates/pixi_toml_edit/src/entry.rs:299 — crates/pixi_toml_edit/src/entry.rs:299-303 | crates/pixi_toml_edit/src/entry.rs:356-360 — 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 `crates/pixi_toml_edit/src/entry.rs:299` 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 × 2) trampoline/build-trampoline.py:7 — trampoline/build-trampoline.py:7-11 | trampoline/compress-trampoline.py:7-11 — 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) scripts/create_release.py:48 — scripts/create_release.py:48-52 | scripts/release.py:165-169 — 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 `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.
D3 · God Classes · TooManyMethods · ×6
  • TooManyMethods: Workspace crates/pixi_core/src/workspace/mod.rs:183 — TooManyMethods — 72 methods, declared across 4 files: workspace/mod.rs (65), lock_file/update.rs (4), workspace/workspace_script.rs (2), src/activation.rs (1). The bar is 30 methods; this is 42 over it, 2.40× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. 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: WorkspaceContext crates/pixi_api/src/context.rs:107 — 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: Project crates/pixi_global/src/project/mod.rs:530 — 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: ManifestDocument crates/pixi_manifest/src/manifests/document.rs:26 — 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: WorkspaceManifestMut crates/pixi_manifest/src/manifests/workspace.rs:407 — TooManyMethods — 46 methods. The bar is 30 methods; this is 16 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.
  • TooManyMethods: Config crates/pixi_config/src/lib.rs:1263 — TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. Most of these members implement pixi_config.Config (45 of 45 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×6
  • Edited copy of a member (11 corresponding lines) crates/pixi_core/src/lock_file/satisfiability/legacy/key.rs:212 — crates/pixi_core/src/lock_file/satisfiability/legacy/key.rs:212-222 | crates/pixi_core/src/lock_file/satisfiability/source_record.rs:627-639 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/pixi_install_pypi/src/utils.rs:20 — crates/pixi_install_pypi/src/utils.rs:20-30 | crates/pixi_install_pypi/src/utils.rs:33-43 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/pixi_manifest/src/script/conda/error.rs:195 — crates/pixi_manifest/src/script/conda/error.rs:195-205 | crates/pixi_manifest/src/script/pep723.rs:74-86 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/pixi_manifest/src/target.rs:352 — crates/pixi_manifest/src/target.rs:352-362 | crates/pixi_manifest/src/target.rs:583-593 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/pixi_manifest/src/toml/manifest.rs:871 — crates/pixi_manifest/src/toml/manifest.rs:871-881 | crates/pixi_manifest/src/toml/manifest.rs:889-901 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) crates/pixi_manifest/src/toml/pypi_options.rs:62 — crates/pixi_manifest/src/toml/pypi_options.rs:62-72 | crates/pixi_spec/src/toml.rs:1255-1266 — These two members are one piece of code written twice and then edited apart: 11 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 (13 corresponding lines) · ×6
  • Edited copy of a member (13 corresponding lines) crates/pixi_git/src/git.rs:439 — crates/pixi_git/src/git.rs:439-453 | crates/pixi_git/src/git.rs:497-509 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/pixi_manifest/src/script/conda/manifest.rs:323 — crates/pixi_manifest/src/script/conda/manifest.rs:323-337 | crates/pixi_manifest/src/script/pep723.rs:286-298 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/pixi_reporters/src/main_progress_bar.rs:69 — crates/pixi_reporters/src/main_progress_bar.rs:69-81 | crates/pixi_reporters/src/repodata_reporter.rs:539-551 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/pixi_build_python/src/metadata.rs:289 — crates/pixi_build_python/src/metadata.rs:289-301 | crates/pixi_build_python/src/metadata.rs:307-320 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/pixi_manifest/src/target.rs:393 — crates/pixi_manifest/src/target.rs:393-405 | crates/pixi_manifest/src/target.rs:605-617 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (13 corresponding lines) crates/pixi_reporters/src/repodata_reporter.rs:663 — crates/pixi_reporters/src/repodata_reporter.rs:663-675 | crates/pixi_reporters/src/repodata_reporter.rs:677-689 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×6
  • Duplicated block (18 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:908 — crates/pixi_build_backend/src/intermediate_backend.rs:908-925 | crates/pixi_build_rattler_build/src/protocol.rs:505-522 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/pixi_build_rattler_build/src/protocol.rs:523` calls `unwrap_or` and `crates/pixi_build_backend/src/intermediate_backend.rs:926` 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 (18 lines × 2) crates/pixi_reporters/src/uv_reporter.rs:147 — crates/pixi_reporters/src/uv_reporter.rs:147-164 | crates/pixi_reporters/src/uv_reporter.rs:169-186 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (18 lines × 2) crates/pixi_toml/src/btree_set.rs:32 — crates/pixi_toml/src/btree_set.rs:32-49 | crates/pixi_toml/src/index_set.rs:37-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_toml/src/btree_set.rs:32` 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.
  • Duplicated block (18 lines × 2) crates/pixi_toml/src/btree_set.rs:62 — crates/pixi_toml/src/btree_set.rs:62-79 | crates/pixi_toml/src/index_set.rs:67-84 — 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 `crates/pixi_toml/src/btree_set.rs:62` 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.
  • Duplicated block (18 lines × 2) crates/pixi_utils/src/executable_utils.rs:13 — crates/pixi_utils/src/executable_utils.rs:13-30 | trampoline/src/executable_from_path.rs:17-34 — before extracting anything, compare `crates/pixi_utils/src/executable_utils.rs` and `trampoline/src/executable_from_path.rs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, 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 `crates/pixi_utils/src/executable_utils.rs:13` 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.
  • Duplicated block (18 lines × 2) docs/source_files/pixi_workspaces/pixi_build/workspace/src/python_rich/__init__.py:16 — docs/source_files/pixi_workspaces/pixi_build/workspace/src/python_rich/__init__.py:16-33 | docs/source_files/pixi_workspaces/pixi_build/workspace_variants/src/python_rich/__init__.py:16-33 — before extracting anything, compare `docs/source_files/pixi_workspaces/pixi_build/workspace/src/python_rich/__init__.py` and `docs/source_files/pixi_workspaces/pixi_build/workspace_variants/src/python_rich/__init__.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.
D2 · Cognitive Complexity · pixi_command_dispatcher · ×5
  • pixi_command_dispatcher::keys::solve_pixi_environment::walk_and_resolve (cognitive 28) crates/pixi_command_dispatcher/src/keys/solve_pixi_environment.rs:482 — pixi_command_dispatcher::keys::solve_pixi_environment::walk_and_resolve has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 4 (7 pts), match/switch 3 (6 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_command_dispatcher::input_snapshot::classify_files (cognitive 23) crates/pixi_command_dispatcher/src/input_snapshot.rs:397 — pixi_command_dispatcher::input_snapshot::classify_files has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 5 (15 pts), if/else 2 (7 pts), loops 1 (nesting depth added 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
  • pixi_command_dispatcher::keys::resolve_source_record::assemble_source_record_inner (cognitive 20) crates/pixi_command_dispatcher/src/keys/resolve_source_record.rs:112 — pixi_command_dispatcher::keys::resolve_source_record::assemble_source_record_inner has cognitive complexity 20 (threshold 15). Drivers by points: match/switch 5 (11 pts), if/else 5 (9 pts) (nesting depth added 10). Of this number, 10 points are the body's own statements and 10 belong to one function item inside it that branches. 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.
  • pixi_command_dispatcher::install_pixi::ext::install_inner (cognitive 19) crates/pixi_command_dispatcher/src/install_pixi/ext.rs:98 — pixi_command_dispatcher::install_pixi::ext::install_inner has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), loops 3 (4 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 4). 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.
  • pixi_command_dispatcher::keys::source_build::compute_inner (cognitive 18) crates/pixi_command_dispatcher/src/keys/source_build.rs:239 — pixi_command_dispatcher::keys::source_build::compute_inner has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10, match/switch 3 (4 pts), boolean chains 2, loops 2 (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 · pixi_manifest · ×5
  • pixi_manifest::toml::manifest::validate_task_environments (cognitive 26) crates/pixi_manifest/src/toml/manifest.rs:693 — pixi_manifest::toml::manifest::validate_task_environments has cognitive complexity 26 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (9 pts), match/switch 2 (5 pts), boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_manifest::utils::package_map::deserialize_dependency_table (cognitive 25) crates/pixi_manifest/src/utils/package_map.rs:232 — pixi_manifest::utils::package_map::deserialize_dependency_table has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), match/switch 5 (10 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_manifest::script::conda::metadata::conda_script_spec (cognitive 19) crates/pixi_manifest/src/script/conda/metadata.rs:255 — pixi_manifest::script::conda::metadata::conda_script_spec has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (3 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.
  • pixi_manifest::script::tool_pixi::unsupported_tool_pixi_keys (cognitive 19) crates/pixi_manifest/src/script/tool_pixi.rs:85 — pixi_manifest::script::tool_pixi::unsupported_tool_pixi_keys has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (12 pts), loops 2 (5 pts), match/switch 1 (2 pts) (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.
  • pixi_manifest::script::conda::envelope::parse_block (cognitive 18) crates/pixi_manifest/src/script/conda/envelope.rs:25 — pixi_manifest::script::conda::envelope::parse_block has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×5
  • Edited copy of a member (18 corresponding lines) crates/pixi_uv_conversions/src/git_url.rs:9 — crates/pixi_uv_conversions/src/git_url.rs:9-26 | crates/pixi_uv_conversions/src/git_url.rs:32-54 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) crates/pixi_command_dispatcher/src/cache/workspace.rs:71 — crates/pixi_command_dispatcher/src/cache/workspace.rs:71-88 | crates/pixi_command_dispatcher/src/keys/source_build.rs:124-154 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) crates/pixi_command_dispatcher/src/dev_source_metadata/mod.rs:90 — crates/pixi_command_dispatcher/src/dev_source_metadata/mod.rs:90-107 | crates/pixi_manifest/src/error.rs:318-339 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) crates/pixi_manifest/src/toml/pyproject.rs:365 — crates/pixi_manifest/src/toml/pyproject.rs:365-382 | crates/pixi_manifest/src/toml/pyproject.rs:528-546 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (18 corresponding lines) crates/pixi_cli/src/workspace/requires_pixi/set.rs:12 — crates/pixi_cli/src/workspace/requires_pixi/set.rs:12-36 | crates/pixi_cli/src/workspace/version/set.rs:13-30 — These two members are one piece of code written twice and then edited apart: 18 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) · ×5
  • Edited copy of a member (12 corresponding lines) crates/pixi_manifest/src/pypi/pypi_options.rs:106 — crates/pixi_manifest/src/pypi/pypi_options.rs:106-117 | crates/pixi_manifest/src/pypi/pypi_options.rs:139-150 — 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.
  • Edited copy of a member (12 corresponding lines) crates/pixi_manifest/src/pypi/merge.rs:31 — crates/pixi_manifest/src/pypi/merge.rs:31-45 | crates/pixi_manifest/src/pypi/merge.rs:55-66 — 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.
  • Edited copy of a member (12 corresponding lines) crates/pixi_api/src/workspace/workspace/feature.rs:62 — crates/pixi_api/src/workspace/workspace/feature.rs:62-73 | crates/pixi_api/src/workspace/workspace/feature.rs:79-90 — 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.
  • Edited copy of a member (12 corresponding lines) crates/pixi_compute_engine/src/key_graph.rs:276 — crates/pixi_compute_engine/src/key_graph.rs:276-291 | crates/pixi_compute_engine/src/key_graph.rs:316-327 — 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.
  • Edited copy of a member (12 corresponding lines) crates/pixi_record/src/lib.rs:67 — crates/pixi_record/src/lib.rs:67-78 | crates/pixi_record/src/lib.rs:370-381 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×5
  • Edited copy of a member (14 corresponding lines) crates/pixi_global/src/project/environment.rs:55 — crates/pixi_global/src/project/environment.rs:55-68 | crates/pixi_manifest/src/environment.rs:125-140 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/pixi_manifest/src/target.rs:371 — crates/pixi_manifest/src/target.rs:371-384 | crates/pixi_manifest/src/target.rs:471-484 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/pixi_api/src/workspace/task/mod.rs:172 — crates/pixi_api/src/workspace/task/mod.rs:172-185 | crates/pixi_api/src/workspace/task/mod.rs:194-207 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/pixi_api/src/global/install.rs:93 — crates/pixi_api/src/global/install.rs:93-106 | crates/pixi_api/src/global/uninstall.rs:25-39 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (14 corresponding lines) crates/pixi_cli/src/task.rs:455 — crates/pixi_cli/src/task.rs:455-469 | crates/pixi_cli/src/task.rs:474-487 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×5
  • Duplicated block (22 lines × 2) crates/pixi_cli/src/config.rs:209 — crates/pixi_cli/src/config.rs:209-230 | crates/pixi_cli/src/global/edit.rs:27-48 — 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 (22 lines × 2) crates/pixi_cli/src/update.rs:272 — crates/pixi_cli/src/update.rs:272-293 | crates/pixi_cli/src/upgrade.rs:610-631 — 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 `crates/pixi_cli/src/update.rs:272` 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.
  • Duplicated block (22 lines × 2) crates/pixi_manifest/src/manifests/workspace.rs:562 — crates/pixi_manifest/src/manifests/workspace.rs:562-583 | crates/pixi_manifest/src/manifests/workspace.rs:666-687 — 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) crates/pixi_pypi_spec/src/toml.rs:31 — crates/pixi_pypi_spec/src/toml.rs:31-52 | crates/pixi_spec/src/toml.rs:290-311 — 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 (22 lines × 2) examples/rerun_example/lidar/lidar/__main__.py:28 — examples/rerun_example/lidar/lidar/__main__.py:28-49 | examples/rerun_example/nuscenes_dataset/nuscenes_dataset/__main__.py:39-60 — 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 (12 lines × 2) · ×5
  • Duplicated block (12 lines × 2) crates/pixi_build_cmake/src/main.rs:124 — crates/pixi_build_cmake/src/main.rs:124-135 | crates/pixi_build_r/src/main.rs:228-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_build_cmake/src/main.rs:124` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) crates/pixi_command_dispatcher/src/keys/solve_conda.rs:374 — crates/pixi_command_dispatcher/src/keys/solve_conda.rs:374-385 | crates/pixi_command_dispatcher/src/keys/solve_pixi_environment.rs:608-619 — 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 `crates/pixi_command_dispatcher/src/keys/solve_conda.rs:374` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (12 lines × 2) crates/pixi_core/src/lock_file/resolve/pypi.rs:1114 — crates/pixi_core/src/lock_file/resolve/pypi.rs:1114-1125 | crates/pixi_core/src/lock_file/resolve/pypi.rs:1200-1211 — 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 `crates/pixi_core/src/lock_file/resolve/pypi.rs:1114` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) crates/pixi_build_types/src/variant.rs:76 — crates/pixi_build_types/src/variant.rs:76-87 | crates/pixi_variant/src/lib.rs:82-93 — before extracting anything, compare `crates/pixi_build_types/src/variant.rs` and `crates/pixi_variant/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (12 lines × 2) crates/pixi_api/src/workspace/task/mod.rs:174 — crates/pixi_api/src/workspace/task/mod.rs:174-185 | crates/pixi_api/src/workspace/task/mod.rs:196-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_api/src/workspace/task/mod.rs:174` 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 (6 lines × 2) · ×5
  • Duplicated block (6 lines × 2) crates/pixi_command_dispatcher/src/cache/artifact.rs:535 — crates/pixi_command_dispatcher/src/cache/artifact.rs:535-540 | crates/pixi_command_dispatcher/src/cache/workspace.rs:168-173 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (6 lines × 2) crates/pixi_manifest/src/utils/inheritable_package_map.rs:448 — crates/pixi_manifest/src/utils/inheritable_package_map.rs:448-453 | crates/pixi_manifest/src/utils/package_map.rs:236-241 — before extracting anything, compare `crates/pixi_manifest/src/utils/inheritable_package_map.rs` and `crates/pixi_manifest/src/utils/package_map.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (6 lines × 2) crates/pixi_compute_sources/src/git.rs:205 — crates/pixi_compute_sources/src/git.rs:205-210 | crates/pixi_compute_sources/src/git.rs:236-241 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (6 lines × 2) crates/pixi_task/src/executable_task.rs:367 — crates/pixi_task/src/executable_task.rs:367-372 | crates/pixi_task/src/executable_task.rs:380-385 — 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 `crates/pixi_task/src/executable_task.rs:367` 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 (6 lines × 2) crates/pixi_pypi_spec/src/toml.rs:147 — crates/pixi_pypi_spec/src/toml.rs:147-152 | crates/pixi_spec/src/toml.rs:1203-1208 — 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 `crates/pixi_pypi_spec/src/toml.rs:147` 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.
D2 · Cognitive Complexity · pixi_global · ×4
  • pixi_global::install::create_executable_trampolines (cognitive 27) crates/pixi_global/src/install.rs:119 — pixi_global::install::create_executable_trampolines has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (23 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • pixi_global::install::local_environment_matches_spec (cognitive 22) crates/pixi_global/src/install.rs:273 — pixi_global::install::local_environment_matches_spec has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 2 (3 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 8). Of this number, 13 points are the body's own statements and 9 belong to one function item 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.
  • pixi_global::completions::completions_sync_status (cognitive 21) crates/pixi_global/src/completions.rs:191 — pixi_global::completions::completions_sync_status has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (7 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.
  • pixi_global::common::build_report (cognitive 17) crates/pixi_global/src/common.rs:529 — pixi_global::common::build_report has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 2 (4 pts), match/switch 2 (3 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pixi_build_ros · ×4
  • pixi_build_ros::package_map::resolve_rosdep_to_conda_package_spec (cognitive 24) crates/pixi_build_ros/src/package_map.rs:161 — pixi_build_ros::package_map::resolve_rosdep_to_conda_package_spec has cognitive complexity 24 (threshold 15). Drivers by points: if/else 18 (24 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_build_ros::package_map::merge_unique_items_vec (cognitive 24) crates/pixi_build_ros/src/package_map.rs:565 — pixi_build_ros::package_map::merge_unique_items_vec has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 1, loops 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • pixi_build_ros::package_map::rosdep_nameless_matchspec (cognitive 18) crates/pixi_build_ros/src/package_map.rs:269 — pixi_build_ros::package_map::rosdep_nameless_matchspec has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 3, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
  • pixi_build_ros::package_xml::tokenize_condition (cognitive 16) crates/pixi_build_ros/src/package_xml.rs:369 — pixi_build_ros::package_xml::tokenize_condition has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 2 (7 pts), if/else 5 (6 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (4 members, 50+ identical tokens) crates/pixi_api/src/workspace/shell/mod.rs:104 — crates/pixi_api/src/workspace/shell/mod.rs:104-136 | crates/pixi_api/src/workspace/shell/mod.rs:144-174 | crates/pixi_api/src/workspace/shell/mod.rs:184-234 | crates/pixi_api/src/workspace/shell/mod.rs:249-304 — 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) crates/pixi_build_backend/src/intermediate_backend.rs:255 — crates/pixi_build_backend/src/intermediate_backend.rs:255-667 | crates/pixi_build_backend/src/tools.rs:201-298 | crates/pixi_build_rattler_build/src/protocol.rs:68-364 | crates/pixi_build_rattler_build/src/protocol.rs:369-567 — 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) crates/pixi_build_cmake/src/config.rs:39 — crates/pixi_build_cmake/src/config.rs:39-62 | crates/pixi_build_mojo/src/config.rs:52-116 | crates/pixi_build_r/src/config.rs:44-71 | crates/pixi_build_rust/src/config.rs:87-119 — 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) crates/pixi_manifest/src/feature.rs:295 — crates/pixi_manifest/src/feature.rs:295-311 | crates/pixi_manifest/src/feature.rs:359-375 | crates/pixi_manifest/src/feature.rs:461-477 | crates/pixi_manifest/src/feature.rs:529-545 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×4
  • Edited copy of a member (20 corresponding lines) crates/pixi_utils/src/atomic_write.rs:64 — crates/pixi_utils/src/atomic_write.rs:64-86 | crates/pixi_utils/src/atomic_write.rs:89-108 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) crates/pixi_manifest/src/manifests/document.rs:428 — crates/pixi_manifest/src/manifests/document.rs:428-447 | crates/pixi_manifest/src/manifests/document.rs:540-561 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) crates/pixi_compute_sources/src/ext.rs:40 — crates/pixi_compute_sources/src/ext.rs:40-64 | crates/pixi_compute_sources/src/ext.rs:69-88 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (20 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs:245 — crates/pixi_reporters/src/download_verify_reporter.rs:245-264 | crates/pixi_reporters/src/download_verify_reporter.rs:266-288 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×4
  • Edited copy of a member (22 corresponding lines) crates/pixi_cli/src/workspace/description.rs:43 — crates/pixi_cli/src/workspace/description.rs:43-64 | crates/pixi_cli/src/workspace/feature.rs:50-76 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) crates/pixi_config/src/lib.rs:3085 — crates/pixi_config/src/lib.rs:3085-3106 | crates/pixi_core/src/host.rs:982-1005 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) crates/pixi_global/src/project/manifest.rs:385 — crates/pixi_global/src/project/manifest.rs:385-408 | crates/pixi_global/src/project/manifest.rs:573-594 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (22 corresponding lines) crates/pixi_spec/src/toml.rs:574 — crates/pixi_spec/src/toml.rs:574-595 | crates/pixi_spec/src/toml.rs:1481-1504 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×4
  • Edited copy of a member (17 corresponding lines) crates/pixi_toml_edit/src/style.rs:50 — crates/pixi_toml_edit/src/style.rs:50-66 | crates/pixi_toml_edit/src/style.rs:68-84 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs:168 — crates/pixi_reporters/src/download_verify_reporter.rs:168-184 | crates/pixi_reporters/src/download_verify_reporter.rs:290-316 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) crates/pixi_manifest/src/warning/deprecation.rs:80 — crates/pixi_manifest/src/warning/deprecation.rs:80-96 | crates/pixi_manifest/src/warning/deprecation.rs:101-117 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) crates/pixi_spec/src/lib.rs:334 — crates/pixi_spec/src/lib.rs:334-350 | crates/pixi_spec/src/lib.rs:390-406 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×4
  • Duplicated block (17 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:362 — crates/pixi_build_backend/src/intermediate_backend.rs:362-378 | crates/pixi_build_rattler_build/src/protocol.rs:125-141 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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 `crates/pixi_build_backend/src/intermediate_backend.rs:362` 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 (17 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:927 — crates/pixi_build_backend/src/intermediate_backend.rs:927-943 | crates/pixi_build_rattler_build/src/protocol.rs:524-540 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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 `crates/pixi_build_backend/src/intermediate_backend.rs:927` 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, `crates/pixi_build_rattler_build/src/protocol.rs:523` calls `unwrap_or` and `crates/pixi_build_backend/src/intermediate_backend.rs:926` 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 (17 lines × 2) crates/pixi_utils/src/executable_utils.rs:35 — crates/pixi_utils/src/executable_utils.rs:35-51 | trampoline/src/executable_from_path.rs:39-55 — before extracting anything, compare `crates/pixi_utils/src/executable_utils.rs` and `trampoline/src/executable_from_path.rs` 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. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
  • Duplicated block (17 lines × 2) docs/source_files/pixi_workspaces/pixi_build/getting_started/src/python_rich/__init__.py:15 — docs/source_files/pixi_workspaces/pixi_build/getting_started/src/python_rich/__init__.py:15-31 | docs/source_files/pixi_workspaces/pixi_build/python/src/python_rich/__init__.py:15-31 — before extracting anything, compare `docs/source_files/pixi_workspaces/pixi_build/getting_started/src/python_rich/__init__.py` and `docs/source_files/pixi_workspaces/pixi_build/python/src/python_rich/__init__.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.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×4
  • Duplicated block (10–11 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:807 — crates/pixi_build_backend/src/intermediate_backend.rs:807-816 | crates/pixi_build_rattler_build/src/protocol.rs:462-472 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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 `crates/pixi_build_backend/src/intermediate_backend.rs:807` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10–11 lines × 2) crates/pixi_build_backend_passthrough/src/lib.rs:822 — crates/pixi_build_backend_passthrough/src/lib.rs:822-831 | crates/pixi_build_backend_passthrough/src/lib.rs:981-991 — 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 `crates/pixi_build_backend_passthrough/src/lib.rs:822` 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. 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 (10–11 lines × 2) crates/pixi_url/src/source.rs:159 — crates/pixi_url/src/source.rs:159-168 | crates/pixi_url/src/source.rs:184-194 — 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–11 lines × 2) crates/pixi_url/src/extract.rs:124 — crates/pixi_url/src/extract.rs:124-134 | crates/pixi_url/src/extract.rs:194-203 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D15 · Churn × Complexity Hotspots · Repeated repair · ×3
  • Repeated repair: crates/pixi_command_dispatcher/src/keys/source_build.rs crates/pixi_command_dispatcher/src/keys/source_build.rs:239 — crates/pixi_command_dispatcher/src/keys/source_build.rs changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is pixi_command_dispatcher::keys::source_build::compute_inner at line 239), AT OR 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(build): build outputs with the variants of the siblings they pin (#7466)”; “fix(build): reuse immutable Git build artifacts without checkout (#6887)”; “fix: invalidate source build caches on model and config changes (#7148)”; “fix(dispatcher): add PrefixPlatformMismatchError for source build prefixes (#6984)”. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_command_dispatcher/src/keys/source_build.rs`: 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: crates/pixi_task/src/executable_task.rs crates/pixi_task/src/executable_task.rs:452 — crates/pixi_task/src/executable_task.rs changed 5 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 7 (its worst body is ExecutableTask::save_cache at line 452), AT OR 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: preserve quotes in task arguments (#7091)”; “fix: scope target activation to the platform a run targets (#6822)”; “fix: treat corrupt task-cache JSON as a cache miss (#6824)”. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_task/src/executable_task.rs`: 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: crates/pixi_command_dispatcher/src/cache/backend_metadata.rs crates/pixi_command_dispatcher/src/cache/backend_metadata.rs:116 — crates/pixi_command_dispatcher/src/cache/backend_metadata.rs 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 2 (its worst body is BuildBackendMetadataCacheKey::key at line 116), AT OR 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(cache): use xxh3 for all on-disk cache names (#7408)”; “fix: reuse the build backend environment with a relative exclude-newer (#7384)”; “fix: avoid rebuilds for mtime-only source changes (#6703)”. 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-08-16..2026-11-14, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-16 08:38:39 +01:00' --until='2026-11-14 08:38:39 +01:00' --full-history --no-merges -- crates/pixi_command_dispatcher/src/cache/backend_metadata.rs`: 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 · pixi_glob · ×3
  • pixi_glob::glob_set::walk::set_ignore_hidden_patterns (cognitive 48) crates/pixi_glob/src/glob_set/walk.rs:345 — pixi_glob::glob_set::walk::set_ignore_hidden_patterns has cognitive complexity 48 (threshold 15). Drivers by points: if/else 14 (37 pts), boolean chains 9, loops 1 (2 pts) (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • pixi_glob::glob_set::walk::walk_globs (cognitive 30) crates/pixi_glob/src/glob_set/walk.rs:101 — pixi_glob::glob_set::walk::walk_globs has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (19 pts), loops 4 (6 pts), match/switch 2 (5 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_glob::glob_hash::normalize_line_endings (cognitive 21) crates/pixi_glob/src/glob_hash.rs:94 — pixi_glob::glob_hash::normalize_line_endings has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 2 (7 pts), loops 1 (2 pts) (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.
D4 · Code Duplication · Edited copy of a member (24 corresponding lines) · ×3
  • Edited copy of a member (24 corresponding lines) crates/pixi_cli/src/config.rs:204 — crates/pixi_cli/src/config.rs:204-274 | crates/pixi_cli/src/global/edit.rs:17-50 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) crates/pixi_toml/src/btree_set.rs:26 — crates/pixi_toml/src/btree_set.rs:26-49 | crates/pixi_toml/src/btree_set.rs:56-79 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (24 corresponding lines) crates/pixi_uv_conversions/src/workspace_anchor.rs:32 — crates/pixi_uv_conversions/src/workspace_anchor.rs:32-55 | crates/pixi_uv_conversions/src/workspace_anchor.rs:88-111 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (25 corresponding lines) · ×3
  • Edited copy of a member (25 corresponding lines) crates/pixi_manifest/src/toml/channel.rs:75 — crates/pixi_manifest/src/toml/channel.rs:75-101 | crates/pixi_manifest/src/toml/pypi_options.rs:30-54 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) crates/pixi_build_mojo/src/config.rs:273 — crates/pixi_build_mojo/src/config.rs:273-301 | crates/pixi_build_mojo/src/config.rs:392-416 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (25 corresponding lines) crates/pixi_command_dispatcher/src/ephemeral_env/mod.rs:81 — crates/pixi_command_dispatcher/src/ephemeral_env/mod.rs:81-109 | crates/pixi_command_dispatcher/src/keys/solve_pixi_environment.rs:134-158 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×3
  • Edited copy of a member (19 corresponding lines) crates/pixi_manifest/src/toml/package.rs:83 — crates/pixi_manifest/src/toml/package.rs:83-101 | crates/pixi_manifest/src/toml/package.rs:108-126 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) crates/pixi_core/src/lock_file/records_by_name.rs:157 — crates/pixi_core/src/lock_file/records_by_name.rs:157-175 | crates/pixi_core/src/lock_file/records_by_name.rs:180-207 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (19 corresponding lines) crates/pixi_utils/src/executable_utils.rs:33 — crates/pixi_utils/src/executable_utils.rs:33-51 | trampoline/src/executable_from_path.rs:37-55 — These two members are one piece of code written twice and then edited apart: 19 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 (15 corresponding lines) · ×3
  • Edited copy of a member (15 corresponding lines) crates/pixi_toml_edit/src/entry.rs:280 — crates/pixi_toml_edit/src/entry.rs:280-294 | crates/pixi_toml_edit/src/entry.rs:336-351 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) crates/pixi_cli/src/global/exclude_newer.rs:229 — crates/pixi_cli/src/global/exclude_newer.rs:229-243 | crates/pixi_cli/src/workspace/exclude_newer.rs:530-546 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (15 corresponding lines) crates/pixi_api/src/workspace/workspace/platform.rs:118 — crates/pixi_api/src/workspace/workspace/platform.rs:118-132 | crates/pixi_api/src/workspace/workspace/platform.rs:143-159 — These two members are one piece of code written twice and then edited apart: 15 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 (16 corresponding lines) · ×3
  • Edited copy of a member (16 corresponding lines) crates/pixi_build_python/src/main.rs:85 — crates/pixi_build_python/src/main.rs:85-100 | crates/pixi_build_python/src/main.rs:102-118 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) crates/pixi_utils/src/reqwest.rs:342 — crates/pixi_utils/src/reqwest.rs:342-357 | crates/pixi_utils/src/reqwest.rs:362-380 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (16 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs:141 — crates/pixi_reporters/src/download_verify_reporter.rs:141-156 | crates/pixi_reporters/src/download_verify_reporter.rs:186-201 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×3
  • Edited copy of a member (10 corresponding lines) crates/pixi_manifest/src/manifests/document.rs:503 — crates/pixi_manifest/src/manifests/document.rs:503-514 | crates/pixi_manifest/src/manifests/document.rs:519-528 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) crates/pixi_spec/src/url.rs:108 — crates/pixi_spec/src/url.rs:108-117 | crates/pixi_spec/src/url.rs:211-220 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) crates/pixi_spec/src/lib.rs:258 — crates/pixi_spec/src/lib.rs:258-267 | crates/pixi_spec/src/lib.rs:366-375 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) crates/pixi_install_pypi/src/utils.rs:10 — crates/pixi_install_pypi/src/utils.rs:10-17 | crates/pixi_utils/src/atomic_write.rs:41-47 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) crates/pixi_spec/src/lib.rs:521 — crates/pixi_spec/src/lib.rs:521-527 | crates/pixi_command_dispatcher/src/backend_source_build/mod.rs:381-387 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) crates/pixi_cli/src/remove/error.rs:272 — crates/pixi_cli/src/remove/error.rs:272-282 | crates/pixi_manifest/src/lib.rs:189-195 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×3
  • Edited copy of a member (9 corresponding lines) crates/pixi_api/src/workspace/task/mod.rs:64 — crates/pixi_api/src/workspace/task/mod.rs:64-72 | crates/pixi_cli/src/shared/install_platform.rs:16-26 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) crates/pixi_manifest/src/manifests/document.rs:1203 — crates/pixi_manifest/src/manifests/document.rs:1203-1213 | crates/pixi_manifest/src/manifests/document.rs:1284-1292 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (9 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs:66 — crates/pixi_reporters/src/download_verify_reporter.rs:66-77 | crates/pixi_reporters/src/download_verify_reporter.rs:79-87 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (26 lines × 2) · ×3
  • Duplicated block (26 lines × 2) crates/pixi_build_frontend/src/backend/json_rpc.rs:312 — crates/pixi_build_frontend/src/backend/json_rpc.rs:312-337 | crates/pixi_build_frontend/src/backend/json_rpc.rs:364-389 — 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 `crates/pixi_build_frontend/src/backend/json_rpc.rs:312` 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 (26 lines × 2) crates/pixi_manifest/src/task.rs:996 — crates/pixi_manifest/src/task.rs:996-1021 | crates/pixi_manifest/src/task.rs:1031-1056 — 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 (26 lines × 2) examples/turtlesim/turtle_marker_viz_ROS1.py:14 — examples/turtlesim/turtle_marker_viz_ROS1.py:14-39 | examples/turtlesim/turtle_marker_viz_ROS2.py:26-51 — 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 (20 lines × 2) · ×3
  • Duplicated block (20 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:447 — crates/pixi_build_backend/src/intermediate_backend.rs:447-466 | crates/pixi_build_backend/src/intermediate_backend.rs:838-857 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (20 lines × 2) crates/pixi_build_cmake/src/config.rs:40 — crates/pixi_build_cmake/src/config.rs:40-59 | crates/pixi_build_r/src/config.rs:45-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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_build_cmake/src/config.rs:40` 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) crates/pixi_manifest/src/task.rs:886 — crates/pixi_manifest/src/task.rs:886-905 | crates/pixi_manifest/src/task.rs:972-991 — 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.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×3
  • Sync-over-async blocking crates/pixi_command_dispatcher/src/backend_source_build/mod.rs:159 — `build_v1` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
  • Sync-over-async blocking crates/pixi_command_dispatcher/src/build_backend_metadata/mod.rs:529 — `call_conda_outputs` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
  • Sync-over-async blocking crates/pixi_command_dispatcher/src/keys/source_build.rs:863 — `fetch_matching_output` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs.
D1 · Cyclomatic Complexity · pixi_glob · ×2
  • pixi_glob::glob_set::walk::set_ignore_hidden_patterns (cyclomatic 21) crates/pixi_glob/src/glob_set/walk.rs:345 — pixi_glob::glob_set::walk::set_ignore_hidden_patterns 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.
  • pixi_glob::glob_set::walk::walk_globs (cyclomatic 20) crates/pixi_glob/src/glob_set/walk.rs:101 — pixi_glob::glob_set::walk::walk_globs has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PackageReachability · ×2
  • PackageReachability::collect_reachable_from_non_skipped (cyclomatic 19) crates/pixi_core/src/lock_file/install_subset.rs:401 — PackageReachability::collect_reachable_from_non_skipped 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.
  • PackageReachability::collect_targets_dependencies (cyclomatic 16) crates/pixi_core/src/lock_file/install_subset.rs:323 — PackageReachability::collect_targets_dependencies 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 · pixi_docs · ×2
  • pixi_docs::arguments (cyclomatic 18) crates/pixi_docs/src/main.rs:445 — pixi_docs::arguments 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.
  • pixi_docs::subcommand_to_md (cyclomatic 16) crates/pixi_docs/src/main.rs:137 — pixi_docs::subcommand_to_md 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 · pixi_build_ros · ×2
  • pixi_build_ros::package_map::resolve_rosdep_to_conda_package_spec (cyclomatic 17) crates/pixi_build_ros/src/package_map.rs:161 — pixi_build_ros::package_map::resolve_rosdep_to_conda_package_spec 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.
  • pixi_build_ros::package_map::rosdep_nameless_matchspec (cyclomatic 16) crates/pixi_build_ros/src/package_map.rs:269 — pixi_build_ros::package_map::rosdep_nameless_matchspec 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 · TaskGraph · ×2
  • TaskGraph::from_cmd_args (cyclomatic 16) crates/pixi_task/src/task_graph.rs:226 — TaskGraph::from_cmd_args 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.
  • TaskGraph::merge_args (cyclomatic 16) crates/pixi_task/src/task_graph.rs:552 — TaskGraph::merge_args 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.
D2 · Cognitive Complexity · pixi_api · ×2
  • pixi_api::workspace::run::run (cognitive 54) crates/pixi_api/src/workspace/run/mod.rs:155 — pixi_api::workspace::run::run has cognitive complexity 54 (threshold 15). Drivers by points: if/else 20 (40 pts), match/switch 3 (7 pts), boolean chains 6, loops 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_api::global::install::setup_environment (cognitive 17) crates/pixi_api/src/global/install.rs:108 — pixi_api::global::install::setup_environment has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 3 (5 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LockFileDiff · ×2
  • LockFileDiff::from_lock_files (cognitive 40) crates/pixi_diff/src/lib.rs:38 — LockFileDiff::from_lock_files has cognitive complexity 40 (threshold 15). Drivers by points: loops 10 (23 pts), match/switch 4 (17 pts) (nesting depth added 26). 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.
  • LockFileDiff::print (cognitive 16) crates/pixi_diff/src/lib.rs:181 — LockFileDiff::print has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (9 pts), if/else 2 (5 pts), match/switch 1 (2 pts) (nesting depth added 9). 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 · TaskGraph · ×2
  • TaskGraph::from_cmd_args (cognitive 39) crates/pixi_task/src/task_graph.rs:226 — TaskGraph::from_cmd_args has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (29 pts), match/switch 3 (9 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • TaskGraph::merge_args (cognitive 30) crates/pixi_task/src/task_graph.rs:552 — TaskGraph::merge_args has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (19 pts), match/switch 5 (9 pts), loops 2 (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 · pixi_toml_edit · ×2
  • pixi_toml_edit::array::retain_array_elements (cognitive 31) crates/pixi_toml_edit/src/array.rs:100 — pixi_toml_edit::array::retain_array_elements has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • pixi_toml_edit::entry::remove_inline_table_entry (cognitive 17) crates/pixi_toml_edit/src/entry.rs:160 — pixi_toml_edit::entry::remove_inline_table_entry has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pixi_docs · ×2
  • pixi_docs::arguments (cognitive 29) crates/pixi_docs/src/main.rs:445 — pixi_docs::arguments has cognitive complexity 29 (threshold 15). Drivers by points: if/else 14 (24 pts), boolean chains 4, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • pixi_docs::subcommand_to_md (cognitive 19) crates/pixi_docs/src/main.rs:137 — pixi_docs::subcommand_to_md has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 5). 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 · PackageReachability · ×2
  • PackageReachability::collect_reachable_from_non_skipped (cognitive 28) crates/pixi_core/src/lock_file/install_subset.rs:401 — PackageReachability::collect_reachable_from_non_skipped has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 8 (10 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • PackageReachability::collect_targets_dependencies (cognitive 23) crates/pixi_core/src/lock_file/install_subset.rs:323 — PackageReachability::collect_targets_dependencies has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 6 (7 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
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Medium CVE · ×2
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (33 corresponding lines) · ×2
  • Edited copy of a member (33 corresponding lines) crates/pixi_cli/src/global/expose.rs:72 — crates/pixi_cli/src/global/expose.rs:72-105 | crates/pixi_cli/src/global/shortcut.rs:57-89 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (33 corresponding lines) crates/pixi_compute_sources/src/git.rs:126 — crates/pixi_compute_sources/src/git.rs:126-164 | crates/pixi_compute_sources/src/url.rs:122-154 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×2
  • Edited copy of a member (36 corresponding lines) crates/pixi_manifest/src/manifests/workspace.rs:1648 — crates/pixi_manifest/src/manifests/workspace.rs:1648-1683 | crates/pixi_manifest/src/manifests/workspace.rs:1737-1774 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (36 corresponding lines) crates/pixi_core/src/workspace/mod.rs:605 — crates/pixi_core/src/workspace/mod.rs:605-641 | crates/pixi_core/src/workspace/mod.rs:651-686 — These two members are one piece of code written twice and then edited apart: 36 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 (26 corresponding lines) · ×2
  • Edited copy of a member (26 corresponding lines) crates/pixi_command_dispatcher/src/backend_source_build/ext.rs:33 — crates/pixi_command_dispatcher/src/backend_source_build/ext.rs:33-69 | crates/pixi_command_dispatcher/src/build_backend_metadata/mod.rs:665-690 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (26 corresponding lines) crates/pixi_core/src/lock_file/update.rs:138 — crates/pixi_core/src/lock_file/update.rs:138-164 | crates/pixi_core/src/lock_file/update.rs:207-232 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×2
  • Edited copy of a member (27 corresponding lines) crates/pixi_global/src/project/parsed_manifest.rs:201 — crates/pixi_global/src/project/parsed_manifest.rs:201-230 | crates/pixi_global/src/project/parsed_manifest.rs:235-261 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (27 corresponding lines) crates/pixi_utils/src/executable_utils.rs:4 — crates/pixi_utils/src/executable_utils.rs:4-30 | trampoline/src/executable_from_path.rs:6-34 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×2
  • Edited copy of a member (29 corresponding lines) crates/pixi_cli/src/add.rs:139 — crates/pixi_cli/src/add.rs:139-167 | crates/pixi_cli/src/remove/mod.rs:50-78 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (29 corresponding lines) crates/pixi_build_backend/src/variants.rs:10 — crates/pixi_build_backend/src/variants.rs:10-45 | crates/pixi_manifest/src/toml/environment.rs:59-87 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×2
  • Duplicated block (29 lines × 2) crates/pixi_toml/src/hash_map.rs:50 — crates/pixi_toml/src/hash_map.rs:50-78 | crates/pixi_toml/src/index_map.rs:53-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 `crates/pixi_toml/src/hash_map.rs:50` 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.
  • Duplicated block (29 lines × 2) crates/pixi_manifest/src/utils/inheritable_package_map.rs:455 — crates/pixi_manifest/src/utils/inheritable_package_map.rs:455-483 | crates/pixi_manifest/src/utils/package_map.rs:244-272 — before extracting anything, compare `crates/pixi_manifest/src/utils/inheritable_package_map.rs` and `crates/pixi_manifest/src/utils/package_map.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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 `crates/pixi_manifest/src/utils/inheritable_package_map.rs:455` 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 (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) crates/pixi_cli/src/add.rs:140 — crates/pixi_cli/src/add.rs:140-162 | crates/pixi_cli/src/remove/mod.rs:51-73 — 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 `crates/pixi_cli/src/add.rs:140` 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 (23 lines × 2) crates/pixi_manifest/src/target.rs:417 — crates/pixi_manifest/src/target.rs:417-439 | crates/pixi_manifest/src/target.rs:630-652 — 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. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×2
  • Duplicated block (15 lines × 2) crates/pixi_manifest/src/toml/exclude_newer.rs:138 — crates/pixi_manifest/src/toml/exclude_newer.rs:138-152 | crates/pixi_manifest/src/toml/exclude_newer.rs:328-342 — 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 `crates/pixi_manifest/src/toml/exclude_newer.rs:138` 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 × 2) scripts/local_patch.py:302 — scripts/local_patch.py:302-318 | scripts/local_patch.py:353-367 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×2
  • Duplicated block (11 lines × 4) crates/pixi_build_cmake/src/config.rs:46 — crates/pixi_build_cmake/src/config.rs:46-56 | crates/pixi_build_mojo/src/config.rs:98-108 | crates/pixi_build_r/src/config.rs:51-61 | crates/pixi_build_rust/src/config.rs:100-110 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `crates/pixi_build_rust/src/config.rs:99` calls `collect_system_env` and `crates/pixi_build_cmake/src/config.rs:45` 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 × 4) crates/pixi_build_cmake/src/build_script.rs:21 — crates/pixi_build_cmake/src/build_script.rs:21-31 | crates/pixi_build_python/src/build_script.rs:42-52 | crates/pixi_build_r/src/build_script.rs:23-33 | crates/pixi_build_rust/src/build_script.rs:20-30 — 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 (8–10 lines × 2) · ×2
  • Duplicated block (8–10 lines × 2) crates/pixi_command_dispatcher/src/backend_source_build/ext.rs:59 — crates/pixi_command_dispatcher/src/backend_source_build/ext.rs:59-68 | crates/pixi_command_dispatcher/src/build_backend_metadata/mod.rs:680-687 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8–10 lines × 2) crates/pixi_uv_conversions/src/git_url.rs:10 — crates/pixi_uv_conversions/src/git_url.rs:10-17 | crates/pixi_uv_conversions/src/git_url.rs:33-42 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (6 lines × 3) · ×2
  • Duplicated block (6 lines × 3) crates/pixi_command_dispatcher/src/backend_source_build/ext.rs:59 — crates/pixi_command_dispatcher/src/backend_source_build/ext.rs:59-64 | crates/pixi_command_dispatcher/src/build_backend_metadata/mod.rs:680-685 | crates/pixi_command_dispatcher/src/install_pixi/ext.rs:71-76 — 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 `crates/pixi_command_dispatcher/src/backend_source_build/ext.rs: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.
  • Duplicated block (6 lines × 3) crates/pixi_manifest/src/toml/environment.rs:176 — crates/pixi_manifest/src/toml/environment.rs:176-181 | crates/pixi_manifest/src/toml/feature.rs:220-225 | crates/pixi_manifest/src/toml/target.rs:313-318 — before extracting anything, compare `crates/pixi_manifest/src/toml/environment.rs` and `crates/pixi_manifest/src/toml/feature.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 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, `crates/pixi_manifest/src/toml/environment.rs:183` calls `optional` and `crates/pixi_manifest/src/toml/feature.rs:227` 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.
D1 · Cyclomatic Complexity · Config · ×1
  • Config::set (cyclomatic 97) crates/pixi_config/src/lib.rs:2516 — Config::set has cyclomatic complexity 97 (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 · pixi_install_pypi · ×1
  • pixi_install_pypi::plan::validation::need_reinstall (cyclomatic 37) crates/pixi_install_pypi/src/plan/validation.rs:47 — pixi_install_pypi::plan::validation::need_reinstall has cyclomatic complexity 37 (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 · Item · ×1
  • Item::from (cyclomatic 36) crates/pixi_manifest/src/task.rs:867 — Item::from has cyclomatic complexity 36 (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 · WorkspaceDiscoverer · ×1
  • WorkspaceDiscoverer::discover (cyclomatic 35) crates/pixi_manifest/src/discovery.rs:361 — WorkspaceDiscoverer::discover has cyclomatic complexity 35 (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 · pixi_api · ×1
  • pixi_api::workspace::run::run (cyclomatic 29) crates/pixi_api/src/workspace/run/mod.rs:155 — pixi_api::workspace::run::run 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 · UpdateContext · ×1
  • UpdateContext::update (cyclomatic 29) crates/pixi_core/src/lock_file/update.rs:2595 — UpdateContext::update 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 · Package · ×1
  • Package::new (cyclomatic 28) crates/pixi_api/src/workspace/list/package.rs:55 — Package::new has cyclomatic complexity 28 (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 · PythonGenerator · ×1
  • PythonGenerator::generate_recipe (cyclomatic 27) crates/pixi_build_python/src/main.rs:214 — PythonGenerator::generate_recipe has cyclomatic complexity 27 (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 · TomlManifest · ×1
  • TomlManifest::into_workspace_manifest (cyclomatic 27) crates/pixi_manifest/src/toml/manifest.rs:155 — TomlManifest::into_workspace_manifest has cyclomatic complexity 27 (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 · CachedWheels · ×1
  • CachedWheels::is_cached (cyclomatic 26) crates/pixi_install_pypi/src/plan/cache.rs:100 — CachedWheels::is_cached 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 · WorkspaceLocator · ×1
  • WorkspaceLocator::locate (cyclomatic 24) crates/pixi_core/src/workspace/discovery.rs:362 — WorkspaceLocator::locate has cyclomatic complexity 24 (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 · HostDetector · ×1
  • HostDetector::detect_registrations (cyclomatic 20) crates/pixi_core/src/host.rs:622 — HostDetector::detect_registrations has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · WorkspaceMut · ×1
  • WorkspaceMut::update_dependencies (cyclomatic 20) crates/pixi_core/src/workspace/workspace_mut.rs:433 — WorkspaceMut::update_dependencies has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PtySession · ×1
  • PtySession::interact (cyclomatic 20) crates/pixi_pty/src/unix/pty_session.rs:115 — PtySession::interact has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · pixi_global · ×1
  • pixi_global::common::build_report (cyclomatic 19) crates/pixi_global/src/common.rs:529 — pixi_global::common::build_report has cyclomatic complexity 19 (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 · TomlPackage · ×1
  • TomlPackage::into_manifest (cyclomatic 19) crates/pixi_manifest/src/toml/package.rs:350 — TomlPackage::into_manifest has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · ArtifactCache · ×1
  • ArtifactCache::lookup (cyclomatic 18) crates/pixi_command_dispatcher/src/cache/artifact.rs:583 — ArtifactCache::lookup 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 · CommandDispatcherBuilder · ×1
  • CommandDispatcherBuilder::finish (cyclomatic 18) crates/pixi_command_dispatcher/src/command_dispatcher/builder.rs:358 — CommandDispatcherBuilder::finish 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 · UpdateContextBuilder · ×1
  • UpdateContextBuilder::finish (cyclomatic 17) crates/pixi_core/src/lock_file/update.rs:2298 — UpdateContextBuilder::finish has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · LockFileDiff · ×1
  • LockFileDiff::from_lock_files (cyclomatic 17) crates/pixi_diff/src/lib.rs:38 — LockFileDiff::from_lock_files has cyclomatic complexity 17 (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.
D1 · Cyclomatic Complexity · PyPIEnvironmentUpdater · ×1
  • PyPIEnvironmentUpdater::log_installation_details (cyclomatic 17) crates/pixi_install_pypi/src/lib.rs:911 — PyPIEnvironmentUpdater::log_installation_details has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · pixi_script_shell · ×1
  • pixi_script_shell::execute::evaluate_word (cyclomatic 17) crates/pixi_script_shell/src/execute.rs:271 — pixi_script_shell::execute::evaluate_word has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · SearchEnvironments · ×1
  • SearchEnvironments::find_task (cyclomatic 17) crates/pixi_task/src/task_environment.rs:206 — SearchEnvironments::find_task 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 · pixi_command_dispatcher · ×1
  • pixi_command_dispatcher::install_pixi::ext::install_inner (cyclomatic 16) crates/pixi_command_dispatcher/src/install_pixi/ext.rs:98 — pixi_command_dispatcher::install_pixi::ext::install_inner 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 · Workspace · ×1
  • Workspace::update_lock_file_with_input (cyclomatic 16) crates/pixi_core/src/lock_file/update.rs:326 — Workspace::update_lock_file_with_input 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 · pixi_git · ×1
  • pixi_git::git::fetch (cyclomatic 16) crates/pixi_git/src/git.rs:791 — pixi_git::git::fetch has cyclomatic complexity 16 (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 · Project · ×1
  • Project::environment_in_sync_internal (cyclomatic 16) crates/pixi_global/src/project/mod.rs:1621 — Project::environment_in_sync_internal 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 · pixi_manifest · ×1
  • pixi_manifest::platform::host::apply_conda_overrides (cyclomatic 16) crates/pixi_manifest/src/platform/host.rs:141 — pixi_manifest::platform::host::apply_conda_overrides has cyclomatic complexity 16 (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 · UrlSource · ×1
  • UrlSource::fetch (cyclomatic 16) crates/pixi_url/src/source.rs:145 — UrlSource::fetch 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.
D17 · Explicit Debt · XxxComment · ×1
  • XxxComment tests/integration_python/pixi_global/test_global.py:2816 — # XXX: should this fail instead? — 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.
D17 · Explicit Debt · HackComment · ×1
  • HackComment crates/pixi_config/src/lib.rs:1879 — // HACK: Use win-64 as the default tool platform if currently running on — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D2 · Cognitive Complexity · Config · ×1
  • Config::set (cognitive 118) crates/pixi_config/src/lib.rs:2516 — Config::set has cognitive complexity 118 (threshold 15). Drivers by points: if/else 47 (92 pts), match/switch 12 (25 pts), boolean chains 1 (nesting depth added 58). 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 · Item · ×1
  • Item::from (cognitive 100) crates/pixi_manifest/src/task.rs:867 — Item::from has cognitive complexity 100 (threshold 15). Drivers by points: if/else 25 (73 pts), loops 4 (13 pts), match/switch 6 (12 pts), boolean chains 2 (nesting depth added 63). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · pixi_install_pypi · ×1
  • pixi_install_pypi::plan::validation::need_reinstall (cognitive 82) crates/pixi_install_pypi/src/plan/validation.rs:47 — pixi_install_pypi::plan::validation::need_reinstall has cognitive complexity 82 (threshold 15). Drivers by points: if/else 21 (51 pts), match/switch 12 (30 pts), boolean chains 1 (nesting depth added 48). 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 · WorkspaceDiscoverer · ×1
  • WorkspaceDiscoverer::discover (cognitive 77) crates/pixi_manifest/src/discovery.rs:361 — WorkspaceDiscoverer::discover has cognitive complexity 77 (threshold 15). Drivers by points: if/else 18 (45 pts), match/switch 11 (26 pts), boolean chains 5, loops 1 (nesting depth added 42). 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 · PtySession · ×1
  • PtySession::interact (cognitive 60) crates/pixi_pty/src/unix/pty_session.rs:115 — PtySession::interact has cognitive complexity 60 (threshold 15). Drivers by points: if/else 16 (52 pts), match/switch 2 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 39). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · UpdateContext · ×1
  • UpdateContext::update (cognitive 59) crates/pixi_core/src/lock_file/update.rs:2595 — UpdateContext::update has cognitive complexity 59 (threshold 15). Drivers by points: if/else 10 (27 pts), loops 9 (17 pts), match/switch 7 (14 pts), boolean chains 1 (nesting depth added 32). 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 · PypiExtrasResolver · ×1
  • PypiExtrasResolver::propagate (cognitive 44) crates/pixi_cli/src/tree.rs:228 — PypiExtrasResolver::propagate has cognitive complexity 44 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 7 (18 pts), match/switch 1 (4 pts) (nesting depth added 30). 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 · Package · ×1
  • Package::new (cognitive 43) crates/pixi_api/src/workspace/list/package.rs:55 — Package::new has cognitive complexity 43 (threshold 15). Drivers by points: match/switch 21 (23 pts), if/else 10 (20 pts) (nesting depth added 12). 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 · PythonGenerator · ×1
  • PythonGenerator::generate_recipe (cognitive 43) crates/pixi_build_python/src/main.rs:214 — PythonGenerator::generate_recipe has cognitive complexity 43 (threshold 15). Drivers by points: if/else 27 (32 pts), loops 4 (8 pts), boolean chains 2, match/switch 1 (nesting depth added 9). 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 · CachedWheels · ×1
  • CachedWheels::is_cached (cognitive 42) crates/pixi_install_pypi/src/plan/cache.rs:100 — CachedWheels::is_cached has cognitive complexity 42 (threshold 15). Drivers by points: if/else 13 (27 pts), match/switch 7 (15 pts) (nesting depth added 22). 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 · TomlManifest · ×1
  • TomlManifest::into_workspace_manifest (cognitive 42) crates/pixi_manifest/src/toml/manifest.rs:155 — TomlManifest::into_workspace_manifest has cognitive complexity 42 (threshold 15). Drivers by points: if/else 19 (31 pts), loops 5 (6 pts), match/switch 2 (4 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · InstallPlanner · ×1
  • InstallPlanner::plan (cognitive 34) crates/pixi_install_pypi/src/plan/planner.rs:91 — InstallPlanner::plan has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (22 pts), match/switch 3 (9 pts), loops 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · WorkspaceMut · ×1
  • WorkspaceMut::update_dependencies (cognitive 28) crates/pixi_core/src/workspace/workspace_mut.rs:433 — WorkspaceMut::update_dependencies has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 3, loops 3, match/switch 1 (2 pts) (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 · HostDetector · ×1
  • HostDetector::detect_registrations (cognitive 27) crates/pixi_core/src/host.rs:622 — HostDetector::detect_registrations has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 4 (9 pts), boolean chains 4, loops 4 (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 · UpdateContextBuilder · ×1
  • UpdateContextBuilder::finish (cognitive 27) crates/pixi_core/src/lock_file/update.rs:2298 — UpdateContextBuilder::finish has cognitive complexity 27 (threshold 15). Drivers by points: loops 6 (13 pts), if/else 5 (9 pts), match/switch 5 (nesting depth added 11). 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 · pixi_script_shell · ×1
  • pixi_script_shell::execute::evaluate_word (cognitive 27) crates/pixi_script_shell/src/execute.rs:271 — pixi_script_shell::execute::evaluate_word has cognitive complexity 27 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 3 (8 pts), match/switch 2 (6 pts), boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RattlerBuildBackendInstantiator · ×1
  • RattlerBuildBackendInstantiator::initialize (cognitive 25) crates/pixi_build_rattler_build/src/protocol.rs:670 — RattlerBuildBackendInstantiator::initialize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 3 (8 pts), match/switch 1 (4 pts) (nesting depth added 13). Most of this is not in the body itself: 11 of the 25 points are its own statements and the rest belongs to one function item inside it that branches (extract_workspace_deps). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
D2 · Cognitive Complexity · ArtifactCache · ×1
  • ArtifactCache::lookup (cognitive 25) crates/pixi_command_dispatcher/src/cache/artifact.rs:583 — ArtifactCache::lookup has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (14 pts), match/switch 3 (6 pts), loops 2 (5 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 · SearchEnvironments · ×1
  • SearchEnvironments::find_task (cognitive 24) crates/pixi_task/src/task_environment.rs:206 — SearchEnvironments::find_task has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (15 pts), match/switch 4 (6 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · LockFileDerivedData · ×1
  • LockFileDerivedData::prefix (cognitive 23) crates/pixi_core/src/lock_file/update.rs:1184 — LockFileDerivedData::prefix has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 3, match/switch 2 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RGenerator · ×1
  • RGenerator::generate_recipe (cognitive 22) crates/pixi_build_r/src/main.rs:68 — RGenerator::generate_recipe has cognitive complexity 22 (threshold 15). Drivers by points: if/else 14 (19 pts), loops 2, match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Project · ×1
  • Project::environment_in_sync_internal (cognitive 22) crates/pixi_global/src/project/mod.rs:1621 — Project::environment_in_sync_internal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, loops 1 (2 pts), match/switch 1 (2 pts) (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 · LockedEnvironmentHash · ×1
  • LockedEnvironmentHash::from_environment (cognitive 21) crates/pixi_core/src/environment/mod.rs:308 — LockedEnvironmentHash::from_environment has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), match/switch 2 (5 pts), loops 2 (4 pts) (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 · Workspace · ×1
  • Workspace::update_lock_file_with_input (cognitive 21) crates/pixi_core/src/lock_file/update.rs:326 — Workspace::update_lock_file_with_input has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5, loops 1 (2 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · Entrypoint · ×1
  • Entrypoint::deserialize (cognitive 21) crates/pixi_manifest/src/script/conda/entrypoint.rs:70 — Entrypoint::deserialize has cognitive complexity 21 (threshold 15). Drivers by points: match/switch 4 (11 pts), if/else 4 (8 pts), loops 1 (2 pts) (nesting depth added 12). 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 · TomlPackage · ×1
  • TomlPackage::into_manifest (cognitive 21) crates/pixi_manifest/src/toml/package.rs:350 — TomlPackage::into_manifest has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 7 (9 pts), match/switch 2, boolean chains 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 5 belong to one function item 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 · Parser · ×1
  • Parser::sequence (cognitive 21) crates/pixi_script_shell/src/parse.rs:107 — Parser::sequence has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MojoBackendConfig · ×1
  • MojoBackendConfig::merge_with_target_config (cognitive 20) crates/pixi_build_mojo/src/config.rs:52 — MojoBackendConfig::merge_with_target_config has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (17 pts), match/switch 1 (3 pts) (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 · fmt (cognitive 20) · ×1
  • Info::fmt (cognitive 20) crates/pixi_cli/src/info.rs:472 — Info::fmt has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 3 (4 pts), match/switch 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · DiscoveredBackend · ×1
  • DiscoveredBackend::discover (cognitive 19) crates/pixi_build_discovery/src/discovery.rs:128 — DiscoveredBackend::discover has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PypiNoBuildCheck · ×1
  • PypiNoBuildCheck::check (cognitive 19) crates/pixi_core/src/lock_file/satisfiability/environment.rs:381 — PypiNoBuildCheck::check has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 4 (6 pts) (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 · WorkspaceLocator · ×1
  • WorkspaceLocator::locate (cognitive 19) crates/pixi_core/src/workspace/discovery.rs:362 — WorkspaceLocator::locate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 3, match/switch 3 (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 · PinnedGitCheckout · ×1
  • PinnedGitCheckout::from_locked_url (cognitive 19) crates/pixi_record/src/pinned_source.rs:346 — PinnedGitCheckout::from_locked_url has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SchemaJsonEncoder.normalize_schema (cognitive 19) · ×1
  • SchemaJsonEncoder.normalize_schema (cognitive 19) schema/model.py:1678 — SchemaJsonEncoder.normalize_schema has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 7 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · IntermediateBackend · ×1
  • IntermediateBackend::conda_outputs (cognitive 18) crates/pixi_build_backend/src/intermediate_backend.rs:252 — IntermediateBackend::conda_outputs has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 2 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · pixi_git · ×1
  • pixi_git::git::fetch (cognitive 18) crates/pixi_git/src/git.rs:791 — pixi_git::git::fetch has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), match/switch 4 (5 pts) (nesting depth added 6). 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 · ConditionalInheritablePackageMap · ×1
  • ConditionalInheritablePackageMap::deserialize (cognitive 18) crates/pixi_manifest/src/utils/inheritable_package_map.rs:546 — ConditionalInheritablePackageMap::deserialize has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 4 (10 pts), if/else 6 (7 pts), loops 1 (nesting depth added 7). 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 · pixi_uv_conversions · ×1
  • pixi_uv_conversions::conversions::configure_insecure_hosts_for_tls_bypass (cognitive 18) crates/pixi_uv_conversions/src/conversions.rs:760 — pixi_uv_conversions::conversions::configure_insecure_hosts_for_tls_bypass has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), match/switch 1 (3 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 · CommandDispatcherBuilder · ×1
  • CommandDispatcherBuilder::finish (cognitive 17) crates/pixi_command_dispatcher/src/command_dispatcher/builder.rs:358 — CommandDispatcherBuilder::finish has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. 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 · ExcludeNewerTableMigration · ×1
  • ExcludeNewerTableMigration::new (cognitive 17) crates/pixi_manifest/src/exclude_newer.rs:566 — ExcludeNewerTableMigration::new has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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 · ManifestDocument · ×1
  • ManifestDocument::add_pypi_dependency (cognitive 17) crates/pixi_manifest/src/manifests/document.rs:567 — ManifestDocument::add_pypi_dependency has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 2). 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 · ParsedBlock · ×1
  • ParsedBlock::from_toml_str (cognitive 17) crates/pixi_manifest/src/script/conda/metadata.rs:72 — ParsedBlock::from_toml_str has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), match/switch 5 (7 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · TomlPackageBuild · ×1
  • TomlPackageBuild::into_build_system (cognitive 17) crates/pixi_manifest/src/toml/build_backend.rs:58 — TomlPackageBuild::into_build_system has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (15 pts), loops 1, match/switch 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 · TomlPreview · ×1
  • TomlPreview::into_preview (cognitive 17) crates/pixi_manifest/src/toml/preview.rs:51 — TomlPreview::into_preview has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · PurlDerivationClient · ×1
  • PurlDerivationClient::amend_purls (cognitive 17) crates/pypi_mapping/src/lib.rs:246 — PurlDerivationClient::amend_purls has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3, match/switch 1 (2 pts) (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 · pixi_build_python · ×1
  • pixi_build_python::pypi_mapping::apply_user_map (cognitive 16) crates/pixi_build_python/src/pypi_mapping.rs:501 — pixi_build_python::pypi_mapping::apply_user_map has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), match/switch 3 (7 pts), loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · RosGenerator · ×1
  • RosGenerator::generate_recipe (cognitive 16) crates/pixi_build_ros/src/main.rs:46 — RosGenerator::generate_recipe has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, loops 4 (6 pts), boolean chains 1 (nesting depth added 2). 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 · DetectorInfo · ×1
  • DetectorInfo::from_host (cognitive 16) crates/pixi_cli/src/info.rs:351 — DetectorInfo::from_host has cognitive complexity 16 (threshold 15). Drivers by points: match/switch 5 (8 pts), if/else 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 6). 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 · HostDetection · ×1
  • HostDetection::for_cached_run (cognitive 16) crates/pixi_core/src/host.rs:337 — HostDetection::for_cached_run has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), match/switch 2 (5 pts), boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PyPIEnvironmentUpdater · ×1
  • PyPIEnvironmentUpdater::log_installation_details (cognitive 16) crates/pixi_install_pypi/src/lib.rs:911 — PyPIEnvironmentUpdater::log_installation_details has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), loops 3 (4 pts), match/switch 2 (3 pts) (nesting depth added 4). 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 · UrlSource · ×1
  • UrlSource::fetch (cognitive 16) crates/pixi_url/src/source.rs:145 — UrlSource::fetch has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, match/switch 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member pair (42 shared lines) · ×1
  • Near-duplicate member pair (42 shared lines) crates/pixi_manifest/src/utils/inheritable_package_map.rs:447 — crates/pixi_manifest/src/utils/inheritable_package_map.rs:447-510 | crates/pixi_manifest/src/utils/package_map.rs:235-336 — These two members are variants of one another: 42 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication · Near-duplicate member pair (33 shared lines) · ×1
  • Near-duplicate member pair (33 shared lines) crates/pixi_config/src/lib.rs:1959 — crates/pixi_config/src/lib.rs:1959-2000 | crates/pixi_config/src/lib.rs:2016-2070 — These two members are variants of one another: 33 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 · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (5 members, 50+ identical tokens) crates/pixi_build_backend/src/intermediate_backend.rs:255 — crates/pixi_build_backend/src/intermediate_backend.rs:255-667 | crates/pixi_build_backend/src/intermediate_backend.rs:672-982 | crates/pixi_build_backend/src/rattler_build_integration.rs:46-245 | crates/pixi_build_rattler_build/src/protocol.rs:68-364 | crates/pixi_build_rattler_build/src/protocol.rs:369-567 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication · Edited copy of a member (70 corresponding lines) · ×1
  • Edited copy of a member (70 corresponding lines) crates/pixi_toml_edit/src/array.rs:100 — crates/pixi_toml_edit/src/array.rs:100-185 | crates/pixi_toml_edit/src/entry.rs:160-229 — These two members are one piece of code written twice and then edited apart: 70 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 (58 corresponding lines) · ×1
  • Edited copy of a member (58 corresponding lines) crates/pixi_manifest/src/toml/exclude_newer.rs:127 — crates/pixi_manifest/src/toml/exclude_newer.rs:127-185 | crates/pixi_manifest/src/toml/exclude_newer.rs:317-374 — These two members are one piece of code written twice and then edited apart: 58 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 (61 corresponding lines) · ×1
  • Edited copy of a member (61 corresponding lines) crates/pixi_core/src/lock_file/install_subset.rs:328 — crates/pixi_core/src/lock_file/install_subset.rs:328-388 | crates/pixi_core/src/lock_file/install_subset.rs:405-477 — These two members are one piece of code written twice and then edited apart: 61 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 (59 corresponding lines) · ×1
  • Edited copy of a member (59 corresponding lines) crates/pixi_manifest/src/manifests/workspace.rs:560 — crates/pixi_manifest/src/manifests/workspace.rs:560-618 | crates/pixi_manifest/src/manifests/workspace.rs:664-724 — These two members are one piece of code written twice and then edited apart: 59 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 (55 corresponding lines) · ×1
  • Edited copy of a member (55 corresponding lines) crates/pixi_uv_conversions/src/conversions.rs:125 — crates/pixi_uv_conversions/src/conversions.rs:125-181 | crates/pixi_uv_conversions/src/conversions.rs:191-245 — These two members are one piece of code written twice and then edited apart: 55 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×1
  • Edited copy of a member (40 corresponding lines) crates/pixi_toml/src/hash_map.rs:37 — crates/pixi_toml/src/hash_map.rs:37-78 | crates/pixi_toml/src/index_map.rs:45-84 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (46 corresponding lines) · ×1
  • Edited copy of a member (46 corresponding lines) crates/pixi_build_frontend/src/backend/json_rpc.rs:298 — crates/pixi_build_frontend/src/backend/json_rpc.rs:298-343 | crates/pixi_build_frontend/src/backend/json_rpc.rs:350-395 — These two members are one piece of code written twice and then edited apart: 46 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 (50 corresponding lines) · ×1
  • Edited copy of a member (50 corresponding lines) crates/pixi_command_dispatcher/src/cache/common.rs:52 — crates/pixi_command_dispatcher/src/cache/common.rs:52-110 | crates/pixi_command_dispatcher/src/cache/common.rs:247-296 — These two members are one piece of code written twice and then edited apart: 50 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 (38 corresponding lines) · ×1
  • Edited copy of a member (38 corresponding lines) crates/pixi_core/src/workspace/mod.rs:1107 — crates/pixi_core/src/workspace/mod.rs:1107-1157 | crates/pixi_core/src/workspace/mod.rs:1179-1216 — These two members are one piece of code written twice and then edited apart: 38 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 (32 corresponding lines) · ×1
  • Edited copy of a member (32 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs:384 — crates/pixi_reporters/src/download_verify_reporter.rs:384-426 | crates/pixi_reporters/src/repodata_reporter.rs:700-731 — These two members are one piece of code written twice and then edited apart: 32 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 (43 corresponding lines) · ×1
  • Edited copy of a member (43 corresponding lines) crates/pixi_core/src/workspace/mod.rs:553 — crates/pixi_core/src/workspace/mod.rs:553-595 | crates/pixi_core/src/workspace/mod.rs:697-742 — These two members are one piece of code written twice and then edited apart: 43 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 (57 corresponding lines) · ×1
  • Edited copy of a member (57 corresponding lines) crates/pixi_command_dispatcher/src/build/conversion.rs:77 — crates/pixi_command_dispatcher/src/build/conversion.rs:77-133 | crates/pixi_command_dispatcher/src/build/dependencies.rs:483-547 — These two members are one piece of code written twice and then edited apart: 57 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 (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) crates/pixi_manifest/src/toml/pypi_options.rs:76 — crates/pixi_manifest/src/toml/pypi_options.rs:76-110 | crates/pixi_manifest/src/toml/pypi_options.rs:114-148 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 21+ corresponding lines) crates/pixi_url/src/extract.rs:123 — crates/pixi_url/src/extract.rs:123-148 | crates/pixi_url/src/extract.rs:158-186 | crates/pixi_url/src/extract.rs:193-213 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 36+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 36+ corresponding lines) crates/pixi_api/src/workspace/workspace/channel.rs:79 — crates/pixi_api/src/workspace/workspace/channel.rs:79-116 | crates/pixi_api/src/workspace/workspace/channel.rs:123-158 | crates/pixi_api/src/workspace/workspace/channel.rs:164-200 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 36 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) crates/pixi_cli/src/workspace/channel.rs:100 — crates/pixi_cli/src/workspace/channel.rs:100-127 | crates/pixi_cli/src/workspace/platform.rs:467-495 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) crates/pixi_command_dispatcher/src/keys/solve_conda.rs:73 — crates/pixi_command_dispatcher/src/keys/solve_conda.rs:73-111 | crates/pixi_manifest/src/build_system.rs:82-123 — These two members are one piece of code written twice and then edited apart: 39 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (7 members, 19+ corresponding lines) crates/pixi_build_rust/src/metadata.rs:210 — crates/pixi_build_rust/src/metadata.rs:210-232 | crates/pixi_build_rust/src/metadata.rs:239-259 | crates/pixi_build_rust/src/metadata.rs:266-284 | crates/pixi_build_rust/src/metadata.rs:291-309 | crates/pixi_build_rust/src/metadata.rs:318-338 | crates/pixi_build_rust/src/metadata.rs:354-377 | crates/pixi_build_rust/src/metadata.rs:384-404 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 19 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) crates/pixi_reporters/src/download_verify_reporter.rs:110 — crates/pixi_reporters/src/download_verify_reporter.rs:110-139 | crates/pixi_reporters/src/main_progress_bar.rs:121-153 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 15+ corresponding lines) crates/pixi_toml_edit/src/entry.rs:262 — crates/pixi_toml_edit/src/entry.rs:262-276 | crates/pixi_toml_edit/src/entry.rs:298-313 | crates/pixi_toml_edit/src/entry.rs:355-369 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) crates/pixi_cli/src/install.rs:89 — crates/pixi_cli/src/install.rs:89-111 | crates/pixi_cli/src/run.rs:125-147 — 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 (21 corresponding lines) · ×1
  • Edited copy of a member (21 corresponding lines) crates/pixi_reporters/src/uv_reporter.rs:144 — crates/pixi_reporters/src/uv_reporter.rs:144-164 | crates/pixi_reporters/src/uv_reporter.rs:166-186 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) crates/pixi_api/src/workspace/workspace/activation.rs:127 — crates/pixi_api/src/workspace/workspace/activation.rs:127-144 | crates/pixi_api/src/workspace/workspace/activation.rs:154-171 | crates/pixi_api/src/workspace/workspace/activation.rs:180-197 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 14+ corresponding lines) crates/pixi_build_cmake/src/main.rs:174 — crates/pixi_build_cmake/src/main.rs:174-187 | crates/pixi_build_mojo/src/main.rs:229-242 | crates/pixi_build_python/src/main.rs:588-601 | crates/pixi_build_r/src/main.rs:312-325 | crates/pixi_build_ros/src/main.rs:395-408 | crates/pixi_build_rust/src/main.rs:224-237 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 16+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 16+ corresponding lines) crates/pixi_build_types/src/project_model.rs:935 — crates/pixi_build_types/src/project_model.rs:935-954 | crates/pixi_build_types/src/project_model.rs:960-975 | crates/pixi_build_types/src/project_model.rs:1073-1088 | crates/pixi_build_types/src/project_model.rs:1138-1156 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 8+ corresponding lines) crates/pixi_manifest/src/features_ext.rs:249 — crates/pixi_manifest/src/features_ext.rs:249-256 | crates/pixi_manifest/src/features_ext.rs:271-278 | crates/pixi_manifest/src/features_ext.rs:295-302 | crates/pixi_manifest/src/features_ext.rs:312-320 | crates/pixi_manifest/src/features_ext.rs:330-337 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 7+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 7+ corresponding lines) crates/pixi_command_dispatcher/src/cache/artifact.rs:524 — crates/pixi_command_dispatcher/src/cache/artifact.rs:524-531 | crates/pixi_command_dispatcher/src/cache/artifact.rs:534-540 | crates/pixi_command_dispatcher/src/cache/workspace.rs:157-164 | crates/pixi_command_dispatcher/src/cache/workspace.rs:167-173 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 15+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 15+ corresponding lines) crates/pixi_build_types/src/project_model.rs:888 — crates/pixi_build_types/src/project_model.rs:888-906 | crates/pixi_build_types/src/project_model.rs:913-929 | crates/pixi_build_types/src/project_model.rs:979-993 | crates/pixi_build_types/src/project_model.rs:997-1011 | crates/pixi_build_types/src/project_model.rs:1095-1109 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×1
  • Edited copy of a member (6 corresponding lines) crates/pixi_api/src/workspace/workspace/platform.rs:48 — crates/pixi_api/src/workspace/workspace/platform.rs:48-54 | crates/pixi_core/src/workspace/mod.rs:1265-1270 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) crates/pixi_build_types/src/extra_group_name.rs:133 — crates/pixi_build_types/src/extra_group_name.rs:133-136 | crates/pixi_path/src/lib.rs:416-419 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (85 lines × 2) · ×1
  • Duplicated block (85 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:536 — crates/pixi_build_backend/src/intermediate_backend.rs:536-620 | crates/pixi_build_rattler_build/src/protocol.rs:233-317 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_rattler_build/src/protocol.rs` as WHOLE FILES: this scan already matched 12 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 `crates/pixi_build_backend/src/intermediate_backend.rs:536` 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.
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) crates/pixi_build_types/src/variant.rs:26 — crates/pixi_build_types/src/variant.rs:26-65 | crates/pixi_variant/src/lib.rs:32-71 — before extracting anything, compare `crates/pixi_build_types/src/variant.rs` and `crates/pixi_variant/src/lib.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (35 lines × 2) · ×1
  • Duplicated block (35 lines × 2) crates/pixi_cli/src/workspace/export/conda_environment.rs:193 — crates/pixi_cli/src/workspace/export/conda_environment.rs:193-227 | crates/pixi_cli/src/workspace/export/conda_environment.rs:364-398 — 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 `crates/pixi_cli/src/workspace/export/conda_environment.rs:193` 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 (30–31 lines × 2) · ×1
  • Duplicated block (30–31 lines × 2) crates/pixi_manifest/src/toml/feature.rs:191 — crates/pixi_manifest/src/toml/feature.rs:191-220 | crates/pixi_manifest/src/toml/manifest.rs:1006-1036 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (24–26 lines × 2) · ×1
  • Duplicated block (24–26 lines × 2) crates/pixi_api/src/workspace/remove/mod.rs:88 — crates/pixi_api/src/workspace/remove/mod.rs:88-113 | crates/pixi_api/src/workspace/remove/mod.rs:126-149 — 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 `crates/pixi_api/src/workspace/remove/mod.rs:88` 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 (24–25 lines × 2) · ×1
  • Duplicated block (24–25 lines × 2) crates/pixi_build_backend/src/intermediate_backend.rs:343 — crates/pixi_build_backend/src/intermediate_backend.rs:343-366 | crates/pixi_build_backend/src/intermediate_backend.rs:765-789 — 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 `crates/pixi_build_backend/src/intermediate_backend.rs:343` 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 (23–24 lines × 3) · ×1
  • Duplicated block (23–24 lines × 3) crates/pixi_api/src/workspace/workspace/channel.rs:85 — crates/pixi_api/src/workspace/workspace/channel.rs:85-108 | crates/pixi_api/src/workspace/workspace/channel.rs:128-150 | crates/pixi_api/src/workspace/workspace/channel.rs:169-192 — 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 `crates/pixi_api/src/workspace/workspace/channel.rs:85` 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 (22–24 lines × 2) · ×1
  • Duplicated block (22–24 lines × 2) crates/pixi_core/src/lock_file/install_subset.rs:359 — crates/pixi_core/src/lock_file/install_subset.rs:359-380 | crates/pixi_core/src/lock_file/install_subset.rs:446-469 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (21–22 lines × 2) · ×1
  • Duplicated block (21–22 lines × 2) crates/pixi_api/src/workspace/run/mod.rs:196 — crates/pixi_api/src/workspace/run/mod.rs:196-216 | crates/pixi_cli/src/conda_script.rs:86-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) crates/pixi_build_r/src/main.rs:162 — crates/pixi_build_r/src/main.rs:162-182 | crates/pixi_build_r/src/main.rs:193-213 — 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 `crates/pixi_build_r/src/main.rs:162` 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–20 lines × 2) · ×1
  • Duplicated block (18–20 lines × 2) crates/pixi_core/src/lock_file/update.rs:2455 — crates/pixi_core/src/lock_file/update.rs:2455-2474 | crates/pixi_core/src/lock_file/update.rs:2499-2516 — 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 `crates/pixi_core/src/lock_file/update.rs:2455` 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 (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) crates/pixi_build_rattler_build/src/protocol.rs:83 — crates/pixi_build_rattler_build/src/protocol.rs:83-101 | crates/pixi_build_rattler_build/src/protocol.rs:398-416 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (17–18 lines × 2) · ×1
  • Duplicated block (17–18 lines × 2) crates/pixi_cli/src/global/expose.rs:151 — crates/pixi_cli/src/global/expose.rs:151-167 | crates/pixi_cli/src/global/shortcut.rs:165-182 — before extracting anything, compare `crates/pixi_cli/src/global/expose.rs` and `crates/pixi_cli/src/global/shortcut.rs` 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. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_cli/src/global/expose.rs:151` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `project` to `&mut pixi_global::Project` in one and `&mut Project` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×1
  • Duplicated block (17 lines × 3) crates/pixi_build_backend/src/intermediate_backend.rs:784 — crates/pixi_build_backend/src/intermediate_backend.rs:784-800 | crates/pixi_build_backend/src/rattler_build_integration.rs:88-104 | crates/pixi_build_rattler_build/src/protocol.rs:440-456 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_backend/src/rattler_build_integration.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 `crates/pixi_build_backend/src/intermediate_backend.rs:784` 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 (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) crates/pixi_build_backend/src/tools.rs:203 — crates/pixi_build_backend/src/tools.rs:203-218 | crates/pixi_build_rattler_build/src/protocol.rs:83-98 | crates/pixi_build_rattler_build/src/protocol.rs:398-413 — 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.
D4 · Code Duplication · Duplicated block (13–16 lines × 2) · ×1
  • Duplicated block (13–16 lines × 2) crates/pixi_build_backend/src/dependencies.rs:179 — crates/pixi_build_backend/src/dependencies.rs:179-191 | crates/pixi_build_backend/src/dependencies.rs:276-291 — 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 `crates/pixi_build_backend/src/dependencies.rs:179` 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) crates/pixi_command_dispatcher/src/cache/common.rs:200 — crates/pixi_command_dispatcher/src/cache/common.rs:200-215 | crates/pixi_command_dispatcher/src/cache/common.rs:268-282 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (13–15 lines × 3) · ×1
  • Duplicated block (13–15 lines × 3) crates/pixi_build_cmake/src/main.rs:68 — crates/pixi_build_cmake/src/main.rs:68-82 | crates/pixi_build_mojo/src/main.rs:47-61 | crates/pixi_build_rust/src/main.rs:55-67 — 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. 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 (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) crates/pixi_install_pypi/src/plan/cache.rs:141 — crates/pixi_install_pypi/src/plan/cache.rs:141-155 | crates/pixi_install_pypi/src/plan/cache.rs:189-202 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (14 lines × 5) · ×1
  • Duplicated block (14 lines × 5) crates/pixi_build_backend/src/intermediate_backend.rs:368 — crates/pixi_build_backend/src/intermediate_backend.rs:368-381 | crates/pixi_build_backend/src/intermediate_backend.rs:790-803 | crates/pixi_build_backend/src/rattler_build_integration.rs:94-107 | crates/pixi_build_rattler_build/src/protocol.rs:131-144 | crates/pixi_build_rattler_build/src/protocol.rs:446-459 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_backend/src/rattler_build_integration.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 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 `crates/pixi_build_backend/src/intermediate_backend.rs:368` 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 (10–14 lines × 2) · ×1
  • Duplicated block (10–14 lines × 2) crates/pixi_command_dispatcher/src/build/dependencies.rs:392 — crates/pixi_command_dispatcher/src/build/dependencies.rs:392-405 | crates/pixi_core/src/lock_file/satisfiability/source_record.rs:529-538 — 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 `crates/pixi_command_dispatcher/src/build/dependencies.rs:392` 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 (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) crates/pixi_core/src/lock_file/install_subset.rs:176 — crates/pixi_core/src/lock_file/install_subset.rs:176-189 | crates/pixi_core/src/lock_file/install_subset.rs:214-225 — 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 `crates/pixi_core/src/lock_file/install_subset.rs:176` 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 (11–14 lines × 2) · ×1
  • Duplicated block (11–14 lines × 2) crates/pixi_core/src/lock_file/resolve/pypi.rs:1033 — crates/pixi_core/src/lock_file/resolve/pypi.rs:1033-1046 | crates/pixi_core/src/lock_file/resolve/pypi.rs:1063-1073 — 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 `crates/pixi_core/src/lock_file/resolve/pypi.rs:1033` 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, `crates/pixi_core/src/lock_file/resolve/pypi.rs:1059` calls `from_str`, `map_err`, `ExpectedPath` and `crates/pixi_core/src/lock_file/resolve/pypi.rs:1027` 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–14 lines × 2) · ×1
  • Duplicated block (9–14 lines × 2) crates/pixi_manifest/src/toml/platform.rs:335 — crates/pixi_manifest/src/toml/platform.rs:335-348 | crates/pixi_manifest/src/toml/platform.rs:1103-1111 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_manifest/src/toml/platform.rs:335` 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–13 lines × 2) · ×1
  • Duplicated block (10–13 lines × 2) crates/pixi_build_backend_passthrough/src/lib.rs:812 — crates/pixi_build_backend_passthrough/src/lib.rs:812-821 | crates/pixi_build_backend_passthrough/src/lib.rs:995-1007 — 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 `crates/pixi_build_backend_passthrough/src/lib.rs:812` 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 (12–13 lines × 2) · ×1
  • Duplicated block (12–13 lines × 2) crates/pixi_core/src/lock_file/install_subset.rs:330 — crates/pixi_core/src/lock_file/install_subset.rs:330-342 | crates/pixi_core/src/lock_file/install_subset.rs:407-418 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (10–12 lines × 2) · ×1
  • Duplicated block (10–12 lines × 2) crates/pixi_manifest/src/manifests/workspace.rs:1652 — crates/pixi_manifest/src/manifests/workspace.rs:1652-1661 | crates/pixi_manifest/src/manifests/workspace.rs:1741-1752 — 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 `crates/pixi_manifest/src/manifests/workspace.rs:1652` 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 (11–12 lines × 2) · ×1
  • Duplicated block (11–12 lines × 2) crates/pixi_manifest/src/toml/environment.rs:165 — crates/pixi_manifest/src/toml/environment.rs:165-175 | crates/pixi_manifest/src/toml/feature.rs:180-191 — before extracting anything, compare `crates/pixi_manifest/src/toml/environment.rs` and `crates/pixi_manifest/src/toml/feature.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) crates/pixi_manifest/src/toml/document.rs:81 — crates/pixi_manifest/src/toml/document.rs:81-91 | crates/pixi_manifest/src/toml/document.rs:110-120 | crates/pixi_manifest/src/toml/document.rs:160-170 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1
  • Duplicated block (9–10 lines × 2) crates/pixi_core/src/lock_file/satisfiability/source_record.rs:387 — crates/pixi_core/src/lock_file/satisfiability/source_record.rs:387-396 | crates/pixi_core/src/lock_file/satisfiability/source_record.rs:398-406 — 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 `crates/pixi_core/src/lock_file/satisfiability/source_record.rs:387` 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 (9 lines × 4) · ×1
  • Duplicated block (9 lines × 4) crates/pixi_manifest/src/feature.rs:303 — crates/pixi_manifest/src/feature.rs:303-311 | crates/pixi_manifest/src/feature.rs:367-375 | crates/pixi_manifest/src/feature.rs:469-477 | crates/pixi_manifest/src/feature.rs:537-545 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `crates/pixi_manifest/src/feature.rs:303` 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 × 3) · ×1
  • Duplicated block (9 lines × 3) crates/pixi_api/src/workspace/shell/mod.rs:186 — crates/pixi_api/src/workspace/shell/mod.rs:186-194 | crates/pixi_api/src/workspace/shell/mod.rs:251-259 | crates/pixi_api/src/workspace/shell/mod.rs:316-324 — 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 `crates/pixi_api/src/workspace/shell/mod.rs:186` 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 (7–9 lines × 2) · ×1
  • Duplicated block (7–9 lines × 2) crates/pixi_uv_conversions/src/conversions.rs:162 — crates/pixi_uv_conversions/src/conversions.rs:162-170 | crates/pixi_uv_conversions/src/conversions.rs:230-236 — 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 `crates/pixi_uv_conversions/src/conversions.rs:162` 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 (7–8 lines × 4) · ×1
  • Duplicated block (7–8 lines × 4) crates/pixi_api/src/workspace/shell/mod.rs:116 — crates/pixi_api/src/workspace/shell/mod.rs:116-123 | crates/pixi_api/src/workspace/shell/mod.rs:156-163 | crates/pixi_api/src/workspace/shell/mod.rs:211-218 | crates/pixi_api/src/workspace/shell/mod.rs:271-277 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×1
  • Duplicated block (8 lines × 3) crates/pixi_build_backend/src/intermediate_backend.rs:485 — crates/pixi_build_backend/src/intermediate_backend.rs:485-492 | crates/pixi_build_backend/src/rattler_build_integration.rs:132-139 | crates/pixi_build_rattler_build/src/protocol.rs:180-187 — before extracting anything, compare `crates/pixi_build_backend/src/intermediate_backend.rs` and `crates/pixi_build_backend/src/rattler_build_integration.rs` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×1
  • Duplicated block (7–8 lines × 2) crates/pixi_stable_hash/src/json.rs:76 — crates/pixi_stable_hash/src/json.rs:76-82 | crates/pixi_stable_hash/src/json.rs:84-91 — 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 `crates/pixi_stable_hash/src/json.rs:84` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5–6 lines × 2) · ×1
  • Duplicated block (5–6 lines × 2) crates/pixi_cli/src/config.rs:638 — crates/pixi_cli/src/config.rs:638-642 | crates/pixi_cli/src/config.rs:771-776 — 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 `crates/pixi_cli/src/config.rs:638` 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 (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) crates/pixi_manifest/src/task.rs:927 — crates/pixi_manifest/src/task.rs:927-934 | crates/pixi_manifest/src/task.rs:1004-1008 | crates/pixi_manifest/src/task.rs:1039-1043 — 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 `crates/pixi_manifest/src/task.rs:927` 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 · Edited copy of a member (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) examples/turtlesim/turtle_marker_viz_ROS1.py:9 — examples/turtlesim/turtle_marker_viz_ROS1.py:9-45 | examples/turtlesim/turtle_marker_viz_ROS2.py:21-57 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×1
  • Edited copy of a member (5 corresponding lines) scripts/release.py:47 — scripts/release.py:47-51 | scripts/release_backends.py:155-159 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) crates/pixi_spec/src/url.rs:109 — crates/pixi_spec/src/url.rs:109-115 | crates/pixi_spec/src/url.rs:167-173 | crates/pixi_spec/src/url.rs:212-218 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `crates/pixi_spec/src/url.rs:174` calls `is_empty` and `crates/pixi_spec/src/url.rs:116` 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 (16–18 lines × 2) · ×1
  • Duplicated block (16–18 lines × 2) examples/rerun_example/lidar/lidar/__main__.py:78 — examples/rerun_example/lidar/lidar/__main__.py:78-93 | examples/rerun_example/nuscenes_dataset/nuscenes_dataset/__main__.py:300-317 — 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.
D5 · Coupling · Unstable project pixi_api · ×1
  • Unstable project pixi_api — pixi_api has instability 0.94 with 1 dependents.
D5 · Coupling · Unstable project pixi_command_dispatcher · ×1
  • Unstable project pixi_command_dispatcher — pixi_command_dispatcher has instability 0.83 with 4 dependents.
D5 · Coupling · Unstable project pixi_compute_sources · ×1
  • Unstable project pixi_compute_sources — pixi_compute_sources has instability 0.91 with 1 dependents.
D5 · Coupling · Unstable project pixi_core · ×1
  • Unstable project pixi_core — pixi_core has instability 0.86 with 4 dependents.
D5 · Coupling · Unstable project pixi_global · ×1
  • Unstable project pixi_global — pixi_global has instability 0.88 with 2 dependents.
D5 · Coupling · Unstable project pixi_install_pypi · ×1
  • Unstable project pixi_install_pypi — pixi_install_pypi has instability 0.87 with 2 dependents.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: PtyProcess (LCOM4 4) crates/pixi_pty/src/unix/pty_process.rs:28 — PtyProcess'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.
P3 · Security & performance tooling · SAST runs, but gates no merge · ×1
  • SAST runs, but gates no merge — `scorecard.yml` run(s) a static-analysis scan, but no workflow that runs one is triggered by a pull request (or a merge queue, or an unfiltered push) — the scan fires on a schedule or a manual dispatch only. A vulnerable change therefore merges clean and is reported on the next scheduled run, by which time it is on the default branch and the only remedy is a follow-up fix. Add the pull-request trigger to the workflow that runs the scan so the finding arrives before the merge rather than after it.
Minor — 24 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×7
  • Duplicated predicate scripts/release.py:60 — `(ROOT / ".jj").is_dir() and shutil.which("jj") is not None` appears character-identically in 2 files — scripts/release.py, scripts/release_backends.py. 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 crates/pixi_api/src/workspace/run/mod.rs:290 — `allow_installs && user_platform.is_none()` appears character-identically in 2 files — crates/pixi_api/src/workspace/run/mod.rs, crates/pixi_cli/src/conda_script.rs. 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 crates/pixi_cli/src/list.rs:203 — `args.workspace_config.script.is_some() && args.environment.is_some()` appears character-identically in 3 files — crates/pixi_cli/src/list.rs, crates/pixi_cli/src/tree.rs, crates/pixi_cli/src/workspace/export/conda_environment.rs. 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 crates/pixi_config/src/lib.rs:1964 — `e.kind() == std::io::ErrorKind::NotFound || e.kind() == std::io::ErrorKind::NotADirectory` appears character-identically in 2 files — crates/pixi_config/src/lib.rs, crates/pixi_core/src/workspace/registry.rs. 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 crates/pixi_cli/src/init.rs:197 — `extension.eq_ignore_ascii_case("py") || extension.eq_ignore_ascii_case("pyw")` appears character-identically in 3 files — crates/pixi_cli/src/init.rs, crates/pixi_core/src/workspace/discovery.rs, crates/pixi_manifest/src/script/pep723.rs. 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 crates/pixi_cli/src/add.rs:619 — `is_script && !lock_file_exists && requested == LockFileUsage::Update` appears character-identically in 3 files — crates/pixi_cli/src/add.rs, crates/pixi_cli/src/remove/mod.rs, crates/pixi_cli/src/workspace/channel.rs. 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 crates/pixi_cli/src/add.rs:444 — `workspace.is_conda_script() && !args.dependency_config.platforms.is_empty()` appears character-identically in 2 files — crates/pixi_cli/src/add.rs, crates/pixi_cli/src/remove/mod.rs. 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.
X7 · Silent fallback defaults · Silent fallback default on Err · ×4
  • Silent fallback default on Err crates/pixi_cli/src/clean.rs:433 — `workspace_build_cache_dirs` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/pixi_core/src/lock_file/virtual_packages.rs:183 — `required_virtual_package_specs` turns every `Err` into `Vec::new()` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/pixi_manifest/src/manifests/document.rs:756 — `pypi_dependency_location` turns every `Err` into `false` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
  • Silent fallback default on Err crates/pixi_task/src/task_environment.rs:248 — `find_task` turns every `Err` into `false` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or propagate it with `?`. 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 arm or in the doc comment, and the row stops firing.
D16 · Bus Factor · Off-boarding risk · ×3
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: crates/pixi_toml_edit/src/entry.rs, crates/pixi_script_shell/src/parse.rs, crates/pixi_toml_edit/src/array.rs, crates/pixi_script_shell/src/execute.rs, crates/pixi_toml_edit/src/style.rs. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: scripts/build_pgo.py, crates/pixi_utils/src/tls.rs, crates/pixi_compute_sources/src/url.rs, crates/pixi_cli/src/install_ping.rs, crates/pixi_command_dispatcher/src/solve_binary.rs. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 3 significant file(s) lose their only recent owner: crates/pixi_cli/src/publish/discovery.rs, crates/pixi_manifest/src/script/conda/envelope.rs, crates/pixi_manifest/src/warning/mod.rs. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (14 single-owned of 450 analysed files in total, 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; 450 of the 628 production source files in this repository met that bar). They are anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: crates/pixi_manifest/src/toml/exclude_newer.rs.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found trampoline/src/main.rs:1 — 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/`. ADRs are expected here because `trampoline/src/main.rs` makes this repository a deployable product (line 1).
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 1 of 450 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; 450 of the 628 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: crates/pixi_reporters/src/release_notes.rs. 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.
D34 · Knowledge Freshness · Orphaned file · ×1
  • Orphaned file crates/pixi_reporters/src/release_notes.rs: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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 28/40 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `crates/pixi`, `crates/pixi_build_mojo`, `crates/pixi_build_r`, `crates/pixi_build_rust` and 7 more.
X5 · Nullable reference types · Nullable reference types not enabled everywhere · ×1
  • Nullable reference types not enabled everywhere — 0/1 C# file(s) are in a nullable-enabled context. This repository commits no project file, so nothing sets <Nullable>enable</Nullable> for it: a file is enabled only by its own `#nullable enable`, by a Unity `csc.rsp` with `-nullable:enable` for its assembly, or as a file-based app (`#:` directives) whose `#:property Nullable` does not turn it off. NRTs catch a whole class of null-deref bugs at compile time.
Minor — 20 finding(s)
D12 · Dependency Hygiene · Outdated · ×20
  • Outdated: mimalloc — `mimalloc` is locked at 0.1.51 but 0.1.52 is the current stable release on crates.io, and it already satisfies the `"0.1.51"` requirement declared in crates/pixi_allocator/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p mimalloc` and commit the updated REDACTED.
  • Outdated: rattler — `rattler` is locked at 0.55.7 but 0.55.8 is the current stable release on crates.io, and it already satisfies the `"0.55.5"` requirement declared in crates/pixi_cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler` and commit the updated REDACTED.
  • Outdated: rattler_cache — `rattler_cache` is locked at 0.12.3 but 0.12.4 is the current stable release on crates.io, and it already satisfies the `"0.12.1"` requirement declared in crates/pixi_command_dispatcher/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_cache` and commit the updated REDACTED.
  • Outdated: rattler_conda_types — `rattler_conda_types` is locked at 0.58.3 but 0.58.4 is the current stable release on crates.io, and it already satisfies the `"0.58"` requirement declared in crates/pixi_api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_conda_types` and commit the updated REDACTED.
  • Outdated: rattler_config — `rattler_config` is locked at 0.12.2 but 0.12.3 is the current stable release on crates.io, and it already satisfies the `"0.12.0"` requirement declared in crates/pixi_cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_config` and commit the updated REDACTED.
  • Outdated: rattler_environment_digest — `rattler_environment_digest` is locked at 0.1.7 but 0.1.8 is the current stable release on crates.io, and it already satisfies the `"0.1"` requirement declared in crates/pixi_core/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_environment_digest` and commit the updated REDACTED.
  • Outdated: rattler_index — `rattler_index` is locked at 0.34.7 but 0.34.8 is the current stable release on crates.io, and it already satisfies the `"0.34.5"` requirement declared in crates/pixi_cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_index` and commit the updated REDACTED.
  • Outdated: rattler_lock — `rattler_lock` is locked at 0.34.14 but 0.34.15 is the current stable release on crates.io, and it already satisfies the `"0.34"` requirement declared in crates/pixi_api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_lock` and commit the updated REDACTED.
  • Outdated: rattler_networking — `rattler_networking` is locked at 0.34.8 but 0.34.9 is the current stable release on crates.io, and it already satisfies the `"0.34"` requirement declared in crates/pixi_auth/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_networking` and commit the updated REDACTED.
  • Outdated: rattler_package_streaming — `rattler_package_streaming` is locked at 0.28.5 but 0.28.6 is the current stable release on crates.io, and it already satisfies the `"0.28"` requirement declared in crates/pixi_build_backend_passthrough/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_package_streaming` and commit the updated REDACTED.
  • Outdated: rattler_repodata_gateway — `rattler_repodata_gateway` is locked at 0.38.3 but 0.38.4 is the current stable release on crates.io, and it already satisfies the `"0.38"` requirement declared in crates/pixi_api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_repodata_gateway` and commit the updated REDACTED.
  • Outdated: rattler_s3 — `rattler_s3` is locked at 0.4.6 but 0.4.7 is the current stable release on crates.io, and it already satisfies the `"0.4.1"` requirement declared in crates/pixi_cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_s3` and commit the updated REDACTED.
  • Outdated: rattler_shell — `rattler_shell` is locked at 0.29.9 but 0.29.10 is the current stable release on crates.io, and it already satisfies the `"0.29"` requirement declared in crates/pixi_api/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_shell` and commit the updated REDACTED.
  • Outdated: rattler_solve — `rattler_solve` is locked at 13.0.0 but 13.0.1 is the current stable release on crates.io, and it already satisfies the `"13.0.0"` requirement declared in crates/pixi_cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_solve` and commit the updated REDACTED.
  • Outdated: rattler_upload — `rattler_upload` is locked at 0.15.5 but 0.15.6 is the current stable release on crates.io, and it already satisfies the `"0.15.3"` requirement declared in crates/pixi_cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_upload` and commit the updated REDACTED.
  • Outdated: rattler_virtual_packages — `rattler_virtual_packages` is locked at 8.1.7 but 8.1.8 is the current stable release on crates.io, and it already satisfies the `"8.1.4"` requirement declared in crates/pixi_build_backend/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rattler_virtual_packages` and commit the updated REDACTED.
  • Outdated: rustls-pki-types — `rustls-pki-types` is locked at 1.15.1 but 1.16.0 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/pixi_utils/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p rustls-pki-types` and commit the updated REDACTED.
  • Outdated: toml_edit — `toml_edit` is locked at 0.25.17+spec-1.1.0 but 0.25.19+spec-1.1.0 is the current stable release on crates.io, and it already satisfies the `"0.25.0"` requirement declared in crates/pixi_cli/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p toml_edit` and commit the updated REDACTED.
  • Outdated: webpki-root-certs — `webpki-root-certs` is locked at 1.0.11 but 1.0.12 is the current stable release on crates.io, and it already satisfies the `"1"` requirement declared in crates/pixi_utils/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p webpki-root-certs` and commit the updated REDACTED.
  • Outdated: zstd — `zstd` is locked at 0.14.3 but 0.14.4 is the current stable release on crates.io, and it already satisfies the `"0.14.0"` requirement declared in crates/pixi_global/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p zstd` and commit the updated REDACTED.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-89b92f075464420087a0c2458b8a20a3/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-89b92f075464420087a0c2458b8a20a3/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude docs/reference/cli/pixi/global/exclude-newer --exclude docs/reference/cli/pixi/upload --exclude docs/reference/cli/pixi/workspace/activation/env --exclude docs/reference/cli/pixi/workspace/activation/script --exclude docs/reference/cli/pixi/workspace/channel --exclude docs/reference/cli/pixi/workspace/environment --exclude docs/reference/cli/pixi/workspace/exclude-newer --exclude docs/reference/cli/pixi/workspace/platform --exclude docs/reference/cli/pixi/workspace/preview --exclude docs/reference/cli/pixi/workspace/register --exclude docs/reference/cli/pixi/workspace/requires-pixi --exclude docs/reference/cli/pixi/workspace/version .5artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .38artifacts/raw/osv-scanner.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .0artifacts/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 1 file(s) — `docs/source_files/conda_scripts/main.cs` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciesosv-scanner—osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm .0artifacts/raw/osv-scanner.json

Run 01a1db0f-f83e-72a3-8b62-ca366facb78e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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