AI Slop Code RIsk Monitor

sozu-proxy/sozu

Sōzu HTTP reverse proxy, configurable at runtime, fast and safe, built in Rust. It is awesome!

7.4 Moderate pattern signal View on GitHub

Maintenance and Governance Review

This report summarizes scanner evidence for sozu-proxy/sozu, a Rust project with 3,743 GitHub stars. SynthScan examined 323,005 lines of code across 367 source files, recording 2204 pattern matches distributed across 13 syntactic categories. The legacy adjusted pattern signal is 7.4 (Moderate 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.

7.4
Adjusted Signal
7.4
Raw Pattern Score
100%
Time Factor
2026-10-11
Last Push
3.7K
Stars
Rust
Language
323.0K
Lines of Code
367
Files
2.2K
Pattern Hits
2026-10-12
Scan Date
0.00
HC Hit Rate

Risk Review · v3

Use each vector to guide manual verification of the underlying findings.

Cognitive Ownership Risk 23.1/100 · LOW

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

Hallucinated Dependency & Supply Chain Risk 0.0/100 · LOW

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

Agent Over-Engineering Ratio 10.2/100 · LOW

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

PR Review Velocity Impact 34.1/100 · MEDIUM

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

Run additional scans to build a history of the legacy pattern signal. Score changes are not a measure of AI adoption or code quality.

No multi-scan history yet — run the scanner again to build trend data.

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 1MEDIUM 242LOW 1961

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 2204 distinct pattern matches across 13 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 Block1897 hits · 1557 pts
SeverityFileLineSnippetContext
LOWos-build/config.toml1# top level optionsCOMMENT
LOWos-build/config.toml21# but they could be written to a UDP address:COMMENT
LOWos-build/config.toml41# `bin/config.toml` for the full schema rationale.COMMENT
LOWos-build/config.toml61COMMENT
LOWos-build/config.toml81COMMENT
LOWos-build/config.toml101# how much time (in milliseconds) sozu command line will wait for a command to complete.COMMENT
LOWos-build/config.toml121connect_timeout = 3COMMENT
LOWos-build/config.toml141# You can see those statistics with sozu command line, like this: `sozu metrics get` orCOMMENT
LOWos-build/config.toml161# specify a different IP than the one the socket sees, for logs and forwarded headersCOMMENT
LOWos-build/config.toml181# frontend timed out while waiting on a backend (a connect timeout fails overCOMMENT
LOWos-build/config.toml201COMMENT
LOWos-build/config.toml221# a 504 response means a connected backend sent no response in time, or theCOMMENT
LOWbin/build.rs61 // `fips > ring > aws-lc-rs > openssl`. Several can be active in theCOMMENT
LOWbin/config.toml1# sozu proxy test config fileCOMMENT
LOWbin/config.toml21COMMENT
LOWbin/config.toml41# access_logs_target = "file:///var/logs/sozu-access.log"COMMENT
LOWbin/config.toml61# operator-friendly tail + machine-parseable archive.COMMENT
LOWbin/config.toml81# opens it to every local account. Sozu does not set the group: use a setgidCOMMENT
LOWbin/config.toml101max_command_buffer_size = 163840COMMENT
LOWbin/config.toml121handle_process_affinity = falseCOMMENT
LOWbin/config.toml141# header when present, else `peer_addr`. When the limit is reached:COMMENT
LOWbin/config.toml161# This is a SECOND, INDEPENDENT counter beside `max_connections_per_ip`,COMMENT
LOWbin/config.toml181#COMMENT
LOWbin/config.toml201# Linux-only kernel-pipe capacity, in bytes, requested for theCOMMENT
LOWbin/config.toml221# min_buffers = 1COMMENT
LOWbin/config.toml241# maximum time of inactivity for a frontend socket, in secondsCOMMENT
LOWbin/config.toml261COMMENT
LOWbin/config.toml281# the complete configuration, and send an ActivateListener message afterwardsCOMMENT
LOWbin/config.toml301[[listeners]]COMMENT
LOWbin/config.toml321# answer_401 = "/absolute/path/to/custom_401.http"COMMENT
LOWbin/config.toml341# a cluster. Defaults to "SOZUBALANCEID"COMMENT
LOWbin/config.toml361# - "both": X-Forwarded-For/-Proto/-Port and RFC 7239 ForwardedCOMMENT
LOWbin/config.toml381# a 401 response is sent when a frontend has a Deny ruleCOMMENT
LOWbin/config.toml401# defines the sticky session cookie's name, if `sticky_session` is activated forCOMMENT
LOWbin/config.toml421# "Forwarding headers"). Default: "both".COMMENT
LOWbin/config.toml441# 31_536_000 seconds (1 year) — the HSTS preload list minimum.COMMENT
LOWbin/config.toml461# force_replace_backend = falseCOMMENT
LOWbin/config.toml501# Supported group names:COMMENT
LOWbin/config.toml521# default certificate and keyCOMMENT
LOWbin/config.toml541COMMENT
LOWbin/config.toml561# keep being served and the cap still sends GOAWAY(ENHANCE_YOUR_CALM).COMMENT
LOWbin/config.toml581#COMMENT
LOWbin/config.toml601# possible options are "http" or "tcp"COMMENT
LOWbin/config.toml621# when the listener expects one), or `affinity_header` /COMMENT
LOWbin/config.toml641# load_metric = "connections"COMMENT
LOWbin/config.toml661COMMENT
LOWbin/config.toml681#COMMENT
LOWbin/config.toml701COMMENT
LOWbin/tests/sozu_top_e2e.rs1//! Subprocess e2e tests for the `sozu top` TUI subcommand.COMMENT
LOWbin/tests/sozu_top_e2e.rs101/// `sozu start`, waits for the command socket to appear, runs the TUICOMMENT
LOWbin/tests/main_upgrade_transfer_rejection_e2e.rs1//! A rejected main-upgrade candidate must leave the old command graph live.COMMENT
LOWbin/tests/listener_validate_before_commit_e2e.rs1//! sozu#1301 end-to-end smoke test.COMMENT
LOWbin/tests/main_upgrade_compatibility_matrix_e2e.rs1//! Main-upgrade compatibility across the 2.2.1 / transactional-v2 boundary.COMMENT
LOWbin/tests/main_upgrade_compatibility_matrix_e2e.rs21//! The forward 2.2.1 -> current compatibility contract has its own positiveCOMMENT
LOWbin/tests/command_socket_mode_e2e.rs1//! `command_socket_mode` end-to-end test: `sozu start` must give the commandCOMMENT
LOWbin/tests/upgrade_pid_file_failure_e2e.rs1//! A main upgrade whose pid file cannot be written must roll back, not stopCOMMENT
LOWbin/tests/upgrade_fd_inheritance_e2e.rs1//! sozu#1668 end-to-end test: after worker and main upgrades, no sozu processCOMMENT
LOWbin/tests/sigterm_soft_stop_e2e.rs1//! sozu#1555 end-to-end test: `SIGTERM` to every process, as `systemctl stop`COMMENT
LOWbin/tests/load_state_rollback_e2e.rs1//! sozu#1313 end-to-end coverage: the state replay, against a real master andCOMMENT
LOWbin/tests/load_state_rollback_e2e.rs21//! 3. [`a_mixed_state_file_keeps_the_accepted_entries_and_reverts_the_rejected_one`]COMMENT
1837 more matches not shown…
Decorative Section Separators228 hits · 687 pts
SeverityFileLineSnippetContext
MEDIUMbin/src/ctl/top/snapshot_tests.rs231// ── OVERVIEW pane ─────────────────────────────────────────────────────COMMENT
MEDIUMbin/src/ctl/top/snapshot_tests.rs251// ── CLUSTERS pane ─────────────────────────────────────────────────────COMMENT
MEDIUMbin/src/ctl/top/snapshot_tests.rs273// ── BACKENDS pane ─────────────────────────────────────────────────────COMMENT
MEDIUMbin/src/ctl/top/snapshot_tests.rs284// ── LISTENERS pane ────────────────────────────────────────────────────COMMENT
MEDIUMbin/src/ctl/top/snapshot_tests.rs295// ── H2 pane ───────────────────────────────────────────────────────────COMMENT
MEDIUMbin/src/ctl/top/snapshot_tests.rs306// ── EVENTS pane (empty) ───────────────────────────────────────────────COMMENT
MEDIUM.github/workflows/simulation-sweep.yml63 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/simulation-sweep.yml71 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/simulation-sweep.yml105 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/simulation-sweep.yml113 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/simulation-sweep.yml143 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/simulation-sweep.yml145 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM⚡.github/workflows/ci.yml638 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM⚡.github/workflows/ci.yml646 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/ci.yml59 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/ci.yml62 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/ci.yml420 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/ci.yml422 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/ci.yml480 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/ci.yml488 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/ci.yml522 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/ci.yml529 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/ci.yml547 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/ci.yml572 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/ci.yml692 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/ci.yml694 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/workflows/ci.yml972 # ┌──────────────────────────────────────────────────────────────┐COMMENT
MEDIUM.github/workflows/ci.yml974 # └──────────────────────────────────────────────────────────────┘COMMENT
MEDIUM.github/scripts/check_doc_citations.py1041# ── Rule 2: drifted citations ─────────────────────────────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py1437# ── Rule 3: dead test-name citations ──────────────────────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py1669# ── Rule 4: pinned snippets ───────────────────────────────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py1903# ── Rule 5: line numbers cited from a Rust comment ──────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py2033# ── The audit mode: a citation that was ALREADY wrong ────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py3095 # ── Rule 2 ────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py3250 # ── Rule 3 ────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py3294 # ── Rule 4 ────────────────────────────────────────────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py3322 # ── Rule 5 ──────────────────────────────────────────────────────COMMENT
MEDIUM.github/scripts/check_doc_citations.py3395 # ── The audit mode ────────────────────────────────────────────────────COMMENT
MEDIUMlib/benches/h2_scheduling.rs178// ─── RFC 9218 §4 round-robin fairness simulation ────────────────────────COMMENT
MEDIUMlib/benches/h2_stream_table.rs297// ─── Groups 1 and 2: the per-frame lookup ───────────────────────────────COMMENT
MEDIUMlib/benches/h2_stream_table.rs348// ─── Group 3: steady-state churn ────────────────────────────────────────COMMENT
MEDIUMlib/benches/h2_stream_table.rs377// ─── Group 4: the composite write pass ──────────────────────────────────COMMENT
MEDIUMlib/benches/h2_stream_table.rs415// ─── Wiring ─────────────────────────────────────────────────────────────COMMENT
MEDIUMlib/src/https.rs2752 // ── HSTS listener-default → frontend inheritance ─────────────────COMMENT
MEDIUMlib/src/backends.rs2486 // ── #892: per-cluster availability tracker ──────────────────────────COMMENT
MEDIUMlib/src/backends.rs2486 // ── #892: per-cluster availability tracker ──────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1001 // ── Header filtering ─────────────────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1208 // ── Header lowercasing ───────────────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1234 // ── HPACK dynamic-table-size-update (RFC 7541 §4.2 / §6.3) ────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1358 // ── Elided headers ──────────────────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1382 // ── Invalid header name characters ──────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1430 // ── Flow control during DATA emission ────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1494 // ── END_STREAM flag management ──────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1549 // ── Finalize ────────────────────────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1629 // ── ChunkHeader ─────────────────────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1648 // ── RFC 9218 incremental yield: solo-bucket guard ───────────────────COMMENT
MEDIUMlib/src/protocol/mux/converter.rs1836 // ── HPACK budget over-run ────────────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/pkawa.rs1794 // ── parse_rfc9218_priority ────────────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/pkawa.rs1861 // ── is_connection_specific_header ─────────────────────────────────────COMMENT
MEDIUMlib/src/protocol/mux/pkawa.rs1887 // ── is_invalid_h2_header ─────────────────────────────────────────────COMMENT
168 more matches not shown…
Verbosity Indicators25 hits · 41 pts
SeverityFileLineSnippetContext
LOWe2e/src/tests/listener_update_tests.rs1192 // Step 1: deactivate.COMMENT
LOWe2e/src/tests/listener_update_tests.rs1203 // Step 2: update a H2 knob while deactivated.COMMENT
LOWe2e/src/tests/listener_update_tests.rs1217 // Step 3: reactivate.COMMENT
LOWe2e/src/tests/listener_update_tests.rs1230 // Step 4: verify knob in state.COMMENT
LOW⚡e2e/src/tests/h2_security_tests.rs2175 // Step 2: Send DATA frame with body (no END_STREAM).COMMENT
LOW⚡e2e/src/tests/h2_security_tests.rs2181 // Step 3: Send trailer HEADERS with END_STREAM + END_HEADERS.COMMENT
LOW⚡e2e/src/tests/h2_security_tests.rs2260 // Step 2: Send DATA frame with body (no END_STREAM).COMMENT
LOW⚡e2e/src/tests/h2_security_tests.rs2266 // Step 3: Send trailer HEADERS with a pseudo-header (:method GET).COMMENT
LOWe2e/src/tests/h2_security_tests.rs111 // Step 1: Send HEADERS on stream 1 WITHOUT END_HEADERS.COMMENT
LOWe2e/src/tests/h2_security_tests.rs151 // Step 2: Send 30 CONTINUATION frames, each referencing the dynamic tableCOMMENT
LOWe2e/src/tests/h2_security_tests.rs2158 // Step 1: Send HEADERS for POST on stream 1 (no END_STREAM, has END_HEADERS).COMMENT
LOWe2e/src/tests/h2_security_tests.rs2195 // Step 4: Read response from sozu.COMMENT
LOWe2e/src/tests/h2_security_tests.rs2248 // Step 1: Send HEADERS for POST on stream 1 (no END_STREAM).COMMENT
LOWe2e/src/tests/h2_security_tests.rs2283 // Step 4: Read response.COMMENT
LOWe2e/src/tests/h2_security_tests.rs2424 // Step 1: Send SETTINGS with HEADER_TABLE_SIZE=0 (setting id=1, value=0).COMMENT
LOWe2e/src/tests/h2_security_tests.rs2439 // Step 2: Send a HEADERS request using only static table referencesCOMMENT
LOWe2e/src/tests/h2_security_tests.rs2465 // Step 3: Read response.COMMENT
LOW⚡e2e/src/tests/h2_tests.rs9134 // Step 1: Read sozu's client preface + SETTINGSCOMMENT
LOW⚡e2e/src/tests/h2_tests.rs9141 // Step 2: Send our SETTINGS (empty) + SETTINGS ACKCOMMENT
LOW⚡e2e/src/tests/h2_tests.rs9155 // Step 3: Read sozu's SETTINGS ACK + HEADERS requestCOMMENT
LOW⚡e2e/src/tests/h2_tests.rs9164 // Step 4: Send a valid HEADERS response + DATA on stream 1COMMENT
LOWe2e/src/tests/h2_tests.rs8990 // Step 1: Verify the listener works with the original certificateCOMMENT
LOWe2e/src/tests/h2_tests.rs9012 // Step 2: Replace the certificate (using the same cert for test purposes)COMMENT
LOWe2e/src/tests/h2_tests.rs9033 // Step 3: New connection should work with the (replaced) certificateCOMMENT
LOWe2e/src/tests/h2_tests.rs9201 // Step 5: Flood with the specified frame typeCOMMENT
Structural Annotation Overuse25 hits · 41 pts
SeverityFileLineSnippetContext
LOWe2e/src/tests/listener_update_tests.rs1192 // Step 1: deactivate.COMMENT
LOWe2e/src/tests/listener_update_tests.rs1203 // Step 2: update a H2 knob while deactivated.COMMENT
LOWe2e/src/tests/listener_update_tests.rs1217 // Step 3: reactivate.COMMENT
LOWe2e/src/tests/listener_update_tests.rs1230 // Step 4: verify knob in state.COMMENT
LOW⚡e2e/src/tests/h2_security_tests.rs2175 // Step 2: Send DATA frame with body (no END_STREAM).COMMENT
LOW⚡e2e/src/tests/h2_security_tests.rs2181 // Step 3: Send trailer HEADERS with END_STREAM + END_HEADERS.COMMENT
LOW⚡e2e/src/tests/h2_security_tests.rs2260 // Step 2: Send DATA frame with body (no END_STREAM).COMMENT
LOW⚡e2e/src/tests/h2_security_tests.rs2266 // Step 3: Send trailer HEADERS with a pseudo-header (:method GET).COMMENT
LOWe2e/src/tests/h2_security_tests.rs111 // Step 1: Send HEADERS on stream 1 WITHOUT END_HEADERS.COMMENT
LOWe2e/src/tests/h2_security_tests.rs151 // Step 2: Send 30 CONTINUATION frames, each referencing the dynamic tableCOMMENT
LOWe2e/src/tests/h2_security_tests.rs2158 // Step 1: Send HEADERS for POST on stream 1 (no END_STREAM, has END_HEADERS).COMMENT
LOWe2e/src/tests/h2_security_tests.rs2195 // Step 4: Read response from sozu.COMMENT
LOWe2e/src/tests/h2_security_tests.rs2248 // Step 1: Send HEADERS for POST on stream 1 (no END_STREAM).COMMENT
LOWe2e/src/tests/h2_security_tests.rs2283 // Step 4: Read response.COMMENT
LOWe2e/src/tests/h2_security_tests.rs2424 // Step 1: Send SETTINGS with HEADER_TABLE_SIZE=0 (setting id=1, value=0).COMMENT
LOWe2e/src/tests/h2_security_tests.rs2439 // Step 2: Send a HEADERS request using only static table referencesCOMMENT
LOWe2e/src/tests/h2_security_tests.rs2465 // Step 3: Read response.COMMENT
LOW⚡e2e/src/tests/h2_tests.rs9134 // Step 1: Read sozu's client preface + SETTINGSCOMMENT
LOW⚡e2e/src/tests/h2_tests.rs9141 // Step 2: Send our SETTINGS (empty) + SETTINGS ACKCOMMENT
LOW⚡e2e/src/tests/h2_tests.rs9155 // Step 3: Read sozu's SETTINGS ACK + HEADERS requestCOMMENT
LOW⚡e2e/src/tests/h2_tests.rs9164 // Step 4: Send a valid HEADERS response + DATA on stream 1COMMENT
LOWe2e/src/tests/h2_tests.rs8990 // Step 1: Verify the listener works with the original certificateCOMMENT
LOWe2e/src/tests/h2_tests.rs9012 // Step 2: Replace the certificate (using the same cert for test purposes)COMMENT
LOWe2e/src/tests/h2_tests.rs9033 // Step 3: New connection should work with the (replaced) certificateCOMMENT
LOWe2e/src/tests/h2_tests.rs9201 // Step 5: Flood with the specified frame typeCOMMENT
AI Slop Vocabulary12 hits · 41 pts
SeverityFileLineSnippetContext
MEDIUMbin/src/command/requests.rs4163 // higher-leverage of the two reason-join paths.COMMENT
MEDIUM⚡.github/workflows/ci.yml641 # │ The sozu-sim harness is cfg-gated off in the main matrix │COMMENT
MEDIUMlib/src/tcp.rs5070 // (robust to any starting value), not an absolute reading. TheCOMMENT
MEDIUMlib/src/router/mod.rs7697 // section's prose was itself ADDED by the sozu#1356 fix this harnessCOMMENT
MEDIUMe2e/src/tests/udp_tests.rs415 // a handful) keeps the distribution sanity check below robust: with aCOMMENT
MEDIUMe2e/src/tests/tests.rs5867/// upgrade (sozu#1688). The harness seeds the new worker from its mirrorCOMMENT
MEDIUM⚡sim/Cargo.toml16# Test-only harness crate: never published, never linked by the `sozu` binary.COMMENT
MEDIUM⚡sim/Cargo.toml19# `#[cfg(tokio_unstable)]` gates the harness (see tests/udp_simulation.rs); declareCOMMENT
MEDIUM⚡sim/Cargo.toml24# The harness is an integration test (tests/udp_simulation.rs, tests/tcp_preread_sim.rs,COMMENT
MEDIUMsim/tests/metrics_lease_sim.rs108//! # What this harness does NOT coverCOMMENT
MEDIUMsim/tests/backend_selection_sim.rs460 "seed={:#x}: the window must close one second later on the harness's clock",CODE
MEDIUMsim/tests/h2_simulation.rs133//! # Why the clock is the harness's and not moonpool'sCOMMENT
Modern AI Meta-Vocabulary2 hits · 6 pts
SeverityFileLineSnippetContext
MEDIUMe2e/src/tests/hsts_tests.rs236/// e2e tests reuse the existing TLS scaffold (cert generation,COMMENT
MEDIUMe2e/src/tests/tests.rs5578// * `test_x_real_ip_elide_h2_trailer` — H2 trailer regression (Codex finding); scaffold pending.COMMENT
Empty Error Handlers1 hit · 5 pts
SeverityFileLineSnippetContext
HIGHe2e/lifecycle/keepalive_cookie.py129except subprocess.TimeoutExpired:CODE
Deep Nesting9 hits · 4 pts
SeverityFileLineSnippetContext
LOW.github/scripts/check_doc_citations.py949CODE
LOW.github/scripts/check_doc_citations.py1185CODE
LOW.github/scripts/check_doc_citations.py1273CODE
LOW.github/scripts/check_doc_citations.py1568CODE
LOW.github/scripts/check_doc_citations.py1616CODE
LOW.github/scripts/check_doc_citations.py1780CODE
LOW.github/scripts/check_doc_citations.py1972CODE
LOW.github/scripts/check_doc_citations.py2308CODE
LOW.github/scripts/check_doc_citations.py3014CODE
Example Usage Blocks1 hit · 2 pts
SeverityFileLineSnippetContext
LOW.github/scripts/check_doc_citations.py714# Usage:COMMENT
Slop Phrases1 hit · 2 pts
SeverityFileLineSnippetContext
LOWcommand/src/logging/access_logs.rs26 /// Don't forget to use std::mem::forget or ManuallyDrop over one of your ownersCOMMENT
Unused Imports1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/workflows/bench_logs.py4CODE
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOW.github/scripts/check_doc_citations.py1972def check_rust_comment_citations(root, historical=None, show=False, out=sys.stdout):CODE
Excessive Try-Catch Wrapping1 hit · 1 pts
SeverityFileLineSnippetContext
LOWe2e/lifecycle/tcp_upgrade/client.py62except Exception as error: # the result file records the observed lifecycle boundaryCODE