psycopg 3.3.7
- Source
- https://github.com/psycopg/psycopg
- Artifact scanned
psycopg-3.3.7-py3-none-any.whl- Compared with
psycopg-3.3.6-py3-none-any.whl(0 signals introduced since)- Files
- 86 scanned, 4 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 1 info
- Scan time
- 2.1 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 1 of 1 warn and critical signal; 1 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-11-03 05:27
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
) = # On Windows, for the moment, avoid using wait_c, because it was reported tolikely benign psycopg selects its platform-specific wait implementation by looking up a function name in globals().Reasoning
The code selects a wait function by name from globals() after choosing an implementation (wait_c, wait_epoll, etc.) based on platform/availability. This is a common, legitimate dispatch pattern in psycopg for selecting the best I/O wait backend; the name comes from a fixed set of internal function names, not untrusted input. The AST flag is a generic dynamic-attribute heuristic.
Reproduce This Scan
Run disclude locally to verify. These commands scan the published file; the "new in this release" marks come from comparing it with the previous release's file, which they don't repeat. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
|