AI Slop Code Risk Monitor

rust-postgres/rust-postgres

SlopCodeMonitor badge for rust-postgres/rust-postgres Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

Native PostgreSQL driver for the Rust programming language

3.3 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for rust-postgres/rust-postgres, a Rust project with 4,028 GitHub stars. SynthScan examined 29,556 lines of code across 156 source files, recording 99 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 3.3 (Low 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.

3.3
Adjusted Signal
3.3
Raw Pattern Score
100%
Time Factor
2026-10-03
Last Push
4.0K
Stars
Rust
Language
29.6K
Lines of Code
156
Files
99
Pattern Hits
2026-10-31
Scan Date
0.00
HC Hit Rate

Risk Review · Payload v1

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

Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.

Cognitive Ownership Risk 15.1/100 · LOW

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

Which changes need focused human review? 99 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

This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.

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 1LOW 98

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 99 distinct pattern matches across 2 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 Block98 hits · 94 pts
SeverityFileLineSnippetContext
LOWtokio-postgres/src/types.rs1//! Types.COMMENT
LOWtokio-postgres/src/client.rs61COMMENT
LOWtokio-postgres/src/client.rs381 return Err(Error::column_count());COMMENT
LOWtokio-postgres/src/client.rs401 /// ```no_runCOMMENT
LOWtokio-postgres/src/client.rs521 /// their Postgres type. Thus, this is suitable in environments where prepared statements aren'tCOMMENT
LOWtokio-postgres/src/client.rs541 /// let mut it = pin!(client.query_typed_raw(COMMENT
LOWtokio-postgres/src/client.rs641 /// PostgreSQL does not support parameters in `COPY` statements, so this method does not take any.COMMENT
LOWtokio-postgres/src/client.rs661 /// functionality to safely embed that data in the request. Do not form statements via string concatenation and passCOMMENT
LOWtokio-postgres/src/client.rs681 simple_query::simple_query(self.inner(), query).awaitCOMMENT
LOWtokio-postgres/src/config.rs41}COMMENT
LOWtokio-postgres/src/config.rs81/// Load balancing configuration.COMMENT
LOWtokio-postgres/src/config.rs101}COMMENT
LOWtokio-postgres/src/config.rs121/// * `host` - The host to connect to. On Unix platforms, if the host starts with a `/` character it is treated as theCOMMENT
LOWtokio-postgres/src/config.rs141/// * If `hostaddr` is specified without `host`, the value for `hostaddr` gives the server network address.COMMENT
LOWtokio-postgres/src/config.rs161/// * `keepalives_retries` - The maximum number of TCP keepalive probes that will be sent before dropping a connection.COMMENT
LOWtokio-postgres/src/config.rs181///COMMENT
LOWtokio-postgres/src/config.rs201/// ## ExamplesCOMMENT
LOWtokio-postgres/src/lib.rs1//! An asynchronous, pipelined, PostgreSQL client.COMMENT
LOWtokio-postgres/src/lib.rs21//! }COMMENT
LOWtokio-postgres/src/lib.rs41//! polled, not in the order that their futures are created.COMMENT
LOWtokio-postgres/src/lib.rs61//! | | process query 3 |COMMENT
LOWtokio-postgres/src/lib.rs81//! client.prepare("SELECT * FROM foo"),COMMENT
LOWtokio-postgres/src/lib.rs101//!COMMENT
LOWtokio-postgres/src/lib.rs241 /// Notices use the same format as errors, but aren't "errors" per-se.COMMENT
LOWtokio-postgres/src/cancel_token.rs21 /// Attempts to cancel the in-progress query on the connection associatedCOMMENT
LOWtokio-postgres/src/error/mod.rs261 /// If the error was associated with a specific table, the name of theCOMMENT
LOWpostgres-openssl/src/lib.rs1//! TLS support for `tokio-postgres` and `postgres` via `openssl`.COMMENT
LOWpostgres-openssl/src/lib.rs21//!COMMENT
LOWpostgres-protocol/src/lib.rs1//! Low level Postgres protocol APIs.COMMENT
LOWpostgres-protocol/src/escape/mod.rs1//! Provides functions for escaping literals and identifiers for useCOMMENT
LOWpostgres-protocol/src/escape/mod.rs61 // identifier.COMMENT
LOWpostgres-protocol/src/password/mod.rs41 // 4013](https://tools.ietf.org/html/rfc4013), if possible.COMMENT
LOWpostgres-protocol/src/message/mod.rs1//! Postgres message protocol support.COMMENT
LOWpostgres-protocol/src/authentication/sasl.rs121 },COMMENT
LOWpostgres-native-tls/src/lib.rs1//! TLS support for `tokio-postgres` and `postgres` via `native-tls`.COMMENT
LOWpostgres-native-tls/src/lib.rs21//! "host=localhost user=postgres sslmode=require",COMMENT
LOWpostgres-native-tls/src/lib.rs41//! let connector = TlsConnector::builder()COMMENT
LOWcodegen/src/errcodes.txt1#COMMENT
LOWcodegen/src/errcodes.txt21# doc/src/sgml/errcodes-table.sgmlCOMMENT
LOWcodegen/src/errcodes.txt41# Section: section descriptionCOMMENT
LOWcodegen/src/errcodes.txt61# The SQL spec requires that all the elements of a SQLSTATE code beCOMMENT
LOWpostgres/src/client.rs41 params.parse::<Config>()?.connect(tls_mode)COMMENT
LOWpostgres/src/client.rs61 ///COMMENT
LOWpostgres/src/client.rs81 T: ?Sized + ToStatement,COMMENT
LOWpostgres/src/client.rs101 ///COMMENT
LOWpostgres/src/client.rs121 query: &str,COMMENT
LOWpostgres/src/client.rs141 ///COMMENT
LOWpostgres/src/client.rs161 ///COMMENT
LOWpostgres/src/client.rs181 /// let foo: i32 = row.get("foo");COMMENT
LOWpostgres/src/client.rs201 /// The `query` argument can either be a `Statement`, or a raw query string. If the same statement will beCOMMENT
LOWpostgres/src/client.rs241 ///COMMENT
LOWpostgres/src/client.rs261 /// ```COMMENT
LOWpostgres/src/client.rs321 ///COMMENT
LOWpostgres/src/client.rs341COMMENT
LOWpostgres/src/client.rs361 }COMMENT
LOWpostgres/src/client.rs381 /// # let mut client = Client::connect("host=localhost user=postgres", NoTls)?;COMMENT
LOWpostgres/src/client.rs401 P: BorrowToSql,COMMENT
LOWpostgres/src/client.rs421 /// let mut client = Client::connect("host=localhost user=postgres", NoTls)?;COMMENT
LOWpostgres/src/client.rs441 ///COMMENT
LOWpostgres/src/client.rs461 /// # Ok(())COMMENT
38 more matches not shown…
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMpostgres-types/src/lib.rs131//! `#[postgres(name = "...")]` takes precendence when used in conjunction with `#[postgres(rename_all = "...")]`:COMMENT