PyPI / python-dateutil / 3.0.0
python-dateutil 3.0.0
- Source
- https://github.com/dateutil/dateutil
- Artifact scanned
python_dateutil-3.0.0-py2.py3-none-any.whl- Compared with
python_dateutil-2.9.0.post0-py2.py3-none-any.whl(1 signals introduced since)- Files
- 22 scanned, 5 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 2 info
- Scan time
- 3.2 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-10-22 23:39
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
warn→ info by reviewframe-introspectiondateutil/zoneinfo/__init__.py:39:13new in this release= 1 = # The body of this module =likely benign dateutil's zoneinfo module uses sys._getframe to walk the call stack to its own module frame, a benign introspection idiom.Reasoning
This is a known dateutil pattern in zoneinfo/__init__.py that uses sys._getframe to locate the module's own frame so it can compute the module's path (used for resolving the bundled tarball/caching). It only walks f_back to the top of the stack and does not execute code, decode data, or touch the network. The snippet and file context point to legitimate use.
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.
|