SWIFT ANALYZER / RULE CATALOG
138 rules about whole-program Swift behavior, from state that becomes stale across await to repeated collection work and sensitive data reaching logs.
Rules: 138 · conditions: 141
repository-unused@1.0.0Unused declaration or declaration group. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
architecture.production-used-only-by-tests@1.0.0Production code used only by tests. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
architecture.forbidden-dependency@1.0.0Forbidden dependency or layer bypass. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
api.access-narrowing@1.0.0Excessive API visibility. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
architecture.unused-product-dependency@1.0.0Unused product dependency. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
architecture.undeclared-direct-provider@1.0.0Undeclared direct provider. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
architecture.dependency-cycle@1.0.0Disallowed component cycle. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
api.implementation-type-leakage@1.0.0Implementation type exposed through an API. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
architecture.registration-contract-mismatch@1.0.0Incompatible registration or entry point. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.arch.10@1.0.0Required resource missing from a shipping variant. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.arch.11@1.0.0Parameter unused across its dispatch family. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.arch.12@1.0.0Property is written but never observed. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.arch.13@1.0.0Redundant protocol or conformance. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.arch.14@1.0.0Semantically redundant import. It examines repository-wide reachability, dependencies, resources, and API boundaries. The result remains unknown when the required evidence is incomplete.
concurrency.incompatible-isolation@1.0.0Call crosses incompatible isolation. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
concurrency.unproven-mainactor-entry@1.0.0MainActor entry without a proven context. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
concurrency.detached-task-context-loss@1.0.0Required context lost through detachment. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
concurrency.dispatch-isolation-mismatch@1.0.0Callback runs in an incompatible scheduler context. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.05@1.0.0Invalid isolation assumption. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.06@1.0.0Resource used outside its execution domain. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.07@1.0.0Thread-affine value survives a suspension. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.08@1.0.0Required task-local value or executor preference is lost. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
concurrency.main-actor-blocking@1.0.0Blocking call on a critical executor. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.10@1.0.0Expensive computation on a critical executor. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.11@1.0.0Removable scheduling boundary. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.12@1.0.0Cost amplified by actor crossings. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.13@1.0.0Independent work is unintentionally serialized. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
portfolio.exec.14@1.0.0Custom SerialExecutor violates serialization. It examines isolation, executor, scheduler, and execution-domain relationships. The result remains unknown when the required evidence is incomplete.
concurrency.state-freshness-across-suspension@1.0.0State check becomes stale across await. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.actor-invariant-exposure@1.0.0Broken invariant is observable during suspension. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.obsolete-generation-commit@1.0.0Stale result overwrites a newer generation. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
portfolio.async.04@1.0.0Operation requiring single-flight starts more than once. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
portfolio.async.05@1.0.0Code depends on an unspecified actor-task order. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.lost-continuation-resume@1.0.0Continuation can finish without resume. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.double-continuation-resume@1.0.0Continuation can resume more than once. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.cancel-register-start-race@1.0.0Cancellation is lost between registration and start. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.cancelled-forbidden-effect@1.0.0Forbidden commit after cancellation or rejection. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.unresponsive-cancellation-work@1.0.0Work does not honor its cancellation contract. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.timeout-sibling-outlives-race@1.0.0Timeout or first result does not finish its scope. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.task-outlives-scope@1.0.0Task outlives its required lifecycle scope. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
portfolio.async.13@1.0.0Required task result or error is lost. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.guard-held-across-suspension@1.0.0Guard is held across a disallowed await. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
concurrency.sole-producer-self-block@1.0.0Wait cycle blocks required producers. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
portfolio.async.16@1.0.0Synchronous waits exhaust the cooperative pool. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
portfolio.async.17@1.0.0Priority inversion through opaque waiting. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
portfolio.async.18@1.0.0Shared-memory race across an unsafe or legacy boundary. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
portfolio.async.19@1.0.0Synchronous callback re-enters an unfinished protocol. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
portfolio.async.20@1.0.0Custom executor loses or repeats a job. It examines task ordering, suspension, cancellation, progress, and async obligations. The result remains unknown when the required evidence is incomplete.
lifetime.escaping-value@1.0.0Borrowed pointer or view escapes its lifetime. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
portfolio.life.02@1.0.0Use after free. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
portfolio.life.03@1.0.0Repeated or incompatible deallocation. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
portfolio.life.04@1.0.0Unowned access after owner deallocation. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
lifetime.unmanaged-ownership-balance@1.0.0Unmanaged ownership imbalance. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
lifetime.ownership-cycle@1.0.0Strong ownership cycle without a valid termination. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
portfolio.life.07@1.0.0Required weak consumer is released too early. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
lifetime.registration-outlives-scope@1.0.0Registration outlives its allowed scope. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
lifetime.undischarged-resource-obligation@1.0.0Cleanup obligation is not discharged. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
portfolio.life.10@1.0.0Closed or transferred resource is still used. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
portfolio.life.11@1.0.0Read from an uninitialized buffer region. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
correctness.pointer-count-initialization@1.0.0Pointer or count exceeds its valid extent. It examines ownership, resource state, and lifetime obligations across program paths. The result remains unknown when the required evidence is incomplete.
performance.repeated-linear-traversal@1.0.0Repeated linear traversal. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
performance.repeated-sorting@1.0.0Repeated invariant sorting. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
performance.repeated-consumed-materialization@1.0.0Repeated consumed materialization. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
performance.array-fifo-shifts@1.0.0Array used as a growing shifting FIFO. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.06@1.0.0Full sort used for an extremum or top-k result. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
performance.comparator-projection-amplification@1.0.0Expensive projection repeated by a comparator. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.08@1.0.0Eager materialization before a short consumer. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.09@1.0.0Repeated physical copy-on-write detach. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.10@1.0.0Get-copy-modify-set amplifies cost. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.12@1.0.0Capacity policy violates the amortized bound. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.13@1.0.0Repeated element-by-element bridging. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.14@1.0.0Repeated expensive hashing or equality work. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.15@1.0.0Small slice retains large storage. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.16@1.0.0Fine-grained tasks amplify scheduling work. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
portfolio.perf.17@1.0.0Fanout retains excessive live data. It examines repeated work, allocation, traversal, retention, and scheduling cost. The result remains unknown when the required evidence is incomplete.
security.sensitive-data-flow@1.0.0Sensitive data reaches logs. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
security.sql-structure-injection@1.0.0SQL injection. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
security.shell-command-injection@1.0.0Shell injection. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
security.format-position-injection@1.0.0Format-string injection. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
security.path-traversal@1.0.0Path traversal outside the extraction root. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
security.javascript-code-injection@1.0.0JavaScript or HTML context injection. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
security.privileged-url-input@1.0.0Unprivileged input controls a privileged URL sink. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.09@1.0.0Predicate injection. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.10@1.0.0Regular-expression injection. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.11@1.0.0Algorithmic denial of service through a regular expression. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.12@1.0.0External-entity expansion from untrusted XML. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.13@1.0.0TLS trust evaluation is effectively disabled. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.14@1.0.0Cryptography does not provide the claimed property. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.15@1.0.0Keyed nonce or IV is reused in an unsafe mode. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.16@1.0.0Unsafe password-derivation contract. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.17@1.0.0Predictable randomness in a security-sensitive value. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.18@1.0.0Untrusted deserialization crosses the allowed-type boundary. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.19@1.0.0Privileged effect bypasses required authorization. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.20@1.0.0Security validator or sanitizer is bypassed. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.21@1.0.0Embedded secret reaches a security-sensitive use. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.22@1.0.0WebView receives forbidden capabilities. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.23@1.0.0Cryptographic key has insufficient strength. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.24@1.0.0Dependency is fetched over an untrusted channel. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.25@1.0.0Non-reproducible dependency resolution violates policy. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
portfolio.sec.26@1.0.0Debug capability is exposed in a shipping product. It examines trust boundaries, sensitive flows, validation, and security-sensitive effects. The result remains unknown when the required evidence is incomplete.
correctness.equality-hash-contract@1.0.0Equality and hashing disagree. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
correctness.persisted-process-hash@1.0.0Process-local hash is used as a stable identity. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
correctness.regex-range-units@1.0.0Incompatible length or index units. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
correctness.invalidated-collection-index@1.0.0Invalidated collection index is used. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
correctness.mutable-collection-key@1.0.0Key changes equality or hash while in a collection. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
correctness.bounded-ordering-law@1.0.0Ordering laws are violated. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
correctness.canonical-output-nondeterminism@1.0.0Unstable ordering reaches canonical output. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.08@1.0.0Size or count exceeds its numeric range. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.09@1.0.0Non-finite value reaches a finite-only consumer. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.10@1.0.0Interprocedural path reaches an invalid force operation. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.11@1.0.0Single-pass sequence is consumed more than once. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.12@1.0.0Copy violates the state-independence contract. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.13@1.0.0Producer and consumer canonicalize identity differently. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.14@1.0.0Written value is lost before observation. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.15@1.0.0Predicate does not distinguish valid states. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.16@1.0.0Conditional-result branches are semantically identical. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.17@1.0.0Control-flow region is unreachable. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.18@1.0.0Computed result is discarded without a useful effect. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.cor.19@1.0.0Comparison violates its numeric precision contract. It examines value, collection, identity, ordering, and control-flow contracts. The result remains unknown when the required evidence is incomplete.
portfolio.stream.01@1.0.0Buffer or accumulator lacks a required bound. It examines buffering, delivery, progress, retry, and transaction boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.stream.02@1.0.0Drop policy violates required event delivery. It examines buffering, delivery, progress, retry, and transaction boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.stream.03@1.0.0Concurrent next calls on a single-consumer iterator. It examines buffering, delivery, progress, retry, and transaction boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.stream.04@1.0.0Stream is not finished on a required terminal path. It examines buffering, delivery, progress, retry, and transaction boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.stream.05@1.0.0Retry or refresh forms a loop without progress or budget. It examines buffering, delivery, progress, retry, and transaction boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.stream.06@1.0.0Retry duplicates a non-idempotent effect. It examines buffering, delivery, progress, retry, and transaction boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.stream.07@1.0.0Related changes escape a required transaction. It examines buffering, delivery, progress, retry, and transaction boundaries. The result remains unknown when the required evidence is incomplete.
portfolio.ui.01@1.0.0Element identity is unstable across updates. It examines SwiftUI identity, update, and state-lifecycle behavior. The result remains unknown when the required evidence is incomplete.
portfolio.ui.02@1.0.0Distinct elements share one identity. It examines SwiftUI identity, update, and state-lifecycle behavior. The result remains unknown when the required evidence is incomplete.
portfolio.ui.03@1.0.0View computation causes a state-update cycle. It examines SwiftUI identity, update, and state-lifecycle behavior. The result remains unknown when the required evidence is incomplete.
portfolio.ui.04@1.0.0One-time state does not update with required input. It examines SwiftUI identity, update, and state-lifecycle behavior. The result remains unknown when the required evidence is incomplete.
portfolio.change.01@1.0.0Source API change breaks an admitted consumer. It examines source, ABI, dependency, resource, and cache compatibility across changes. The result remains unknown when the required evidence is incomplete.
portfolio.change.02@1.0.0ABI change breaks binary compatibility. It examines source, ABI, dependency, resource, and cache compatibility across changes. The result remains unknown when the required evidence is incomplete.
portfolio.change.03@1.0.0Existing signature gains incompatible behavior. It examines source, ABI, dependency, resource, and cache compatibility across changes. The result remains unknown when the required evidence is incomplete.
portfolio.change.04@1.0.0Consumer silently binds to a different symbol. It examines source, ABI, dependency, resource, and cache compatibility across changes. The result remains unknown when the required evidence is incomplete.
portfolio.change.05@1.0.0Version range admits an incompatible provider. It examines source, ABI, dependency, resource, and cache compatibility across changes. The result remains unknown when the required evidence is incomplete.
portfolio.change.06@1.0.0Change bypasses required consumer review. It examines source, ABI, dependency, resource, and cache compatibility across changes. The result remains unknown when the required evidence is incomplete.
portfolio.change.07@1.0.0Comparable resource bound regresses. It examines source, ABI, dependency, resource, and cache compatibility across changes. The result remains unknown when the required evidence is incomplete.
portfolio.change.08@1.0.0Cache key or invalidation omits a result dependency. It examines source, ABI, dependency, resource, and cache compatibility across changes. The result remains unknown when the required evidence is incomplete.
One RuleID can group several conditions. Result kind does not define severity, and first-result strategy does not imply readiness.