An HTTP library for Rust
This report summarizes scanner evidence for hyperium/hyper, a Rust project with 16,361 GitHub stars. SynthScan examined 31,719 lines of code across 124 source files, recording 142 pattern matches distributed across 2 syntactic categories. The legacy adjusted pattern signal is 4.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.
Use each vector to guide manual verification of the underlying findings.
Can maintainers explain intent, assumptions, and trade-offs? 142 finding(s).
Are imports declared and package/API names verified? 0 finding(s).
Are wrappers, guards, and repeated structures necessary? 0 finding(s).
Which changes need focused human review? 142 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 142 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.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | capi/examples/upload.c | 1 | #include <stdlib.h> | COMMENT |
| LOW | capi/examples/client.c | 1 | #include <stdlib.h> | COMMENT |
| LOW | tests/h1_shutdown_while_buffered.rs | 1 | // Test: Ensures poll_shutdown() is never called with buffered data | COMMENT |
| LOW | tests/h1_ready_in_flight.rs | 1 | // Test: an HTTP/1 client connection must not report ready while a request is | COMMENT |
| LOW | tests/client.rs | 3241 | assert!(res.is_err(), "should timeout waiting for response"); | COMMENT |
| LOW | tests/client.rs | 3261 | // one byte of connection window for stream B. | COMMENT |
| LOW | tests/h1_flush_before_yield.rs | 1 | // Test: `poll_loop` must never yield leaving buffered bytes unflushed. | COMMENT |
| LOW | examples/params.rs | 21 | static NOTNUMERIC: &[u8] = b"Number field is not numeric"; | COMMENT |
| LOW | examples/hello-http2.rs | 61 | // .await point allows the Tokio runtime to pull the task off of the thread until the task | COMMENT |
| LOW | examples/single_threaded.rs | 1 | #![deny(warnings)] | COMMENT |
| LOW | benches/connect.rs | 1 | #![feature(test)] | COMMENT |
| LOW | benches/connect.rs | 21 | // .expect("rt build"); | COMMENT |
| LOW | src/upgrade.rs | 1 | //! HTTP Upgrades. | COMMENT |
| LOW | src/upgrade.rs | 21 | //! either the appropriate method, if wanting to `CONNECT`, or headers such as | COMMENT |
| LOW | src/upgrade.rs | 61 | /// was used to speak HTTP before the upgrade. It can be used directly | COMMENT |
| LOW | src/upgrade.rs | 81 | /// HTTP state machine may have already read before completing an upgrade. | COMMENT |
| LOW | src/upgrade.rs | 301 | impl<T: Read + Write + Unpin + 'static> Io for T {} | COMMENT |
| LOW | src/error.rs | 1 | //! Error and Result module. | COMMENT |
| LOW | src/error.rs | 21 | /// is unspecified. **You must not depend on it.** The wording and details may | COMMENT |
| LOW | src/error.rs | 141 | ))] | COMMENT |
| LOW | src/error.rs | 161 | /// The dispatch task is gone. | COMMENT |
| LOW | src/error.rs | 201 | /// reason phrase. | COMMENT |
| LOW | src/error.rs | 221 | /// `content-length` and `transfer-encoding`). | COMMENT |
| LOW | src/error.rs | 261 | /// | COMMENT |
| LOW | src/lib.rs | 1 | #![deny(missing_docs)] | COMMENT |
| LOW | src/lib.rs | 21 | //! | COMMENT |
| LOW | src/lib.rs | 41 | //! closes the underlying TCP connection. Any subsequent call on the same | COMMENT |
| LOW | src/lib.rs | 61 | //! more feature flags that are required for that item to be used. | COMMENT |
| LOW | src/lib.rs | 81 | //! The following is a list of feature flags and their corresponding `RUSTFLAG`: | COMMENT |
| LOW | src/lib.rs | 101 | //! Some parts of hyper are documented as NOT being part of the stable API. The | COMMENT |
| LOW | src/ext/h1_reason_phrase.rs | 1 | use bytes::Bytes; | COMMENT |
| LOW | src/ext/h1_reason_phrase.rs | 21 | /// // Print out the non-canonical reason phrase, if it has one... | COMMENT |
| LOW | src/ext/h1_reason_phrase.rs | 41 | COMMENT | |
| LOW | src/ext/informational.rs | 1 | use std::sync::Arc; | COMMENT |
| LOW | src/ext/mod.rs | 1 | //! Extensions for HTTP messages in Hyper. | COMMENT |
| LOW | src/ext/mod.rs | 21 | //! // use the extension | COMMENT |
| LOW | src/ext/mod.rs | 61 | #[cfg(all(feature = "http1", feature = "client"))] | COMMENT |
| LOW | src/ext/mod.rs | 141 | /// [`preserve_header_case`] was set to true and the response included | COMMENT |
| LOW | src/ext/mod.rs | 201 | #[cfg(feature = "ffi")] | COMMENT |
| LOW | src/body/incoming.rs | 21 | use crate::proto::h2::ping; | COMMENT |
| LOW | src/body/incoming.rs | 61 | /// A sender half created through [`Body::channel()`]. | COMMENT |
| LOW | src/body/mod.rs | 1 | //! Streaming bodies for Requests and Responses. | COMMENT |
| LOW | src/body/mod.rs | 21 | //! | COMMENT |
| LOW | src/body/mod.rs | 41 | //! | COMMENT |
| LOW | src/server/mod.rs | 1 | //! HTTP Server. | COMMENT |
| LOW | src/server/conn/http2.rs | 21 | pin_project! { | COMMENT |
| LOW | src/server/conn/http2.rs | 121 | } | COMMENT |
| LOW | src/server/conn/http2.rs | 141 | /// See <https://rustsec.org/advisories/RUSTSEC-2024-0003.html> for more information. | COMMENT |
| LOW | src/server/conn/http2.rs | 221 | /// connection alive. | COMMENT |
| LOW | src/server/conn/mod.rs | 1 | //! Server connection API. | COMMENT |
| LOW | src/server/conn/http1.rs | 41 | where | COMMENT |
| LOW | src/server/conn/http1.rs | 61 | /// http.half_close(false); | COMMENT |
| LOW | src/server/conn/http1.rs | 81 | h1_header_read_timeout: Dur, | COMMENT |
| LOW | src/server/conn/http1.rs | 161 | /// Poll the connection for completion, but without calling `shutdown` | COMMENT |
| LOW | src/server/conn/http1.rs | 301 | /// If this is enabled and a header line does not start with a valid header | COMMENT |
| LOW | src/server/conn/http1.rs | 321 | /// | COMMENT |
| LOW | src/server/conn/http1.rs | 361 | /// Set a timeout for reading client request headers. If a client does not | COMMENT |
| LOW | src/server/conn/http1.rs | 381 | /// | COMMENT |
| LOW | src/server/conn/http1.rs | 441 | /// | COMMENT |
| LOW | src/rt/timer.rs | 1 | //! Provides a timer trait with timer-like functions. | COMMENT |
| 80 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | examples/upgrades.rs | 110 | // Don't forget to enable upgrades on the connection. | COMMENT |
| LOW | examples/upgrades.rs | 163 | // Don't forget to enable upgrades on the connection. | COMMENT |