Executive summary
PyO3/maturin falls short of our standard for production, in part because the project keeps no record of its design decisions. It scores 67 out of 100 and is rated Adequate, and 15 of its 16 critical findings are security problems in the build pipeline and in its servers and containers.
Maturity, at 62, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Writing log messages as searchable templates is another step, worth about 3 points. Raising Maturity to 70 would lift the score to about 70.
Nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two pipeline steps install packages that can change without warning. Pinning each tool to an exact version and pinning what the pipeline installs would close both risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command, and the two unsafe settings in infrastructure or container files need changing to safe values. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 35,122 lines, about €49,000 to rebuild.
If Maturity rose from 62 to 70, the lowest score rated Strong, the score would rise from 67 to about 70.
New since the last survey: 22 findings
- Cyclomatic Complexity · PgoContext::run_instrumentation (cyclomatic 16) src/pgo.rs
- God Classes · TooManyFields: ToolMaturin src/pyproject_toml.rs
- Churn × Complexity Hotspots · Hotspot: src/python_interpreter/config.rs src/python_interpreter/config.rs
- Churn × Complexity Hotspots · Hotspot: src/pgo.rs src/pgo.rs
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 4 findings
- Churn × Complexity Hotspots · Hotspot: src/develop/mod.rs src/develop/mod.rs
- Churn × Complexity Hotspots · Hotspot: src/build_context/builder.rs src/build_context/builder.rs
- Churn × Complexity Hotspots · Hotspot: src/bridge/detection.rs src/bridge/detection.rs
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €49,000 · Estimate
| Cost to rebuild | €16,000 to €81,000, for 269 to 853 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 67. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 35,122 lines of product code |
| What it is not | Not 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. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 archive_source | 2 auditwheel.audit | 3 auditwheel.platform_tag | 4 ci | 5 compression | 6 main | 7 module_writer.private | 8 new_project | 9 auditwheel.policy | 10 pgo | 11 pyproject_toml | 12 cargo_options | 13 metadata | 14 commands | 15 module_writer | 16 project_layout | 17 module_writer.path_writer | 18 module_writer.sdist_writer | 19 module_writer.virtual_writer | 20 module_writer.wheel_writer | 21 build_context | 22 python_interpreter | 23 source_distribution | 24 bridge | 25 bridge.detection | 26 build_options | 27 build_orchestrator | 28 ci.github.render | 29 ci.github.resolve | 30 compile | 31 develop | 32 python_interpreter.discovery | 33 auditwheel.repair | 34 binding_generator | 35 build_context.builder | 36 auditwheel.linux | 37 binding_generator.bin_binding | 38 binding_generator.cffi_binding | 39 binding_generator.pyo3_binding | 40 binding_generator.uniffi_binding |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 archive_source | ||||||||||||||||||||||||||||||||||||||||
| 2 auditwheel.audit | ||||||||||||||||||||||||||||||||||||||||
| 3 auditwheel.platform_tag | ||||||||||||||||||||||||||||||||||||||||
| 4 ci | ||||||||||||||||||||||||||||||||||||||||
| 5 compression | ||||||||||||||||||||||||||||||||||||||||
| 6 main | ||||||||||||||||||||||||||||||||||||||||
| 7 module_writer.private | ||||||||||||||||||||||||||||||||||||||||
| 8 new_project | ||||||||||||||||||||||||||||||||||||||||
| 9 auditwheel.policy | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 pgo | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 pyproject_toml | 2 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 12 cargo_options | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 metadata | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 commands | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 module_writer | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 16 project_layout | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 17 module_writer.path_writer | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 module_writer.sdist_writer | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 19 module_writer.virtual_writer | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 20 module_writer.wheel_writer | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 build_context | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||
| 22 python_interpreter | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 23 source_distribution | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 24 bridge | 1 | |||||||||||||||||||||||||||||||||||||||
| 25 bridge.detection | 1 | 2 | 3 | |||||||||||||||||||||||||||||||||||||
| 26 build_options | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 27 build_orchestrator | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 28 ci.github.render | 6 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 ci.github.resolve | 2 | 3 | 1 | |||||||||||||||||||||||||||||||||||||
| 30 compile | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 31 develop | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 python_interpreter.discovery | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||||||
| 33 auditwheel.repair | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 binding_generator | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 35 build_context.builder | 2 | 3 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 auditwheel.linux | 2 | 1 | 2 | 2 | ||||||||||||||||||||||||||||||||||||
| 37 binding_generator.bin_binding | 2 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 binding_generator.cffi_binding | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 binding_generator.pyo3_binding | 1 | 2 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 40 binding_generator.uniffi_binding | 1 | 1 | 1 |
9→3 auditwheel.policy uses auditwheel.platform_tag✕
- Connections
- 1 pair of types, where a type in auditwheel.policy uses a type in auditwheel.platform_tag.
- The types involved
maturin.auditwheel.policy.Policy→maturin.auditwheel.platform_tag.PlatformTag
- Direction
- auditwheel.policy uses auditwheel.platform_tag, so a change to auditwheel.platform_tag can break auditwheel.policy, while a change to auditwheel.policy can't break auditwheel.platform_tag.
- Position
- Below the diagonal: auditwheel.policy uses a module listed above it, which is the healthy direction.
10→21 pgo uses build_context part of a loop✕
- Connections
- 1 pair of types, where a type in pgo uses a type in build_context.
- The types involved
maturin.pgo.PgoContext→maturin.build_context.BuildContext
- Direction
- pgo uses build_context, so a change to build_context can break pgo, while a change to pgo can't break build_context.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→22 pgo uses python_interpreter part of a loop✕
- Connections
- 1 pair of types, where a type in pgo uses a type in python_interpreter.
- The types involved
maturin.pgo.PgoContext→maturin.python_interpreter.PythonInterpreter
- Direction
- pgo uses python_interpreter, so a change to python_interpreter can break pgo, while a change to pgo can't break python_interpreter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→2 pyproject_toml uses auditwheel.audit✕
- Connections
- 2 pairs of types, where a type in pyproject_toml uses a type in auditwheel.audit.
- The types involved
maturin.pyproject_toml.PyProjectToml→maturin.auditwheel.audit.AuditWheelModematurin.pyproject_toml.ToolMaturin→maturin.auditwheel.audit.AuditWheelMode
- Direction
- pyproject_toml uses auditwheel.audit, so a change to auditwheel.audit can break pyproject_toml, while a change to pyproject_toml can't break auditwheel.audit.
- Position
- Below the diagonal: pyproject_toml uses a module listed above it, which is the healthy direction.
11→3 pyproject_toml uses auditwheel.platform_tag✕
- Connections
- 2 pairs of types, where a type in pyproject_toml uses a type in auditwheel.platform_tag.
- The types involved
maturin.pyproject_toml.PyProjectToml→maturin.auditwheel.platform_tag.CompatibilityTagmaturin.pyproject_toml.ToolMaturin→maturin.auditwheel.platform_tag.CompatibilityTag
- Direction
- pyproject_toml uses auditwheel.platform_tag, so a change to auditwheel.platform_tag can break pyproject_toml, while a change to pyproject_toml can't break auditwheel.platform_tag.
- Position
- Below the diagonal: pyproject_toml uses a module listed above it, which is the healthy direction.
11→24 pyproject_toml uses bridge part of a loop✕
- Connections
- 2 pairs of types, where a type in pyproject_toml uses a type in bridge.
- The types involved
maturin.pyproject_toml.PyProjectToml→maturin.bridge.Bindingsmaturin.pyproject_toml.ToolMaturin→maturin.bridge.Bindings
- Direction
- pyproject_toml uses bridge, so a change to bridge can break pyproject_toml, while a change to pyproject_toml can't break bridge.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→11 cargo_options uses pyproject_toml✕
- Connections
- 1 pair of types, where a type in cargo_options uses a type in pyproject_toml.
- The types involved
maturin.cargo_options.CargoOptions→maturin.pyproject_toml.ToolMaturin
- Direction
- cargo_options uses pyproject_toml, so a change to pyproject_toml can break cargo_options, while a change to cargo_options can't break pyproject_toml.
- Position
- Below the diagonal: cargo_options uses a module listed above it, which is the healthy direction.
13→11 metadata uses pyproject_toml✕
- Connections
- 1 pair of types, where a type in metadata uses a type in pyproject_toml.
- The types involved
maturin.metadata.Metadata24→maturin.pyproject_toml.PyProjectToml
- Direction
- metadata uses pyproject_toml, so a change to pyproject_toml can break metadata, while a change to metadata can't break pyproject_toml.
- Position
- Below the diagonal: metadata uses a module listed above it, which is the healthy direction.
14→4 commands uses ci✕
- Connections
- 1 pair of types, where a type in commands uses a type in ci.
- The types involved
maturin.commands.commands$module→maturin.ci.GenerateCI
- Direction
- commands uses ci, so a change to ci can break commands, while a change to commands can't break ci.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
14→6 commands uses main✕
- Connections
- 1 pair of types, where a type in commands uses a type in main.
- The types involved
maturin.commands.commands$module→maturin.main.Command
- Direction
- commands uses main, so a change to main can break commands, while a change to commands can't break main.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
14→8 commands uses new_project✕
- Connections
- 1 pair of types, where a type in commands uses a type in new_project.
- The types involved
maturin.commands.commands$module→maturin.new_project.GenerateProjectOptions
- Direction
- commands uses new_project, so a change to new_project can break commands, while a change to commands can't break new_project.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
14→12 commands uses cargo_options✕
- Connections
- 1 pair of types, where a type in commands uses a type in cargo_options.
- The types involved
maturin.commands.commands$module→maturin.cargo_options.TargetTriple
- Direction
- commands uses cargo_options, so a change to cargo_options can break commands, while a change to commands can't break cargo_options.
- Position
- Below the diagonal: commands uses a module listed above it, which is the healthy direction.
15→1 module_writer uses archive_source✕
- Connections
- 1 pair of types, where a type in module_writer uses a type in archive_source.
- The types involved
maturin.module_writer.ModuleWriterInternal→maturin.archive_source.ArchiveSource
- Direction
- module_writer uses archive_source, so a change to archive_source can break module_writer, while a change to module_writer can't break archive_source.
- Position
- Below the diagonal: module_writer uses a module listed above it, which is the healthy direction.
15→7 module_writer uses module_writer.private✕
- Connections
- 2 pairs of types, where a type in module_writer uses a type in module_writer.private.
- The types involved
maturin.module_writer.ModuleWriter→maturin.module_writer.private.Sealedmaturin.module_writer.ModuleWriterInternal→maturin.module_writer.private.Sealed
- Direction
- module_writer uses module_writer.private, so a change to module_writer.private can break module_writer, while a change to module_writer can't break module_writer.private.
- Position
- Below the diagonal: module_writer uses a module listed above it, which is the healthy direction.
15→8 module_writer uses new_project✕
- Connections
- 1 pair of types, where a type in module_writer uses a type in new_project.
- The types involved
maturin.module_writer.module_writer$module→maturin.new_project.ProjectLayout
- Direction
- module_writer uses new_project, so a change to new_project can break module_writer, while a change to module_writer can't break new_project.
- Position
- Below the diagonal: module_writer uses a module listed above it, which is the healthy direction.
15→11 module_writer uses pyproject_toml✕
- Connections
- 1 pair of types, where a type in module_writer uses a type in pyproject_toml.
- The types involved
maturin.module_writer.module_writer$module→maturin.pyproject_toml.PyProjectToml
- Direction
- module_writer uses pyproject_toml, so a change to pyproject_toml can break module_writer, while a change to module_writer can't break pyproject_toml.
- Position
- Below the diagonal: module_writer uses a module listed above it, which is the healthy direction.
15→13 module_writer uses metadata✕
- Connections
- 1 pair of types, where a type in module_writer uses a type in metadata.
- The types involved
maturin.module_writer.module_writer$module→maturin.metadata.Metadata24
- Direction
- module_writer uses metadata, so a change to metadata can break module_writer, while a change to module_writer can't break metadata.
- Position
- Below the diagonal: module_writer uses a module listed above it, which is the healthy direction.
15→19 module_writer uses module_writer.virtual_writer part of a loop✕
- Connections
- 1 pair of types, where a type in module_writer uses a type in module_writer.virtual_writer.
- The types involved
maturin.module_writer.module_writer$module→maturin.module_writer.virtual_writer.VirtualWriter
- Direction
- module_writer uses module_writer.virtual_writer, so a change to module_writer.virtual_writer can break module_writer, while a change to module_writer can't break module_writer.virtual_writer.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→8 project_layout uses new_project✕
- Connections
- 1 pair of types, where a type in project_layout uses a type in new_project.
- The types involved
maturin.project_layout.ProjectResolver→maturin.new_project.ProjectLayout
- Direction
- project_layout uses new_project, so a change to new_project can break project_layout, while a change to project_layout can't break new_project.
- Position
- Below the diagonal: project_layout uses a module listed above it, which is the healthy direction.
16→11 project_layout uses pyproject_toml✕
- Connections
- 1 pair of types, where a type in project_layout uses a type in pyproject_toml.
- The types involved
maturin.project_layout.ProjectResolver→maturin.pyproject_toml.PyProjectToml
- Direction
- project_layout uses pyproject_toml, so a change to pyproject_toml can break project_layout, while a change to project_layout can't break pyproject_toml.
- Position
- Below the diagonal: project_layout uses a module listed above it, which is the healthy direction.
16→12 project_layout uses cargo_options✕
- Connections
- 1 pair of types, where a type in project_layout uses a type in cargo_options.
- The types involved
maturin.project_layout.ProjectResolver→maturin.cargo_options.CargoOptions
- Direction
- project_layout uses cargo_options, so a change to cargo_options can break project_layout, while a change to project_layout can't break cargo_options.
- Position
- Below the diagonal: project_layout uses a module listed above it, which is the healthy direction.
16→13 project_layout uses metadata✕
- Connections
- 1 pair of types, where a type in project_layout uses a type in metadata.
- The types involved
maturin.project_layout.ProjectResolver→maturin.metadata.Metadata24
- Direction
- project_layout uses metadata, so a change to metadata can break project_layout, while a change to project_layout can't break metadata.
- Position
- Below the diagonal: project_layout uses a module listed above it, which is the healthy direction.
17→1 module_writer.path_writer uses archive_source✕
- Connections
- 1 pair of types, where a type in module_writer.path_writer uses a type in archive_source.
- The types involved
maturin.module_writer.path_writer.PathWriter→maturin.archive_source.ArchiveSource
- Direction
- module_writer.path_writer uses archive_source, so a change to archive_source can break module_writer.path_writer, while a change to module_writer.path_writer can't break archive_source.
- Position
- Below the diagonal: module_writer.path_writer uses a module listed above it, which is the healthy direction.
17→7 module_writer.path_writer uses module_writer.private✕
- Connections
- 1 pair of types, where a type in module_writer.path_writer uses a type in module_writer.private.
- The types involved
maturin.module_writer.path_writer.PathWriter→maturin.module_writer.private.Sealed
- Direction
- module_writer.path_writer uses module_writer.private, so a change to module_writer.private can break module_writer.path_writer, while a change to module_writer.path_writer can't break module_writer.private.
- Position
- Below the diagonal: module_writer.path_writer uses a module listed above it, which is the healthy direction.
17→15 module_writer.path_writer uses module_writer✕
- Connections
- 1 pair of types, where a type in module_writer.path_writer uses a type in module_writer.
- The types involved
maturin.module_writer.path_writer.PathWriter→maturin.module_writer.ModuleWriterInternal
- Direction
- module_writer.path_writer uses module_writer, so a change to module_writer can break module_writer.path_writer, while a change to module_writer.path_writer can't break module_writer.
- Position
- Below the diagonal: module_writer.path_writer uses a module listed above it, which is the healthy direction.
18→1 module_writer.sdist_writer uses archive_source✕
- Connections
- 1 pair of types, where a type in module_writer.sdist_writer uses a type in archive_source.
- The types involved
maturin.module_writer.sdist_writer.SDistWriter→maturin.archive_source.ArchiveSource
- Direction
- module_writer.sdist_writer uses archive_source, so a change to archive_source can break module_writer.sdist_writer, while a change to module_writer.sdist_writer can't break archive_source.
- Position
- Below the diagonal: module_writer.sdist_writer uses a module listed above it, which is the healthy direction.
18→7 module_writer.sdist_writer uses module_writer.private✕
- Connections
- 1 pair of types, where a type in module_writer.sdist_writer uses a type in module_writer.private.
- The types involved
maturin.module_writer.sdist_writer.SDistWriter→maturin.module_writer.private.Sealed
- Direction
- module_writer.sdist_writer uses module_writer.private, so a change to module_writer.private can break module_writer.sdist_writer, while a change to module_writer.sdist_writer can't break module_writer.private.
- Position
- Below the diagonal: module_writer.sdist_writer uses a module listed above it, which is the healthy direction.
18→13 module_writer.sdist_writer uses metadata✕
- Connections
- 1 pair of types, where a type in module_writer.sdist_writer uses a type in metadata.
- The types involved
maturin.module_writer.sdist_writer.SDistWriter→maturin.metadata.Metadata24
- Direction
- module_writer.sdist_writer uses metadata, so a change to metadata can break module_writer.sdist_writer, while a change to module_writer.sdist_writer can't break metadata.
- Position
- Below the diagonal: module_writer.sdist_writer uses a module listed above it, which is the healthy direction.
18→15 module_writer.sdist_writer uses module_writer✕
- Connections
- 1 pair of types, where a type in module_writer.sdist_writer uses a type in module_writer.
- The types involved
maturin.module_writer.sdist_writer.SDistWriter→maturin.module_writer.ModuleWriterInternal
- Direction
- module_writer.sdist_writer uses module_writer, so a change to module_writer can break module_writer.sdist_writer, while a change to module_writer.sdist_writer can't break module_writer.
- Position
- Below the diagonal: module_writer.sdist_writer uses a module listed above it, which is the healthy direction.
19→1 module_writer.virtual_writer uses archive_source✕
- Connections
- 1 pair of types, where a type in module_writer.virtual_writer uses a type in archive_source.
- The types involved
maturin.module_writer.virtual_writer.VirtualWriter→maturin.archive_source.ArchiveSource
- Direction
- module_writer.virtual_writer uses archive_source, so a change to archive_source can break module_writer.virtual_writer, while a change to module_writer.virtual_writer can't break archive_source.
- Position
- Below the diagonal: module_writer.virtual_writer uses a module listed above it, which is the healthy direction.
19→7 module_writer.virtual_writer uses module_writer.private✕
- Connections
- 1 pair of types, where a type in module_writer.virtual_writer uses a type in module_writer.private.
- The types involved
maturin.module_writer.virtual_writer.VirtualWriter→maturin.module_writer.private.Sealed
- Direction
- module_writer.virtual_writer uses module_writer.private, so a change to module_writer.private can break module_writer.virtual_writer, while a change to module_writer.virtual_writer can't break module_writer.private.
- Position
- Below the diagonal: module_writer.virtual_writer uses a module listed above it, which is the healthy direction.
19→13 module_writer.virtual_writer uses metadata✕
- Connections
- 1 pair of types, where a type in module_writer.virtual_writer uses a type in metadata.
- The types involved
maturin.module_writer.virtual_writer.VirtualWriter→maturin.metadata.Metadata24
- Direction
- module_writer.virtual_writer uses metadata, so a change to metadata can break module_writer.virtual_writer, while a change to module_writer.virtual_writer can't break metadata.
- Position
- Below the diagonal: module_writer.virtual_writer uses a module listed above it, which is the healthy direction.
19→15 module_writer.virtual_writer uses module_writer✕
- Connections
- 1 pair of types, where a type in module_writer.virtual_writer uses a type in module_writer.
- The types involved
maturin.module_writer.virtual_writer.VirtualWriter→maturin.module_writer.ModuleWriter
- Direction
- module_writer.virtual_writer uses module_writer, so a change to module_writer can break module_writer.virtual_writer, while a change to module_writer.virtual_writer can't break module_writer.
- Position
- Below the diagonal: module_writer.virtual_writer uses a module listed above it, which is the healthy direction.
20→1 module_writer.wheel_writer uses archive_source✕
- Connections
- 1 pair of types, where a type in module_writer.wheel_writer uses a type in archive_source.
- The types involved
maturin.module_writer.wheel_writer.WheelWriter→maturin.archive_source.ArchiveSource
- Direction
- module_writer.wheel_writer uses archive_source, so a change to archive_source can break module_writer.wheel_writer, while a change to module_writer.wheel_writer can't break archive_source.
- Position
- Below the diagonal: module_writer.wheel_writer uses a module listed above it, which is the healthy direction.
20→7 module_writer.wheel_writer uses module_writer.private✕
- Connections
- 1 pair of types, where a type in module_writer.wheel_writer uses a type in module_writer.private.
- The types involved
maturin.module_writer.wheel_writer.WheelWriter→maturin.module_writer.private.Sealed
- Direction
- module_writer.wheel_writer uses module_writer.private, so a change to module_writer.private can break module_writer.wheel_writer, while a change to module_writer.wheel_writer can't break module_writer.private.
- Position
- Below the diagonal: module_writer.wheel_writer uses a module listed above it, which is the healthy direction.
20→13 module_writer.wheel_writer uses metadata✕
- Connections
- 1 pair of types, where a type in module_writer.wheel_writer uses a type in metadata.
- The types involved
maturin.module_writer.wheel_writer.WheelWriter→maturin.metadata.Metadata24
- Direction
- module_writer.wheel_writer uses metadata, so a change to metadata can break module_writer.wheel_writer, while a change to module_writer.wheel_writer can't break metadata.
- Position
- Below the diagonal: module_writer.wheel_writer uses a module listed above it, which is the healthy direction.
20→15 module_writer.wheel_writer uses module_writer✕
- Connections
- 1 pair of types, where a type in module_writer.wheel_writer uses a type in module_writer.
- The types involved
maturin.module_writer.wheel_writer.WheelWriter→maturin.module_writer.ModuleWriterInternal
- Direction
- module_writer.wheel_writer uses module_writer, so a change to module_writer can break module_writer.wheel_writer, while a change to module_writer.wheel_writer can't break module_writer.
- Position
- Below the diagonal: module_writer.wheel_writer uses a module listed above it, which is the healthy direction.
21→2 build_context uses auditwheel.audit✕
- Connections
- 1 pair of types, where a type in build_context uses a type in auditwheel.audit.
- The types involved
maturin.build_context.PythonContext→maturin.auditwheel.audit.AuditWheelMode
- Direction
- build_context uses auditwheel.audit, so a change to auditwheel.audit can break build_context, while a change to build_context can't break auditwheel.audit.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→3 build_context uses auditwheel.platform_tag✕
- Connections
- 1 pair of types, where a type in build_context uses a type in auditwheel.platform_tag.
- The types involved
maturin.build_context.PythonContext→maturin.auditwheel.platform_tag.PlatformTag
- Direction
- build_context uses auditwheel.platform_tag, so a change to auditwheel.platform_tag can break build_context, while a change to build_context can't break auditwheel.platform_tag.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→5 build_context uses compression✕
- Connections
- 1 pair of types, where a type in build_context uses a type in compression.
- The types involved
maturin.build_context.ArtifactContext→maturin.compression.CompressionOptions
- Direction
- build_context uses compression, so a change to compression can break build_context, while a change to build_context can't break compression.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→8 build_context uses new_project✕
- Connections
- 1 pair of types, where a type in build_context uses a type in new_project.
- The types involved
maturin.build_context.ProjectContext→maturin.new_project.ProjectLayout
- Direction
- build_context uses new_project, so a change to new_project can break build_context, while a change to build_context can't break new_project.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→10 build_context uses pgo✕
- Connections
- 1 pair of types, where a type in build_context uses a type in pgo.
- The types involved
maturin.build_context.ArtifactContext→maturin.pgo.PgoPhase
- Direction
- build_context uses pgo, so a change to pgo can break build_context, while a change to build_context can't break pgo.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→11 build_context uses pyproject_toml✕
- Connections
- 3 pairs of types, where a type in build_context uses a type in pyproject_toml.
- The types involved
maturin.build_context.ArtifactContext→maturin.pyproject_toml.SbomConfigmaturin.build_context.ProjectContext→maturin.pyproject_toml.ConditionalFeaturematurin.build_context.ProjectContext→maturin.pyproject_toml.PyProjectToml
- Direction
- build_context uses pyproject_toml, so a change to pyproject_toml can break build_context, while a change to build_context can't break pyproject_toml.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→12 build_context uses cargo_options✕
- Connections
- 1 pair of types, where a type in build_context uses a type in cargo_options.
- The types involved
maturin.build_context.ProjectContext→maturin.cargo_options.CargoOptions
- Direction
- build_context uses cargo_options, so a change to cargo_options can break build_context, while a change to build_context can't break cargo_options.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→13 build_context uses metadata✕
- Connections
- 1 pair of types, where a type in build_context uses a type in metadata.
- The types involved
maturin.build_context.ProjectContext→maturin.metadata.Metadata24
- Direction
- build_context uses metadata, so a change to metadata can break build_context, while a change to build_context can't break metadata.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→19 build_context uses module_writer.virtual_writer✕
- Connections
- 1 pair of types, where a type in build_context uses a type in module_writer.virtual_writer.
- The types involved
maturin.build_context.BuildContext→maturin.module_writer.virtual_writer.VirtualWriter
- Direction
- build_context uses module_writer.virtual_writer, so a change to module_writer.virtual_writer can break build_context, while a change to build_context can't break module_writer.virtual_writer.
- Position
- Below the diagonal: build_context uses a module listed above it, which is the healthy direction.
21→22 build_context uses python_interpreter part of a loop✕
- Connections
- 2 pairs of types, where a type in build_context uses a type in python_interpreter.
- The types involved
maturin.build_context.BuildContext→maturin.python_interpreter.PythonInterpretermaturin.build_context.PythonContext→maturin.python_interpreter.PythonInterpreter
- Direction
- build_context uses python_interpreter, so a change to python_interpreter can break build_context, while a change to build_context can't break python_interpreter.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→24 build_context uses bridge part of a loop✕
- Connections
- 1 pair of types, where a type in build_context uses a type in bridge.
- The types involved
maturin.build_context.ProjectContext→maturin.bridge.BridgeModel
- Direction
- build_context uses bridge, so a change to bridge can break build_context, while a change to build_context can't break bridge.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→30 build_context uses compile part of a loop✕
- Connections
- 1 pair of types, where a type in build_context uses a type in compile.
- The types involved
maturin.build_context.BuildContext→maturin.compile.BuildArtifact
- Direction
- build_context uses compile, so a change to compile can break build_context, while a change to build_context can't break compile.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→21 python_interpreter uses build_context✕
- Connections
- 1 pair of types, where a type in python_interpreter uses a type in build_context.
- The types involved
maturin.python_interpreter.PythonInterpreter→maturin.build_context.ProjectContext
- Direction
- python_interpreter uses build_context, so a change to build_context can break python_interpreter, while a change to python_interpreter can't break build_context.
- Position
- Below the diagonal: python_interpreter uses a module listed above it, which is the healthy direction.
22→24 python_interpreter uses bridge part of a loop✕
- Connections
- 3 pairs of types, where a type in python_interpreter uses a type in bridge.
- The types involved
maturin.python_interpreter.PythonInterpreter→maturin.bridge.BridgeModelmaturin.python_interpreter.PythonInterpreter→maturin.bridge.StableAbimaturin.python_interpreter.PythonInterpreter→maturin.bridge.StableAbiKind
- Direction
- python_interpreter uses bridge, so a change to bridge can break python_interpreter, while a change to python_interpreter can't break bridge.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→11 source_distribution uses pyproject_toml✕
- Connections
- 1 pair of types, where a type in source_distribution uses a type in pyproject_toml.
- The types involved
maturin.source_distribution.source_distribution$module→maturin.pyproject_toml.PyProjectToml
- Direction
- source_distribution uses pyproject_toml, so a change to pyproject_toml can break source_distribution, while a change to source_distribution can't break pyproject_toml.
- Position
- Below the diagonal: source_distribution uses a module listed above it, which is the healthy direction.
23→13 source_distribution uses metadata✕
- Connections
- 1 pair of types, where a type in source_distribution uses a type in metadata.
- The types involved
maturin.source_distribution.source_distribution$module→maturin.metadata.Metadata24
- Direction
- source_distribution uses metadata, so a change to metadata can break source_distribution, while a change to source_distribution can't break metadata.
- Position
- Below the diagonal: source_distribution uses a module listed above it, which is the healthy direction.
23→19 source_distribution uses module_writer.virtual_writer✕
- Connections
- 1 pair of types, where a type in source_distribution uses a type in module_writer.virtual_writer.
- The types involved
maturin.source_distribution.source_distribution$module→maturin.module_writer.virtual_writer.VirtualWriter
- Direction
- source_distribution uses module_writer.virtual_writer, so a change to module_writer.virtual_writer can break source_distribution, while a change to source_distribution can't break module_writer.virtual_writer.
- Position
- Below the diagonal: source_distribution uses a module listed above it, which is the healthy direction.
23→21 source_distribution uses build_context✕
- Connections
- 3 pairs of types, where a type in source_distribution uses a type in build_context.
- The types involved
maturin.source_distribution.SdistContext→maturin.build_context.ProjectContextmaturin.source_distribution.source_distribution$module→maturin.build_context.ArtifactContextmaturin.source_distribution.source_distribution$module→maturin.build_context.ProjectContext
- Direction
- source_distribution uses build_context, so a change to build_context can break source_distribution, while a change to source_distribution can't break build_context.
- Position
- Below the diagonal: source_distribution uses a module listed above it, which is the healthy direction.
24→22 bridge uses python_interpreter✕
- Connections
- 1 pair of types, where a type in bridge uses a type in python_interpreter.
- The types involved
maturin.bridge.BridgeModel→maturin.python_interpreter.PythonInterpreter
- Direction
- bridge uses python_interpreter, so a change to python_interpreter can break bridge, while a change to bridge can't break python_interpreter.
- Position
- Below the diagonal: bridge uses a module listed above it, which is the healthy direction.
25→11 bridge.detection uses pyproject_toml✕
- Connections
- 1 pair of types, where a type in bridge.detection uses a type in pyproject_toml.
- The types involved
maturin.bridge.detection.detection$module→maturin.pyproject_toml.PyProjectToml
- Direction
- bridge.detection uses pyproject_toml, so a change to pyproject_toml can break bridge.detection, while a change to bridge.detection can't break pyproject_toml.
- Position
- Below the diagonal: bridge.detection uses a module listed above it, which is the healthy direction.
25→12 bridge.detection uses cargo_options✕
- Connections
- 2 pairs of types, where a type in bridge.detection uses a type in cargo_options.
- The types involved
maturin.bridge.detection.CrateDependencies→maturin.cargo_options.CargoOptionsmaturin.bridge.detection.detection$module→maturin.cargo_options.CargoOptions
- Direction
- bridge.detection uses cargo_options, so a change to cargo_options can break bridge.detection, while a change to bridge.detection can't break cargo_options.
- Position
- Below the diagonal: bridge.detection uses a module listed above it, which is the healthy direction.
25→24 bridge.detection uses bridge✕
- Connections
- 3 pairs of types, where a type in bridge.detection uses a type in bridge.
- The types involved
maturin.bridge.detection.detection$module→maturin.bridge.Bindingsmaturin.bridge.detection.detection$module→maturin.bridge.BridgeModelmaturin.bridge.detection.detection$module→maturin.bridge.StableAbiKind
- Direction
- bridge.detection uses bridge, so a change to bridge can break bridge.detection, while a change to bridge.detection can't break bridge.
- Position
- Below the diagonal: bridge.detection uses a module listed above it, which is the healthy direction.
26→2 build_options uses auditwheel.audit✕
- Connections
- 1 pair of types, where a type in build_options uses a type in auditwheel.audit.
- The types involved
maturin.build_options.PlatformOptions→maturin.auditwheel.audit.AuditWheelMode
- Direction
- build_options uses auditwheel.audit, so a change to auditwheel.audit can break build_options, while a change to build_options can't break auditwheel.audit.
- Position
- Below the diagonal: build_options uses a module listed above it, which is the healthy direction.
26→3 build_options uses auditwheel.platform_tag✕
- Connections
- 1 pair of types, where a type in build_options uses a type in auditwheel.platform_tag.
- The types involved
maturin.build_options.PlatformOptions→maturin.auditwheel.platform_tag.CompatibilityTag
- Direction
- build_options uses auditwheel.platform_tag, so a change to auditwheel.platform_tag can break build_options, while a change to build_options can't break auditwheel.platform_tag.
- Position
- Below the diagonal: build_options uses a module listed above it, which is the healthy direction.
26→5 build_options uses compression✕
- Connections
- 1 pair of types, where a type in build_options uses a type in compression.
- The types involved
maturin.build_options.BuildOptions→maturin.compression.CompressionOptions
- Direction
- build_options uses compression, so a change to compression can break build_options, while a change to build_options can't break compression.
- Position
- Below the diagonal: build_options uses a module listed above it, which is the healthy direction.
26→12 build_options uses cargo_options✕
- Connections
- 1 pair of types, where a type in build_options uses a type in cargo_options.
- The types involved
maturin.build_options.BuildOptions→maturin.cargo_options.CargoOptions
- Direction
- build_options uses cargo_options, so a change to cargo_options can break build_options, while a change to build_options can't break cargo_options.
- Position
- Below the diagonal: build_options uses a module listed above it, which is the healthy direction.
26→24 build_options uses bridge✕
- Connections
- 1 pair of types, where a type in build_options uses a type in bridge.
- The types involved
maturin.build_options.PythonOptions→maturin.bridge.Bindings
- Direction
- build_options uses bridge, so a change to bridge can break build_options, while a change to build_options can't break bridge.
- Position
- Below the diagonal: build_options uses a module listed above it, which is the healthy direction.
26→35 build_options uses build_context.builder part of a loop✕
- Connections
- 1 pair of types, where a type in build_options uses a type in build_context.builder.
- The types involved
maturin.build_options.BuildOptions→maturin.build_context.builder.BuildContextBuilder
- Direction
- build_options uses build_context.builder, so a change to build_context.builder can break build_options, while a change to build_options can't break build_context.builder.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→2 build_orchestrator uses auditwheel.audit✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in auditwheel.audit.
- The types involved
maturin.build_orchestrator.build_orchestrator$module→maturin.auditwheel.audit.AuditWheelMode
- Direction
- build_orchestrator uses auditwheel.audit, so a change to auditwheel.audit can break build_orchestrator, while a change to build_orchestrator can't break auditwheel.audit.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→3 build_orchestrator uses auditwheel.platform_tag✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in auditwheel.platform_tag.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.auditwheel.platform_tag.PlatformTag
- Direction
- build_orchestrator uses auditwheel.platform_tag, so a change to auditwheel.platform_tag can break build_orchestrator, while a change to build_orchestrator can't break auditwheel.platform_tag.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→9 build_orchestrator uses auditwheel.policy✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in auditwheel.policy.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.auditwheel.policy.Policy
- Direction
- build_orchestrator uses auditwheel.policy, so a change to auditwheel.policy can break build_orchestrator, while a change to build_orchestrator can't break auditwheel.policy.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→10 build_orchestrator uses pgo✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in pgo.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.pgo.PgoPhase
- Direction
- build_orchestrator uses pgo, so a change to pgo can break build_orchestrator, while a change to build_orchestrator can't break pgo.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→11 build_orchestrator uses pyproject_toml✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in pyproject_toml.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.pyproject_toml.Format
- Direction
- build_orchestrator uses pyproject_toml, so a change to pyproject_toml can break build_orchestrator, while a change to build_orchestrator can't break pyproject_toml.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→13 build_orchestrator uses metadata✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in metadata.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.metadata.Metadata24
- Direction
- build_orchestrator uses metadata, so a change to metadata can break build_orchestrator, while a change to build_orchestrator can't break metadata.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→19 build_orchestrator uses module_writer.virtual_writer✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in module_writer.virtual_writer.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.module_writer.virtual_writer.VirtualWriter
- Direction
- build_orchestrator uses module_writer.virtual_writer, so a change to module_writer.virtual_writer can break build_orchestrator, while a change to build_orchestrator can't break module_writer.virtual_writer.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→21 build_orchestrator uses build_context✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in build_context.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.build_context.BuildContext
- Direction
- build_orchestrator uses build_context, so a change to build_context can break build_orchestrator, while a change to build_orchestrator can't break build_context.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→22 build_orchestrator uses python_interpreter✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in python_interpreter.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.python_interpreter.PythonInterpreter
- Direction
- build_orchestrator uses python_interpreter, so a change to python_interpreter can break build_orchestrator, while a change to build_orchestrator can't break python_interpreter.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
27→24 build_orchestrator uses bridge✕
- Connections
- 1 pair of types, where a type in build_orchestrator uses a type in bridge.
- The types involved
maturin.build_orchestrator.BuildOrchestrator→maturin.bridge.StableAbi
- Direction
- build_orchestrator uses bridge, so a change to bridge can break build_orchestrator, while a change to build_orchestrator can't break bridge.
- Position
- Below the diagonal: build_orchestrator uses a module listed above it, which is the healthy direction.
28→4 ci.github.render uses ci✕
- Connections
- 6 pairs of types, where a type in ci.github.render uses a type in ci.
- The types involved
maturin.ci.github.render.RenderContext→maturin.ci.GenerateCImaturin.ci.github.render.RenderContext→maturin.ci.ResolvedCIConfigmaturin.ci.github.render.render$module→maturin.ci.GenerateCImaturin.ci.github.render.render$module→maturin.ci.Platformmaturin.ci.github.render.render$module→maturin.ci.ResolvedCIConfigmaturin.ci.github.render.render$module→maturin.ci.ResolvedTarget
- Direction
- ci.github.render uses ci, so a change to ci can break ci.github.render, while a change to ci.github.render can't break ci.
- Position
- Below the diagonal: ci.github.render uses a module listed above it, which is the healthy direction.
28→24 ci.github.render uses bridge✕
- Connections
- 1 pair of types, where a type in ci.github.render uses a type in bridge.
- The types involved
maturin.ci.github.render.render$module→maturin.bridge.BridgeModel
- Direction
- ci.github.render uses bridge, so a change to bridge can break ci.github.render, while a change to ci.github.render can't break bridge.
- Position
- Below the diagonal: ci.github.render uses a module listed above it, which is the healthy direction.
29→4 ci.github.resolve uses ci✕
- Connections
- 2 pairs of types, where a type in ci.github.resolve uses a type in ci.
- The types involved
maturin.ci.github.resolve.resolve$module→maturin.ci.GenerateCImaturin.ci.github.resolve.resolve$module→maturin.ci.Platform
- Direction
- ci.github.resolve uses ci, so a change to ci can break ci.github.resolve, while a change to ci.github.resolve can't break ci.
- Position
- Below the diagonal: ci.github.resolve uses a module listed above it, which is the healthy direction.
29→11 ci.github.resolve uses pyproject_toml✕
- Connections
- 3 pairs of types, where a type in ci.github.resolve uses a type in pyproject_toml.
- The types involved
maturin.ci.github.resolve.resolve$module→maturin.pyproject_toml.GitHubCIConfigmaturin.ci.github.resolve.resolve$module→maturin.pyproject_toml.PlatformCIConfigmaturin.ci.github.resolve.resolve$module→maturin.pyproject_toml.TargetCIConfig
- Direction
- ci.github.resolve uses pyproject_toml, so a change to pyproject_toml can break ci.github.resolve, while a change to ci.github.resolve can't break pyproject_toml.
- Position
- Below the diagonal: ci.github.resolve uses a module listed above it, which is the healthy direction.
29→24 ci.github.resolve uses bridge✕
- Connections
- 1 pair of types, where a type in ci.github.resolve uses a type in bridge.
- The types involved
maturin.ci.github.resolve.resolve$module→maturin.bridge.BridgeModel
- Direction
- ci.github.resolve uses bridge, so a change to bridge can break ci.github.resolve, while a change to ci.github.resolve can't break bridge.
- Position
- Below the diagonal: ci.github.resolve uses a module listed above it, which is the healthy direction.
30→6 compile uses main✕
- Connections
- 1 pair of types, where a type in compile uses a type in main.
- The types involved
maturin.compile.compile$module→maturin.main.Command
- Direction
- compile uses main, so a change to main can break compile, while a change to compile can't break main.
- Position
- Below the diagonal: compile uses a module listed above it, which is the healthy direction.
30→21 compile uses build_context✕
- Connections
- 1 pair of types, where a type in compile uses a type in build_context.
- The types involved
maturin.compile.compile$module→maturin.build_context.BuildContext
- Direction
- compile uses build_context, so a change to build_context can break compile, while a change to compile can't break build_context.
- Position
- Below the diagonal: compile uses a module listed above it, which is the healthy direction.
30→22 compile uses python_interpreter✕
- Connections
- 1 pair of types, where a type in compile uses a type in python_interpreter.
- The types involved
maturin.compile.compile$module→maturin.python_interpreter.PythonInterpreter
- Direction
- compile uses python_interpreter, so a change to python_interpreter can break compile, while a change to compile can't break python_interpreter.
- Position
- Below the diagonal: compile uses a module listed above it, which is the healthy direction.
30→24 compile uses bridge✕
- Connections
- 1 pair of types, where a type in compile uses a type in bridge.
- The types involved
maturin.compile.compile$module→maturin.bridge.BridgeModel
- Direction
- compile uses bridge, so a change to bridge can break compile, while a change to compile can't break bridge.
- Position
- Below the diagonal: compile uses a module listed above it, which is the healthy direction.
31→5 develop uses compression✕
- Connections
- 1 pair of types, where a type in develop uses a type in compression.
- The types involved
maturin.develop.DevelopOptions→maturin.compression.CompressionOptions
- Direction
- develop uses compression, so a change to compression can break develop, while a change to develop can't break compression.
- Position
- Below the diagonal: develop uses a module listed above it, which is the healthy direction.
31→12 develop uses cargo_options✕
- Connections
- 1 pair of types, where a type in develop uses a type in cargo_options.
- The types involved
maturin.develop.DevelopOptions→maturin.cargo_options.CargoOptions
- Direction
- develop uses cargo_options, so a change to cargo_options can break develop, while a change to develop can't break cargo_options.
- Position
- Below the diagonal: develop uses a module listed above it, which is the healthy direction.
31→21 develop uses build_context✕
- Connections
- 1 pair of types, where a type in develop uses a type in build_context.
- The types involved
maturin.develop.develop$module→maturin.build_context.BuildContext
- Direction
- develop uses build_context, so a change to build_context can break develop, while a change to develop can't break build_context.
- Position
- Below the diagonal: develop uses a module listed above it, which is the healthy direction.
31→24 develop uses bridge✕
- Connections
- 1 pair of types, where a type in develop uses a type in bridge.
- The types involved
maturin.develop.DevelopOptions→maturin.bridge.Bindings
- Direction
- develop uses bridge, so a change to bridge can break develop, while a change to develop can't break bridge.
- Position
- Below the diagonal: develop uses a module listed above it, which is the healthy direction.
32→6 python_interpreter.discovery uses main✕
- Connections
- 1 pair of types, where a type in python_interpreter.discovery uses a type in main.
- The types involved
maturin.python_interpreter.discovery.discovery$module→maturin.main.Command
- Direction
- python_interpreter.discovery uses main, so a change to main can break python_interpreter.discovery, while a change to python_interpreter.discovery can't break main.
- Position
- Below the diagonal: python_interpreter.discovery uses a module listed above it, which is the healthy direction.
32→22 python_interpreter.discovery uses python_interpreter✕
- Connections
- 2 pairs of types, where a type in python_interpreter.discovery uses a type in python_interpreter.
- The types involved
maturin.python_interpreter.discovery.WindowsInterpreterFinder→maturin.python_interpreter.PythonInterpretermaturin.python_interpreter.discovery.discovery$module→maturin.python_interpreter.PythonInterpreter
- Direction
- python_interpreter.discovery uses python_interpreter, so a change to python_interpreter can break python_interpreter.discovery, while a change to python_interpreter.discovery can't break python_interpreter.
- Position
- Below the diagonal: python_interpreter.discovery uses a module listed above it, which is the healthy direction.
32→24 python_interpreter.discovery uses bridge✕
- Connections
- 2 pairs of types, where a type in python_interpreter.discovery uses a type in bridge.
- The types involved
maturin.python_interpreter.discovery.WindowsInterpreterFinder→maturin.bridge.BridgeModelmaturin.python_interpreter.discovery.discovery$module→maturin.bridge.BridgeModel
- Direction
- python_interpreter.discovery uses bridge, so a change to bridge can break python_interpreter.discovery, while a change to python_interpreter.discovery can't break bridge.
- Position
- Below the diagonal: python_interpreter.discovery uses a module listed above it, which is the healthy direction.
33→9 auditwheel.repair uses auditwheel.policy✕
- Connections
- 1 pair of types, where a type in auditwheel.repair uses a type in auditwheel.policy.
- The types involved
maturin.auditwheel.repair.AuditResult→maturin.auditwheel.policy.Policy
- Direction
- auditwheel.repair uses auditwheel.policy, so a change to auditwheel.policy can break auditwheel.repair, while a change to auditwheel.repair can't break auditwheel.policy.
- Position
- Below the diagonal: auditwheel.repair uses a module listed above it, which is the healthy direction.
33→30 auditwheel.repair uses compile✕
- Connections
- 2 pairs of types, where a type in auditwheel.repair uses a type in compile.
- The types involved
maturin.auditwheel.repair.AuditedArtifact→maturin.compile.BuildArtifactmaturin.auditwheel.repair.WheelRepairer→maturin.compile.BuildArtifact
- Direction
- auditwheel.repair uses compile, so a change to compile can break auditwheel.repair, while a change to auditwheel.repair can't break compile.
- Position
- Below the diagonal: auditwheel.repair uses a module listed above it, which is the healthy direction.
34→1 binding_generator uses archive_source✕
- Connections
- 1 pair of types, where a type in binding_generator uses a type in archive_source.
- The types involved
maturin.binding_generator.InstallDest→maturin.archive_source.ArchiveSource
- Direction
- binding_generator uses archive_source, so a change to archive_source can break binding_generator, while a change to binding_generator can't break archive_source.
- Position
- Below the diagonal: binding_generator uses a module listed above it, which is the healthy direction.
34→19 binding_generator uses module_writer.virtual_writer✕
- Connections
- 2 pairs of types, where a type in binding_generator uses a type in module_writer.virtual_writer.
- The types involved
maturin.binding_generator.InstallDest→maturin.module_writer.virtual_writer.VirtualWritermaturin.binding_generator.binding_generator$module→maturin.module_writer.virtual_writer.VirtualWriter
- Direction
- binding_generator uses module_writer.virtual_writer, so a change to module_writer.virtual_writer can break binding_generator, while a change to binding_generator can't break module_writer.virtual_writer.
- Position
- Below the diagonal: binding_generator uses a module listed above it, which is the healthy direction.
34→21 binding_generator uses build_context✕
- Connections
- 2 pairs of types, where a type in binding_generator uses a type in build_context.
- The types involved
maturin.binding_generator.BindingGenerator→maturin.build_context.BuildContextmaturin.binding_generator.binding_generator$module→maturin.build_context.BuildContext
- Direction
- binding_generator uses build_context, so a change to build_context can break binding_generator, while a change to binding_generator can't break build_context.
- Position
- Below the diagonal: binding_generator uses a module listed above it, which is the healthy direction.
34→30 binding_generator uses compile✕
- Connections
- 1 pair of types, where a type in binding_generator uses a type in compile.
- The types involved
maturin.binding_generator.BindingGenerator→maturin.compile.BuildArtifact
- Direction
- binding_generator uses compile, so a change to compile can break binding_generator, while a change to binding_generator can't break compile.
- Position
- Below the diagonal: binding_generator uses a module listed above it, which is the healthy direction.
35→3 build_context.builder uses auditwheel.platform_tag✕
- Connections
- 2 pairs of types, where a type in build_context.builder uses a type in auditwheel.platform_tag.
- The types involved
maturin.build_context.builder.ResolvedPlatformTags→maturin.auditwheel.platform_tag.PlatformTagmaturin.build_context.builder.builder$module→maturin.auditwheel.platform_tag.CompatibilityTag
- Direction
- build_context.builder uses auditwheel.platform_tag, so a change to auditwheel.platform_tag can break build_context.builder, while a change to build_context.builder can't break auditwheel.platform_tag.
- Position
- Below the diagonal: build_context.builder uses a module listed above it, which is the healthy direction.
35→11 build_context.builder uses pyproject_toml✕
- Connections
- 3 pairs of types, where a type in build_context.builder uses a type in pyproject_toml.
- The types involved
maturin.build_context.builder.BuildContextBuilder→maturin.pyproject_toml.PyProjectTomlmaturin.build_context.builder.BuildContextBuilder→maturin.pyproject_toml.SbomConfigmaturin.build_context.builder.builder$module→maturin.pyproject_toml.PyProjectToml
- Direction
- build_context.builder uses pyproject_toml, so a change to pyproject_toml can break build_context.builder, while a change to build_context.builder can't break pyproject_toml.
- Position
- Below the diagonal: build_context.builder uses a module listed above it, which is the healthy direction.
35→12 build_context.builder uses cargo_options✕
- Connections
- 1 pair of types, where a type in build_context.builder uses a type in cargo_options.
- The types involved
maturin.build_context.builder.builder$module→maturin.cargo_options.TargetTriple
- Direction
- build_context.builder uses cargo_options, so a change to cargo_options can break build_context.builder, while a change to build_context.builder can't break cargo_options.
- Position
- Below the diagonal: build_context.builder uses a module listed above it, which is the healthy direction.
35→13 build_context.builder uses metadata✕
- Connections
- 1 pair of types, where a type in build_context.builder uses a type in metadata.
- The types involved
maturin.build_context.builder.BuildContextBuilder→maturin.metadata.Metadata24
- Direction
- build_context.builder uses metadata, so a change to metadata can break build_context.builder, while a change to build_context.builder can't break metadata.
- Position
- Below the diagonal: build_context.builder uses a module listed above it, which is the healthy direction.
35→24 build_context.builder uses bridge✕
- Connections
- 2 pairs of types, where a type in build_context.builder uses a type in bridge.
- The types involved
maturin.build_context.builder.BuildContextBuilder→maturin.bridge.BridgeModelmaturin.build_context.builder.builder$module→maturin.bridge.BridgeModel
- Direction
- build_context.builder uses bridge, so a change to bridge can break build_context.builder, while a change to build_context.builder can't break bridge.
- Position
- Below the diagonal: build_context.builder uses a module listed above it, which is the healthy direction.
35→25 build_context.builder uses bridge.detection✕
- Connections
- 1 pair of types, where a type in build_context.builder uses a type in bridge.detection.
- The types involved
maturin.build_context.builder.BuildContextBuilder→maturin.bridge.detection.CrateDependencies
- Direction
- build_context.builder uses bridge.detection, so a change to bridge.detection can break build_context.builder, while a change to build_context.builder can't break bridge.detection.
- Position
- Below the diagonal: build_context.builder uses a module listed above it, which is the healthy direction.
35→26 build_context.builder uses build_options✕
- Connections
- 1 pair of types, where a type in build_context.builder uses a type in build_options.
- The types involved
maturin.build_context.builder.BuildContextBuilder→maturin.build_options.BuildOptions
- Direction
- build_context.builder uses build_options, so a change to build_options can break build_context.builder, while a change to build_context.builder can't break build_options.
- Position
- Below the diagonal: build_context.builder uses a module listed above it, which is the healthy direction.
36→3 auditwheel.linux uses auditwheel.platform_tag✕
- Connections
- 2 pairs of types, where a type in auditwheel.linux uses a type in auditwheel.platform_tag.
- The types involved
maturin.auditwheel.linux.ElfRepairer→maturin.auditwheel.platform_tag.PlatformTagmaturin.auditwheel.linux.linux$module→maturin.auditwheel.platform_tag.PlatformTag
- Direction
- auditwheel.linux uses auditwheel.platform_tag, so a change to auditwheel.platform_tag can break auditwheel.linux, while a change to auditwheel.linux can't break auditwheel.platform_tag.
- Position
- Below the diagonal: auditwheel.linux uses a module listed above it, which is the healthy direction.
36→9 auditwheel.linux uses auditwheel.policy✕
- Connections
- 1 pair of types, where a type in auditwheel.linux uses a type in auditwheel.policy.
- The types involved
maturin.auditwheel.linux.linux$module→maturin.auditwheel.policy.Policy
- Direction
- auditwheel.linux uses auditwheel.policy, so a change to auditwheel.policy can break auditwheel.linux, while a change to auditwheel.linux can't break auditwheel.policy.
- Position
- Below the diagonal: auditwheel.linux uses a module listed above it, which is the healthy direction.
36→30 auditwheel.linux uses compile✕
- Connections
- 2 pairs of types, where a type in auditwheel.linux uses a type in compile.
- The types involved
maturin.auditwheel.linux.ElfRepairer→maturin.compile.BuildArtifactmaturin.auditwheel.linux.linux$module→maturin.compile.BuildArtifact
- Direction
- auditwheel.linux uses compile, so a change to compile can break auditwheel.linux, while a change to auditwheel.linux can't break compile.
- Position
- Below the diagonal: auditwheel.linux uses a module listed above it, which is the healthy direction.
36→33 auditwheel.linux uses auditwheel.repair✕
- Connections
- 2 pairs of types, where a type in auditwheel.linux uses a type in auditwheel.repair.
- The types involved
maturin.auditwheel.linux.ElfRepairer→maturin.auditwheel.repair.PatchKindmaturin.auditwheel.linux.ElfRepairer→maturin.auditwheel.repair.WheelRepairer
- Direction
- auditwheel.linux uses auditwheel.repair, so a change to auditwheel.repair can break auditwheel.linux, while a change to auditwheel.linux can't break auditwheel.repair.
- Position
- Below the diagonal: auditwheel.linux uses a module listed above it, which is the healthy direction.
37→13 binding_generator.bin_binding uses metadata✕
- Connections
- 2 pairs of types, where a type in binding_generator.bin_binding uses a type in metadata.
- The types involved
maturin.binding_generator.bin_binding.BinBindingGenerator→maturin.metadata.Metadata24maturin.binding_generator.bin_binding.bin_binding$module→maturin.metadata.Metadata24
- Direction
- binding_generator.bin_binding uses metadata, so a change to metadata can break binding_generator.bin_binding, while a change to binding_generator.bin_binding can't break metadata.
- Position
- Below the diagonal: binding_generator.bin_binding uses a module listed above it, which is the healthy direction.
37→21 binding_generator.bin_binding uses build_context✕
- Connections
- 1 pair of types, where a type in binding_generator.bin_binding uses a type in build_context.
- The types involved
maturin.binding_generator.bin_binding.BinBindingGenerator→maturin.build_context.BuildContext
- Direction
- binding_generator.bin_binding uses build_context, so a change to build_context can break binding_generator.bin_binding, while a change to binding_generator.bin_binding can't break build_context.
- Position
- Below the diagonal: binding_generator.bin_binding uses a module listed above it, which is the healthy direction.
37→30 binding_generator.bin_binding uses compile✕
- Connections
- 2 pairs of types, where a type in binding_generator.bin_binding uses a type in compile.
- The types involved
maturin.binding_generator.bin_binding.BinBindingGenerator→maturin.compile.BuildArtifactmaturin.binding_generator.bin_binding.bin_binding$module→maturin.compile.BuildArtifact
- Direction
- binding_generator.bin_binding uses compile, so a change to compile can break binding_generator.bin_binding, while a change to binding_generator.bin_binding can't break compile.
- Position
- Below the diagonal: binding_generator.bin_binding uses a module listed above it, which is the healthy direction.
37→34 binding_generator.bin_binding uses binding_generator✕
- Connections
- 1 pair of types, where a type in binding_generator.bin_binding uses a type in binding_generator.
- The types involved
maturin.binding_generator.bin_binding.BinBindingGenerator→maturin.binding_generator.BindingGenerator
- Direction
- binding_generator.bin_binding uses binding_generator, so a change to binding_generator can break binding_generator.bin_binding, while a change to binding_generator.bin_binding can't break binding_generator.
- Position
- Below the diagonal: binding_generator.bin_binding uses a module listed above it, which is the healthy direction.
38→21 binding_generator.cffi_binding uses build_context✕
- Connections
- 1 pair of types, where a type in binding_generator.cffi_binding uses a type in build_context.
- The types involved
maturin.binding_generator.cffi_binding.CffiBindingGenerator→maturin.build_context.BuildContext
- Direction
- binding_generator.cffi_binding uses build_context, so a change to build_context can break binding_generator.cffi_binding, while a change to binding_generator.cffi_binding can't break build_context.
- Position
- Below the diagonal: binding_generator.cffi_binding uses a module listed above it, which is the healthy direction.
38→22 binding_generator.cffi_binding uses python_interpreter✕
- Connections
- 1 pair of types, where a type in binding_generator.cffi_binding uses a type in python_interpreter.
- The types involved
maturin.binding_generator.cffi_binding.CffiBindingGenerator→maturin.python_interpreter.PythonInterpreter
- Direction
- binding_generator.cffi_binding uses python_interpreter, so a change to python_interpreter can break binding_generator.cffi_binding, while a change to binding_generator.cffi_binding can't break python_interpreter.
- Position
- Below the diagonal: binding_generator.cffi_binding uses a module listed above it, which is the healthy direction.
38→30 binding_generator.cffi_binding uses compile✕
- Connections
- 1 pair of types, where a type in binding_generator.cffi_binding uses a type in compile.
- The types involved
maturin.binding_generator.cffi_binding.CffiBindingGenerator→maturin.compile.BuildArtifact
- Direction
- binding_generator.cffi_binding uses compile, so a change to compile can break binding_generator.cffi_binding, while a change to binding_generator.cffi_binding can't break compile.
- Position
- Below the diagonal: binding_generator.cffi_binding uses a module listed above it, which is the healthy direction.
38→34 binding_generator.cffi_binding uses binding_generator✕
- Connections
- 1 pair of types, where a type in binding_generator.cffi_binding uses a type in binding_generator.
- The types involved
maturin.binding_generator.cffi_binding.CffiBindingGenerator→maturin.binding_generator.BindingGenerator
- Direction
- binding_generator.cffi_binding uses binding_generator, so a change to binding_generator can break binding_generator.cffi_binding, while a change to binding_generator.cffi_binding can't break binding_generator.
- Position
- Below the diagonal: binding_generator.cffi_binding uses a module listed above it, which is the healthy direction.
39→21 binding_generator.pyo3_binding uses build_context✕
- Connections
- 1 pair of types, where a type in binding_generator.pyo3_binding uses a type in build_context.
- The types involved
maturin.binding_generator.pyo3_binding.Pyo3BindingGenerator→maturin.build_context.BuildContext
- Direction
- binding_generator.pyo3_binding uses build_context, so a change to build_context can break binding_generator.pyo3_binding, while a change to binding_generator.pyo3_binding can't break build_context.
- Position
- Below the diagonal: binding_generator.pyo3_binding uses a module listed above it, which is the healthy direction.
39→22 binding_generator.pyo3_binding uses python_interpreter✕
- Connections
- 2 pairs of types, where a type in binding_generator.pyo3_binding uses a type in python_interpreter.
- The types involved
maturin.binding_generator.pyo3_binding.Pyo3BindingGenerator→maturin.python_interpreter.PythonInterpretermaturin.binding_generator.pyo3_binding.pyo3_binding$module→maturin.python_interpreter.PythonInterpreter
- Direction
- binding_generator.pyo3_binding uses python_interpreter, so a change to python_interpreter can break binding_generator.pyo3_binding, while a change to binding_generator.pyo3_binding can't break python_interpreter.
- Position
- Below the diagonal: binding_generator.pyo3_binding uses a module listed above it, which is the healthy direction.
39→24 binding_generator.pyo3_binding uses bridge✕
- Connections
- 2 pairs of types, where a type in binding_generator.pyo3_binding uses a type in bridge.
- The types involved
maturin.binding_generator.pyo3_binding.Pyo3BindingGenerator→maturin.bridge.StableAbiKindmaturin.binding_generator.pyo3_binding.pyo3_binding$module→maturin.bridge.StableAbiKind
- Direction
- binding_generator.pyo3_binding uses bridge, so a change to bridge can break binding_generator.pyo3_binding, while a change to binding_generator.pyo3_binding can't break bridge.
- Position
- Below the diagonal: binding_generator.pyo3_binding uses a module listed above it, which is the healthy direction.
39→30 binding_generator.pyo3_binding uses compile✕
- Connections
- 1 pair of types, where a type in binding_generator.pyo3_binding uses a type in compile.
- The types involved
maturin.binding_generator.pyo3_binding.Pyo3BindingGenerator→maturin.compile.BuildArtifact
- Direction
- binding_generator.pyo3_binding uses compile, so a change to compile can break binding_generator.pyo3_binding, while a change to binding_generator.pyo3_binding can't break compile.
- Position
- Below the diagonal: binding_generator.pyo3_binding uses a module listed above it, which is the healthy direction.
39→34 binding_generator.pyo3_binding uses binding_generator✕
- Connections
- 1 pair of types, where a type in binding_generator.pyo3_binding uses a type in binding_generator.
- The types involved
maturin.binding_generator.pyo3_binding.Pyo3BindingGenerator→maturin.binding_generator.BindingGenerator
- Direction
- binding_generator.pyo3_binding uses binding_generator, so a change to binding_generator can break binding_generator.pyo3_binding, while a change to binding_generator.pyo3_binding can't break binding_generator.
- Position
- Below the diagonal: binding_generator.pyo3_binding uses a module listed above it, which is the healthy direction.
40→21 binding_generator.uniffi_binding uses build_context✕
- Connections
- 1 pair of types, where a type in binding_generator.uniffi_binding uses a type in build_context.
- The types involved
maturin.binding_generator.uniffi_binding.UniFfiBindingGenerator→maturin.build_context.BuildContext
- Direction
- binding_generator.uniffi_binding uses build_context, so a change to build_context can break binding_generator.uniffi_binding, while a change to binding_generator.uniffi_binding can't break build_context.
- Position
- Below the diagonal: binding_generator.uniffi_binding uses a module listed above it, which is the healthy direction.
40→30 binding_generator.uniffi_binding uses compile✕
- Connections
- 1 pair of types, where a type in binding_generator.uniffi_binding uses a type in compile.
- The types involved
maturin.binding_generator.uniffi_binding.UniFfiBindingGenerator→maturin.compile.BuildArtifact
- Direction
- binding_generator.uniffi_binding uses compile, so a change to compile can break binding_generator.uniffi_binding, while a change to binding_generator.uniffi_binding can't break compile.
- Position
- Below the diagonal: binding_generator.uniffi_binding uses a module listed above it, which is the healthy direction.
40→34 binding_generator.uniffi_binding uses binding_generator✕
- Connections
- 1 pair of types, where a type in binding_generator.uniffi_binding uses a type in binding_generator.
- The types involved
maturin.binding_generator.uniffi_binding.UniFfiBindingGenerator→maturin.binding_generator.BindingGenerator
- Direction
- binding_generator.uniffi_binding uses binding_generator, so a change to binding_generator can break binding_generator.uniffi_binding, while a change to binding_generator.uniffi_binding can't break binding_generator.
- Position
- Below the diagonal: binding_generator.uniffi_binding uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 24 | Medium |
| A05:2025 — Injection | 14 | High / Critical |
| A02:2025 — Security Misconfiguration | 11 | High / Critical |
Roadmap
First, address the absence of Architecture Decision Records by documenting significant design choices in a dedicated folder, and clarify test execution steps in the project README. Next, resolve the widespread issues with interpolated log messages to ensure proper structured logging. Finally, mitigate off-boarding risks by addressing the identified bus factor concerns to maintain team continuity.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +4.9 pts | Low | ADR Quality |
| 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. | +4.6 pts | Medium | Architecture documentation |
| Interpolated log message defeats structured logging | +3.3 pts | Medium | Structured logging |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.6 pts | Low | Bus Factor |
| 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. | +2.4 pts | Medium | Documentation (README) |
| Improve Dependency Hygiene — currently 8.3/10. | +1.6 pts | Medium | Dependency Hygiene |
| Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with maturin::compile::compile_target (cognitive 92), maturin::module_writer::py_preamble::find_python_insertion_point (cognitive 75). | +0.8 pts | Medium | Cognitive Complexity |
| Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED. | +0.6 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium advisory (unmaintained): REDACTED |
| src/cargo_options.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/pyproject_toml.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| maturin/__init__.py | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/compile.rs | 7.0 | Mixed | Cyclomatic Complexity: maturin::compile::compile_target (cyclomatic 33) |
| src/auditwheel/linux.rs | 7.0 | Mixed | Cyclomatic Complexity: maturin::auditwheel::linux::auditwheel_rs (cyclomatic 21) |
| src/source_distribution/cargo_toml_rewrite.rs | 7.0 | Mixed | Cyclomatic Complexity: maturin::source_distribution::cargo_toml_rewrite::rewrite_cargo_toml_targets (cyclomatic 27) |
| src/python_interpreter/config.rs | 7.0 | Mixed | Cyclomatic Complexity: InterpreterConfig::lookup_one (cyclomatic 26) |
| src/build_context/builder.rs | 7.1 | Mixed | Cyclomatic Complexity: BuildContextBuilder::build (cyclomatic 18) |
| src/metadata.rs | 7.1 | Mixed | Cyclomatic Complexity: Metadata24::merge_license (cyclomatic 16) |
| src/module_writer/py_preamble.rs | 7.2 | Mixed | Cyclomatic Complexity: maturin::module_writer::py_preamble::find_python_insertion_point (cyclomatic 43) |
| src/python_interpreter/discovery.rs | 7.2 | Mixed | Cyclomatic Complexity: maturin::python_interpreter::discovery::find_all_windows (cyclomatic 23) |
| src/bridge/detection.rs | 7.2 | Mixed | Cyclomatic Complexity: maturin::bridge::detection::find_bridge_with_deps (cyclomatic 18) |
| src/develop/mod.rs | 7.2 | Mixed | Cyclomatic Complexity: maturin::develop::develop (cyclomatic 16) |
| src/project_layout.rs | 7.2 | Mixed | Cognitive Complexity: ProjectResolver::resolve_manifest_paths (cognitive 33) |
| tests/common/pep517.rs | 7.3 | Mixed | Explicit Debt: HackComment |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 62 of 62 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 62 dimensions across the health lenses
- 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, 215 of 258 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Watchdog duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs, .py) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`, or `coverage run -m pytest` then `coverage xml`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a 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 — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — anylinux2014' ]\n then\n yum install -y libffi-devel openssh-clients\n else\n apk add --no-cache libffi-dev\n fi\n python3.9 -m pip install --no-cache-dir cffi\n python3.10 -m pip install --no-cache-dir cffi\n python3.11 -m pip install --no-cache-dir cffi\n python3.12 -m pip install --no-cache-dir cffi\n mkdir /io\n" did not complete successfully: exit code: 1; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X16 Unfloored truncation loop — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X18 Disposal-pattern correctness — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 58 further occurrence(s) are not listed individually; the score already reflects all 98.
- X5 Nullable reference types — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Python, Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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 is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (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.
- 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 Complexity
21 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was maturin::module_writer::py_preamble::find_python_insertion_point at 43. A further 1 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 maturin::run at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: src/main.rs (maturin::run at 18). 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.
What to do
- Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with maturin::module_writer::py_preamble::find_python_insertion_point (cyclomatic 43), maturin::compile::compile_target (cyclomatic 33). — 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 7.0 to about 7.5/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
51 method(s) exceeded the cognitive complexity threshold of 15; the worst was maturin::compile::compile_target at 92.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cognitive Complexity — start with maturin::compile::compile_target (cognitive 92), maturin::module_writer::py_preamble::find_python_insertion_point (cognitive 75). — 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 Cognitive Complexity from 2.6 to about 3.9/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
21 god class(es) detected.
What to do
- Resolve the 8 FileTooLong finding(s) in God Classes — start with compile.rs, mod.rs, build_orchestrator.rs. — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 5 MethodTooLong finding(s) in God Classes — start with config.rs (2), builder.rs, pgo.rs. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 FunctionTooLong finding(s) in God Classes — start with py_preamble.rs, mod.rs, cargo_toml_rewrite.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
15 duplicated block group(s) detected. 5 of the 15 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.
What to do
- Resolve the 2 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with render.rs, config.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with metadata.rs, py_preamble.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with config.rs, lib.rs. — One of this dimension's main actionable groups (2 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D5 · Coupling
6 production modules (Cargo+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 3 of the 6 (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).
D6 · Cohesion (LCOM4)
0 of 35 classes have LCOM4 above 3.
D9 · Test Distribution
384 test methods: 313 unit, 71 integration, 0 BDD, 0 e2e. The Rust suite contributes 364 `#[test]` function(s) across 61 file(s) declaring at least one; its unit/integration split is Cargo's own — 9 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test. The Python suite contributes 20 test function(s) across 13 file(s) declaring at least one — every `def test…` in a file pytest or unittest would collect, which is those frameworks' own definition of a case; a parametrize table counts once, so this is a floor. Its tier split is read from file names and paths only.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 61 test files): measured (0 flaky).
D12 · Dependency Hygiene
34 outdated, 0 yanked direct Cargo dependencies. 75 of 81 direct crates were graded against crates.io (0 not published there, 6 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.
What to do
- Improve Dependency Hygiene — currently 8.3/10. — 34 outdated, 0 yanked direct Cargo dependencies. 75 of 81 direct crates were graded against crates.io (0 not published there, 6 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.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 441 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. This repository publishes itself under MIT OR Apache-2.0, 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.
D15 · Churn × Complexity Hotspots
Top hotspots: src/python_interpreter/config.rs (3×26=78); src/compile.rs (3×19=57); src/pgo.rs (2×16=32)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with config.rs, compile.rs, pgo.rs. — One of this dimension's main actionable groups (4 warning-level).
D16 · Bus Factor
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/auditwheel/macos.rs. Counted over 75 of the 229 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
8 deducted task-comment markers across 35122 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 6 TodoComment finding(s) in Explicit Debt — start with cargo_options.rs (2), pyproject_toml.rs (2), uniffi_binding.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 HackComment finding(s) in Explicit Debt — start with pep517.rs (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 27 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
14 finding(s): 0 critical, 13 high, 0 medium, 1 low. semgrep hit a parse error in 2 file(s) — `REDACTED`, `src/main.rs` (line 318) — 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 3 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.
What to do
- Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
- 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).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
D30 · Dependency Vulnerabilities
19 finding(s): 0 critical, 0 high, 19 medium, 0 low.
What to do
- Resolve the 11 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 warning-level).
- Resolve the 7 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 1 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
11 finding(s): 0 critical, 2 high, 6 medium, 3 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
D34 · Knowledge Freshness
2 of 75 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/module_writer/wheel_writer.rs. Counted over 75 of the 229 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: get_interpreter_metadata.py↔mod.rs 89%; audit.rs↔policy.rs 61%; cargo_toml.rs↔metadata.rs 59%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with patchelf.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 4 Change coupling finding(s) in Change Coupling — start with get_interpreter_metadata.py, audit.rs, cargo_toml.rs. — One of this dimension's main actionable groups (4 warning-level).
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- 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).
- 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).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 1 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX8 · Test isolation
AX9 · CQS / query purity
M1 · Documentation (README)
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.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 53 of 78 project(s) that lack one — worth up to 1.4 pts.
M2 · Architecture documentation
- 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 structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Consider OpenTelemetry tracing/metrics (opentelemetry with tracing-opentelemetry) and a health-check endpoint (a /health route on your axum/actix router) for operability.
P3 · Security & performance tooling
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `netlify.toml` configures this repository's static hosting, including its response headers, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — netlify.toml:1
What to do
- Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X17 · Uncapped recursion over a caller-supplied document
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug!` at line 392 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/compile.rs:392
- `debug!` at line 572 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/compile.rs:572
- `debug!` at line 639 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/compile.rs:639
- `debug!` at line 685 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/compile.rs:685
- `debug!` at line 899 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/compile.rs:899
- `debug!` at line 915 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/compile.rs:915
- `debug!` at line 1003 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/compile.rs:1003
- `trace!` at line 1023 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `trace!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/compile.rs:1023
- `debug!` at line 334 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/cross_compile.rs:334
- `debug!` at line 437 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/metadata.rs:437
- `debug!` at line 119 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/pgo.rs:119
- `debug!` at line 174 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/pgo.rs:174
- `debug!` at line 228 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/pgo.rs:228
- `debug!` at line 242 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/pgo.rs:242
- `debug!` at line 260 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/pgo.rs:260
- `debug!` at line 373 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/pgo.rs:373
- `debug!` at line 395 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/pgo.rs:395
- `debug!` at line 263 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/project_layout.rs:263
- `debug!` at line 276 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/project_layout.rs:276
- `debug!` at line 281 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/project_layout.rs:281
- `debug!` at line 291 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/project_layout.rs:291
- `debug!` at line 297 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/project_layout.rs:297
- `debug!` at line 353 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/project_layout.rs:353
- `debug!` at line 372 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/project_layout.rs:372
- `debug!` at line 458 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/project_layout.rs:458
- `debug!` at line 287 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/upload.rs:287
- `debug!` at line 319 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/upload.rs:319
- `debug!` at line 331 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/upload.rs:331
- `debug!` at line 580 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/upload.rs:580
- `error!` at line 388 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `error!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/target/mod.rs:388
- `debug!` at line 30 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:30
- `debug!` at line 117 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:117
- `debug!` at line 399 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:399
- `debug!` at line 657 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:657
- `debug!` at line 721 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:721
- `debug!` at line 748 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:748
- `debug!` at line 787 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:787
- `debug!` at line 806 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:806
- `debug!` at line 829 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/cargo_toml_rewrite.rs:829
- `debug!` at line 112 is handed a format string with `{…}` values in it, so tracing records one finished `message` field — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Record the values as fields beside a constant message instead: `debug!(order_id = %order_id, status = ?status, "order status updated")` (`%` records a value by its `Display`, `?` by its `Debug`, a bare name as itself), which a JSON subscriber, OpenTelemetry or a log store keeps as queryable keys. An error goes in as a field too: `error = %err`. — src/source_distribution/mod.rs:112
What to do
- Interpolated log message defeats structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by D2, X4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 62% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 72% | Strong | Solid. |
| Security | 78% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 86% | Strong | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 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
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 56 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (1 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's Python imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — anylinux2014' ]\n then\n yum install -y libffi-devel openssh-clients\n else\n apk add --no-cache libffi-dev\n fi\n python3.9 -m pip install --no-cache-dir cffi\n python3.10 -m pip install --no-cache-dir cffi\n python3.11 -m pip install --no-cache-dir cffi\n python3.12 -m pip install --no-cache-dir cffi\n mkdir /io\n" 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 a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~4467 lines of test source are present (.rs, .py) 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.
- 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 — Naming consistency is measured on C# only; JavaScript, Python, Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Python, 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+ projects each declaring an entity of their own. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .py, .rs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- 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) — 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- 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 included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- 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
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 27 current-state document(s) make no claim of a kind M4 checks. 16 claim(s) of kinds M4 does not check were not checked (path 16); M4 checks only links and versions.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Python, Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF2 Allocation hygiene — Not applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- X16 Unfloored truncation loop — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X2 Cancellation propagation — no C# was loaded; this repository's Python and Rust were read, and no request in it can be cancelled by a caller — a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation; a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 16 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: patchelf.rs ↔ mod.rs src/auditwheel/patchelf.rs:1
Serious — 151 finding(s)
- maturin::compile::compile_target (cognitive 92) src/compile.rs:999
- maturin::module_writer::py_preamble::find_python_insertion_point (cognitive 75) src/module_writer/py_preamble.rs:16
- maturin::python_interpreter::discovery::find_all_windows (cognitive 57) src/python_interpreter/discovery.rs:161
- maturin::compile::create_build_command (cognitive 41) src/compile.rs:735
- maturin::python_interpreter::discovery::check_executable (cognitive 37) src/python_interpreter/discovery.rs:300
- maturin::source_distribution::cargo_toml_rewrite::rewrite_cargo_toml_targets (cognitive 37) src/source_distribution/cargo_toml_rewrite.rs:651
- maturin::auditwheel::linux::policy_is_satisfied (cognitive 36) src/auditwheel/linux.rs:161
- maturin::source_distribution::cargo_toml_rewrite::rewrite_cargo_toml (cognitive 36) src/source_distribution/cargo_toml_rewrite.rs:25
- maturin::bridge::detection::find_bridge_with_deps (cognitive 33) src/bridge/detection.rs:41
- maturin::source_distribution::cargo_toml_rewrite::resolve_workspace_package_fields (cognitive 29) src/source_distribution/cargo_toml_rewrite.rs:193
- maturin::module_writer::write_python_part (cognitive 28) src/module_writer/mod.rs:157
- maturin::build_context::builder::resolve_platform_tags (cognitive 27) src/build_context/builder.rs:485
- maturin::compile::configure_pyo3_env (cognitive 27) src/compile.rs:858
- maturin::auditwheel::linux::check_external_libs_policy (cognitive 25) src/auditwheel/linux.rs:750
- maturin::binding_generator::generate_binding (cognitive 25) src/binding_generator/mod.rs:373
- maturin::source_distribution::path_deps::find_path_deps (cognitive 23) src/source_distribution/path_deps.rs:79
- maturin::auditwheel::linux::auditwheel_rs (cognitive 22) src/auditwheel/linux.rs:307
- maturin::compile::native_library_has_python_entrypoint (cognitive 22) src/compile.rs:1194
- maturin::compile::cargo_build_command (cognitive 21) src/compile.rs:367
- maturin::source_distribution::pyproject::add_pyproject_metadata (cognitive 21) src/source_distribution/pyproject.rs:239
- maturin::module_writer::write_dist_info (cognitive 20) src/module_writer/mod.rs:340
- maturin::auditwheel::linux::find_versioned_libraries (cognitive 19) src/auditwheel/linux.rs:114
- maturin::auditwheel::linux::get_policy_and_libs (cognitive 19) src/auditwheel/linux.rs:648
- maturin::develop::install_dependencies (cognitive 19) src/develop/mod.rs:121
- maturin::ci::github::resolve::resolve_config (cognitive 18) src/ci/github/resolve.rs:162
- maturin::module_writer::py_preamble::find_python_insertion_point (cyclomatic 43) src/module_writer/py_preamble.rs:16
- maturin::compile::compile_target (cyclomatic 33) src/compile.rs:999
- maturin::source_distribution::cargo_toml_rewrite::rewrite_cargo_toml_targets (cyclomatic 27) src/source_distribution/cargo_toml_rewrite.rs:651
- maturin::python_interpreter::discovery::find_all_windows (cyclomatic 23) src/python_interpreter/discovery.rs:161
- maturin::auditwheel::linux::auditwheel_rs (cyclomatic 21) src/auditwheel/linux.rs:307
- maturin::auditwheel::linux::policy_is_satisfied (cyclomatic 20) src/auditwheel/linux.rs:161
- maturin::compile::create_build_command (cyclomatic 19) src/compile.rs:735
- maturin::compile::configure_pyo3_env (cyclomatic 19) src/compile.rs:858
- maturin::bridge::detection::find_bridge_with_deps (cyclomatic 18) src/bridge/detection.rs:41
- maturin::cross_compile::search_lib_dir (cyclomatic 17) src/cross_compile.rs:161
- maturin::build_context::builder::resolve_platform_tags (cyclomatic 16) src/build_context/builder.rs:485
- maturin::develop::develop (cyclomatic 16) src/develop/mod.rs:363
- maturin::source_distribution::cargo_toml_rewrite::resolve_workspace_package_fields (cyclomatic 16) src/source_distribution/cargo_toml_rewrite.rs:193
- maturin::source_distribution::cargo_toml_rewrite::resolved_dep_to_toml (cyclomatic 16) src/source_distribution/cargo_toml_rewrite.rs:578
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: src/compile.rs src/compile.rs
- FileTooLong: source_distribution/mod.rs src/source_distribution/mod.rs
- FileTooLong: src/build_orchestrator.rs src/build_orchestrator.rs
- FileTooLong: src/metadata.rs src/metadata.rs
- FileTooLong: github/render.rs src/ci/github/render.rs
- FileTooLong: python_interpreter/resolver.rs src/python_interpreter/resolver.rs
- FileTooLong: source_distribution/cargo_toml_rewrite.rs src/source_distribution/cargo_toml_rewrite.rs
- FileTooLong: auditwheel/linux.rs src/auditwheel/linux.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment src/cargo_options.rs:21
- TodoComment src/cargo_options.rs:247
- TodoComment src/pyproject_toml.rs:153
- TodoComment src/pyproject_toml.rs:342
- TodoComment src/binding_generator/uniffi_binding.rs:206
- TodoComment maturin/__init__.py:38
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: InterpreterConfig.lookup_one src/python_interpreter/config.rs:73
- MethodTooLong: BuildContextBuilder.build src/build_context/builder.rs:78
- MethodTooLong: PgoContext.run_instrumentation src/pgo.rs:132
- MethodTooLong: ProjectResolver.resolve src/project_layout.rs:62
- MethodTooLong: InterpreterConfig.from_pyo3_config src/python_interpreter/config.rs:326
- Hotspot: src/python_interpreter/config.rs src/python_interpreter/config.rs:73
- Hotspot: src/compile.rs src/compile.rs:858
- Hotspot: src/pgo.rs src/pgo.rs:132
- Hotspot: src/binding_generator/mod.rs src/binding_generator/mod.rs:373
- FunctionTooLong: maturin::module_writer::py_preamble::find_python_insertion_point src/module_writer/py_preamble.rs:16
- FunctionTooLong: maturin::develop::develop src/develop/mod.rs:363
- FunctionTooLong: maturin::source_distribution::cargo_toml_rewrite::rewrite_cargo_toml_targets src/source_distribution/cargo_toml_rewrite.rs:651
- FunctionTooLong: maturin::compile::compile_target src/compile.rs:999
- Change coupling: get_interpreter_metadata.py ↔ mod.rs src/python_interpreter/get_interpreter_metadata.py:1
- Change coupling: audit.rs ↔ policy.rs src/auditwheel/audit.rs:1
- Change coupling: cargo_toml.rs ↔ metadata.rs src/cargo_toml.rs:1
- Change coupling: build_options.rs ↔ get_interpreter_metadata.py src/build_options.rs:1
- ClassTooLong: BuildOrchestrator src/build_orchestrator.rs:35
- ClassTooLong: Metadata24 src/metadata.rs:40
- ClassTooLong: InterpreterResolver src/python_interpreter/resolver.rs:191
- InterpreterConfig::lookup_one (cyclomatic 26) src/python_interpreter/config.rs:73
- InterpreterConfig::from_pyo3_config (cyclomatic 21) src/python_interpreter/config.rs:326
- HackComment tests/common/pep517.rs:85
- HackComment tests/common/pep517.rs:90
- Metadata24::merge_license (cognitive 41) src/metadata.rs:367
- Metadata24::from_cargo_toml (cognitive 23) src/metadata.rs:565
- ProjectResolver::resolve_manifest_paths (cognitive 33) src/project_layout.rs:248
- ProjectResolver::resolve (cognitive 26) src/project_layout.rs:62
- InterpreterConfig::lookup_one (cognitive 25) src/python_interpreter/config.rs:73
- InterpreterConfig::from_pyo3_config (cognitive 18) src/python_interpreter/config.rs:326
- Duplicated block (15 lines × 2) src/ci/github/render.rs:327
- Duplicated block (15 lines × 2) src/python_interpreter/config.rs:96
- Duplicated block (13 lines × 2) src/metadata.rs:422
- Duplicated block (13 lines × 2) src/module_writer/py_preamble.rs:167
- Duplicated block (12 lines × 2) src/python_interpreter/config.rs:266
- Duplicated block (12 lines × 2) test-crates/pyo3-abi3t/src/lib.rs:9
- Duplicated block (6 lines × 2) src/ci/github/render.rs:628
- Duplicated block (6 lines × 2) maturin/__init__.py:127
- CargoOptions::merge_with_pyproject_toml (cyclomatic 21) src/cargo_options.rs:233
- BuildContext::add_external_libs (cyclomatic 20) src/build_context/repair.rs:147
- BuildContextBuilder::build (cyclomatic 18) src/build_context/builder.rs:78
- Metadata24::merge_license (cyclomatic 16) src/metadata.rs:367
- PgoContext::run_instrumentation (cyclomatic 16) src/pgo.rs:132
- PgoContext::run_instrumentation (cognitive 31) src/pgo.rs:132
- BuildContext::add_external_libs (cognitive 29) src/build_context/repair.rs:147
- Pyo3BindingGenerator::generate_bindings (cognitive 24) src/binding_generator/pyo3_binding.rs:93
- BuildContextBuilder::build (cognitive 24) src/build_context/builder.rs:78
- noxfile.update_pyo3 (cognitive 24) REDACTED:39
- InstallDest::add_debuginfo (cognitive 23) src/binding_generator/mod.rs:214
- CargoOptions::merge_with_pyproject_toml (cognitive 23) src/cargo_options.rs:233
- InterpreterResolver::discover_native (cognitive 21) src/python_interpreter/resolver.rs:427
- ProjectLayout::determine (cognitive 18) src/project_layout.rs:428
- MacOSRepairer::audit (cognitive 17) src/auditwheel/macos.rs:33
- CrateDependencies::resolve (cognitive 16) src/bridge/detection.rs:455
- TooManyFields: ToolMaturin src/pyproject_toml.rs:357
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/auditwheel/linux.rs:515
- Duplicated block (14 lines × 2) src/python_interpreter/config.rs:127
- Duplicated block (7 lines × 2) src/auditwheel/platform_tag.rs:106
- Duplicated block (28 lines × 6) test-crates/cffi-mixed-implicit/src/lib.rs:15
- Duplicated block (20 lines × 7) test-crates/cffi-mixed-implicit/src/lib.rs:15
- Duplicated block (11 lines × 3) test-crates/lib_with_path_dep/src/lib.rs:4
- Duplicated block (10 lines × 2) test-crates/workspace-inheritance/python/src/lib.rs:5
Minor — 57 finding(s)
- Interpolated log message defeats structured logging src/compile.rs:392
- Interpolated log message defeats structured logging src/compile.rs:572
- Interpolated log message defeats structured logging src/compile.rs:639
- Interpolated log message defeats structured logging src/compile.rs:685
- Interpolated log message defeats structured logging src/compile.rs:899
- Interpolated log message defeats structured logging src/compile.rs:915
- Interpolated log message defeats structured logging src/compile.rs:1003
- Interpolated log message defeats structured logging src/compile.rs:1023
- Interpolated log message defeats structured logging src/cross_compile.rs:334
- Interpolated log message defeats structured logging src/metadata.rs:437
- Interpolated log message defeats structured logging src/pgo.rs:119
- Interpolated log message defeats structured logging src/pgo.rs:174
- Interpolated log message defeats structured logging src/pgo.rs:228
- Interpolated log message defeats structured logging src/pgo.rs:242
- Interpolated log message defeats structured logging src/pgo.rs:260
- Interpolated log message defeats structured logging src/pgo.rs:373
- Interpolated log message defeats structured logging src/pgo.rs:395
- Interpolated log message defeats structured logging src/project_layout.rs:263
- Interpolated log message defeats structured logging src/project_layout.rs:276
- Interpolated log message defeats structured logging src/project_layout.rs:281
- Interpolated log message defeats structured logging src/project_layout.rs:291
- Interpolated log message defeats structured logging src/project_layout.rs:297
- Interpolated log message defeats structured logging src/project_layout.rs:353
- Interpolated log message defeats structured logging src/project_layout.rs:372
- Interpolated log message defeats structured logging src/project_layout.rs:458
- REDACTED
- REDACTED
- REDACTED
- Orphaned file src/module_writer/wheel_writer.rs:1
- Orphaned file src/compression.rs:1
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No security response headers detected netlify.toml:1
- Duplicated predicate maturin/__init__.py:79
Minor — 34 finding(s)
- Outdated: anyhow
- Outdated: bytesize
- Outdated: cargo-config2
- Outdated: cbindgen
- Outdated: cc
- Outdated: cfg-if
- Outdated: clap
- Outdated: configparser
- Outdated: console
- Outdated: flate2
- Outdated: fs-err
- Outdated: glob
- Outdated: goblin
- Outdated: ignore
- Outdated: indexmap
- Outdated: lddtree
- Outdated: libc
- Outdated: memmap2
- Outdated: normpath
- Outdated: platform-info
- Outdated: reflink-copy
- Outdated: regex
- Outdated: rustls-pki-types
- Outdated: schemars
- Outdated: serde
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3752d8bd146c4d538a76a1e07344dd73/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3752d8bd146c4d538a76a1e07344dd73/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 14 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 19 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | artifacts/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. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-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 Confinement | runtime-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 Enforcement | runtime-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 Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |