AI Slop Code RIsk Monitor

kube-rs/kube

Rust Kubernetes client and controller runtime

9.3 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for kube-rs/kube, a Rust project with 3,845 GitHub stars. SynthScan examined 49,269 lines of code across 223 source files, recording 453 pattern matches distributed across 6 syntactic categories. The legacy adjusted pattern signal is 9.3 (Moderate pattern signal); it is not an authorship estimate.

Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.

9.3
Adjusted Signal
9.3
Raw Pattern Score
100%
Time Factor
2026-10-05
Last Push
3.8K
Stars
Rust
Language
49.3K
Lines of Code
223
Files
453
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 37.3/100 · MEDIUM

Can maintainers explain intent, assumptions, and trade-offs? 453 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

Are imports declared and package/API names verified? 0 finding(s).

Agent Over-Engineering Ratio 0.0/100 · LOW

Are wrappers, guards, and repeated structures necessary? 0 finding(s).

PR Review Velocity Impact 38.1/100 · MEDIUM

Which changes need focused human review? 453 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

Severity Breakdown

Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.

CRITICAL 0HIGH 1MEDIUM 7LOW 445

Directory Score Breakdown

This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.

Pattern Findings

The scanner identified 453 distinct pattern matches across 6 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.

Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.

Over-Commented Block440 hits · 424 pts
SeverityFileLineSnippetContext
LOWrelease.toml1# Release process :: cargo-release >= 0.18.3COMMENT
LOWkube-runtime/src/events.rs21const CACHE_TTL: SignedDuration = SignedDuration::from_mins(6);COMMENT
LOWkube-runtime/src/events.rs41COMMENT
LOWkube-runtime/src/events.rs61 ///COMMENT
LOWkube-runtime/src/events.rs101 pub reason: String,COMMENT
LOWkube-runtime/src/events.rs121 ///COMMENT
LOWkube-runtime/src/events.rs161 Self {COMMENT
LOWkube-runtime/src/events.rs181/// instance: std::env::var("CONTROLLER_POD_NAME").ok(),COMMENT
LOWkube-runtime/src/events.rs201/// },COMMENT
LOWkube-runtime/src/wait.rs21///COMMENT
LOWkube-runtime/src/wait.rs41/// use k8s_openapi::apiextensions_apiserver::pkg::apis::apiextensions::v1::CustomResourceDefinition;COMMENT
LOWkube-runtime/src/wait.rs81/// use k8s_openapi::api::core::v1::Pod;COMMENT
LOWkube-runtime/src/wait.rs101 /// # UsageCOMMENT
LOWkube-runtime/src/wait.rs121 /// # use kube_runtime::wait::Condition;COMMENT
LOWkube-runtime/src/lib.rs1//! Common components for building Kubernetes operatorsCOMMENT
LOWkube-runtime/src/finalizer.rs81/// in your [`applier`](crate::applier)/[`Controller`](crate::Controller)'s `reconcile` function.COMMENT
LOWkube-runtime/src/finalizer.rs101/// If [`Event::Apply`] is ever started then [`Event::Cleanup`] must succeed before the Kubernetes object deletion complCOMMENT
LOWkube-runtime/src/finalizer.rs121///COMMENT
LOWkube-runtime/src/finalizer.rs241pub enum Event<K> {COMMENT
LOWkube-runtime/src/watcher.rs61pub type Result<T, E = Error> = std::result::Result<T, E>;COMMENT
LOWkube-runtime/src/watcher.rs81 /// A series of `InitApply` events are expected to follow until all matching objectsCOMMENT
LOWkube-runtime/src/watcher.rs121 /// This allows for memory optimizations in watch streams.COMMENT
LOWkube-runtime/src/watcher.rs201 api: Api<K>,COMMENT
LOWkube-runtime/src/watcher.rs221 /// This is faster and much less taxing on the apiserver, but can resultCOMMENT
LOWkube-runtime/src/watcher.rs241 ///COMMENT
LOWkube-runtime/src/watcher.rs261 ///COMMENT
LOWkube-runtime/src/watcher.rs281 /// streaming list bookmarks (opt-in feature gate in Kubernetes 1.27).COMMENT
LOWkube-runtime/src/watcher.rs321///COMMENT
LOWkube-runtime/src/watcher.rs361 /// Configure typed label selectorsCOMMENT
LOWkube-runtime/src/watcher.rs781///COMMENT
LOWkube-runtime/src/watcher.rs801/// # async fn wrapper() -> Result<(), watcher::Error> {COMMENT
LOWkube-runtime/src/watcher.rs821/// This will normally happen immediately, but you can use [`StreamBackoff`](crate::utils::StreamBackoff)COMMENT
LOWkube-runtime/src/watcher.rs861/// [`try_for_each`](futures::TryStreamExt::try_for_each) and [`try_concat`](futures::TryStreamExt::try_concat))COMMENT
LOWkube-runtime/src/watcher.rs881/// println!("Applied: {}", p.name_any());COMMENT
LOWkube-runtime/src/watcher.rs921/// ## Scope WarningCOMMENT
LOWkube-runtime/src/scheduler.rs21 /// The time the message is scheduled forCOMMENT
LOWkube-runtime/src/scheduler.rs41 ///COMMENT
LOWkube-runtime/src/reflector/store.rs81 ///COMMENT
LOWkube-runtime/src/reflector/store.rs281COMMENT
LOWkube-runtime/src/reflector/object_ref.rs101#[derive(Educe)]COMMENT
LOWkube-runtime/src/reflector/object_ref.rs121/// ```COMMENT
LOWkube-runtime/src/reflector/object_ref.rs141 ///COMMENT
LOWkube-runtime/src/reflector/dispatcher.rs41 /// Messages will be buffered until all active readers have received a copyCOMMENT
LOWkube-runtime/src/reflector/dispatcher.rs61 // Calls broadcast on the channel. Will return when the channel has enoughCOMMENT
LOWkube-runtime/src/reflector/dispatcher.rs81/// shared stream reader should be polled independently and driven to readinessCOMMENT
LOWkube-runtime/src/reflector/dispatcher.rs381COMMENT
LOWkube-runtime/src/reflector/mod.rs21/// It passes the raw [`watcher()`] stream through unmodified.COMMENT
LOWkube-runtime/src/reflector/mod.rs41/// use k8s_openapi::api::core::v1::Node;COMMENT
LOWkube-runtime/src/reflector/mod.rs61/// # }COMMENT
LOWkube-runtime/src/reflector/mod.rs81///COMMENT
LOWkube-runtime/src/reflector/mod.rs101///COMMENT
LOWkube-runtime/src/utils/mod.rs41/// like a streaming variant of pattern matching.COMMENT
LOWkube-runtime/src/utils/watch_ext.rs61 {COMMENT
LOWkube-runtime/src/utils/watch_ext.rs81 /// deploy.managed_fields_mut().clear();COMMENT
LOWkube-runtime/src/utils/watch_ext.rs101 ///COMMENT
LOWkube-runtime/src/utils/watch_ext.rs121 /// # fn example(api: Api<Deployment>) {COMMENT
LOWkube-runtime/src/utils/watch_ext.rs141 /// # let client: kube::Client = todo!();COMMENT
LOWkube-runtime/src/utils/watch_ext.rs161COMMENT
LOWkube-runtime/src/utils/watch_ext.rs181 /// tokio::spawn(async move {COMMENT
LOWkube-runtime/src/utils/watch_ext.rs201 /// .await;COMMENT
380 more matches not shown…
Self-Referential Comments6 hits · 18 pts
SeverityFileLineSnippetContext
MEDIUMkube-runtime/Cargo.toml22# Define the configuration attribute `docsrs`. Used to enable `doc_cfg` feature.COMMENT
MEDIUMkube-client/Cargo.toml41# Define the configuration attribute `docsrs`. Used to enable `doc_cfg` feature.COMMENT
MEDIUMkube-core/src/params.rs579/// # Creating a patch via serde_jsonCOMMENT
MEDIUMkube-core/src/params.rs594/// # Creating a patch from a typeCOMMENT
MEDIUMscripts/release-pre.sh8 # Create a new UNRELEASED header, and add compare url to itCOMMENT
MEDIUMkube/Cargo.toml69# Define the configuration attribute `docsrs`. Used to enable `doc_cfg` feature.COMMENT
Synthetic Comment Markers1 hit · 8 pts
SeverityFileLineSnippetContext
HIGHkube-core/src/response.rs137 /// be completed as requested.COMMENT
Example Usage Blocks4 hits · 6 pts
SeverityFileLineSnippetContext
LOWkube-client/src/client/mod.rs443 /// ### Example usage:COMMENT
LOWkube-client/src/client/mod.rs492 /// ### Example usage:COMMENT
LOWkube-client/src/client/mod.rs526 /// ### Example usage:COMMENT
LOWscripts/release-afterdoc.sh33# Usage:COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMkube-runtime/src/reflector/mod.rs71/// While generally acceptable, there are techniques you can leverage to reduce the memory usageCOMMENT
Structural Annotation Overuse1 hit · 2 pts
SeverityFileLineSnippetContext
LOWkube-core/src/crd.rs24 /// NOTE: This function returns *declared* short names (at compile-time, using the `#[kube(shortname = "foo")]`)COMMENT