h11 0.16.0

Source: https://github.com/python-hyper/h11
Tag scanned: v0.16.0
Compared with: v0.15.0 (0 signals introduced since)
Files: 49 scanned, 15 skipped (binary, oversized, or unrecognised)
Signals: 0 critical · 0 warn · 1 info
Scan time: 3.6 s
LLM review: Reviewed by claude-haiku-5-5 (Anthropic): 1 of 1 warn and critical signal; 1 demoted to info.
Disclude version: 4.1.0
Scanned (UTC): 2026-10-21 21:19

Signals

Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.

info ~~critical~~ → info by review dynamic-execution setup.py:4:1

`exec` at module scope (runs on import) on a non-literal expression (ast pass, confidence 0.80)
```
# defines __version__
exec(open("h11/_version.py").read())

setup(
```
likely benign LLM, confidence 0.85 A setup.py that exec()s the contents of the project's own h11/_version.py to obtain __version__.
Reasoning
The exec reads a local package file, h11/_version.py, relative to the project root and runs it to populate __version__. This is an old and common setup.py idiom for single-sourcing a version string. It is a poor practice because it executes code at import and build time, but it reads a fixed in-repo path with no network, decoding, or shell activity, so it shows no sign of malicious intent. The finding is severe only because the pass flags any non-literal exec at module scope.

Reproduce This Scan

Run disclude locally to verify. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.

cargo install disclude --version 4.1.0
git clone https://github.com/python-hyper/h11 h11 && cd h11
git checkout v0.16.0
disclude scan --severity info --diff v0.15.0 .