gitpython 3.2.1
- Source
- https://github.com/gitpython-developers/GitPython
- Artifact scanned
gitpython-3.2.1-py3-none-any.whl- Compared with
gitpython-3.2.0-py3-none-any.whl(0 signals introduced since)- Files
- 38 scanned, 6 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 1 info
- Scan time
- 2.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-23 08:33
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
* ::`` . * :///-///0d9390866f9ce42870d3116094cd49e0019a970a * :///-////--dismissed A commit hash inside a GitHub URL in a GitPython docstring was flagged as a base64-like blob.Reasoning
The flagged 'base64-like blob' is actually a GitHub commit SHA (0d9390866f9ce42870d3116094cd49e0019a970a) inside a URL in a docstring. It is a hex string in a documentation comment, not an encoded payload. Raw-pass base64 heuristics produce false positives on such strings.
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.
|