duckdb 2.0.0
- Source
- https://github.com/duckdb/duckdb-python
- Tag scanned
v2.0.0- Compared with
v1.5.6(6 signals introduced since)- Files
- 574 scanned, 24 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 17 info
- Scan time
- 8.5 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 6 of 6 warn and critical signals; 6 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 07:29
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
for; dolikely benign A README loop that runs benchmark pytest under a local or release virtualenv Python.Reasoning
The loop runs pytest for benchmark modules under two interpreter paths the developer chose, in a documentation example. The variable command is a normal way to document running with a venv, and nothing in the snippet is hidden or malicious.
-
= 1 : | None = += 1likely benign Frame walk to locate the external caller of the module's own functions.Reasoning
Walking up the stack with sys._getframe while skipping frames from the same module is a standard way to find the real caller for warnings or stack-level adjustment. It is a common library pattern, not evasion.
-
info
warn→ info by reviewdynamic-attributeduckdb/experimental/spark/sql/functions.py:6859:9new in this release): =likely benign Module-level registration of Spark-compatible function wrappers via globals().Reasoning
Assigning generated wrapper functions into globals() during module setup is how this PySpark-compatibility layer exposes many named functions. The names come from a known list of Spark functions, so this is ordinary dynamic module construction.
-
info
warn→ info by reviewdynamic-attributeduckdb/experimental/spark/sql/functions.py:6903:9new in this release): =likely benign Second globals() registration of a marker-carrying wrapper function.Reasoning
This is the same globals() registration pattern as the earlier finding, wrapping a function and storing it under a name. It is consistent with building a compatibility API and does not hide behaviour.
-
info
warn→ info by reviewframe-introspectiontests/fast/arrow/test_dbapi_arrow.py:702:16new in this release= = . + 2likely benign Test computes the current line number to check where a warning is attributed.Reasoning
In a test, inspect.currentframe().f_lineno is used to compute the expected line number for a warning assertion. It is a routine testing technique with no execution or concealment involved.
-
info
warn→ info by reviewdynamic-executiontests/fast/test_versioning.py:668:9new in this release: = assert ==likely benign Test execs a version source file to read its PACKAGE_COMMIT value.Reasoning
The exec runs the contents of a file read from a path into a namespace, then checks PACKAGE_COMMIT. This is a plausible way to load a generated version module in a test. The source is a local file, not a network or encoded payload, but exec on file content is still worth a note, so confidence is moderate.
-
# noqa: D101 : : | None : -
= # noqa: F841 = -
= 2**17 + 1 = -
= = -
= -
= assert assert == -
= -
= -
-
-
=
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.
&&