PyPI / psycopg2-binary / 2.9.13
psycopg2-binary 2.9.13
- Source
- https://github.com/psycopg/psycopg2
- Artifact scanned
psycopg2_binary-2.9.13.tar.gz- Compared with
psycopg2_binary-2.9.12.tar.gz(0 signals introduced since)- Files
- 160 scanned, 17 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 9 info
- Scan time
- 5.8 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 6 of 6 warn and critical signals; 6 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 06:13
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
likely benign Build script invokes a helper script located via a directory variable and strips shared libraries.
Reasoning
This is a psycopg build script. The variable command ${dir}/print_so_versions.sh is a sibling script resolved from the script's own directory, and find output is only passed as an argument. Standard build tooling pattern, not malicious.
-
;likely benign Runs a local libpq build helper chosen by OS case branch, with path derived from the script directory.Reasoning
The dir variable is computed from the script location and used to run build_libpq.sh, a sibling build helper. This is ordinary cibuildwheel setup logic in a database driver repository.
-
| | ;likely benign Runs the libpq build helper for RHEL-family distributions via a script-relative directory variable.Reasoning
Same pattern as the alpine branch: a sibling build script invoked via a script-relative directory variable in the centos/rocky/almalinux branch. Legitimate build logic.
-
# Build dependency libraries # Show dependency treelikely benign macOS wheel build hook invokes the project's libpq build script via a project-directory variable.Reasoning
prjdir is the project directory used to call the repository's own build_libpq.sh during macOS wheel building. Expected behavior of a build hook, with no network fetch or decoding shown.
-
for; do && break if [; thenlikely benign Retry loop in CI waits for PostgreSQL readiness, using an unnecessary eval on a fixed command.Reasoning
eval is applied to the literal pg_isready in a retry loop waiting for PostgreSQL to start in CI. It is pointless but harmless and contains no obfuscated or attacker-controlled content.
-
is and . -
likely benign Unit test literal containing a sequence of byte escapes used as composite-type test input.
Reasoning
This is a test for PostgreSQL composite record parsing that deliberately feeds all control and printable ASCII bytes through escape sequences. The hex escapes are the test data itself, so the entropy hit is a false positive from a raw pass.
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.
|
&&