Executive summary
spinframework/spin falls short of our standard for production because it has packages with a known security hole and pipeline tools referenced by a changeable name. It scores 56 out of 100 and is rated Adequate, and 117 of its 119 critical findings are security problems.
Security and Compliance, at 48, is the weakest lens and counts most in the score. The best first step is checking access in every handler, worth about 6 points. Stopping the 19 pipeline steps that hand secrets to unpinned tools would lift Security and Compliance itself, worth about 3 points. Raising Security and Compliance to 70 would lift the score to about 63.
Seventy-six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty secrets can leak from the build pipeline, and six pipeline steps put outside input straight into a shell command, so an attacker can run commands in the build pipeline. Pinning each tool to an exact version, limiting each secret to its own step and passing outside input through environment variables would close these risks. Updating the vulnerable packages would fix the four packages with a known security hole, and the five pipeline steps that install packages without pinning their versions need the packages they install pinned to exact versions. The part of the code nobody has worked on for a long time needs someone to learn and document it before anyone changes it.
The product code is 67,800 lines, about €80,000 to rebuild.
If Security and Compliance rose from 48 to 70, the lowest score rated Strong, the score would rise from 56 to about 63.
New since the last survey: 37 findings
- 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
- 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
- Knowledge Freshness · Orphaned knowledge crates/key-value-aws/src/store.rs
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Outbound HTTP resilience · Outbound HTTP without resilience crates/doctor/src/rustlang/target.rs
- Outbound HTTP resilience · Outbound HTTP without resilience crates/plugins/src/manager.rs
Fixed since the last survey: 10 findings
- Code Duplication · Duplicated block (8–10 lines × 2) crates/oci/src/client.rs
- Churn × Complexity Hotspots · Hotspot: src/lib.rs src/lib.rs
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0320 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0321 REDACTED
- Dependency Vulnerabilities · Medium vulnerability: RUSTSEC-2026-0325 REDACTED
- Supply-chain Provenance & Signing REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €80,000 · Estimate
| Cost to rebuild | €26,000 to €130,000, for 440 to 1,397 hours of work, about 0.5 person-years for 1 to 2 engineers |
|---|---|
| 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.8 at a score of 56. 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: 67,800 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 spin_capabilities | 2 spin_cli.commands.new | 3 spin_connection_semaphore | 4 spin_expressions | 5 spin_factor_key_value.runtime_config | 6 spin_http_routes | 7 spin_manifest.schema.v2 | 8 spin_outbound_networking_config.allowed_hosts | 9 spin_resource_table | 10 spin_core.store | 11 spin_doctor | 12 spin_factor_outbound_mysql.client | 13 spin_llm_local | 14 spin_locked_app.locked | 15 spin_manifest.schema.v2.component | 16 spin_app | 17 spin_core | 18 spin_factors.prepare | 19 spin_factors.factor | 20 spin_factor_otel | 21 spin_factor_sqlite | 22 spin_factor_key_value | 23 spin_factor_llm | 24 spin_factor_outbound_http.wasi | 25 spin_factor_outbound_mqtt.host | 26 spin_factor_outbound_mysql | 27 spin_factor_outbound_pg | 28 spin_factor_key_value.host | 29 spin_factor_outbound_http | 30 spin_factor_outbound_networking | 31 spin_factors_executor | 32 spin_manifest.schema.v2.trigger | 33 spin_runtime_factors | 34 spin_cli.commands.deps | 35 spin_loader.local | 36 spin_trigger_http | 37 spin_environments.loader | 38 spin_trigger.cli | 39 spin_trigger_http.server | 40 spin_build.manifest |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 spin_capabilities | ||||||||||||||||||||||||||||||||||||||||
| 2 spin_cli.commands.new | ||||||||||||||||||||||||||||||||||||||||
| 3 spin_connection_semaphore | ||||||||||||||||||||||||||||||||||||||||
| 4 spin_expressions | ||||||||||||||||||||||||||||||||||||||||
| 5 spin_factor_key_value.runtime_config | ||||||||||||||||||||||||||||||||||||||||
| 6 spin_http_routes | ||||||||||||||||||||||||||||||||||||||||
| 7 spin_manifest.schema.v2 | ||||||||||||||||||||||||||||||||||||||||
| 8 spin_outbound_networking_config.allowed_hosts | ||||||||||||||||||||||||||||||||||||||||
| 9 spin_resource_table | ||||||||||||||||||||||||||||||||||||||||
| 10 spin_core.store | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 spin_doctor | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 spin_factor_outbound_mysql.client | 2 | |||||||||||||||||||||||||||||||||||||||
| 13 spin_llm_local | 1 | |||||||||||||||||||||||||||||||||||||||
| 14 spin_locked_app.locked | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 spin_manifest.schema.v2.component | 2 | |||||||||||||||||||||||||||||||||||||||
| 16 spin_app | 5 | |||||||||||||||||||||||||||||||||||||||
| 17 spin_core | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 spin_factors.prepare | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 spin_factors.factor | 1 | 2 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 20 spin_factor_otel | 3 | 2 | ||||||||||||||||||||||||||||||||||||||
| 21 spin_factor_sqlite | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 22 spin_factor_key_value | 2 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 spin_factor_llm | 1 | 2 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 24 spin_factor_outbound_http.wasi | 3 | 1 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 25 spin_factor_outbound_mqtt.host | 1 | 2 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 spin_factor_outbound_mysql | 2 | 3 | 1 | 1 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 27 spin_factor_outbound_pg | 2 | 2 | 1 | 1 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 28 spin_factor_key_value.host | 2 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 29 spin_factor_outbound_http | 2 | 1 | 1 | 2 | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||
| 30 spin_factor_outbound_networking | 3 | 2 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 31 spin_factors_executor | 1 | 2 | 1 | 1 | 4 | 5 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||
| 32 spin_manifest.schema.v2.trigger | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 spin_runtime_factors | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 34 spin_cli.commands.deps | 2 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 35 spin_loader.local | 1 | 3 | 1 | 1 | 3 | 2 | 1 | 2 | ||||||||||||||||||||||||||||||||
| 36 spin_trigger_http | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 spin_environments.loader | 1 | 1 | 3 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 38 spin_trigger.cli | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||||
| 39 spin_trigger_http.server | 3 | 2 | 4 | |||||||||||||||||||||||||||||||||||||
| 40 spin_build.manifest | 1 | 2 | 1 | 1 |
10→17 spin_core.store uses spin_core part of a loop✕
- Connections
- 1 pair of types, where a type in spin_core.store uses a type in spin_core.
- The types involved
spin_core.store.AsState→spin_core.State
- Direction
- spin_core.store uses spin_core, so a change to spin_core can break spin_core.store, while a change to spin_core.store can't break spin_core.
- 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→4 spin_doctor uses spin_expressions✕
- Connections
- 1 pair of types, where a type in spin_doctor uses a type in spin_expressions.
- The types involved
spin_doctor.DryRunNotSupported→spin_expressions.Error
- Direction
- spin_doctor uses spin_expressions, so a change to spin_expressions can break spin_doctor, while a change to spin_doctor can't break spin_expressions.
- Position
- Below the diagonal: spin_doctor uses a module listed above it, which is the healthy direction.
12→2 spin_factor_outbound_mysql.client uses spin_cli.commands.new✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_mysql.client uses a type in spin_cli.commands.new.
- The types involved
spin_factor_outbound_mysql.client.Client→spin_cli.commands.new.ParameterValuespin_factor_outbound_mysql.client.client$module→spin_cli.commands.new.ParameterValue
- Direction
- spin_factor_outbound_mysql.client uses spin_cli.commands.new, so a change to spin_cli.commands.new can break spin_factor_outbound_mysql.client, while a change to spin_factor_outbound_mysql.client can't break spin_cli.commands.new.
- Position
- Below the diagonal: spin_factor_outbound_mysql.client uses a module listed above it, which is the healthy direction.
13→23 spin_llm_local uses spin_factor_llm part of a loop✕
- Connections
- 1 pair of types, where a type in spin_llm_local uses a type in spin_factor_llm.
- The types involved
spin_llm_local.LocalLlmEngine→spin_factor_llm.LlmEngine
- Direction
- spin_llm_local uses spin_factor_llm, so a change to spin_factor_llm can break spin_llm_local, while a change to spin_llm_local can't break spin_factor_llm.
- 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.
14→1 spin_locked_app.locked uses spin_capabilities✕
- Connections
- 1 pair of types, where a type in spin_locked_app.locked uses a type in spin_capabilities.
- The types involved
spin_locked_app.locked.LockedComponentDependency→spin_capabilities.InheritConfiguration
- Direction
- spin_locked_app.locked uses spin_capabilities, so a change to spin_capabilities can break spin_locked_app.locked, while a change to spin_locked_app.locked can't break spin_capabilities.
- Position
- Below the diagonal: spin_locked_app.locked uses a module listed above it, which is the healthy direction.
15→37 spin_manifest.schema.v2.component uses spin_environments.loader part of a loop✕
- Connections
- 2 pairs of types, where a type in spin_manifest.schema.v2.component uses a type in spin_environments.loader.
- The types involved
spin_manifest.schema.v2.component.Component→spin_environments.loader.ComponentSourcespin_manifest.schema.v2.component.ComponentProfileOverride→spin_environments.loader.ComponentSource
- Direction
- spin_manifest.schema.v2.component uses spin_environments.loader, so a change to spin_environments.loader can break spin_manifest.schema.v2.component, while a change to spin_manifest.schema.v2.component can't break spin_environments.loader.
- 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→14 spin_app uses spin_locked_app.locked✕
- Connections
- 5 pairs of types, where a type in spin_app uses a type in spin_locked_app.locked.
- The types involved
spin_app.App→spin_locked_app.locked.LockedAppspin_app.AppComponent→spin_locked_app.locked.LockedComponentspin_app.AppComponent→spin_locked_app.locked.LockedComponentSourcespin_app.AppTrigger→spin_locked_app.locked.LockedTriggerspin_app.spin_app$module→spin_locked_app.locked.LockedApp
- Direction
- spin_app uses spin_locked_app.locked, so a change to spin_locked_app.locked can break spin_app, while a change to spin_app can't break spin_locked_app.locked.
- Position
- Below the diagonal: spin_app uses a module listed above it, which is the healthy direction.
17→10 spin_core uses spin_core.store✕
- Connections
- 2 pairs of types, where a type in spin_core uses a type in spin_core.store.
- The types involved
spin_core.Engine→spin_core.store.StoreBuilderspin_core.State→spin_core.store.AsState
- Direction
- spin_core uses spin_core.store, so a change to spin_core.store can break spin_core, while a change to spin_core can't break spin_core.store.
- Position
- Below the diagonal: spin_core uses a module listed above it, which is the healthy direction.
17→15 spin_core uses spin_manifest.schema.v2.component✕
- Connections
- 1 pair of types, where a type in spin_core uses a type in spin_manifest.schema.v2.component.
- The types involved
spin_core.Engine→spin_manifest.schema.v2.component.Component
- Direction
- spin_core uses spin_manifest.schema.v2.component, so a change to spin_manifest.schema.v2.component can break spin_core, while a change to spin_core can't break spin_manifest.schema.v2.component.
- Position
- Below the diagonal: spin_core uses a module listed above it, which is the healthy direction.
18→16 spin_factors.prepare uses spin_app✕
- Connections
- 1 pair of types, where a type in spin_factors.prepare uses a type in spin_app.
- The types involved
spin_factors.prepare.PrepareContext→spin_app.AppComponent
- Direction
- spin_factors.prepare uses spin_app, so a change to spin_app can break spin_factors.prepare, while a change to spin_factors.prepare can't break spin_app.
- Position
- Below the diagonal: spin_factors.prepare uses a module listed above it, which is the healthy direction.
18→22 spin_factors.prepare uses spin_factor_key_value part of a loop✕
- Connections
- 1 pair of types, where a type in spin_factors.prepare uses a type in spin_factor_key_value.
- The types involved
spin_factors.prepare.PrepareContext→spin_factor_key_value.AppState
- Direction
- spin_factors.prepare uses spin_factor_key_value, so a change to spin_factor_key_value can break spin_factors.prepare, while a change to spin_factors.prepare can't break spin_factor_key_value.
- 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.
19→5 spin_factors.factor uses spin_factor_key_value.runtime_config✕
- Connections
- 1 pair of types, where a type in spin_factors.factor uses a type in spin_factor_key_value.runtime_config.
- The types involved
spin_factors.factor.ConfigureAppContext→spin_factor_key_value.runtime_config.RuntimeConfig
- Direction
- spin_factors.factor uses spin_factor_key_value.runtime_config, so a change to spin_factor_key_value.runtime_config can break spin_factors.factor, while a change to spin_factors.factor can't break spin_factor_key_value.runtime_config.
- Position
- Below the diagonal: spin_factors.factor uses a module listed above it, which is the healthy direction.
19→16 spin_factors.factor uses spin_app✕
- Connections
- 2 pairs of types, where a type in spin_factors.factor uses a type in spin_app.
- The types involved
spin_factors.factor.ConfigureAppContext→spin_app.Appspin_factors.factor.ConfiguredApp→spin_app.App
- Direction
- spin_factors.factor uses spin_app, so a change to spin_app can break spin_factors.factor, while a change to spin_factors.factor can't break spin_app.
- Position
- Below the diagonal: spin_factors.factor uses a module listed above it, which is the healthy direction.
19→17 spin_factors.factor uses spin_core✕
- Connections
- 1 pair of types, where a type in spin_factors.factor uses a type in spin_core.
- The types involved
spin_factors.factor.FactorField→spin_core.State
- Direction
- spin_factors.factor uses spin_core, so a change to spin_core can break spin_factors.factor, while a change to spin_factors.factor can't break spin_core.
- Position
- Below the diagonal: spin_factors.factor uses a module listed above it, which is the healthy direction.
19→18 spin_factors.factor uses spin_factors.prepare✕
- Connections
- 1 pair of types, where a type in spin_factors.factor uses a type in spin_factors.prepare.
- The types involved
spin_factors.factor.Factor→spin_factors.prepare.PrepareContext
- Direction
- spin_factors.factor uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factors.factor, while a change to spin_factors.factor can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factors.factor uses a module listed above it, which is the healthy direction.
19→22 spin_factors.factor uses spin_factor_key_value part of a loop✕
- Connections
- 2 pairs of types, where a type in spin_factors.factor uses a type in spin_factor_key_value.
- The types involved
spin_factors.factor.ConfigureAppContext→spin_factor_key_value.AppStatespin_factors.factor.ConfiguredApp→spin_factor_key_value.AppState
- Direction
- spin_factors.factor uses spin_factor_key_value, so a change to spin_factor_key_value can break spin_factors.factor, while a change to spin_factors.factor can't break spin_factor_key_value.
- 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.
20→18 spin_factor_otel uses spin_factors.prepare✕
- Connections
- 3 pairs of types, where a type in spin_factor_otel uses a type in spin_factors.prepare.
- The types involved
spin_factor_otel.InstanceState→spin_factors.prepare.SelfInstanceBuilderspin_factor_otel.OtelFactor→spin_factors.prepare.PrepareContextspin_factor_otel.OtelFactorState→spin_factors.prepare.PrepareContext
- Direction
- spin_factor_otel uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_otel, while a change to spin_factor_otel can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_otel uses a module listed above it, which is the healthy direction.
20→19 spin_factor_otel uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factor_otel uses a type in spin_factors.factor.
- The types involved
spin_factor_otel.OtelFactor→spin_factors.factor.ConfigureAppContextspin_factor_otel.OtelFactor→spin_factors.factor.Factor
- Direction
- spin_factor_otel uses spin_factors.factor, so a change to spin_factors.factor can break spin_factor_otel, while a change to spin_factor_otel can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factor_otel uses a module listed above it, which is the healthy direction.
21→18 spin_factor_sqlite uses spin_factors.prepare✕
- Connections
- 1 pair of types, where a type in spin_factor_sqlite uses a type in spin_factors.prepare.
- The types involved
spin_factor_sqlite.SqliteFactor→spin_factors.prepare.PrepareContext
- Direction
- spin_factor_sqlite uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_sqlite, while a change to spin_factor_sqlite can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_sqlite uses a module listed above it, which is the healthy direction.
21→19 spin_factor_sqlite uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factor_sqlite uses a type in spin_factors.factor.
- The types involved
spin_factor_sqlite.SqliteFactor→spin_factors.factor.ConfigureAppContextspin_factor_sqlite.SqliteFactor→spin_factors.factor.Factor
- Direction
- spin_factor_sqlite uses spin_factors.factor, so a change to spin_factors.factor can break spin_factor_sqlite, while a change to spin_factor_sqlite can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factor_sqlite uses a module listed above it, which is the healthy direction.
22→3 spin_factor_key_value uses spin_connection_semaphore✕
- Connections
- 2 pairs of types, where a type in spin_factor_key_value uses a type in spin_connection_semaphore.
- The types involved
spin_factor_key_value.AppState→spin_connection_semaphore.ConnectionSemaphorespin_factor_key_value.InstanceBuilder→spin_connection_semaphore.ConnectionSemaphore
- Direction
- spin_factor_key_value uses spin_connection_semaphore, so a change to spin_connection_semaphore can break spin_factor_key_value, while a change to spin_factor_key_value can't break spin_connection_semaphore.
- Position
- Below the diagonal: spin_factor_key_value uses a module listed above it, which is the healthy direction.
22→18 spin_factor_key_value uses spin_factors.prepare✕
- Connections
- 2 pairs of types, where a type in spin_factor_key_value uses a type in spin_factors.prepare.
- The types involved
spin_factor_key_value.InstanceBuilder→spin_factors.prepare.FactorInstanceBuilderspin_factor_key_value.KeyValueFactor→spin_factors.prepare.PrepareContext
- Direction
- spin_factor_key_value uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_key_value, while a change to spin_factor_key_value can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_key_value uses a module listed above it, which is the healthy direction.
22→19 spin_factor_key_value uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factor_key_value uses a type in spin_factors.factor.
- The types involved
spin_factor_key_value.KeyValueFactor→spin_factors.factor.ConfigureAppContextspin_factor_key_value.KeyValueFactor→spin_factors.factor.Factor
- Direction
- spin_factor_key_value uses spin_factors.factor, so a change to spin_factors.factor can break spin_factor_key_value, while a change to spin_factor_key_value can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factor_key_value uses a module listed above it, which is the healthy direction.
22→20 spin_factor_key_value uses spin_factor_otel✕
- Connections
- 1 pair of types, where a type in spin_factor_key_value uses a type in spin_factor_otel.
- The types involved
spin_factor_key_value.InstanceBuilder→spin_factor_otel.OtelFactorState
- Direction
- spin_factor_key_value uses spin_factor_otel, so a change to spin_factor_otel can break spin_factor_key_value, while a change to spin_factor_key_value can't break spin_factor_otel.
- Position
- Below the diagonal: spin_factor_key_value uses a module listed above it, which is the healthy direction.
23→4 spin_factor_llm uses spin_expressions✕
- Connections
- 1 pair of types, where a type in spin_factor_llm uses a type in spin_expressions.
- The types involved
spin_factor_llm.InstanceState→spin_expressions.Error
- Direction
- spin_factor_llm uses spin_expressions, so a change to spin_expressions can break spin_factor_llm, while a change to spin_factor_llm can't break spin_expressions.
- Position
- Below the diagonal: spin_factor_llm uses a module listed above it, which is the healthy direction.
23→13 spin_factor_llm uses spin_llm_local✕
- Connections
- 2 pairs of types, where a type in spin_factor_llm uses a type in spin_llm_local.
- The types involved
spin_factor_llm.InstanceState→spin_llm_local.InferencingModelspin_factor_llm.LlmEngine→spin_llm_local.InferencingModel
- Direction
- spin_factor_llm uses spin_llm_local, so a change to spin_llm_local can break spin_factor_llm, while a change to spin_factor_llm can't break spin_llm_local.
- Position
- Below the diagonal: spin_factor_llm uses a module listed above it, which is the healthy direction.
23→18 spin_factor_llm uses spin_factors.prepare✕
- Connections
- 2 pairs of types, where a type in spin_factor_llm uses a type in spin_factors.prepare.
- The types involved
spin_factor_llm.InstanceState→spin_factors.prepare.SelfInstanceBuilderspin_factor_llm.LlmFactor→spin_factors.prepare.PrepareContext
- Direction
- spin_factor_llm uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_llm, while a change to spin_factor_llm can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_llm uses a module listed above it, which is the healthy direction.
23→19 spin_factor_llm uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factor_llm uses a type in spin_factors.factor.
- The types involved
spin_factor_llm.LlmFactor→spin_factors.factor.ConfigureAppContextspin_factor_llm.LlmFactor→spin_factors.factor.Factor
- Direction
- spin_factor_llm uses spin_factors.factor, so a change to spin_factors.factor can break spin_factor_llm, while a change to spin_factor_llm can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factor_llm uses a module listed above it, which is the healthy direction.
23→20 spin_factor_llm uses spin_factor_otel✕
- Connections
- 1 pair of types, where a type in spin_factor_llm uses a type in spin_factor_otel.
- The types involved
spin_factor_llm.InstanceState→spin_factor_otel.OtelFactorState
- Direction
- spin_factor_llm uses spin_factor_otel, so a change to spin_factor_otel can break spin_factor_llm, while a change to spin_factor_llm can't break spin_factor_otel.
- Position
- Below the diagonal: spin_factor_llm uses a module listed above it, which is the healthy direction.
24→3 spin_factor_outbound_http.wasi uses spin_connection_semaphore✕
- Connections
- 3 pairs of types, where a type in spin_factor_outbound_http.wasi uses a type in spin_connection_semaphore.
- The types involved
spin_factor_outbound_http.wasi.ConnectOptions→spin_connection_semaphore.ConnectionSemaphorespin_factor_outbound_http.wasi.PermittedTcpStream→spin_connection_semaphore.ConnectionPermitspin_factor_outbound_http.wasi.RequestSender→spin_connection_semaphore.ConnectionSemaphore
- Direction
- spin_factor_outbound_http.wasi uses spin_connection_semaphore, so a change to spin_connection_semaphore can break spin_factor_outbound_http.wasi, while a change to spin_factor_outbound_http.wasi can't break spin_connection_semaphore.
- Position
- Below the diagonal: spin_factor_outbound_http.wasi uses a module listed above it, which is the healthy direction.
24→4 spin_factor_outbound_http.wasi uses spin_expressions✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_http.wasi uses a type in spin_expressions.
- The types involved
spin_factor_outbound_http.wasi.wasi$module→spin_expressions.Error
- Direction
- spin_factor_outbound_http.wasi uses spin_expressions, so a change to spin_expressions can break spin_factor_outbound_http.wasi, while a change to spin_factor_outbound_http.wasi can't break spin_expressions.
- Position
- Below the diagonal: spin_factor_outbound_http.wasi uses a module listed above it, which is the healthy direction.
24→8 spin_factor_outbound_http.wasi uses spin_outbound_networking_config.allowed_hosts✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_http.wasi uses a type in spin_outbound_networking_config.allowed_hosts.
- The types involved
spin_factor_outbound_http.wasi.RequestSender→spin_outbound_networking_config.allowed_hosts.OutboundAllowedHosts
- Direction
- spin_factor_outbound_http.wasi uses spin_outbound_networking_config.allowed_hosts, so a change to spin_outbound_networking_config.allowed_hosts can break spin_factor_outbound_http.wasi, while a change to spin_factor_outbound_http.wasi can't break spin_outbound_networking_config.allowed_hosts.
- Position
- Below the diagonal: spin_factor_outbound_http.wasi uses a module listed above it, which is the healthy direction.
24→21 spin_factor_outbound_http.wasi uses spin_factor_sqlite✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_http.wasi uses a type in spin_factor_sqlite.
- The types involved
spin_factor_outbound_http.wasi.PermittedTcpStream→spin_factor_sqlite.Connectionspin_factor_outbound_http.wasi.RustlsStream→spin_factor_sqlite.Connection
- Direction
- spin_factor_outbound_http.wasi uses spin_factor_sqlite, so a change to spin_factor_sqlite can break spin_factor_outbound_http.wasi, while a change to spin_factor_outbound_http.wasi can't break spin_factor_sqlite.
- Position
- Below the diagonal: spin_factor_outbound_http.wasi uses a module listed above it, which is the healthy direction.
24→29 spin_factor_outbound_http.wasi uses spin_factor_outbound_http part of a loop✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_http.wasi uses a type in spin_factor_outbound_http.
- The types involved
spin_factor_outbound_http.wasi.RequestSender→spin_factor_outbound_http.SelfRequestOrigin
- Direction
- spin_factor_outbound_http.wasi uses spin_factor_outbound_http, so a change to spin_factor_outbound_http can break spin_factor_outbound_http.wasi, while a change to spin_factor_outbound_http.wasi can't break spin_factor_outbound_http.
- 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.
25→3 spin_factor_outbound_mqtt.host uses spin_connection_semaphore✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mqtt.host uses a type in spin_connection_semaphore.
- The types involved
spin_factor_outbound_mqtt.host.InstanceState→spin_connection_semaphore.ConnectionSemaphore
- Direction
- spin_factor_outbound_mqtt.host uses spin_connection_semaphore, so a change to spin_connection_semaphore can break spin_factor_outbound_mqtt.host, while a change to spin_factor_outbound_mqtt.host can't break spin_connection_semaphore.
- Position
- Below the diagonal: spin_factor_outbound_mqtt.host uses a module listed above it, which is the healthy direction.
25→4 spin_factor_outbound_mqtt.host uses spin_expressions✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_mqtt.host uses a type in spin_expressions.
- The types involved
spin_factor_outbound_mqtt.host.InstanceState→spin_expressions.Errorspin_factor_outbound_mqtt.host.host$module→spin_expressions.Error
- Direction
- spin_factor_outbound_mqtt.host uses spin_expressions, so a change to spin_expressions can break spin_factor_outbound_mqtt.host, while a change to spin_factor_outbound_mqtt.host can't break spin_expressions.
- Position
- Below the diagonal: spin_factor_outbound_mqtt.host uses a module listed above it, which is the healthy direction.
25→8 spin_factor_outbound_mqtt.host uses spin_outbound_networking_config.allowed_hosts✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mqtt.host uses a type in spin_outbound_networking_config.allowed_hosts.
- The types involved
spin_factor_outbound_mqtt.host.InstanceState→spin_outbound_networking_config.allowed_hosts.OutboundAllowedHosts
- Direction
- spin_factor_outbound_mqtt.host uses spin_outbound_networking_config.allowed_hosts, so a change to spin_outbound_networking_config.allowed_hosts can break spin_factor_outbound_mqtt.host, while a change to spin_factor_outbound_mqtt.host can't break spin_outbound_networking_config.allowed_hosts.
- Position
- Below the diagonal: spin_factor_outbound_mqtt.host uses a module listed above it, which is the healthy direction.
25→9 spin_factor_outbound_mqtt.host uses spin_resource_table✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mqtt.host uses a type in spin_resource_table.
- The types involved
spin_factor_outbound_mqtt.host.InstanceState→spin_resource_table.Table
- Direction
- spin_factor_outbound_mqtt.host uses spin_resource_table, so a change to spin_resource_table can break spin_factor_outbound_mqtt.host, while a change to spin_factor_outbound_mqtt.host can't break spin_resource_table.
- Position
- Below the diagonal: spin_factor_outbound_mqtt.host uses a module listed above it, which is the healthy direction.
25→18 spin_factor_outbound_mqtt.host uses spin_factors.prepare✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mqtt.host uses a type in spin_factors.prepare.
- The types involved
spin_factor_outbound_mqtt.host.InstanceState→spin_factors.prepare.SelfInstanceBuilder
- Direction
- spin_factor_outbound_mqtt.host uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_outbound_mqtt.host, while a change to spin_factor_outbound_mqtt.host can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_outbound_mqtt.host uses a module listed above it, which is the healthy direction.
25→20 spin_factor_outbound_mqtt.host uses spin_factor_otel✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mqtt.host uses a type in spin_factor_otel.
- The types involved
spin_factor_outbound_mqtt.host.InstanceState→spin_factor_otel.OtelFactorState
- Direction
- spin_factor_outbound_mqtt.host uses spin_factor_otel, so a change to spin_factor_otel can break spin_factor_outbound_mqtt.host, while a change to spin_factor_outbound_mqtt.host can't break spin_factor_otel.
- Position
- Below the diagonal: spin_factor_outbound_mqtt.host uses a module listed above it, which is the healthy direction.
26→2 spin_factor_outbound_mysql uses spin_cli.commands.new✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_mysql uses a type in spin_cli.commands.new.
- The types involved
spin_factor_outbound_mysql.InstanceState→spin_cli.commands.new.ParameterValuespin_factor_outbound_mysql.MysqlFactorData→spin_cli.commands.new.ParameterValue
- Direction
- spin_factor_outbound_mysql uses spin_cli.commands.new, so a change to spin_cli.commands.new can break spin_factor_outbound_mysql, while a change to spin_factor_outbound_mysql can't break spin_cli.commands.new.
- Position
- Below the diagonal: spin_factor_outbound_mysql uses a module listed above it, which is the healthy direction.
26→3 spin_factor_outbound_mysql uses spin_connection_semaphore✕
- Connections
- 3 pairs of types, where a type in spin_factor_outbound_mysql uses a type in spin_connection_semaphore.
- The types involved
spin_factor_outbound_mysql.AppState→spin_connection_semaphore.ConnectionSemaphorespin_factor_outbound_mysql.InstanceState→spin_connection_semaphore.ConnectionSemaphorespin_factor_outbound_mysql.InstanceStateInner→spin_connection_semaphore.ConnectionPermit
- Direction
- spin_factor_outbound_mysql uses spin_connection_semaphore, so a change to spin_connection_semaphore can break spin_factor_outbound_mysql, while a change to spin_factor_outbound_mysql can't break spin_connection_semaphore.
- Position
- Below the diagonal: spin_factor_outbound_mysql uses a module listed above it, which is the healthy direction.
26→4 spin_factor_outbound_mysql uses spin_expressions✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mysql uses a type in spin_expressions.
- The types involved
spin_factor_outbound_mysql.InstanceState→spin_expressions.Error
- Direction
- spin_factor_outbound_mysql uses spin_expressions, so a change to spin_expressions can break spin_factor_outbound_mysql, while a change to spin_factor_outbound_mysql can't break spin_expressions.
- Position
- Below the diagonal: spin_factor_outbound_mysql uses a module listed above it, which is the healthy direction.
26→8 spin_factor_outbound_mysql uses spin_outbound_networking_config.allowed_hosts✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mysql uses a type in spin_outbound_networking_config.allowed_hosts.
- The types involved
spin_factor_outbound_mysql.InstanceStateInner→spin_outbound_networking_config.allowed_hosts.OutboundAllowedHosts
- Direction
- spin_factor_outbound_mysql uses spin_outbound_networking_config.allowed_hosts, so a change to spin_outbound_networking_config.allowed_hosts can break spin_factor_outbound_mysql, while a change to spin_factor_outbound_mysql can't break spin_outbound_networking_config.allowed_hosts.
- Position
- Below the diagonal: spin_factor_outbound_mysql uses a module listed above it, which is the healthy direction.
26→9 spin_factor_outbound_mysql uses spin_resource_table✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mysql uses a type in spin_resource_table.
- The types involved
spin_factor_outbound_mysql.InstanceStateInner→spin_resource_table.Table
- Direction
- spin_factor_outbound_mysql uses spin_resource_table, so a change to spin_resource_table can break spin_factor_outbound_mysql, while a change to spin_factor_outbound_mysql can't break spin_resource_table.
- Position
- Below the diagonal: spin_factor_outbound_mysql uses a module listed above it, which is the healthy direction.
26→18 spin_factor_outbound_mysql uses spin_factors.prepare✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_mysql uses a type in spin_factors.prepare.
- The types involved
spin_factor_outbound_mysql.InstanceState→spin_factors.prepare.SelfInstanceBuilderspin_factor_outbound_mysql.OutboundMysqlFactor→spin_factors.prepare.PrepareContext
- Direction
- spin_factor_outbound_mysql uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_outbound_mysql, while a change to spin_factor_outbound_mysql can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_outbound_mysql uses a module listed above it, which is the healthy direction.
26→19 spin_factor_outbound_mysql uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_mysql uses a type in spin_factors.factor.
- The types involved
spin_factor_outbound_mysql.OutboundMysqlFactor→spin_factors.factor.ConfigureAppContextspin_factor_outbound_mysql.OutboundMysqlFactor→spin_factors.factor.Factor
- Direction
- spin_factor_outbound_mysql uses spin_factors.factor, so a change to spin_factors.factor can break spin_factor_outbound_mysql, while a change to spin_factor_outbound_mysql can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factor_outbound_mysql uses a module listed above it, which is the healthy direction.
26→20 spin_factor_outbound_mysql uses spin_factor_otel✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_mysql uses a type in spin_factor_otel.
- The types involved
spin_factor_outbound_mysql.InstanceStateInner→spin_factor_otel.OtelFactorState
- Direction
- spin_factor_outbound_mysql uses spin_factor_otel, so a change to spin_factor_otel can break spin_factor_outbound_mysql, while a change to spin_factor_outbound_mysql can't break spin_factor_otel.
- Position
- Below the diagonal: spin_factor_outbound_mysql uses a module listed above it, which is the healthy direction.
27→2 spin_factor_outbound_pg uses spin_cli.commands.new✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_pg uses a type in spin_cli.commands.new.
- The types involved
spin_factor_outbound_pg.InstanceState→spin_cli.commands.new.ParameterValuespin_factor_outbound_pg.PgFactorData→spin_cli.commands.new.ParameterValue
- Direction
- spin_factor_outbound_pg uses spin_cli.commands.new, so a change to spin_cli.commands.new can break spin_factor_outbound_pg, while a change to spin_factor_outbound_pg can't break spin_cli.commands.new.
- Position
- Below the diagonal: spin_factor_outbound_pg uses a module listed above it, which is the healthy direction.
27→3 spin_factor_outbound_pg uses spin_connection_semaphore✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_pg uses a type in spin_connection_semaphore.
- The types involved
spin_factor_outbound_pg.AppState→spin_connection_semaphore.ConnectionSemaphorespin_factor_outbound_pg.InstanceState→spin_connection_semaphore.ConnectionSemaphore
- Direction
- spin_factor_outbound_pg uses spin_connection_semaphore, so a change to spin_connection_semaphore can break spin_factor_outbound_pg, while a change to spin_factor_outbound_pg can't break spin_connection_semaphore.
- Position
- Below the diagonal: spin_factor_outbound_pg uses a module listed above it, which is the healthy direction.
27→4 spin_factor_outbound_pg uses spin_expressions✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_pg uses a type in spin_expressions.
- The types involved
spin_factor_outbound_pg.InstanceState→spin_expressions.Error
- Direction
- spin_factor_outbound_pg uses spin_expressions, so a change to spin_expressions can break spin_factor_outbound_pg, while a change to spin_factor_outbound_pg can't break spin_expressions.
- Position
- Below the diagonal: spin_factor_outbound_pg uses a module listed above it, which is the healthy direction.
27→9 spin_factor_outbound_pg uses spin_resource_table✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_pg uses a type in spin_resource_table.
- The types involved
spin_factor_outbound_pg.InstanceState→spin_resource_table.Table
- Direction
- spin_factor_outbound_pg uses spin_resource_table, so a change to spin_resource_table can break spin_factor_outbound_pg, while a change to spin_factor_outbound_pg can't break spin_resource_table.
- Position
- Below the diagonal: spin_factor_outbound_pg uses a module listed above it, which is the healthy direction.
27→18 spin_factor_outbound_pg uses spin_factors.prepare✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_pg uses a type in spin_factors.prepare.
- The types involved
spin_factor_outbound_pg.InstanceState→spin_factors.prepare.SelfInstanceBuilderspin_factor_outbound_pg.OutboundPgFactor→spin_factors.prepare.PrepareContext
- Direction
- spin_factor_outbound_pg uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_outbound_pg, while a change to spin_factor_outbound_pg can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_outbound_pg uses a module listed above it, which is the healthy direction.
27→19 spin_factor_outbound_pg uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_pg uses a type in spin_factors.factor.
- The types involved
spin_factor_outbound_pg.OutboundPgFactor→spin_factors.factor.ConfigureAppContextspin_factor_outbound_pg.OutboundPgFactor→spin_factors.factor.Factor
- Direction
- spin_factor_outbound_pg uses spin_factors.factor, so a change to spin_factors.factor can break spin_factor_outbound_pg, while a change to spin_factor_outbound_pg can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factor_outbound_pg uses a module listed above it, which is the healthy direction.
27→20 spin_factor_outbound_pg uses spin_factor_otel✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_pg uses a type in spin_factor_otel.
- The types involved
spin_factor_outbound_pg.InstanceState→spin_factor_otel.OtelFactorState
- Direction
- spin_factor_outbound_pg uses spin_factor_otel, so a change to spin_factor_otel can break spin_factor_outbound_pg, while a change to spin_factor_outbound_pg can't break spin_factor_otel.
- Position
- Below the diagonal: spin_factor_outbound_pg uses a module listed above it, which is the healthy direction.
28→3 spin_factor_key_value.host uses spin_connection_semaphore✕
- Connections
- 2 pairs of types, where a type in spin_factor_key_value.host uses a type in spin_connection_semaphore.
- The types involved
spin_factor_key_value.host.KeyValueDispatch→spin_connection_semaphore.ConnectionSemaphorespin_factor_key_value.host.host$module→spin_connection_semaphore.ConnectionSemaphore
- Direction
- spin_factor_key_value.host uses spin_connection_semaphore, so a change to spin_connection_semaphore can break spin_factor_key_value.host, while a change to spin_factor_key_value.host can't break spin_connection_semaphore.
- Position
- Below the diagonal: spin_factor_key_value.host uses a module listed above it, which is the healthy direction.
28→4 spin_factor_key_value.host uses spin_expressions✕
- Connections
- 2 pairs of types, where a type in spin_factor_key_value.host uses a type in spin_expressions.
- The types involved
spin_factor_key_value.host.KeyValueDispatch→spin_expressions.Errorspin_factor_key_value.host.host$module→spin_expressions.Error
- Direction
- spin_factor_key_value.host uses spin_expressions, so a change to spin_expressions can break spin_factor_key_value.host, while a change to spin_factor_key_value.host can't break spin_expressions.
- Position
- Below the diagonal: spin_factor_key_value.host uses a module listed above it, which is the healthy direction.
28→9 spin_factor_key_value.host uses spin_resource_table✕
- Connections
- 1 pair of types, where a type in spin_factor_key_value.host uses a type in spin_resource_table.
- The types involved
spin_factor_key_value.host.KeyValueDispatch→spin_resource_table.Table
- Direction
- spin_factor_key_value.host uses spin_resource_table, so a change to spin_resource_table can break spin_factor_key_value.host, while a change to spin_factor_key_value.host can't break spin_resource_table.
- Position
- Below the diagonal: spin_factor_key_value.host uses a module listed above it, which is the healthy direction.
28→20 spin_factor_key_value.host uses spin_factor_otel✕
- Connections
- 1 pair of types, where a type in spin_factor_key_value.host uses a type in spin_factor_otel.
- The types involved
spin_factor_key_value.host.KeyValueDispatch→spin_factor_otel.OtelFactorState
- Direction
- spin_factor_key_value.host uses spin_factor_otel, so a change to spin_factor_otel can break spin_factor_key_value.host, while a change to spin_factor_key_value.host can't break spin_factor_otel.
- Position
- Below the diagonal: spin_factor_key_value.host uses a module listed above it, which is the healthy direction.
28→22 spin_factor_key_value.host uses spin_factor_key_value✕
- Connections
- 1 pair of types, where a type in spin_factor_key_value.host uses a type in spin_factor_key_value.
- The types involved
spin_factor_key_value.host.host$module→spin_factor_key_value.SwapError
- Direction
- spin_factor_key_value.host uses spin_factor_key_value, so a change to spin_factor_key_value can break spin_factor_key_value.host, while a change to spin_factor_key_value.host can't break spin_factor_key_value.
- Position
- Below the diagonal: spin_factor_key_value.host uses a module listed above it, which is the healthy direction.
29→3 spin_factor_outbound_http uses spin_connection_semaphore✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_http uses a type in spin_connection_semaphore.
- The types involved
spin_factor_outbound_http.AppState→spin_connection_semaphore.ConnectionSemaphorespin_factor_outbound_http.InstanceHttpHooks→spin_connection_semaphore.ConnectionSemaphore
- Direction
- spin_factor_outbound_http uses spin_connection_semaphore, so a change to spin_connection_semaphore can break spin_factor_outbound_http, while a change to spin_factor_outbound_http can't break spin_connection_semaphore.
- Position
- Below the diagonal: spin_factor_outbound_http uses a module listed above it, which is the healthy direction.
29→8 spin_factor_outbound_http uses spin_outbound_networking_config.allowed_hosts✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_http uses a type in spin_outbound_networking_config.allowed_hosts.
- The types involved
spin_factor_outbound_http.InstanceHttpHooks→spin_outbound_networking_config.allowed_hosts.OutboundAllowedHosts
- Direction
- spin_factor_outbound_http uses spin_outbound_networking_config.allowed_hosts, so a change to spin_outbound_networking_config.allowed_hosts can break spin_factor_outbound_http, while a change to spin_factor_outbound_http can't break spin_outbound_networking_config.allowed_hosts.
- Position
- Below the diagonal: spin_factor_outbound_http uses a module listed above it, which is the healthy direction.
29→12 spin_factor_outbound_http uses spin_factor_outbound_mysql.client✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_http uses a type in spin_factor_outbound_mysql.client.
- The types involved
spin_factor_outbound_http.InstanceHttpHooks→spin_factor_outbound_mysql.client.Client
- Direction
- spin_factor_outbound_http uses spin_factor_outbound_mysql.client, so a change to spin_factor_outbound_mysql.client can break spin_factor_outbound_http, while a change to spin_factor_outbound_http can't break spin_factor_outbound_mysql.client.
- Position
- Below the diagonal: spin_factor_outbound_http uses a module listed above it, which is the healthy direction.
29→18 spin_factor_outbound_http uses spin_factors.prepare✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_http uses a type in spin_factors.prepare.
- The types involved
spin_factor_outbound_http.InstanceState→spin_factors.prepare.SelfInstanceBuilderspin_factor_outbound_http.OutboundHttpFactor→spin_factors.prepare.PrepareContext
- Direction
- spin_factor_outbound_http uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_outbound_http, while a change to spin_factor_outbound_http can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_outbound_http uses a module listed above it, which is the healthy direction.
29→19 spin_factor_outbound_http uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_http uses a type in spin_factors.factor.
- The types involved
spin_factor_outbound_http.OutboundHttpFactor→spin_factors.factor.ConfigureAppContextspin_factor_outbound_http.OutboundHttpFactor→spin_factors.factor.Factor
- Direction
- spin_factor_outbound_http uses spin_factors.factor, so a change to spin_factors.factor can break spin_factor_outbound_http, while a change to spin_factor_outbound_http can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factor_outbound_http uses a module listed above it, which is the healthy direction.
29→20 spin_factor_outbound_http uses spin_factor_otel✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_http uses a type in spin_factor_otel.
- The types involved
spin_factor_outbound_http.InstanceHttpHooks→spin_factor_otel.OtelFactorState
- Direction
- spin_factor_outbound_http uses spin_factor_otel, so a change to spin_factor_otel can break spin_factor_outbound_http, while a change to spin_factor_outbound_http can't break spin_factor_otel.
- Position
- Below the diagonal: spin_factor_outbound_http uses a module listed above it, which is the healthy direction.
29→24 spin_factor_outbound_http uses spin_factor_outbound_http.wasi✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_http uses a type in spin_factor_outbound_http.wasi.
- The types involved
spin_factor_outbound_http.AppState→spin_factor_outbound_http.wasi.HttpClientsspin_factor_outbound_http.InstanceHttpHooks→spin_factor_outbound_http.wasi.HttpClients
- Direction
- spin_factor_outbound_http uses spin_factor_outbound_http.wasi, so a change to spin_factor_outbound_http.wasi can break spin_factor_outbound_http, while a change to spin_factor_outbound_http can't break spin_factor_outbound_http.wasi.
- Position
- Below the diagonal: spin_factor_outbound_http uses a module listed above it, which is the healthy direction.
30→3 spin_factor_outbound_networking uses spin_connection_semaphore✕
- Connections
- 3 pairs of types, where a type in spin_factor_outbound_networking uses a type in spin_connection_semaphore.
- The types involved
spin_factor_outbound_networking.AppState→spin_connection_semaphore.ConnectionSemaphorespin_factor_outbound_networking.AppState→spin_connection_semaphore.LimitedSemaphorespin_factor_outbound_networking.spin_factor_outbound_networking$module→spin_connection_semaphore.ConnectionSemaphore
- Direction
- spin_factor_outbound_networking uses spin_connection_semaphore, so a change to spin_connection_semaphore can break spin_factor_outbound_networking, while a change to spin_factor_outbound_networking can't break spin_connection_semaphore.
- Position
- Below the diagonal: spin_factor_outbound_networking uses a module listed above it, which is the healthy direction.
30→8 spin_factor_outbound_networking uses spin_outbound_networking_config.allowed_hosts✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_networking uses a type in spin_outbound_networking_config.allowed_hosts.
- The types involved
spin_factor_outbound_networking.InstanceBuilder→spin_outbound_networking_config.allowed_hosts.OutboundAllowedHostsspin_factor_outbound_networking.spin_factor_outbound_networking$module→spin_outbound_networking_config.allowed_hosts.OutboundAllowedHosts
- Direction
- spin_factor_outbound_networking uses spin_outbound_networking_config.allowed_hosts, so a change to spin_outbound_networking_config.allowed_hosts can break spin_factor_outbound_networking, while a change to spin_factor_outbound_networking can't break spin_outbound_networking_config.allowed_hosts.
- Position
- Below the diagonal: spin_factor_outbound_networking uses a module listed above it, which is the healthy direction.
30→18 spin_factor_outbound_networking uses spin_factors.prepare✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_networking uses a type in spin_factors.prepare.
- The types involved
spin_factor_outbound_networking.InstanceBuilder→spin_factors.prepare.FactorInstanceBuilderspin_factor_outbound_networking.OutboundNetworkingFactor→spin_factors.prepare.PrepareContext
- Direction
- spin_factor_outbound_networking uses spin_factors.prepare, so a change to spin_factors.prepare can break spin_factor_outbound_networking, while a change to spin_factor_outbound_networking can't break spin_factors.prepare.
- Position
- Below the diagonal: spin_factor_outbound_networking uses a module listed above it, which is the healthy direction.
30→19 spin_factor_outbound_networking uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factor_outbound_networking uses a type in spin_factors.factor.
- The types involved
spin_factor_outbound_networking.OutboundNetworkingFactor→spin_factors.factor.ConfigureAppContextspin_factor_outbound_networking.OutboundNetworkingFactor→spin_factors.factor.Factor
- Direction
- spin_factor_outbound_networking uses spin_factors.factor, so a change to spin_factors.factor can break spin_factor_outbound_networking, while a change to spin_factor_outbound_networking can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factor_outbound_networking uses a module listed above it, which is the healthy direction.
30→22 spin_factor_outbound_networking uses spin_factor_key_value✕
- Connections
- 1 pair of types, where a type in spin_factor_outbound_networking uses a type in spin_factor_key_value.
- The types involved
spin_factor_outbound_networking.spin_factor_outbound_networking$module→spin_factor_key_value.AppState
- Direction
- spin_factor_outbound_networking uses spin_factor_key_value, so a change to spin_factor_key_value can break spin_factor_outbound_networking, while a change to spin_factor_outbound_networking can't break spin_factor_key_value.
- Position
- Below the diagonal: spin_factor_outbound_networking uses a module listed above it, which is the healthy direction.
31→5 spin_factors_executor uses spin_factor_key_value.runtime_config✕
- Connections
- 1 pair of types, where a type in spin_factors_executor uses a type in spin_factor_key_value.runtime_config.
- The types involved
spin_factors_executor.FactorsExecutor→spin_factor_key_value.runtime_config.RuntimeConfig
- Direction
- spin_factors_executor uses spin_factor_key_value.runtime_config, so a change to spin_factor_key_value.runtime_config can break spin_factors_executor, while a change to spin_factors_executor can't break spin_factor_key_value.runtime_config.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
31→10 spin_factors_executor uses spin_core.store✕
- Connections
- 2 pairs of types, where a type in spin_factors_executor uses a type in spin_core.store.
- The types involved
spin_factors_executor.FactorsInstanceBuilder→spin_core.store.StoreBuilderspin_factors_executor.InstanceState→spin_core.store.AsState
- Direction
- spin_factors_executor uses spin_core.store, so a change to spin_core.store can break spin_factors_executor, while a change to spin_factors_executor can't break spin_core.store.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
31→14 spin_factors_executor uses spin_locked_app.locked✕
- Connections
- 1 pair of types, where a type in spin_factors_executor uses a type in spin_locked_app.locked.
- The types involved
spin_factors_executor.TriggerDependency→spin_locked_app.locked.LockedComponentDependency
- Direction
- spin_factors_executor uses spin_locked_app.locked, so a change to spin_locked_app.locked can break spin_factors_executor, while a change to spin_factors_executor can't break spin_locked_app.locked.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
31→15 spin_factors_executor uses spin_manifest.schema.v2.component✕
- Connections
- 1 pair of types, where a type in spin_factors_executor uses a type in spin_manifest.schema.v2.component.
- The types involved
spin_factors_executor.FactorsInstanceBuilder→spin_manifest.schema.v2.component.Component
- Direction
- spin_factors_executor uses spin_manifest.schema.v2.component, so a change to spin_manifest.schema.v2.component can break spin_factors_executor, while a change to spin_factors_executor can't break spin_manifest.schema.v2.component.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
31→16 spin_factors_executor uses spin_app✕
- Connections
- 4 pairs of types, where a type in spin_factors_executor uses a type in spin_app.
- The types involved
spin_factors_executor.ComponentLoader→spin_app.AppComponentspin_factors_executor.FactorsExecutor→spin_app.Appspin_factors_executor.FactorsExecutorApp→spin_app.Appspin_factors_executor.FactorsInstanceBuilder→spin_app.AppComponent
- Direction
- spin_factors_executor uses spin_app, so a change to spin_app can break spin_factors_executor, while a change to spin_factors_executor can't break spin_app.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
31→17 spin_factors_executor uses spin_core✕
- Connections
- 5 pairs of types, where a type in spin_factors_executor uses a type in spin_core.
- The types involved
spin_factors_executor.ComponentLoader→spin_core.Enginespin_factors_executor.FactorsExecutor→spin_core.Enginespin_factors_executor.FactorsExecutor→spin_core.EngineBuilderspin_factors_executor.FactorsExecutorApp→spin_core.Enginespin_factors_executor.InstanceState→spin_core.State
- Direction
- spin_factors_executor uses spin_core, so a change to spin_core can break spin_factors_executor, while a change to spin_factors_executor can't break spin_core.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
31→19 spin_factors_executor uses spin_factors.factor✕
- Connections
- 2 pairs of types, where a type in spin_factors_executor uses a type in spin_factors.factor.
- The types involved
spin_factors_executor.ExecutorHooks→spin_factors.factor.ConfiguredAppspin_factors_executor.FactorsExecutorApp→spin_factors.factor.ConfiguredApp
- Direction
- spin_factors_executor uses spin_factors.factor, so a change to spin_factors.factor can break spin_factors_executor, while a change to spin_factors_executor can't break spin_factors.factor.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
31→22 spin_factors_executor uses spin_factor_key_value✕
- Connections
- 1 pair of types, where a type in spin_factors_executor uses a type in spin_factor_key_value.
- The types involved
spin_factors_executor.FactorsInstanceBuilder→spin_factor_key_value.InstanceBuilder
- Direction
- spin_factors_executor uses spin_factor_key_value, so a change to spin_factor_key_value can break spin_factors_executor, while a change to spin_factors_executor can't break spin_factor_key_value.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
31→23 spin_factors_executor uses spin_factor_llm✕
- Connections
- 1 pair of types, where a type in spin_factors_executor uses a type in spin_factor_llm.
- The types involved
spin_factors_executor.CpuTimeCallHook→spin_factor_llm.InstanceState
- Direction
- spin_factors_executor uses spin_factor_llm, so a change to spin_factor_llm can break spin_factors_executor, while a change to spin_factors_executor can't break spin_factor_llm.
- Position
- Below the diagonal: spin_factors_executor uses a module listed above it, which is the healthy direction.
32→9 spin_manifest.schema.v2.trigger uses spin_resource_table✕
- Connections
- 1 pair of types, where a type in spin_manifest.schema.v2.trigger uses a type in spin_resource_table.
- The types involved
spin_manifest.schema.v2.trigger.Trigger→spin_resource_table.Table
- Direction
- spin_manifest.schema.v2.trigger uses spin_resource_table, so a change to spin_resource_table can break spin_manifest.schema.v2.trigger, while a change to spin_manifest.schema.v2.trigger can't break spin_resource_table.
- Position
- Below the diagonal: spin_manifest.schema.v2.trigger uses a module listed above it, which is the healthy direction.
32→31 spin_manifest.schema.v2.trigger uses spin_factors_executor✕
- Connections
- 1 pair of types, where a type in spin_manifest.schema.v2.trigger uses a type in spin_factors_executor.
- The types involved
spin_manifest.schema.v2.trigger.TriggerDependencies→spin_factors_executor.TriggerDependency
- Direction
- spin_manifest.schema.v2.trigger uses spin_factors_executor, so a change to spin_factors_executor can break spin_manifest.schema.v2.trigger, while a change to spin_manifest.schema.v2.trigger can't break spin_factors_executor.
- Position
- Below the diagonal: spin_manifest.schema.v2.trigger uses a module listed above it, which is the healthy direction.
33→20 spin_runtime_factors uses spin_factor_otel✕
- Connections
- 1 pair of types, where a type in spin_runtime_factors uses a type in spin_factor_otel.
- The types involved
spin_runtime_factors.TriggerFactors→spin_factor_otel.OtelFactor
- Direction
- spin_runtime_factors uses spin_factor_otel, so a change to spin_factor_otel can break spin_runtime_factors, while a change to spin_runtime_factors can't break spin_factor_otel.
- Position
- Below the diagonal: spin_runtime_factors uses a module listed above it, which is the healthy direction.
33→21 spin_runtime_factors uses spin_factor_sqlite✕
- Connections
- 1 pair of types, where a type in spin_runtime_factors uses a type in spin_factor_sqlite.
- The types involved
spin_runtime_factors.TriggerFactors→spin_factor_sqlite.SqliteFactor
- Direction
- spin_runtime_factors uses spin_factor_sqlite, so a change to spin_factor_sqlite can break spin_runtime_factors, while a change to spin_runtime_factors can't break spin_factor_sqlite.
- Position
- Below the diagonal: spin_runtime_factors uses a module listed above it, which is the healthy direction.
33→22 spin_runtime_factors uses spin_factor_key_value✕
- Connections
- 1 pair of types, where a type in spin_runtime_factors uses a type in spin_factor_key_value.
- The types involved
spin_runtime_factors.TriggerFactors→spin_factor_key_value.KeyValueFactor
- Direction
- spin_runtime_factors uses spin_factor_key_value, so a change to spin_factor_key_value can break spin_runtime_factors, while a change to spin_runtime_factors can't break spin_factor_key_value.
- Position
- Below the diagonal: spin_runtime_factors uses a module listed above it, which is the healthy direction.
33→23 spin_runtime_factors uses spin_factor_llm✕
- Connections
- 1 pair of types, where a type in spin_runtime_factors uses a type in spin_factor_llm.
- The types involved
spin_runtime_factors.TriggerFactors→spin_factor_llm.LlmFactor
- Direction
- spin_runtime_factors uses spin_factor_llm, so a change to spin_factor_llm can break spin_runtime_factors, while a change to spin_runtime_factors can't break spin_factor_llm.
- Position
- Below the diagonal: spin_runtime_factors uses a module listed above it, which is the healthy direction.
33→26 spin_runtime_factors uses spin_factor_outbound_mysql✕
- Connections
- 1 pair of types, where a type in spin_runtime_factors uses a type in spin_factor_outbound_mysql.
- The types involved
spin_runtime_factors.TriggerFactors→spin_factor_outbound_mysql.OutboundMysqlFactor
- Direction
- spin_runtime_factors uses spin_factor_outbound_mysql, so a change to spin_factor_outbound_mysql can break spin_runtime_factors, while a change to spin_runtime_factors can't break spin_factor_outbound_mysql.
- Position
- Below the diagonal: spin_runtime_factors uses a module listed above it, which is the healthy direction.
33→27 spin_runtime_factors uses spin_factor_outbound_pg✕
- Connections
- 1 pair of types, where a type in spin_runtime_factors uses a type in spin_factor_outbound_pg.
- The types involved
spin_runtime_factors.TriggerFactors→spin_factor_outbound_pg.OutboundPgFactor
- Direction
- spin_runtime_factors uses spin_factor_outbound_pg, so a change to spin_factor_outbound_pg can break spin_runtime_factors, while a change to spin_runtime_factors can't break spin_factor_outbound_pg.
- Position
- Below the diagonal: spin_runtime_factors uses a module listed above it, which is the healthy direction.
33→29 spin_runtime_factors uses spin_factor_outbound_http✕
- Connections
- 1 pair of types, where a type in spin_runtime_factors uses a type in spin_factor_outbound_http.
- The types involved
spin_runtime_factors.TriggerFactors→spin_factor_outbound_http.OutboundHttpFactor
- Direction
- spin_runtime_factors uses spin_factor_outbound_http, so a change to spin_factor_outbound_http can break spin_runtime_factors, while a change to spin_runtime_factors can't break spin_factor_outbound_http.
- Position
- Below the diagonal: spin_runtime_factors uses a module listed above it, which is the healthy direction.
33→30 spin_runtime_factors uses spin_factor_outbound_networking✕
- Connections
- 2 pairs of types, where a type in spin_runtime_factors uses a type in spin_factor_outbound_networking.
- The types involved
spin_runtime_factors.TriggerFactors→spin_factor_outbound_networking.OutboundNetworkingFactorspin_runtime_factors.spin_runtime_factors$module→spin_factor_outbound_networking.OutboundNetworkingFactor
- Direction
- spin_runtime_factors uses spin_factor_outbound_networking, so a change to spin_factor_outbound_networking can break spin_runtime_factors, while a change to spin_runtime_factors can't break spin_factor_outbound_networking.
- Position
- Below the diagonal: spin_runtime_factors uses a module listed above it, which is the healthy direction.
34→1 spin_cli.commands.deps uses spin_capabilities✕
- Connections
- 2 pairs of types, where a type in spin_cli.commands.deps uses a type in spin_capabilities.
- The types involved
spin_cli.commands.deps.Inheritance→spin_capabilities.InheritConfigurationspin_cli.commands.deps.deps$module→spin_capabilities.InheritConfiguration
- Direction
- spin_cli.commands.deps uses spin_capabilities, so a change to spin_capabilities can break spin_cli.commands.deps, while a change to spin_cli.commands.deps can't break spin_capabilities.
- Position
- Below the diagonal: spin_cli.commands.deps uses a module listed above it, which is the healthy direction.
34→7 spin_cli.commands.deps uses spin_manifest.schema.v2✕
- Connections
- 1 pair of types, where a type in spin_cli.commands.deps uses a type in spin_manifest.schema.v2.
- The types involved
spin_cli.commands.deps.deps$module→spin_manifest.schema.v2.AppManifest
- Direction
- spin_cli.commands.deps uses spin_manifest.schema.v2, so a change to spin_manifest.schema.v2 can break spin_cli.commands.deps, while a change to spin_cli.commands.deps can't break spin_manifest.schema.v2.
- Position
- Below the diagonal: spin_cli.commands.deps uses a module listed above it, which is the healthy direction.
34→15 spin_cli.commands.deps uses spin_manifest.schema.v2.component✕
- Connections
- 1 pair of types, where a type in spin_cli.commands.deps uses a type in spin_manifest.schema.v2.component.
- The types involved
spin_cli.commands.deps.deps$module→spin_manifest.schema.v2.component.Component
- Direction
- spin_cli.commands.deps uses spin_manifest.schema.v2.component, so a change to spin_manifest.schema.v2.component can break spin_cli.commands.deps, while a change to spin_cli.commands.deps can't break spin_manifest.schema.v2.component.
- Position
- Below the diagonal: spin_cli.commands.deps uses a module listed above it, which is the healthy direction.
34→31 spin_cli.commands.deps uses spin_factors_executor✕
- Connections
- 1 pair of types, where a type in spin_cli.commands.deps uses a type in spin_factors_executor.
- The types involved
spin_cli.commands.deps.deps$module→spin_factors_executor.TriggerDependency
- Direction
- spin_cli.commands.deps uses spin_factors_executor, so a change to spin_factors_executor can break spin_cli.commands.deps, while a change to spin_cli.commands.deps can't break spin_factors_executor.
- Position
- Below the diagonal: spin_cli.commands.deps uses a module listed above it, which is the healthy direction.
34→32 spin_cli.commands.deps uses spin_manifest.schema.v2.trigger✕
- Connections
- 1 pair of types, where a type in spin_cli.commands.deps uses a type in spin_manifest.schema.v2.trigger.
- The types involved
spin_cli.commands.deps.deps$module→spin_manifest.schema.v2.trigger.Trigger
- Direction
- spin_cli.commands.deps uses spin_manifest.schema.v2.trigger, so a change to spin_manifest.schema.v2.trigger can break spin_cli.commands.deps, while a change to spin_cli.commands.deps can't break spin_manifest.schema.v2.trigger.
- Position
- Below the diagonal: spin_cli.commands.deps uses a module listed above it, which is the healthy direction.
35→1 spin_loader.local uses spin_capabilities✕
- Connections
- 1 pair of types, where a type in spin_loader.local uses a type in spin_capabilities.
- The types involved
spin_loader.local.local$module→spin_capabilities.InheritConfiguration
- Direction
- spin_loader.local uses spin_capabilities, so a change to spin_capabilities can break spin_loader.local, while a change to spin_loader.local can't break spin_capabilities.
- Position
- Below the diagonal: spin_loader.local uses a module listed above it, which is the healthy direction.
35→4 spin_loader.local uses spin_expressions✕
- Connections
- 3 pairs of types, where a type in spin_loader.local uses a type in spin_expressions.
- The types involved
spin_loader.local.LocalLoader→spin_expressions.Errorspin_loader.local.LocalLoader→spin_expressions.Resolverspin_loader.local.local$module→spin_expressions.Error
- Direction
- spin_loader.local uses spin_expressions, so a change to spin_expressions can break spin_loader.local, while a change to spin_loader.local can't break spin_expressions.
- Position
- Below the diagonal: spin_loader.local uses a module listed above it, which is the healthy direction.
35→7 spin_loader.local uses spin_manifest.schema.v2✕
- Connections
- 1 pair of types, where a type in spin_loader.local uses a type in spin_manifest.schema.v2.
- The types involved
spin_loader.local.LocalLoader→spin_manifest.schema.v2.AppManifest
- Direction
- spin_loader.local uses spin_manifest.schema.v2, so a change to spin_manifest.schema.v2 can break spin_loader.local, while a change to spin_loader.local can't break spin_manifest.schema.v2.
- Position
- Below the diagonal: spin_loader.local uses a module listed above it, which is the healthy direction.
35→14 spin_loader.local uses spin_locked_app.locked✕
- Connections
- 1 pair of types, where a type in spin_loader.local uses a type in spin_locked_app.locked.
- The types involved
spin_loader.local.local$module→spin_locked_app.locked.Variable
- Direction
- spin_loader.local uses spin_locked_app.locked, so a change to spin_locked_app.locked can break spin_loader.local, while a change to spin_loader.local can't break spin_locked_app.locked.
- Position
- Below the diagonal: spin_loader.local uses a module listed above it, which is the healthy direction.
35→15 spin_loader.local uses spin_manifest.schema.v2.component✕
- Connections
- 3 pairs of types, where a type in spin_loader.local uses a type in spin_manifest.schema.v2.component.
- The types involved
spin_loader.local.LocalLoader→spin_manifest.schema.v2.component.Componentspin_loader.local.LocalLoader→spin_manifest.schema.v2.component.ComponentDependenciesspin_loader.local.local$module→spin_manifest.schema.v2.component.Component
- Direction
- spin_loader.local uses spin_manifest.schema.v2.component, so a change to spin_manifest.schema.v2.component can break spin_loader.local, while a change to spin_loader.local can't break spin_manifest.schema.v2.component.
- Position
- Below the diagonal: spin_loader.local uses a module listed above it, which is the healthy direction.
35→31 spin_loader.local uses spin_factors_executor✕
- Connections
- 2 pairs of types, where a type in spin_loader.local uses a type in spin_factors_executor.
- The types involved
spin_loader.local.LocalLoader→spin_factors_executor.TriggerDependencyspin_loader.local.WasmLoader→spin_factors_executor.TriggerDependency
- Direction
- spin_loader.local uses spin_factors_executor, so a change to spin_factors_executor can break spin_loader.local, while a change to spin_loader.local can't break spin_factors_executor.
- Position
- Below the diagonal: spin_loader.local uses a module listed above it, which is the healthy direction.
35→32 spin_loader.local uses spin_manifest.schema.v2.trigger✕
- Connections
- 1 pair of types, where a type in spin_loader.local uses a type in spin_manifest.schema.v2.trigger.
- The types involved
spin_loader.local.LocalLoader→spin_manifest.schema.v2.trigger.Trigger
- Direction
- spin_loader.local uses spin_manifest.schema.v2.trigger, so a change to spin_manifest.schema.v2.trigger can break spin_loader.local, while a change to spin_loader.local can't break spin_manifest.schema.v2.trigger.
- Position
- Below the diagonal: spin_loader.local uses a module listed above it, which is the healthy direction.
35→37 spin_loader.local uses spin_environments.loader part of a loop✕
- Connections
- 2 pairs of types, where a type in spin_loader.local uses a type in spin_environments.loader.
- The types involved
spin_loader.local.LocalLoader→spin_environments.loader.ComponentSourcespin_loader.local.WasmLoader→spin_environments.loader.ComponentSource
- Direction
- spin_loader.local uses spin_environments.loader, so a change to spin_environments.loader can break spin_loader.local, while a change to spin_loader.local can't break spin_environments.loader.
- 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.
36→4 spin_trigger_http uses spin_expressions✕
- Connections
- 1 pair of types, where a type in spin_trigger_http uses a type in spin_expressions.
- The types involved
spin_trigger_http.spin_trigger_http$module→spin_expressions.Error
- Direction
- spin_trigger_http uses spin_expressions, so a change to spin_expressions can break spin_trigger_http, while a change to spin_trigger_http can't break spin_expressions.
- Position
- Below the diagonal: spin_trigger_http uses a module listed above it, which is the healthy direction.
36→16 spin_trigger_http uses spin_app✕
- Connections
- 1 pair of types, where a type in spin_trigger_http uses a type in spin_app.
- The types involved
spin_trigger_http.HttpTrigger→spin_app.App
- Direction
- spin_trigger_http uses spin_app, so a change to spin_app can break spin_trigger_http, while a change to spin_trigger_http can't break spin_app.
- Position
- Below the diagonal: spin_trigger_http uses a module listed above it, which is the healthy direction.
36→32 spin_trigger_http uses spin_manifest.schema.v2.trigger✕
- Connections
- 1 pair of types, where a type in spin_trigger_http uses a type in spin_manifest.schema.v2.trigger.
- The types involved
spin_trigger_http.HttpTrigger→spin_manifest.schema.v2.trigger.Trigger
- Direction
- spin_trigger_http uses spin_manifest.schema.v2.trigger, so a change to spin_manifest.schema.v2.trigger can break spin_trigger_http, while a change to spin_trigger_http can't break spin_manifest.schema.v2.trigger.
- Position
- Below the diagonal: spin_trigger_http uses a module listed above it, which is the healthy direction.
37→1 spin_environments.loader uses spin_capabilities✕
- Connections
- 1 pair of types, where a type in spin_environments.loader uses a type in spin_capabilities.
- The types involved
spin_environments.loader.WrappedComponentDependency→spin_capabilities.InheritConfiguration
- Direction
- spin_environments.loader uses spin_capabilities, so a change to spin_capabilities can break spin_environments.loader, while a change to spin_environments.loader can't break spin_capabilities.
- Position
- Below the diagonal: spin_environments.loader uses a module listed above it, which is the healthy direction.
37→7 spin_environments.loader uses spin_manifest.schema.v2✕
- Connections
- 1 pair of types, where a type in spin_environments.loader uses a type in spin_manifest.schema.v2.
- The types involved
spin_environments.loader.ApplicationToValidate→spin_manifest.schema.v2.AppManifest
- Direction
- spin_environments.loader uses spin_manifest.schema.v2, so a change to spin_manifest.schema.v2 can break spin_environments.loader, while a change to spin_environments.loader can't break spin_manifest.schema.v2.
- Position
- Below the diagonal: spin_environments.loader uses a module listed above it, which is the healthy direction.
37→15 spin_environments.loader uses spin_manifest.schema.v2.component✕
- Connections
- 3 pairs of types, where a type in spin_environments.loader uses a type in spin_manifest.schema.v2.component.
- The types involved
spin_environments.loader.ComponentSourceLoader→spin_manifest.schema.v2.component.Componentspin_environments.loader.ComponentToValidate→spin_manifest.schema.v2.component.Componentspin_environments.loader.WrappedComponentDependencies→spin_manifest.schema.v2.component.ComponentDependencies
- Direction
- spin_environments.loader uses spin_manifest.schema.v2.component, so a change to spin_manifest.schema.v2.component can break spin_environments.loader, while a change to spin_environments.loader can't break spin_manifest.schema.v2.component.
- Position
- Below the diagonal: spin_environments.loader uses a module listed above it, which is the healthy direction.
37→32 spin_environments.loader uses spin_manifest.schema.v2.trigger✕
- Connections
- 1 pair of types, where a type in spin_environments.loader uses a type in spin_manifest.schema.v2.trigger.
- The types involved
spin_environments.loader.ApplicationToValidate→spin_manifest.schema.v2.trigger.Trigger
- Direction
- spin_environments.loader uses spin_manifest.schema.v2.trigger, so a change to spin_manifest.schema.v2.trigger can break spin_environments.loader, while a change to spin_environments.loader can't break spin_manifest.schema.v2.trigger.
- Position
- Below the diagonal: spin_environments.loader uses a module listed above it, which is the healthy direction.
37→35 spin_environments.loader uses spin_loader.local✕
- Connections
- 2 pairs of types, where a type in spin_environments.loader uses a type in spin_loader.local.
- The types involved
spin_environments.loader.ApplicationToValidate→spin_loader.local.WasmLoaderspin_environments.loader.ComponentSourceLoader→spin_loader.local.WasmLoader
- Direction
- spin_environments.loader uses spin_loader.local, so a change to spin_loader.local can break spin_environments.loader, while a change to spin_environments.loader can't break spin_loader.local.
- Position
- Below the diagonal: spin_environments.loader uses a module listed above it, which is the healthy direction.
38→5 spin_trigger.cli uses spin_factor_key_value.runtime_config✕
- Connections
- 1 pair of types, where a type in spin_trigger.cli uses a type in spin_factor_key_value.runtime_config.
- The types involved
spin_trigger.cli.RuntimeFactorsBuilder→spin_factor_key_value.runtime_config.RuntimeConfig
- Direction
- spin_trigger.cli uses spin_factor_key_value.runtime_config, so a change to spin_factor_key_value.runtime_config can break spin_trigger.cli, while a change to spin_trigger.cli can't break spin_factor_key_value.runtime_config.
- Position
- Below the diagonal: spin_trigger.cli uses a module listed above it, which is the healthy direction.
38→16 spin_trigger.cli uses spin_app✕
- Connections
- 1 pair of types, where a type in spin_trigger.cli uses a type in spin_app.
- The types involved
spin_trigger.cli.TriggerAppBuilder→spin_app.App
- Direction
- spin_trigger.cli uses spin_app, so a change to spin_app can break spin_trigger.cli, while a change to spin_trigger.cli can't break spin_app.
- Position
- Below the diagonal: spin_trigger.cli uses a module listed above it, which is the healthy direction.
38→31 spin_trigger.cli uses spin_factors_executor✕
- Connections
- 1 pair of types, where a type in spin_trigger.cli uses a type in spin_factors_executor.
- The types involved
spin_trigger.cli.RuntimeFactorsBuilder→spin_factors_executor.FactorsExecutor
- Direction
- spin_trigger.cli uses spin_factors_executor, so a change to spin_factors_executor can break spin_trigger.cli, while a change to spin_trigger.cli can't break spin_factors_executor.
- Position
- Below the diagonal: spin_trigger.cli uses a module listed above it, which is the healthy direction.
38→36 spin_trigger.cli uses spin_trigger_http✕
- Connections
- 3 pairs of types, where a type in spin_trigger.cli uses a type in spin_trigger_http.
- The types involved
spin_trigger.cli.FactorsTriggerCommand→spin_trigger_http.CliArgsspin_trigger.cli.RuntimeFactorsBuilder→spin_trigger_http.CliArgsspin_trigger.cli.TriggerAppBuilder→spin_trigger_http.CliArgs
- Direction
- spin_trigger.cli uses spin_trigger_http, so a change to spin_trigger_http can break spin_trigger.cli, while a change to spin_trigger.cli can't break spin_trigger_http.
- Position
- Below the diagonal: spin_trigger.cli uses a module listed above it, which is the healthy direction.
39→6 spin_trigger_http.server uses spin_http_routes✕
- Connections
- 3 pairs of types, where a type in spin_trigger_http.server uses a type in spin_http_routes.
- The types involved
spin_trigger_http.server.HttpServer→spin_http_routes.RouteMatchspin_trigger_http.server.HttpServer→spin_http_routes.Routerspin_trigger_http.server.HttpServer→spin_http_routes.TriggerLookupKey
- Direction
- spin_trigger_http.server uses spin_http_routes, so a change to spin_http_routes can break spin_trigger_http.server, while a change to spin_trigger_http.server can't break spin_http_routes.
- Position
- Below the diagonal: spin_trigger_http.server uses a module listed above it, which is the healthy direction.
39→10 spin_trigger_http.server uses spin_core.store✕
- Connections
- 2 pairs of types, where a type in spin_trigger_http.server uses a type in spin_core.store.
- The types involved
spin_trigger_http.server.HttpWorkerState→spin_core.store.Storespin_trigger_http.server.server$module→spin_core.store.Store
- Direction
- spin_trigger_http.server uses spin_core.store, so a change to spin_core.store can break spin_trigger_http.server, while a change to spin_trigger_http.server can't break spin_core.store.
- Position
- Below the diagonal: spin_trigger_http.server uses a module listed above it, which is the healthy direction.
39→36 spin_trigger_http.server uses spin_trigger_http✕
- Connections
- 4 pairs of types, where a type in spin_trigger_http.server uses a type in spin_trigger_http.
- The types involved
spin_trigger_http.server.HttpHandlerState→spin_trigger_http.InstanceReuseConfigspin_trigger_http.server.HttpServer→spin_trigger_http.InstanceReuseConfigspin_trigger_http.server.HttpServer→spin_trigger_http.NotFoundRouteKindspin_trigger_http.server.HttpServer→spin_trigger_http.OutputFormat
- Direction
- spin_trigger_http.server uses spin_trigger_http, so a change to spin_trigger_http can break spin_trigger_http.server, while a change to spin_trigger_http.server can't break spin_trigger_http.
- Position
- Below the diagonal: spin_trigger_http.server uses a module listed above it, which is the healthy direction.
40→4 spin_build.manifest uses spin_expressions✕
- Connections
- 1 pair of types, where a type in spin_build.manifest uses a type in spin_expressions.
- The types involved
spin_build.manifest.ManifestBuildInfo→spin_expressions.Error
- Direction
- spin_build.manifest uses spin_expressions, so a change to spin_expressions can break spin_build.manifest, while a change to spin_build.manifest can't break spin_expressions.
- Position
- Below the diagonal: spin_build.manifest uses a module listed above it, which is the healthy direction.
40→7 spin_build.manifest uses spin_manifest.schema.v2✕
- Connections
- 2 pairs of types, where a type in spin_build.manifest uses a type in spin_manifest.schema.v2.
- The types involved
spin_build.manifest.ManifestBuildInfo→spin_manifest.schema.v2.AppManifestspin_build.manifest.manifest$module→spin_manifest.schema.v2.AppManifest
- Direction
- spin_build.manifest uses spin_manifest.schema.v2, so a change to spin_manifest.schema.v2 can break spin_build.manifest, while a change to spin_build.manifest can't break spin_manifest.schema.v2.
- Position
- Below the diagonal: spin_build.manifest uses a module listed above it, which is the healthy direction.
40→15 spin_build.manifest uses spin_manifest.schema.v2.component✕
- Connections
- 1 pair of types, where a type in spin_build.manifest uses a type in spin_manifest.schema.v2.component.
- The types involved
spin_build.manifest.ComponentBuildInfo→spin_manifest.schema.v2.component.ComponentDependencies
- Direction
- spin_build.manifest uses spin_manifest.schema.v2.component, so a change to spin_manifest.schema.v2.component can break spin_build.manifest, while a change to spin_build.manifest can't break spin_manifest.schema.v2.component.
- Position
- Below the diagonal: spin_build.manifest uses a module listed above it, which is the healthy direction.
40→37 spin_build.manifest uses spin_environments.loader✕
- Connections
- 1 pair of types, where a type in spin_build.manifest uses a type in spin_environments.loader.
- The types involved
spin_build.manifest.ComponentBuildInfo→spin_environments.loader.ComponentSource
- Direction
- spin_build.manifest uses spin_environments.loader, so a change to spin_environments.loader can break spin_build.manifest, while a change to spin_build.manifest can't break spin_environments.loader.
- Position
- Below the diagonal: spin_build.manifest 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 |
|---|---|---|
| A05:2025 — Injection | 112 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 69 | High / Critical |
| A02:2025 — Security Misconfiguration | 15 | High / Critical |
Roadmap
First, enforce a protect-by-default authorization model using global authentication guards with explicit public opt-outs, and ensure all server responses include essential security headers like Content-Security-Policy and X-Content-Type-Options. Next, resolve the 19 static analysis findings related to secret exposure in CI workflows, prioritizing the deployment and release pipelines. Then, raise the PHP static analysis level to enforce strict nullable type checking and systematically fix the resulting null reference errors rather than silencing them. Finally, replace interpolated log messages with structured logging to improve observability and debugging capabilities.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable. | +6.4 pts | Medium | Access Controls |
| Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response. | +4.4 pts | Medium | Web-Security Posture |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.1 pts | Low | ADR Quality |
| Resolve the 19 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (3). | +2.7 pts | Medium | Static Analysis (SAST) |
| Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive. | +2.6 pts | Medium | Nullable reference types |
| Interpolated log message defeats structured logging | +2.4 pts | Medium | Structured logging |
| Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 71 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. | +1.2 pts | Low | Static Analysis (SAST) |
| Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. | +1.2 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.9 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| crates/factor-key-value/src/host.rs | 5.6 | Mixed | God Classes: FileTooLong: src/host.rs |
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. 63 of 63 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 — 63 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, 461 of 502 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 READ here — but this repository measures it: a coverage step in CI (`cargo tarpaulin`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, 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. 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`) 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.
- D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.rs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- 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 DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — otel-collector Pulling prometheus Pulling loki Pulling grafana Error Get "https://registry-1.docker.io/v2/": Forbidden tempo Error Get "https://registry-1.docker.io/v2/": Forbidden jaeger Error context canceled otel-collector Error context canceled loki Error context canceled prometheus Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: prometheus Pulling jaeger Pulling grafana Pulling prometheus Error Get "https://registry-1.docker.io/v2/": Forbidden tempo Error Get "https://registry-1.docker.io/v2/": Forbidden loki Error context canceled grafana Error context canceled jaeger Error context canceled otel-collector Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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 Go, PHP, Rust, c, zig 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 Go, PHP, Rust, c, zig is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9). Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X12 Unreachable branch — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, 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.
- X13 Undrained process stream — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, 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.
- X17 Uncapped recursion over a caller-supplied document — 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, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, 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.
- X24 Document value interpolated into markup unescaped — 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, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python 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. 70 further occurrence(s) are not listed individually; the score already reflects all 110.
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.
- 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 (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was spin_dependency_wit::extract_wits at 19. A further 5 function(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 spin_world::wasi_otel::log_conversions::severity_from_u8 at 26 — they are counted neither in the figure above nor in this dimension's score. 3 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: crates/world/src/wasi_otel/log_conversions.rs (spin_world::wasi_otel::log_conversions::severity_from_u8 at 26), crates/factor-outbound-pg/src/types.rs (spin_factor_outbound_pg::types::to_sql_parameter at 25), src/lib.rs (SpinApp::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 15 down to 15 or less in Cyclomatic Complexity — start with spin_dependency_wit::extract_wits (cyclomatic 19), FactorsTriggerCommand::run (cyclomatic 18). — 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 9.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- 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
24 function(s) exceeded the cognitive complexity threshold of 15; the worst was spin_dependency_wit::extract_wits at 41.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with spin_dependency_wit::extract_wits (cognitive 41). — Refactoring it lifts Cognitive Complexity from 7.0 to about 7.4/10.
- 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
22 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 14 FileTooLong finding(s) in God Classes — start with wasi_2023_11_10.rs (2), host.rs (2), lib.rs. — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 6 ClassTooLong finding(s) in God Classes — start with lib.rs, sockets.rs, client.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 FunctionTooLong finding(s) in God Classes — start with lib.rs (2). — One of this dimension's main actionable groups (2 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
53 duplicated block group(s) detected. A further 4 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted. 4 of the 57 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 7 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with host.rs (3), wasi_2023_10_18.rs (2), wasi.rs. — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 6 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with wasi_2023_10_18.rs (2), store.rs, logs.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 6 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with host.rs (2), lib.rs, stdio.rs. — One of this dimension's main actionable groups (6 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
64 production modules (Cargo), 0 dependency cycle(s), 6 unstable depended-on module(s). Read from the build's own module declarations; 14 module(s) off the main sequence, with abstractness counted on 60 of the 64 (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).
What to do
- Resolve the 13 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (13 warning-level).
- Resolve the 1 Unstable project spin-build finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Unstable project spin-factor-outbound-pg finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
4 of 173 classes have LCOM4 above 3.
What to do
- Resolve the 4 Low cohesion finding(s) in Cohesion (LCOM4) — start with host.rs, test_key_value.rs, template.rs. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
501 test methods: 379 unit, 122 integration, 0 BDD, 0 e2e. The Rust suite contributes 501 `#[test]` function(s) across 91 file(s) declaring at least one; its unit/integration split is Cargo's own — 15 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.
D12 · Dependency Hygiene
0 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1088 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. A further 8 crate(s) in the closure resolve from git, a path or a private registry and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under Apache-2.0 WITH LLVM-exception, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
23 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/commands/deps.rs. Counted over 211 of the 304 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 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
81 deducted task-comment markers across 67800 LoC (0.1/KLoC) → score 9.8. 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 79 TodoComment finding(s) in Explicit Debt — start with lib.rs (11), template.rs (7), bert.rs (6). — One of this dimension's main actionable groups (79 warning-level).
- Resolve the 2 FixmeComment finding(s) in Explicit Debt — start with integration_test.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. 56 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
0 of 64 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
112 finding(s): 0 critical, 109 high, 3 medium, 0 low. 71 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `crates/oci/src/client.rs` (line 398, line 1010) — 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 6 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 19 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (3). — One of this dimension's main actionable groups (19 issue-level).
- Resolve the 5 REDACTED finding(s) charged to Static Analysis (SAST) — the other 71 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (76 issue-level, 5 of them charged here).
- Resolve the 6 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (6 issue-level).
D30 · Dependency Vulnerabilities
54 finding(s): 0 critical, 4 high, 49 medium, 1 low.
What to do
- Resolve the 16 Medium advisory (unsound) finding(s) in Dependency Vulnerabilities — start with REDACTED (16). — One of this dimension's main actionable groups (16 warning-level).
- Resolve the 14 Medium advisory (unmaintained) finding(s) in Dependency Vulnerabilities — start with REDACTED (14). — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
D31 · IaC & Container Security
15 finding(s): 0 critical, 4 high, 6 medium, 5 low.
What to do
- Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED, REDACTED. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 5 Low IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
D34 · Knowledge Freshness
7 of 211 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is crates/key-value-aws/src/store.rs. Counted over 211 of the 304 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 Orphaned knowledge finding(s) in Knowledge Freshness — start with store.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 6 Orphaned file finding(s) in Knowledge Freshness — start with default.rs, trace_conversions.rs, schemas.rs. — One of this dimension's main actionable groups (6 recommendation-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: lib.rs↔lib.rs 82%; lib.rs↔runtime_factors.rs 79%; spin.rs↔wasi.rs 71%
What to do
- Resolve the 10 Change coupling finding(s) in Change Coupling — start with lib.rs (5), spin.rs, util.rs. — One of this dimension's main actionable groups (10 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 4 platform declaration(s) and 0 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
C2 · Access Controls
- Authorization rules exist but no route guard, auth middleware or handler that refuses a caller was found.
What to do
- Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
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 69 of 74 project(s) that lack one — worth up to 1.9 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
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- Only 37/39 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `templates/http-go/content`, `templates/redis-go/content`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
- `reqwest::get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×5) — crates/doctor/src/rustlang/target.rs:189, crates/doctor/src/rustlang/target.rs:216, crates/environments/src/environment/env_loader.rs:141, …
- `reqwest::Client::builder(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — crates/factor-outbound-http/src/spin.rs:103, crates/telemetry/src/lib.rs:123
- `Client::builder(TokioExecutor` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/factor-outbound-http/src/wasi.rs:549
- `reqwest::ClientBuilder::new(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — crates/key-value-azure/src/store.rs:105
- `Client::new()` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — crates/plugins/src/manager.rs:225, crates/plugins/src/manager.rs:485
What to do
- Give every client a whole-request bound: `reqwest::Client::builder().timeout(Duration::from_secs(10))` (never `reqwest::get` or `Client::new()`, which have none), ureq's `timeout_global`, or wrap the call in `tokio::time::timeout`; add retry with back-off (`reqwest-retry`'s `RetryTransientMiddleware`, `backoff`) around dependencies that fail.
PF3 · Async & latency hygiene
- `run` is async and calls block_on — a blocking call inside async code stalls the executor thread, and every task scheduled on it for as long as it runs. — src/commands/watch.rs:80
What to do
- Rust: `.await` the future instead of `block_on` (on a Tokio runtime thread it panics outright) and use `tokio::time::sleep(..).await` instead of `std::thread::sleep`; where synchronous code must run, move it to `tokio::task::spawn_blocking` or `block_in_place`.
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 set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `HttpServer::new(` (crates/trigger-http/src/lib.rs:388).
- No handler of this repository's Rust server answers 400, 413 or 422 (`StatusCode::BAD_REQUEST`, `HttpResponse::BadRequest()`, `Status::BadRequest`, tonic `Status::invalid_argument`), and nothing declares validation — no `validator`/`garde` derive, no body limit (`DefaultBodyLimit::max`, `RequestBodyLimitLayer`, `JsonConfig::default().limit(…)`, Rocket `Limits`) — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: `HttpServer::new(` (crates/trigger-http/src/lib.rs:388).
What to do
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body) before a handler acts on it: derive `validator::Validate` (or `garde::Validate`) on the request types and reject with `StatusCode::BAD_REQUEST`, and cap bodies with `DefaultBodyLimit::max`/`RequestBodyLimitLayer` or actix's `JsonConfig::default().limit(…)`.
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
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
- `info!` at line 82 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: `info!(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/commands/external.rs:82
- `info!` at line 87 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: `info!(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/commands/external.rs:87
- `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/commands/external.rs:174
- `info!` at line 248 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: `info!(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/commands/external.rs:248
- `info!` at line 286 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: `info!(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/commands/external.rs:286
- `warn!` at line 60 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: `warn!(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/commands/up.rs:60
- `warn!` at line 349 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: `warn!(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/commands/up.rs:349
- `trace!` at line 422 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/commands/up.rs:422
- `warn!` at line 648 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: `warn!(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/commands/up.rs:648
- `debug!` at line 341 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/commands/watch.rs:341
- `debug!` at line 343 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/commands/watch.rs:343
- `warn!` at line 424 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: `warn!(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/commands/watch.rs:424
- `error!` at line 491 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/commands/watch.rs:491
- `error!` at line 52 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/commands/watch/uppificator.rs:52
- `warn!` at line 114 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: `warn!(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/commands/watch/uppificator.rs:114
- `warn!` at line 118 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: `warn!(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/commands/watch/uppificator.rs:118
- `warn!` at line 126 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: `warn!(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/commands/watch/uppificator.rs:126
- `warn!` at line 54 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: `warn!(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/commands/up/app_source.rs:54
- `info!` at line 146 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: `info!(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`. — crates/trigger-redis/src/lib.rs:146
- `info!` at line 157 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: `info!(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`. — crates/trigger-redis/src/lib.rs:157
- `error!` at line 167 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`. (×2) — crates/trigger-redis/src/lib.rs:167, crates/trigger-http/src/wasi.rs:167
- `trace!` at line 189 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`. — crates/trigger-redis/src/lib.rs:189
- `info!` at line 192 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: `info!(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`. — crates/trigger-redis/src/lib.rs:192
- `info!` at line 41 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: `info!(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`. — crates/trigger-http/src/instrument.rs:41
- `warn!` at line 479 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: `warn!(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`. — crates/trigger-http/src/lib.rs:479
- `error!` at line 139 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`. — crates/trigger-http/src/server.rs:139
- `trace!` at line 153 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`. — crates/trigger-http/src/server.rs:153
- `info!` at line 330 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: `info!(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`. — crates/trigger-http/src/server.rs:330
- `error!` at line 461 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`. — crates/trigger-http/src/server.rs:461
- `warn!` at line 584 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: `warn!(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`. — crates/trigger-http/src/server.rs:584
- `info!` at line 630 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: `info!(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`. — crates/trigger-http/src/server.rs:630
- `trace!` at line 32 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`. — crates/trigger-http/src/spin.rs:32
- `trace!` at line 31 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`. — crates/trigger-http/src/wagi.rs:31
- `trace!` at line 41 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`. — crates/trigger-http/src/wasi.rs:41
- `trace!` at line 143 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`. — crates/trigger-http/src/wasi.rs:143
- `error!` at line 234 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`. — crates/trigger-http/src/wasi.rs:234
- `error!` at line 78 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`. — crates/runtime-factors/src/lib.rs:78
- `info!` at line 56 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: `info!(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`. — crates/plugins/src/lookup.rs:56
- `info!` at line 224 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: `info!(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`. — crates/plugins/src/manager.rs:224
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
What to do
- Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 57% | Adequate — gated by X4, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 97% | Exemplary | Strongest area. |
| Maturity | 65% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 63% | Adequate — gated by P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 48% | Weak — gated by D29, D30, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Strong | Solid. |
Unscored — 4 check(s) recorded observations but carry no score
- D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.rs), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 10 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 — 53 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Go 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; this repository's PHP 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 — Not applicable: 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.
- 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 — compose up failed (exit 18 — an image could not be pulled) — otel-collector Pulling prometheus Pulling loki Pulling grafana Error Get "https://registry-1.docker.io/v2/": Forbidden tempo Error Get "https://registry-1.docker.io/v2/": Forbidden jaeger Error context canceled otel-collector Error context canceled loki Error context canceled prometheus Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: prometheus Pulling jaeger Pulling grafana Pulling prometheus Error Get "https://registry-1.docker.io/v2/": Forbidden tempo Error Get "https://registry-1.docker.io/v2/": Forbidden loki Error context canceled grafana Error context canceled jaeger Error context canceled otel-collector Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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.
- 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 — ~10606 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- 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; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ 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 .go, .php, .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.
- 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 only 1 of the 3 signals this lens looks for (27 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — 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
- 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Go code has 37 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X17 Uncapped recursion over a caller-supplied document — 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 PHP and Rust were read, and no request in it can be cancelled by a caller (amphp's HttpClient or connect) — 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.
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 119 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test declared unreliable: disallowed_private_ips_fails crates/factor-outbound-http/tests/factor_test.rs:92
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge crates/key-value-aws/src/store.rs:1
Serious — 302 finding(s)
- TodoComment tests/integration.rs:1225
- TodoComment tests/integration.rs:2036
- TodoComment tests/testing-framework/src/runtimes/in_process_spin.rs:69
- TodoComment tests/testing-framework/src/runtimes/spin_cli.rs:146
- TodoComment tests/testcases/mod.rs:166
- TodoComment tests/testcases/mod.rs:257
- TodoComment src/commands/external.rs:124
- TodoComment src/commands/external.rs:150
- TodoComment src/commands/up.rs:496
- TodoComment src/commands/watch/buildifier.rs:13
- TodoComment crates/world/src/lib.rs:63
- TodoComment crates/trigger-http/src/server.rs:742
- TodoComment crates/trigger-http/src/tls.rs:9
- TodoComment crates/trigger-http/src/wagi.rs:51
- TodoComment crates/routes/src/lib.rs:420
- TodoComment crates/llm-local/src/bert.rs:183
- TodoComment crates/trigger/src/lib.rs:55
- TodoComment crates/templates/src/git.rs:5
- TodoComment crates/templates/src/git.rs:41
- TodoComment crates/plugins/src/git.rs:100
- TodoComment crates/environments/src/environment/catalogue.rs:284
- TodoComment crates/templates/src/renderer.rs:80
- TodoComment crates/templates/src/renderer.rs:94
- TodoComment crates/templates/src/renderer.rs:100
- TodoComment crates/templates/src/run.rs:102
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- FileTooLong: src/lib.rs crates/capabilities/deny-adapter/src/lib.rs
- FileTooLong: src/wasi_2023_10_18.rs crates/factor-wasi/src/wasi_2023_10_18.rs
- FileTooLong: src/wasi_2023_11_10.rs crates/factor-wasi/src/wasi_2023_11_10.rs
- FileTooLong: src/wasi_2026_03_15.rs crates/factor-wasi/src/wasi_2026_03_15.rs
- FileTooLong: src/local.rs crates/loader/src/local.rs
- FileTooLong: commands/plugins.rs src/commands/plugins.rs
- FileTooLong: src/client.rs crates/oci/src/client.rs
- FileTooLong: src/sockets.rs crates/factor-wasi/src/sockets.rs
- FileTooLong: src/host.rs crates/factor-key-value/src/host.rs
- FileTooLong: src/server.rs crates/trigger-http/src/server.rs
- FileTooLong: src/host.rs crates/factor-outbound-redis/src/host.rs
- FileTooLong: src/wasi.rs crates/factor-outbound-http/src/wasi.rs
- FileTooLong: commands/deps.rs src/commands/deps.rs
- FileTooLong: src/wasi_2023_11_10.rs crates/factor-outbound-http/src/wasi_2023_11_10.rs
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: spin-componentize
- Off the main sequence: spin-resource-table
- Off the main sequence: spin-serde
- Off the main sequence: terminal
- Off the main sequence: spin-telemetry
- Off the main sequence: spin-app
- Off the main sequence: spin-core
- Off the main sequence: spin-wasi-async
- Off the main sequence: spin-http-routes
- Off the main sequence: spin-locked-app
- Off the main sequence: spin-connection-semaphore
- Off the main sequence: spin-manifest
- Off the main sequence: spin-factor-otel
- Outbound HTTP without resilience crates/doctor/src/rustlang/target.rs:189
- Outbound HTTP without resilience crates/doctor/src/rustlang/target.rs:216
- Outbound HTTP without resilience crates/environments/src/environment/env_loader.rs:141
- Outbound HTTP without resilience crates/factor-outbound-http/src/spin.rs:103
- Outbound HTTP without resilience crates/factor-outbound-http/src/wasi.rs:549
- Outbound HTTP without resilience crates/key-value-azure/src/store.rs:105
- Outbound HTTP without resilience crates/loader/src/http.rs:45
- Outbound HTTP without resilience crates/plugins/src/manager.rs:225
- Outbound HTTP without resilience crates/plugins/src/manager.rs:485
- Outbound HTTP without resilience crates/telemetry/src/lib.rs:123
- Outbound HTTP without resilience crates/templates/src/source.rs:229
- Change coupling: lib.rs ↔ lib.rs crates/variables-env/src/lib.rs:1
- Change coupling: lib.rs ↔ runtime_factors.rs crates/factors-derive/src/lib.rs:1
- Change coupling: spin.rs ↔ wasi.rs crates/factor-outbound-http/src/spin.rs:1
- Change coupling: util.rs ↔ lib.rs crates/factor-key-value/src/util.rs:1
- Change coupling: lib.rs ↔ lib.rs crates/factors-derive/src/lib.rs:1
- Change coupling: client.rs ↔ conversions.rs crates/factor-outbound-pg/src/client.rs:1
- Change coupling: lib.rs ↔ lib.rs crates/sqlite-inproc/src/lib.rs:1
- Change coupling: lib.rs ↔ lib.rs crates/factor-variables/src/lib.rs:1
- Change coupling: registry.rs ↔ up.rs src/commands/registry.rs:1
- Change coupling: metrics.rs ↔ traces.rs crates/telemetry/src/metrics.rs:1
- Duplicated block (8 lines × 2) crates/factor-llm/src/host.rs:17
- Duplicated block (8 lines × 2) crates/factor-sqlite/src/host.rs:123
- Duplicated block (8 lines × 2) crates/factor-wasi/src/wasi_2023_10_18.rs:1620
- Duplicated block (8 lines × 2) crates/factor-outbound-http/src/wasi.rs:850
- Duplicated block (8 lines × 2) crates/factor-outbound-mqtt/src/host.rs:92
- Duplicated block (8 lines × 2) crates/dependency-wit/src/lib.rs:328
- Duplicated block (8 lines × 2) crates/factor-wasi/src/wasi_2023_10_18.rs:142
- ClassTooLong: Adapter crates/capabilities/deny-adapter/src/lib.rs:61
- ClassTooLong: SpinSocketsView crates/factor-wasi/src/sockets.rs:47
- ClassTooLong: Client crates/oci/src/client.rs:87
- ClassTooLong: LocalLoader crates/loader/src/local.rs:26
- ClassTooLong: HttpServer crates/trigger-http/src/server.rs:78
- ClassTooLong: KeyValueDispatch crates/factor-key-value/src/host.rs:70
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (11 lines × 2) crates/key-value-redis/src/store.rs:82
- Duplicated block (11 lines × 2) crates/telemetry/src/logs.rs:75
- Duplicated block (11 lines × 2) src/commands/templates.rs:173
- Duplicated block (11 lines × 2) crates/factor-wasi/src/wasi_2023_10_18.rs:915
- Duplicated block (11 lines × 2) crates/llm-remote-http/src/open_ai/mod.rs:75
- Duplicated block (11 lines × 2) crates/factor-wasi/src/wasi_2023_10_18.rs:155
- Duplicated block (9 lines × 2) crates/factor-sqlite/src/host.rs:124
- Duplicated block (9 lines × 2) crates/factor-sqlite/src/host.rs:139
- Duplicated block (9 lines × 2) crates/factors-executor/src/lib.rs:298
- Duplicated block (9 lines × 2) crates/trigger/src/cli/stdio.rs:286
- Duplicated block (9 lines × 2) crates/factor-wasi/src/wasi_2023_10_18.rs:1575
- Duplicated block (9 lines × 2) crates/componentize/src/abi_conformance/test_mysql.rs:139
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (13 lines × 2) crates/factor-sqlite/src/host.rs:236
- Duplicated block (13 lines × 2) src/commands/templates.rs:203
- Duplicated block (13 lines × 2) src/commands/plugins.rs:959
- Duplicated block (13 lines × 2) crates/runtime-config/src/lib.rs:263
- Duplicated block (10 lines × 2) crates/factor-outbound-mqtt/src/host.rs:129
- Duplicated block (10 lines × 2) crates/factor-wasi/src/wasi_2023_10_18.rs:1292
- Duplicated block (10 lines × 2) crates/llm-local/src/bert.rs:338
- Duplicated block (10 lines × 2) crates/oci/src/client.rs:323
- Duplicated block (7 lines × 2) crates/factor-outbound-http/src/spin.rs:195
- Duplicated block (7 lines × 2) crates/factor-variables/src/host.rs:106
- Duplicated block (7 lines × 2) crates/oci/src/client.rs:422
- Duplicated block (7 lines × 2) crates/environments/src/environment/catalogue.rs:206
- Low cohesion: KeyValueDispatch (LCOM4 8) crates/factor-key-value/src/host.rs:70
- Low cohesion: KeyValue (LCOM4 6) crates/componentize/src/abi_conformance/test_key_value.rs:26
- Low cohesion: Template (LCOM4 4) crates/templates/src/template.rs:23
- Low cohesion: ComponentStdioWriter (LCOM4 4) crates/trigger/src/cli/stdio.rs:165
- spin_manifest::normalize::normalize_inline_components (cognitive 22) crates/manifest/src/normalize.rs:21
- spin_manifest::normalize::normalize_dependency_component_refs (cognitive 21) crates/manifest/src/normalize.rs:186
- spin_manifest::normalize::normalize_trigger_ids (cognitive 20) crates/manifest/src/normalize.rs:75
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/factor-key-value/src/host.rs:350
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/factor-sqlite/src/host.rs:122
- Members sharing a duplicated core (4 members, 50+ identical tokens) crates/llm-remote-http/src/default.rs:39
- Duplicated block (14 lines × 2) crates/compose/src/lib.rs:134
- Duplicated block (14 lines × 2) crates/factor-outbound-http/src/wasi.rs:265
- Duplicated block (14 lines × 2) crates/componentize/src/abi_conformance/test_mysql.rs:149
- Duplicated block (6 lines × 2) crates/factor-outbound-mysql/src/host.rs:125
- Duplicated block (6 lines × 2) crates/componentize/src/abi_conformance/test_mysql.rs:93
- Duplicated block (6 lines × 2) crates/componentize/src/abi_conformance/test_inbound_http.rs:13
- FixmeComment crates/core/tests/integration_test.rs:45
- FixmeComment crates/core/tests/integration_test.rs:107
- List::print_templates_table (cognitive 17) src/commands/templates.rs:568
- List::print_plain (cognitive 16) src/commands/plugins.rs:817
- FunctionTooLong: spin_factors_derive::expand_factors crates/factors-derive/src/lib.rs:23
- FunctionTooLong: spin_dependency_wit::extract_wits crates/dependency-wit/src/lib.rs:149
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) crates/environments/src/environment/catalogue.rs:234
- Duplicated block (12 lines × 2) src/commands/plugins.rs:1080
- Duplicated block (4–8 lines × 3) crates/expressions/src/lib.rs:73
- Duplicated block (4–8 lines × 3) crates/factor-key-value/src/host.rs:427
- spin_dependency_wit::extract_wits (cyclomatic 19) crates/dependency-wit/src/lib.rs:149
- FactorsTriggerCommand::run (cyclomatic 18) crates/trigger/src/cli.rs:186
- spin_dependency_wit::extract_wits (cognitive 41) crates/dependency-wit/src/lib.rs:149
- ModuleInfo::from_module (cognitive 28) crates/componentize/src/module_info.rs:20
- DoctorCommand::run (cognitive 24) src/commands/doctor.rs:26
- Catalogue::list (cognitive 21) crates/environments/src/environment/catalogue.rs:136
- ComponentStdioWriter::poll_write (cognitive 21) crates/trigger/src/cli/stdio.rs:220
- TemplateNewCommandCore::run (cognitive 21) src/commands/new.rs:148
- Upgrade::repos_to_upgrade (cognitive 20) src/commands/templates.rs:277
- WitBindgenVersion::detect (cognitive 19) crates/componentize/src/lib.rs:75
- UpCommandInner::run (cognitive 19) src/commands/up.rs:174
- spin_cli::commands::new::env_templates_and_plugins (cognitive 19) src/commands/new.rs:295
- spin_build::build (cognitive 18) crates/build/src/lib.rs:23
- Id::try_from (cognitive 18) crates/serde/src/id.rs:35
- Install::print_installed_templates (cognitive 18) src/commands/templates.rs:163
- spin_componentize::retarget_imports_and_get_exports (cognitive 17) crates/componentize/src/lib.rs:184
- PooledTokioClient::query_async (cognitive 17) crates/factor-outbound-pg/src/client.rs:266
- spin_http::wagi::compose_response (cognitive 17) crates/http/src/wagi/mod.rs:217
- ResolvedRuntimeConfig::summarize (cognitive 17) crates/runtime-config/src/lib.rs:58
- FactorsTriggerCommand::run (cognitive 17) crates/trigger/src/cli.rs:186
- Uppificator::run (cognitive 16) src/commands/watch/uppificator.rs:30
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Members sharing a duplicated core (5 members, 50+ identical tokens) crates/key-value-azure/src/store.rs:154
- Duplicated block (25 lines × 2) crates/key-value-aws/src/store.rs:412
- Duplicated block (19 lines × 2) crates/factor-outbound-http/src/spin.rs:206
- Duplicated block (15 lines × 2) crates/environments/src/environment/catalogue.rs:216
- Duplicated block (10–15 lines × 2) crates/factor-outbound-mysql/src/host.rs:307
- Duplicated block (10 lines × 5) crates/key-value-azure/src/store.rs:162
- Duplicated block (9–10 lines × 4) crates/factor-key-value/src/host.rs:351
- Duplicated block (10 lines × 4) crates/llm-remote-http/src/default.rs:40
- Duplicated block (9 lines × 3) crates/environments/src/environment/catalogue.rs:258
- Duplicated block (8 lines × 3) crates/environments/src/loader.rs:237
- Duplicated block (12 lines × 3) crates/factor-outbound-http/src/wasi.rs:823
- Duplicated block (5 lines × 2) crates/factor-outbound-http/src/wasi_2023_10_18.rs:61
- Duplicated block (16 lines × 2) crates/llm-local/src/lib.rs:188
- Unstable project spin-build
- Unstable project spin-factor-outbound-pg
- Unstable project spin-runtime-config
- Unstable project spin-runtime-factors
- Unstable project spin-trigger-http
- Unstable project spin-trigger-redis
- Coverage collected but not gated
- Sync-over-async blocking src/commands/watch.rs:80
Minor — 80 finding(s)
- Interpolated log message defeats structured logging src/commands/external.rs:82
- Interpolated log message defeats structured logging src/commands/external.rs:87
- Interpolated log message defeats structured logging src/commands/external.rs:174
- Interpolated log message defeats structured logging src/commands/external.rs:248
- Interpolated log message defeats structured logging src/commands/external.rs:286
- Interpolated log message defeats structured logging src/commands/up.rs:60
- Interpolated log message defeats structured logging src/commands/up.rs:349
- Interpolated log message defeats structured logging src/commands/up.rs:422
- Interpolated log message defeats structured logging src/commands/up.rs:648
- Interpolated log message defeats structured logging src/commands/watch.rs:341
- Interpolated log message defeats structured logging src/commands/watch.rs:343
- Interpolated log message defeats structured logging src/commands/watch.rs:424
- Interpolated log message defeats structured logging src/commands/watch.rs:491
- Interpolated log message defeats structured logging src/commands/watch/uppificator.rs:52
- Interpolated log message defeats structured logging src/commands/watch/uppificator.rs:114
- Interpolated log message defeats structured logging src/commands/watch/uppificator.rs:118
- Interpolated log message defeats structured logging src/commands/watch/uppificator.rs:126
- Interpolated log message defeats structured logging src/commands/up/app_source.rs:54
- Interpolated log message defeats structured logging crates/trigger-redis/src/lib.rs:146
- Interpolated log message defeats structured logging crates/trigger-redis/src/lib.rs:157
- Interpolated log message defeats structured logging crates/trigger-redis/src/lib.rs:167
- Interpolated log message defeats structured logging crates/trigger-redis/src/lib.rs:189
- Interpolated log message defeats structured logging crates/trigger-redis/src/lib.rs:192
- Interpolated log message defeats structured logging crates/trigger-http/src/instrument.rs:41
- Interpolated log message defeats structured logging crates/trigger-http/src/lib.rs:479
- Silent fallback default on Err crates/environments/src/environment/catalogue.rs:139
- Silent fallback default on Err crates/plugins/src/badger/store.rs:54
- Silent fallback default on Err crates/plugins/src/util.rs:16
- Silent fallback default on Err src/lib.rs:206
- Silent fallback default on Err src/commands/new.rs:587
- Silent fallback default on Err src/commands/new.rs:605
- Silent fallback default on Err src/commands/plugins.rs:1080
- Silent fallback default on Err src/commands/plugins.rs:1102
- Silent fallback default on Err src/commands/plugins.rs:1117
- Silent fallback default on Err src/completions.rs:43
- Orphaned file crates/llm-remote-http/src/default.rs:1
- Orphaned file crates/world/src/wasi_otel/trace_conversions.rs:1
- Orphaned file crates/llm-remote-http/src/open_ai/schemas.rs:1
- Orphaned file crates/llm-remote-http/src/open_ai/mod.rs:1
- Orphaned file crates/factor-otel/src/host.rs:1
- Orphaned file crates/telemetry/src/propagation.rs:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- Off-boarding risk: anonymized user #3
- Thin authorization enforcement
- Further sole-owners (lower concentration)
- No ADRs found
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- No rollback/health safety
- No changelog
- No security response headers detected
- No inbound request validation detected
- Duplicated predicate crates/factor-outbound-http/src/lib.rs:223
- PHP static analysis does not check null everywhere
Minor — 1 finding(s)
- Off the main sequence: spin-common
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-a5b42e95a2c14e4dbf0e1bf8df6c9a7e/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-a5b42e95a2c14e4dbf0e1bf8df6c9a7e/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 . | 112 | 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 . /tmp/codehealth-osv-sbom-3fd658ad0a3d410db8f320ada7a3f4ff | 54 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 15 | 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 | — |
| 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 . /tmp/codehealth-osv-sbom-3fd658ad0a3d410db8f320ada7a3f4ff | 0 | artifacts/raw/osv-scanner.json |