AI Slop Code Risk Monitor

smoltcp-rs/smoltcp

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

a smol tcp/ip stack

2.1 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

This report summarizes scanner evidence for smoltcp-rs/smoltcp, a Rust project with 4,638 GitHub stars. SynthScan examined 63,847 lines of code across 134 source files, recording 129 pattern matches distributed across 4 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-23
Last Push
4.6K
Stars
Rust
Language
63.8K
Lines of Code
134
Files
129
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.3/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.5/100 · LOW

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

Agent Over-Engineering Ratio 0.0/100 · LOW

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

PR Review Velocity Impact 9.8/100 · LOW

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

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 129 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.

Over-Commented Block120 hits · 119 pts
SeverityFileLineSnippetContext
LOWCargo.toml81COMMENT
LOWexamples/sixlowpan.rs1//! 6lowpan exampleCOMMENT
LOWexamples/sixlowpan.rs21//! iwpan dev wpan0 set pan_id 0xbeefCOMMENT
LOWexamples/sixlowpan_benchmark.rs1//! 6lowpan benchmark exampleCOMMENT
LOWexamples/sixlowpan_benchmark.rs21//! COMMENT
LOWsrc/parsers.rs241 Ok(())COMMENT
LOWsrc/lib.rs1#![cfg_attr(not(any(test, feature = "std")), no_std)]COMMENT
LOWsrc/lib.rs21//!COMMENT
LOWsrc/lib.rs41//!COMMENT
LOWsrc/lib.rs61//! The packet layer APIs are also provided in the module [wire].COMMENT
LOWsrc/wire/ipv6routing.rs61// | Next Header | Hdr Ext Len | Routing Type | Segments Left |COMMENT
LOWsrc/wire/ipv6routing.rs81COMMENT
LOWsrc/wire/ipv6routing.rs101 // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+COMMENT
LOWsrc/wire/ipv4.rs1use byteorder::{ByteOrder, NetworkEndian};COMMENT
LOWsrc/wire/ipv4.rs221 /// [new_unchecked]: #method.new_uncheckedCOMMENT
LOWsrc/wire/ipv6fragment.rs1use super::{Error, Result};COMMENT
LOWsrc/wire/ipsec_ah.rs1use byteorder::{ByteOrder, NetworkEndian};COMMENT
LOWsrc/wire/mod.rs581COMMENT
LOWsrc/wire/dhcpv4.rs541COMMENT
LOWsrc/wire/dhcpv4.rs561/// | server_ip |COMMENT
LOWsrc/wire/dhcpv4.rs581/// It is assumed that the access layer is Ethernet, so `htype` (the field representing theCOMMENT
LOWsrc/wire/dhcpv4.rs601 /// This field is also known as `chaddr` in the RFC and for networks where the access layer isCOMMENT
LOWsrc/wire/dhcpv4.rs621 /// The DHCP server uses the `relay_agent_ip` to determine the subnet on which the relay agentCOMMENT
LOWsrc/wire/dhcpv4.rs641 pub client_identifier: Option<EthernetAddress>,COMMENT
LOWsrc/wire/rpl.rs261 | RplControlMessage::SecureDestinationAdvertisementObjectAckCOMMENT
LOWsrc/wire/rpl.rs321/// ```txtCOMMENT
LOWsrc/wire/rpl.rs421 /// Set the destination advertisement trigger sequence number.COMMENT
LOWsrc/wire/rpl.rs441/// +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+COMMENT
LOWsrc/wire/rpl.rs521COMMENT
LOWsrc/wire/rpl.rs1101 *b = 0;COMMENT
LOWsrc/wire/rpl.rs1181 pub fn clear_route_info_reserved(&mut self) {COMMENT
LOWsrc/wire/rpl.rs1401 /// Getters for the RPL Target Option Message.COMMENT
LOWsrc/wire/rpl.rs1461 /// | Type = 0x06 | Option Length |E| Flags | Path Control |COMMENT
LOWsrc/wire/rpl.rs1561 pub fn set_transit_info_parent_address(&mut self, address: Address) {COMMENT
LOWsrc/wire/rpl.rs1721 }COMMENT
LOWsrc/wire/rpl.rs1881 )COMMENT
LOWsrc/wire/rpl.rs2301COMMENT
LOWsrc/wire/mld.rs21 /// Interface has a filter mode of EXCLUDE for the specified multicast address.COMMENT
LOWsrc/wire/ndiscoption.rs81COMMENT
LOWsrc/wire/ndiscoption.rs101 // | |COMMENT
LOWsrc/wire/ndiscoption.rs121 // | Type | Length | Reserved |COMMENT
LOWsrc/wire/ipv6.rs21COMMENT
LOWsrc/wire/ipv6.rs41COMMENT
LOWsrc/wire/ipv6.rs81 /// Create an IPv6 address based on the provided prefix and hardware identifier.COMMENT
LOWsrc/wire/ipv6.rs101 /// [link-local]: https://tools.ietf.org/html/rfc4291#section-2.5.6COMMENT
LOWsrc/wire/ipv6.rs321#[derive(Debug, PartialEq, Eq, Clone)]COMMENT
LOWsrc/wire/ipv6.rs341// +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+COMMENT
LOWsrc/wire/ipv6.rs381COMMENT
LOWsrc/wire/udp.rs121 /// Validate the packet checksum.COMMENT
LOWsrc/wire/sixlowpan/frag.rs21/// [RFC 4944 § 5.3] specifies the format of the header.COMMENT
LOWsrc/wire/sixlowpan/mod.rs21/// The representation of an unresolved address. 6LoWPAN compression of IPv6 addresses can be withCOMMENT
LOWsrc/wire/sixlowpan/mod.rs41 /// The first 112 bits of the address are elided. The value of the firstCOMMENT
LOWsrc/wire/sixlowpan/nhc.rs41/// +---+---+---+---+---+---+---+---+COMMENT
LOWsrc/wire/sixlowpan/nhc.rs441 routing_hdr.emit(&mut Ipv6RoutingHeader::new_unchecked(COMMENT
LOWsrc/wire/sixlowpan/iphc.rs41/// [RFC 6282 § 3.1] specifies the format of the header.COMMENT
LOWsrc/wire/sixlowpan/iphc.rs61///COMMENT
LOWsrc/iface/packet.rs241 #[cfg(all(feature = "proto-ipv4", feature = "multicast"))]COMMENT
LOWsrc/iface/interface/mod.rs81 SocketStateChanged,COMMENT
LOWsrc/iface/interface/mod.rs121/// The device independent part of an Ethernet network interface.COMMENT
LOWsrc/iface/interface/mod.rs161#[non_exhaustive]COMMENT
60 more matches not shown…
Fake / Example Data6 hits · 6 pts
SeverityFileLineSnippetContext
LOWsrc/iface/interface/tests/sixlowpan.rs353 let udp_data = b"Lorem ipsum dolor sit amet, consectetur adipiscing elit. \CODE
LOWsrc/iface/interface/tests/sixlowpan.rs353 let udp_data = b"Lorem ipsum dolor sit amet, consectetur adipiscing elit. \CODE
LOWsrc/iface/interface/tests/ipv6.rs169 data: b"Lorem Ipsum",CODE
LOWsrc/iface/interface/tests/ipv6.rs423 data: b"Lorem Ipsum",CODE
LOWsrc/iface/interface/tests/ipv6.rs439 data: b"Lorem Ipsum",CODE
LOWsrc/iface/interface/tests/ipv6.rs484 data: b"Lorem Ipsum",CODE
Verbosity Indicators2 hits · 3 pts
SeverityFileLineSnippetContext
LOWsrc/wire/ndiscoption.rs566 // TODO(thvdveld): I think we need to check if the data we are sending is notCOMMENT
LOWsrc/iface/interface/mod.rs1296 // If we have an IPv4 packet, then we need to check if we need to fragment it.COMMENT
AI Slop Vocabulary1 hit · 3 pts
SeverityFileLineSnippetContext
MEDIUMsrc/iface/rpl/trickle.rs2//! shared medium to exchange information in a highly robust, energy efficient, simple, andCOMMENT