a smol tcp/ip stack
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.
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.
Can maintainers explain intent, assumptions, and trade-offs? 123 finding(s).
Are imports declared and package/API names verified? 6 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 129 finding(s).
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.
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.
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.
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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | Cargo.toml | 81 | COMMENT | |
| LOW | examples/sixlowpan.rs | 1 | //! 6lowpan example | COMMENT |
| LOW | examples/sixlowpan.rs | 21 | //! iwpan dev wpan0 set pan_id 0xbeef | COMMENT |
| LOW | examples/sixlowpan_benchmark.rs | 1 | //! 6lowpan benchmark example | COMMENT |
| LOW | examples/sixlowpan_benchmark.rs | 21 | //! | COMMENT |
| LOW | src/parsers.rs | 241 | Ok(()) | COMMENT |
| LOW | src/lib.rs | 1 | #![cfg_attr(not(any(test, feature = "std")), no_std)] | COMMENT |
| LOW | src/lib.rs | 21 | //! | COMMENT |
| LOW | src/lib.rs | 41 | //! | COMMENT |
| LOW | src/lib.rs | 61 | //! The packet layer APIs are also provided in the module [wire]. | COMMENT |
| LOW | src/wire/ipv6routing.rs | 61 | // | Next Header | Hdr Ext Len | Routing Type | Segments Left | | COMMENT |
| LOW | src/wire/ipv6routing.rs | 81 | COMMENT | |
| LOW | src/wire/ipv6routing.rs | 101 | // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | COMMENT |
| LOW | src/wire/ipv4.rs | 1 | use byteorder::{ByteOrder, NetworkEndian}; | COMMENT |
| LOW | src/wire/ipv4.rs | 221 | /// [new_unchecked]: #method.new_unchecked | COMMENT |
| LOW | src/wire/ipv6fragment.rs | 1 | use super::{Error, Result}; | COMMENT |
| LOW | src/wire/ipsec_ah.rs | 1 | use byteorder::{ByteOrder, NetworkEndian}; | COMMENT |
| LOW | src/wire/mod.rs | 581 | COMMENT | |
| LOW | src/wire/dhcpv4.rs | 541 | COMMENT | |
| LOW | src/wire/dhcpv4.rs | 561 | /// | server_ip | | COMMENT |
| LOW | src/wire/dhcpv4.rs | 581 | /// It is assumed that the access layer is Ethernet, so `htype` (the field representing the | COMMENT |
| LOW | src/wire/dhcpv4.rs | 601 | /// This field is also known as `chaddr` in the RFC and for networks where the access layer is | COMMENT |
| LOW | src/wire/dhcpv4.rs | 621 | /// The DHCP server uses the `relay_agent_ip` to determine the subnet on which the relay agent | COMMENT |
| LOW | src/wire/dhcpv4.rs | 641 | pub client_identifier: Option<EthernetAddress>, | COMMENT |
| LOW | src/wire/rpl.rs | 261 | | RplControlMessage::SecureDestinationAdvertisementObjectAck | COMMENT |
| LOW | src/wire/rpl.rs | 321 | /// ```txt | COMMENT |
| LOW | src/wire/rpl.rs | 421 | /// Set the destination advertisement trigger sequence number. | COMMENT |
| LOW | src/wire/rpl.rs | 441 | /// +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | COMMENT |
| LOW | src/wire/rpl.rs | 521 | COMMENT | |
| LOW | src/wire/rpl.rs | 1101 | *b = 0; | COMMENT |
| LOW | src/wire/rpl.rs | 1181 | pub fn clear_route_info_reserved(&mut self) { | COMMENT |
| LOW | src/wire/rpl.rs | 1401 | /// Getters for the RPL Target Option Message. | COMMENT |
| LOW | src/wire/rpl.rs | 1461 | /// | Type = 0x06 | Option Length |E| Flags | Path Control | | COMMENT |
| LOW | src/wire/rpl.rs | 1561 | pub fn set_transit_info_parent_address(&mut self, address: Address) { | COMMENT |
| LOW | src/wire/rpl.rs | 1721 | } | COMMENT |
| LOW | src/wire/rpl.rs | 1881 | ) | COMMENT |
| LOW | src/wire/rpl.rs | 2301 | COMMENT | |
| LOW | src/wire/mld.rs | 21 | /// Interface has a filter mode of EXCLUDE for the specified multicast address. | COMMENT |
| LOW | src/wire/ndiscoption.rs | 81 | COMMENT | |
| LOW | src/wire/ndiscoption.rs | 101 | // | | | COMMENT |
| LOW | src/wire/ndiscoption.rs | 121 | // | Type | Length | Reserved | | COMMENT |
| LOW | src/wire/ipv6.rs | 21 | COMMENT | |
| LOW | src/wire/ipv6.rs | 41 | COMMENT | |
| LOW | src/wire/ipv6.rs | 81 | /// Create an IPv6 address based on the provided prefix and hardware identifier. | COMMENT |
| LOW | src/wire/ipv6.rs | 101 | /// [link-local]: https://tools.ietf.org/html/rfc4291#section-2.5.6 | COMMENT |
| LOW | src/wire/ipv6.rs | 321 | #[derive(Debug, PartialEq, Eq, Clone)] | COMMENT |
| LOW | src/wire/ipv6.rs | 341 | // +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | COMMENT |
| LOW | src/wire/ipv6.rs | 381 | COMMENT | |
| LOW | src/wire/udp.rs | 121 | /// Validate the packet checksum. | COMMENT |
| LOW | src/wire/sixlowpan/frag.rs | 21 | /// [RFC 4944 § 5.3] specifies the format of the header. | COMMENT |
| LOW | src/wire/sixlowpan/mod.rs | 21 | /// The representation of an unresolved address. 6LoWPAN compression of IPv6 addresses can be with | COMMENT |
| LOW | src/wire/sixlowpan/mod.rs | 41 | /// The first 112 bits of the address are elided. The value of the first | COMMENT |
| LOW | src/wire/sixlowpan/nhc.rs | 41 | /// +---+---+---+---+---+---+---+---+ | COMMENT |
| LOW | src/wire/sixlowpan/nhc.rs | 441 | routing_hdr.emit(&mut Ipv6RoutingHeader::new_unchecked( | COMMENT |
| LOW | src/wire/sixlowpan/iphc.rs | 41 | /// [RFC 6282 § 3.1] specifies the format of the header. | COMMENT |
| LOW | src/wire/sixlowpan/iphc.rs | 61 | /// | COMMENT |
| LOW | src/iface/packet.rs | 241 | #[cfg(all(feature = "proto-ipv4", feature = "multicast"))] | COMMENT |
| LOW | src/iface/interface/mod.rs | 81 | SocketStateChanged, | COMMENT |
| LOW | src/iface/interface/mod.rs | 121 | /// The device independent part of an Ethernet network interface. | COMMENT |
| LOW | src/iface/interface/mod.rs | 161 | #[non_exhaustive] | COMMENT |
| 60 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | src/iface/interface/tests/sixlowpan.rs | 353 | let udp_data = b"Lorem ipsum dolor sit amet, consectetur adipiscing elit. \ | CODE |
| LOW | src/iface/interface/tests/sixlowpan.rs | 353 | let udp_data = b"Lorem ipsum dolor sit amet, consectetur adipiscing elit. \ | CODE |
| LOW | src/iface/interface/tests/ipv6.rs | 169 | data: b"Lorem Ipsum", | CODE |
| LOW | src/iface/interface/tests/ipv6.rs | 423 | data: b"Lorem Ipsum", | CODE |
| LOW | src/iface/interface/tests/ipv6.rs | 439 | data: b"Lorem Ipsum", | CODE |
| LOW | src/iface/interface/tests/ipv6.rs | 484 | data: b"Lorem Ipsum", | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | src/wire/ndiscoption.rs | 566 | // TODO(thvdveld): I think we need to check if the data we are sending is not | COMMENT |
| LOW | src/iface/interface/mod.rs | 1296 | // If we have an IPv4 packet, then we need to check if we need to fragment it. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | src/iface/rpl/trickle.rs | 2 | //! shared medium to exchange information in a highly robust, energy efficient, simple, and | COMMENT |