AI Slop Code Risk Monitor

spieglt/FlyingCarpet

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

Cross-platform AirDrop. File transfer between Android, iOS, Linux, macOS, and Windows over ad hoc WiFi. No network infrastructure required, just two devices with WiFi chips (and optionally Bluetooth) in close range.

2.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for spieglt/FlyingCarpet, a Rust project with 5,371 GitHub stars. SynthScan examined 27,985 lines of code across 109 source files, recording 57 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 2.1 (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.

2.1
Adjusted Signal
2.1
Raw Pattern Score
100%
Time Factor
2026-10-24
Last Push
5.4K
Stars
Rust
Language
28.0K
Lines of Code
109
Files
57
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 9.5/100 · LOW

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

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

PR Review Velocity Impact 10.0/100 · LOW

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

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 57 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 Block56 hits · 56 pts
SeverityFileLineSnippetContext
LOWApple/macOS/FlyingCarpetTests/FlyingCarpetTests.swift241 let respHS = try NoiseHandshakeState(role: .responder, psk: psk, prologue: tampered)COMMENT
LOWApple/shared/Bluetooth.swift1//COMMENT
LOWApple/shared/Noise.swift1//COMMENT
LOWApple/shared/Noise.swift361}COMMENT
LOWApple/shared/Receive.swift161 }COMMENT
LOWApple/shared/Transfer.swift901// why slow to send to but fast to receive from android?COMMENT
LOWApple/iOS/FlyingCarpetTests/FlyingCarpetTests.swift1//COMMENT
LOWApple/iOS/FlyingCarpetTests/FlyingCarpetTests.swift181 growth, 64 << 20,COMMENT
LOWApple/iOS/FlyingCarpet/ViewController.swift781 if message == "mac" || message == "ios" {COMMENT
LOWcore/src/lib.rs361 let role = match peer_resource {COMMENT
LOWcore/src/lib.rs761 fc_error(&format!("The other device is running Flying Carpet version {}, which is not compatible with this vCOMMENT
LOWcore/src/lib.rs781// fix testsCOMMENT
LOWcore/src/noise.rs1// Encrypted transport for all transfers (v10+): both hotspot and shared network mode.COMMENT
LOWcore/src/utils.rs81// it under.COMMENT
LOWcore/src/linux/peripheral.rs21/// The address of the central that drove this transfer, filled in by the first characteristicCOMMENT
LOWcore/src/linux/central.rs1//! Bluetooth central (receiving) side of the transfer negotiation.COMMENT
LOWcore/src/linux/central.rs81 ui.output("Peer is running Flying Carpet, connecting over Bluetooth...");COMMENT
LOWcore/src/linux/central.rs221 } else {COMMENT
LOWcore/src/linux/central.rs241// Once it is up, Connect() and service resolution ride the existing LE ACL.COMMENT
LOWcore/src/linux/central.rs381 );COMMENT
LOWcore/src/linux/bluetooth.rs41///COMMENT
LOWcore/src/linux/bluetooth.rs141 // re-pair per transfer, so removing is safe". That premise is false for both: theCOMMENT
LOWcore/src/linux/bluetooth.rs241 drop(app_handle);COMMENT
LOWcore/src/linux/bluetooth.rs281 // This retry was written for a poisoned bond — classic-only or dual-transport, leftCOMMENT
LOWcore/src/windows/peripheral.rs421}COMMENT
LOWcore/src/windows/central.rs121 // let async_result = match _paired_device.GetGattServicesWithCacheModeAsync(BluetoothCacheMode:COMMENT
LOWcore/src/windows/central.rs181 // session.SetMaintainConnection(true)?;COMMENT
LOWcore/src/windows/central.rs201 // println!("get services result: {:?}", services_result.Status());COMMENT
LOWcore/src/windows/bluetooth.rs141 time::sleep(time::Duration::from_secs(1)).await;COMMENT
LOWcore/src/windows/bluetooth.rs281 // flipped Status() to Started at that instant, making it a no-op by timing luckCOMMENT
LOWcore/src/windows/network.rs201 s.encode_utf16().chain(std::iter::once(0)).collect()COMMENT
LOWcore/src/windows/network.rs861/// re-added it, and the user got a UAC prompt on *every* transfer (issue #129) — on everyCOMMENT
LOWcore/src/windows/network.rs881 // window won't close. In an MTA, objects are not thread-affine and no pump is needed.COMMENT
LOWcore/src/windows/network.rs1061 fn join_hotspot() {COMMENT
LOW…src/main/java/dev/spiegl/flyingcarpet/MainViewModel.kt301 }COMMENT
LOW…src/main/java/dev/spiegl/flyingcarpet/MainViewModel.kt501COMMENT
LOW…src/main/java/dev/spiegl/flyingcarpet/MainViewModel.kt721 // The joiner's last BLE step, and where its half of the exchange is complete — theCOMMENT
LOW…src/main/java/dev/spiegl/flyingcarpet/MainViewModel.kt1001 }COMMENT
LOW…src/main/java/dev/spiegl/flyingcarpet/MainViewModel.kt1021 override fun bluetoothFailed() {COMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt81 // one that had completed its exchange would inherit `true` and spend the whole transferCOMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt101 }COMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt481 // "This transfer's post-bond connection has been opened." Cleared in scan() andCOMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt501 // True from stop() until the next scan() or advertise() — i.e. whenever no transferCOMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt541COMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt681 outputText("Discovered ${gatt.services.size} services")COMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt741 // can keep serving a snapshot that has no Flying Carpet service in it.COMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt781 discoveryOutstanding = falseCOMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt801 // and key exchange land first, or you enumerate a stale GATT database. WeCOMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt821 )COMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt961 // outputText("Reading $characteristicUuid")COMMENT
LOW…app/src/main/java/dev/spiegl/flyingcarpet/Bluetooth.kt1021 if (!queued) {COMMENT
LOW…/src/main/java/dev/spiegl/flyingcarpet/MainActivity.kt621 // disabled colors after the transfer ended and only correcting itself on the next drawableCOMMENT
LOW…/src/main/java/dev/spiegl/flyingcarpet/MainActivity.kt761 bluetoothRequestPermissionLauncher = registerForActivityResult(ActivityResultContracts.RequestMultiplePermissionCOMMENT
LOW…/src/main/java/dev/spiegl/flyingcarpet/MainActivity.kt901 }COMMENT
LOW…main/java/dev/spiegl/flyingcarpet/SafDirectoryCache.kt1package dev.spiegl.flyingcarpetCOMMENT
LOW.github/workflows/linux-release.yml1name: Linux ReleaseCOMMENT
Excessive Try-Catch Wrapping1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUMApple/iOS/FlyingCarpet/ViewController.swift67 print("Error emptying documents directory at launch: \(error)")CODE