AI Slop Code RIsk Monitor

actix/actix

Actor framework for Rust.

5.1 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for actix/actix, a Rust project with 9,253 GitHub stars. SynthScan examined 14,792 lines of code across 105 source files, recording 76 pattern matches distributed across 1 syntactic category. The legacy adjusted pattern signal is 5.1 (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.

5.1
Adjusted Signal
5.1
Raw Pattern Score
100%
Time Factor
2026-10-08
Last Push
9.3K
Stars
Rust
Language
14.8K
Lines of Code
105
Files
76
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 22.7/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 76 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 22.7/100 · LOW

Which changes need focused human review? 76 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 0MEDIUM 0LOW 76

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 76 distinct pattern matches across 1 syntactic category. 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 Block76 hits · 76 pts
SeverityFileLineSnippetContext
LOWactix-broker/src/lib.rs1//! A message broker for the Actix actor framework.COMMENT
LOWactix-broker/src/lib.rs21//! #[derive(Clone, Message)]COMMENT
LOWactix-broker/src/lib.rs41//! // Synchronously subscribe to a message on the arbiter (local) brokerCOMMENT
LOWactix-broker/src/lib.rs61//! }COMMENT
LOWactix-derive/src/lib.rs21#[proc_macro_derive(MessageResponse)]COMMENT
LOWactix-derive/src/lib.rs41 #[::actix::__private::main(system = "::actix::System")]COMMENT
LOWactix/examples/weak_recipient.rs1//! WeakRecipient exampleCOMMENT
LOWactix/examples/weak_addr.rs1//! WeakAddr exampleCOMMENT
LOWactix/src/stream.rs21///COMMENT
LOWactix/src/stream.rs41/// }COMMENT
LOWactix/src/registry.rs21 supervisor::Supervisor,COMMENT
LOWactix/src/registry.rs41/// struct Ping;COMMENT
LOWactix/src/registry.rs61/// println!("ping");COMMENT
LOWactix/src/registry.rs201/// #[rtype(result = "()")]COMMENT
LOWactix/src/registry.rs221/// fn handle(&mut self, _: Ping, ctx: &mut Context<Self>) {COMMENT
LOWactix/src/supervisor.rs21 /// A Supervisor manages incoming messages for an actor. In case of actor failure,COMMENT
LOWactix/src/supervisor.rs41 ///COMMENT
LOWactix/src/supervisor.rs61 /// }COMMENT
LOWactix/src/supervisor.rs81 }COMMENT
LOWactix/src/clock.rs1//! Utilities for tracking time.COMMENT
LOWactix/src/handler.rs61///COMMENT
LOWactix/src/handler.rs81/// ```COMMENT
LOWactix/src/handler.rs101/// ```no_runCOMMENT
LOWactix/src/handler.rs121/// async {}COMMENT
LOWactix/src/handler.rs161///COMMENT
LOWactix/src/handler.rs181///COMMENT
LOWactix/src/handler.rs201COMMENT
LOWactix/src/handler.rs221/// }COMMENT
LOWactix/src/handler.rs241/// If `Actor::Context` implements [`AsyncContext`] it's possible to handleCOMMENT
LOWactix/src/handler.rs341/// # impl Actor for MyActorAsync { type Context = actix::Context<Self>; }COMMENT
LOWactix/src/handler.rs361/// # use core::pin::Pin;COMMENT
LOWactix/src/lib.rs1//! Actix is an actor framework.COMMENT
LOWactix/src/lib.rs81 //!COMMENT
LOWactix/src/lib.rs141 handler::{MessageResponse, OneshotSender},COMMENT
LOWactix/src/lib.rs161/// use std::time::{Duration, Instant};COMMENT
LOWactix/src/context_impl.rs281COMMENT
LOWactix/src/sync.rs21 },COMMENT
LOWactix/src/sync.rs41/// struct Fibonacci(pub u32);COMMENT
LOWactix/src/sync.rs61/// Ok(1)COMMENT
LOWactix/src/sync.rs81/// let addr = SyncArbiter::start(2, || SyncActor);COMMENT
LOWactix/src/sync.rs201 M: Message + Send + 'static,COMMENT
LOWactix/src/sync.rs221///COMMENT
LOWactix/src/actor.rs21/// [`Context<A>`](struct.Context.html). The context object is availableCOMMENT
LOWactix/src/actor.rs41/// An actor starts in the `Started` state, during this state theCOMMENT
LOWactix/src/actor.rs61/// a future or stream, in its `Actor::stopping` method.COMMENT
LOWactix/src/actor.rs81COMMENT
LOWactix/src/actor.rs101 fn stopped(&mut self, ctx: &mut Self::Context) {}COMMENT
LOWactix/src/actor.rs161 /// Start a new asynchronous actor given a `Context`.COMMENT
LOWactix/src/actor.rs201///COMMENT
LOWactix/src/actor.rs241 }COMMENT
LOWactix/src/actor.rs301COMMENT
LOWactix/src/actor.rs321 /// println!("PING");COMMENT
LOWactix/src/actor.rs341 /// let addr = sys.block_on(async { MyActor.start() });COMMENT
LOWactix/src/actor.rs361 ///COMMENT
LOWactix/src/utils.rs61COMMENT
LOWactix/src/utils.rs81 /// }COMMENT
LOWactix/src/utils.rs141 ///COMMENT
LOWactix/src/utils.rs161 /// type Context = Context<Self>;COMMENT
LOWactix/src/context.rs81}COMMENT
LOWactix/src/context.rs101 /// actor1_addr: Addr<Actor1>,COMMENT
16 more matches not shown…