AI Slop Code Risk Monitor

valeriansaliou/sonic

SlopCodeMonitor badge for valeriansaliou/sonic Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

🦔 Fast, lightweight & schema-less search backend. An alternative to Elasticsearch that runs on a few MBs of RAM.

1.9 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for valeriansaliou/sonic, a Rust project with 21,372 GitHub stars. SynthScan examined 50,915 lines of code across 268 source files, recording 79 pattern matches distributed across 4 syntactic categories. The legacy adjusted pattern signal is 1.9 (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.

1.9
Adjusted Signal
1.9
Raw Pattern Score
100%
Time Factor
2026-10-30
Last Push
21.4K
Stars
Rust
Language
50.9K
Lines of Code
268
Files
79
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 5.2/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 3.9/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 7.5/100 · LOW

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

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 79 distinct pattern matches across 4 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.

Fake / Example Data30 hits · 40 pts
SeverityFileLineSnippetContext
LOW⚡core/tests/loose_matching.rs161 "Contact me at alice@example.org",CODE
LOW⚡core/tests/loose_matching.rs165 query: "alice@example.org",CODE
LOW⚡core/tests/loose_matching.rs169 "Contact me at alice+foo@example.org",CODE
LOW⚡core/tests/loose_matching.rs172 query: "alice+foo@example.org",CODE
LOWcore/src/lexer/token.rs66 .preprocess("Please contact support@example.org", None)CODE
LOW⚡core/src/lexer/token.rs83 .preprocess("Please contact support@example.org", None)CODE
LOW⚡core/src/lexer/token.rs87 ("support@example.org".to_owned(), TokenKind::Special(SpecialTokenKind::EmailAddress), 15, 34, 2)CODE
LOW⚡core/src/lexer/token.rs95 .preprocess("Please contact support@example.org", None)CODE
LOW⚡core/src/lexer/token.rs208 ("jane.doe@example.org", TokenKind::Special(SpecialTokenKind::EmailAddress)),CODE
LOW⚡core/src/lexer/token.rs209 ("alice@example.org", TokenKind::Special(SpecialTokenKind::EmailAddress)),CODE
LOW⚡core/src/lexer/token.rs211 ("bob+foo@example.org", TokenKind::Special(SpecialTokenKind::EmailAddress)),CODE
LOW⚡server/tests/search_query.rs34 ("msg:1", "olivia@example.org"),CODE
LOW⚡server/tests/search_query.rs35 ("msg:2", "olivio@example.org"),CODE
LOW⚡server/tests/search_query.rs36 ("msg:3", "alicia@example.org"),CODE
LOWserver/tests/search_query.rs62 .query("messages", "default", "olivia@example.org")CODE
LOWserver/tests/search_query.rs85 .query("messages", "default", "olivia@example.org")CODE
LOWserver/tests/search_query.rs109 .query("messages", "default", "olivia@example.org")CODE
LOW⚡docs/tokenizer-pattern-matching.md18 PUSH msg:1 "olivia@example.org"CODE
LOW⚡docs/tokenizer-pattern-matching.md20 PUSH msg:2 "olivio@example.org" # Lev(msg:1, msg:2) = 1CODE
LOW⚡docs/tokenizer-pattern-matching.md22 PUSH msg:3 "alicia@example.org" # Lev(msg:1, msg:3) = 2CODE
LOWdocs/tokenizer-pattern-matching.md39 QUERY "olivia@example.org"CODE
LOWdocs/tokenizer-pattern-matching.md71 QUERY "olivia@example.org"CODE
LOWdocs/tokenizer-pattern-matching.md98 QUERY "olivia@example.org"CODE
LOWdocs/tokenizer-pattern-matching.md132 QUERY "olivia@example.org"CODE
LOWdocs/tokenizer-pattern-matching.md172 QUERY "olivia@example.org"CODE
LOW⚡docs/tokenizer-pattern-matching.md191 PUSH msg:1 "olivia@example.org"CODE
LOW⚡docs/tokenizer-pattern-matching.md193 PUSH msg:2 "olivio@example.org"CODE
LOW⚡docs/tokenizer-pattern-matching.md195 PUSH msg:3 "alicia@example.org"CODE
LOW⚡docs/tokenizer-pattern-matching.md203 "olivia@example.org", "olivio@example.org", "alicia@example.org",CODE
LOW⚡docs/tokenizer-pattern-matching.md208 QUERY "olivia@example.org"CODE
Over-Commented Block39 hits · 39 pts
SeverityFileLineSnippetContext
LOWconfig.cfg21# become enabled by default (opt-out). Sonic won’t enable unreasonableCOMMENT
LOWcore/tests/typo_correction.rs1// SonicCOMMENT
LOWcore/tests/typo_correction.rs21//! };COMMENT
LOWcore/tests/typo_correction.rs41 // <https://github.com/valeriansaliou/sonic/issues/322#issuecomment-4638688602>.COMMENT
LOWcore/tests/back_compat.rs1// SonicCOMMENT
LOWcore/tests/search_term_ranking.rs1// SonicCOMMENT
LOWcore/tests/search_term_ranking.rs21/// been skipped during ingestion can be looked up at query time and the factCOMMENT
LOWcore/tests/non_regression.rs1// SonicCOMMENT
LOWcore/src/config.rs161 /// Whether or not to compress.COMMENT
LOWcore/src/stopwords/amh.rs1// SonicCOMMENT
LOWcore/src/stopwords/tuk.rs1// SonicCOMMENT
LOWcore/src/stopwords/ori.rs1// SonicCOMMENT
LOWcore/src/stopwords/bel.rs1// SonicCOMMENT
LOWcore/src/stopwords/jav.rs1// SonicCOMMENT
LOWcore/src/stopwords/uzb.rs1// SonicCOMMENT
LOWcore/src/stopwords/aka.rs1// SonicCOMMENT
LOWcore/src/stopwords/sin.rs1// SonicCOMMENT
LOWcore/src/stopwords/mkd.rs1// SonicCOMMENT
LOWcore/src/stopwords/sna.rs1// SonicCOMMENT
LOWcore/src/stopwords/tel.rs1// SonicCOMMENT
LOWcore/src/stopwords/cym.rs1// SonicCOMMENT
LOWcore/src/lexer/token.rs1// SonicCOMMENT
LOWcore/src/executor/flushc.rs1// SonicCOMMENT
LOWcore/src/store/kv/util.rs181 if new_val > res {COMMENT
LOWcore/src/store/fst/pool.rs501COMMENT
LOWserver/tests/non_regression.rs1// SonicCOMMENT
LOWserver/benches/common/huggingface/mod.rs1// SonicCOMMENT
LOWserver/src/util/mod.rs1// SonicCOMMENT
LOWserver/src/tasker/mod.rs1// SonicCOMMENT
LOWscripts/make_release.sh1#!/usr/bin/env bashCOMMENT
LOWscripts/build_release_archive.sh1#!/usr/bin/env bashCOMMENT
LOWclient/src/events.rs101}COMMENT
LOWclient/src/channel.rs521 // NOTE: This isn’t ideal, but it would add branching to fix this case,COMMENT
LOWclient/src/channel.rs541 assert_eq!(split_on_whitespace("300 km². ", 4), ("300", " km². "));COMMENT
LOWclient/src/control.rs121 /// uptime: 20868,COMMENT
LOWclient/src/lib.rs1// SonicCOMMENT
LOWclient/src/lib.rs41pub use crate::multiplexer::SonicMultiplexer;COMMENT
LOWclient/src/lib.rs61/// We chose 2 * 4KiB (common memory page size) as the default, which shouldCOMMENT
LOWclient/src/connection.rs61/// `SonicConnection` (necessary when dealing with mutable references).COMMENT
Verbosity Indicators5 hits · 8 pts
SeverityFileLineSnippetContext
LOWcore/src/store/kv/pool.rs244 // Step 1: List keys to be flushedCOMMENT
LOWcore/src/store/kv/pool.rs288 // Step 2: Flush KVs, one-by-one (sequential locking; this avoids global locks)COMMENT
LOWcore/src/store/fst/pool.rs307 // Step 1: List keys to be consolidatedCOMMENT
LOWcore/src/store/fst/pool.rs363 // Step 2: Clear keys to be consolidated from registerCOMMENT
LOWcore/src/store/fst/pool.rs378 // Step 3: Consolidate FSTs, one-by-one (sequential locking; this avoids global locks)COMMENT
Structural Annotation Overuse5 hits · 8 pts
SeverityFileLineSnippetContext
LOWcore/src/store/kv/pool.rs244 // Step 1: List keys to be flushedCOMMENT
LOWcore/src/store/kv/pool.rs288 // Step 2: Flush KVs, one-by-one (sequential locking; this avoids global locks)COMMENT
LOWcore/src/store/fst/pool.rs307 // Step 1: List keys to be consolidatedCOMMENT
LOWcore/src/store/fst/pool.rs363 // Step 2: Clear keys to be consolidated from registerCOMMENT
LOWcore/src/store/fst/pool.rs378 // Step 3: Consolidate FSTs, one-by-one (sequential locking; this avoids global locks)COMMENT