Home / librespot-org / librespot
AI Slop Code Risk Monitor

librespot-org/librespot

SlopCodeMonitor badge for librespot-org/librespot Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).
0.6 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for librespot-org/librespot. SynthScan examined 33,007 lines of code across 172 source files, recording 19 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 0.6 (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.

0.6
Adjusted Signal
0.6
Raw Pattern Score
100%
Time Factor
—
Last Push
—
Stars
—
Language
33.0K
Lines of Code
172
Files
19
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 2.7/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.1/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 2.8/100 · LOW

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

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 19 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 Block18 hits · 18 pts
SeverityFileLineSnippetContext
LOWCargo.toml41# TLS backends (mutually exclusive - compile-time checks in oauth/src/lib.rs)COMMENT
LOWCargo.toml101# Integrates with the PulseAudio sound server for advanced audio routing.COMMENT
LOWoauth/src/lib.rs1#![warn(missing_docs)]COMMENT
LOWcore/src/session.rs901 session.shutdown();COMMENT
LOWcore/src/spotify_id.rs101 let mut dst = [0u8; 22];COMMENT
LOWcore/src/spclient.rs861 /// - of artist: `spotify:user:<user_id>:collection:artist:<artist_id>`COMMENT
LOWaudio/src/fetch/mod.rs81 /// Before playback starts, this many seconds of data must be present.COMMENT
LOWplayback/src/convert.rs41 const SHIFT_S16: u8 = 15; // 16-bit: 2^15 = 32768COMMENT
LOWplayback/src/dither.rs1use rand::SeedableRng;COMMENT
LOWplayback/src/audio_backend/alsa.rs201 channel_count: NUM_CHANNELS,COMMENT
LOWplayback/src/mixer/mappings.rs121 let ideal_factor = f64::ln(db_ratio);COMMENT
LOWconnect/src/spirc.rs301 /// Resumes or pauses the playbackCOMMENT
LOWconnect/src/spirc.rs341 /// Does nothing if we are not the active device.COMMENT
LOWconnect/src/spirc.rs381 ///COMMENT
LOWconnect/src/spirc.rs421COMMENT
LOWconnect/src/model.rs41 ///COMMENT
LOWconnect/src/model.rs121 /// The internal identifier is not the id contained in the uri. And ratherCOMMENT
LOWmetadata/src/artist.rs81pub struct AlbumGroup(pub Albums);COMMENT
Fake / Example Data1 hit · 1 pts
SeverityFileLineSnippetContext
LOWcore/src/cache.rs512 memory.save_credentials(&Credentials::with_access_token("dummy-token"));CODE