AI Slop Code Risk Monitor

dani-garcia/vaultwarden

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

Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs

0.5 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for dani-garcia/vaultwarden, a Rust project with 69,972 GitHub stars. SynthScan examined 80,108 lines of code across 139 source files, recording 35 pattern matches distributed across 5 syntactic categories. The legacy adjusted pattern signal is 0.5 (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.5
Adjusted Signal
0.5
Raw Pattern Score
100%
Time Factor
2026-10-29
Last Push
70.0K
Stars
Rust
Language
80.1K
Lines of Code
139
Files
35
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.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.4/100 · LOW

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

Agent Over-Engineering Ratio 0.3/100 · LOW

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

PR Review Velocity Impact 2.3/100 · LOW

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

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 35 distinct pattern matches across 5 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 Block20 hits · 20 pts
SeverityFileLineSnippetContext
LOWdocker/healthcheck.sh21 key="$1"COMMENT
LOWplaywright/compose/keycloak/setup.sh41# export PATH=$PATH:/opt/keycloak/binCOMMENT
LOW.github/workflows/release.yml21 shell: bashCOMMENT
LOWsrc/util.rs81 // This is the same behavior as upstream Bitwarden.COMMENT
LOWsrc/config.rs501 }COMMENT
LOWsrc/config.rs561 send_purge_schedule: String, false, def, "0 5 * * * *".to_owned();COMMENT
LOWsrc/config.rs621 /// sure to inform all users of any changes to this setting.COMMENT
LOWsrc/config.rs641 /// If signups require email verification, automatically re-send verification email if it hasn't been sent for aCOMMENT
LOWsrc/config.rs681 client {COMMENT
LOWsrc/config.rs701 /// To specify a custom icon service, set a URL template with exactly one instance of `{}`,COMMENT
LOWsrc/auth.rs201 // Expiration timeCOMMENT
LOWsrc/auth.rs241 device: &Device,COMMENT
LOWsrc/main.rs1#![cfg_attr(feature = "unstable", feature(ip))]COMMENT
LOWsrc/static/scripts/datatables.js4281 }COMMENT
LOWsrc/db/models/event.rs121 OrganizationClientExportedVault = 1602,COMMENT
LOWsrc/db/models/user.rs181 } else {COMMENT
LOWsrc/db/models/org_policy.rs61#[derive(Deserialize)]COMMENT
LOWsrc/api/icons.rs301}COMMENT
LOWsrc/api/identity.rs1141 #[field(name = uncased("refresh_token"))]COMMENT
LOWsrc/api/identity.rs1161 device_identifier: Option<DeviceId>,COMMENT
Fake / Example Data5 hits · 6 pts
SeverityFileLineSnippetContext
LOWsrc/static/scripts/datatables.js12153 .attr('placeholder', opts.placeholder)CODE
LOW⚡src/api/core/accounts.rs1940 "email": "user@example.com",CODE
LOW⚡src/api/core/accounts.rs1945 "salt": "user@example.com",CODE
LOW⚡src/api/core/accounts.rs1950 "salt": "user@example.com",CODE
LOWsrc/api/core/accounts.rs1970 "email": "user@example.com",CODE
Redundant / Tautological Comments4 hits · 6 pts
SeverityFileLineSnippetContext
LOWdocker/podman-bake.sh11# Check if a target is given as first argumentCOMMENT
LOWdocker/podman-bake.sh39# Check if and which --build-arg arguments we need to configureCOMMENT
LOWdocker/healthcheck.sh11# Check if the $ENV_FILE file exist and is readableCOMMENT
LOW.github/workflows/release.yml161 # Check if there is a GitHub Container Registry Login and use it for cachingCOMMENT
Hyper-Verbose Identifiers5 hits · 5 pts
SeverityFileLineSnippetContext
LOWsrc/static/scripts/bootstrap.bundle.js353 function bootstrapDelegationHandler(element, selector, fn) {CODE
LOWsrc/static/scripts/bootstrap.bundle.js2386 function getOppositeVariationPlacement(placement) {CODE
LOWsrc/static/scripts/bootstrap.bundle.js2521 function getInnerBoundingClientRect(element, strategy) {CODE
LOWsrc/static/scripts/bootstrap.bundle.js2534 function getClientRectFromMixedType(element, clippingParent, strategy) {CODE
LOWsrc/static/scripts/bootstrap.bundle.js2737 function getExpandedFallbackPlacements(placement) {CODE
Self-Referential Comments1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMsrc/config.rs1539 # This file is not used until those errors are resolved. #\n\COMMENT