PyPI / aiobotocore / 3.9.2
aiobotocore 3.9.2
- Source
- https://github.com/aio-libs/aiobotocore
- Tag scanned
3.9.2- Compared with
3.9.1(0 signals introduced since)- Files
- 147 scanned, 34 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 4 info
- Scan time
- 5.5 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 4 of 4 warn and critical signals; 4 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-21 21:43
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
dismissed Changelog entry linking to a GitHub PR diff; the flagged base64-like string is a diff anchor hash.
Reasoning
The blob is a GitHub diff anchor fragment (#diff-b1675e...R162-R181) inside a changelog link. It is a hash in a URL, not an encoded payload. Benign documentation text.
-
info
warn→ info by reviewpayload-bytes-literaltests/botocore_tests/unit/test_eventstream.py:149:9likely benign Binary event-stream test vector with header bytes in a botocore-derived unit test.Reasoning
This is a test fixture for AWS event-stream binary parsing. The byte escapes encode prelude, CRC and header fields, which is the expected shape for testing a binary protocol decoder in a botocore-derived test suite. Not malicious.
-
info
warn→ info by reviewpayload-bytes-literaltests/botocore_tests/unit/test_eventstream.py:350:9=likely benign Encoded event-stream headers used as test input for a binary protocol parser.Reasoning
Same pattern as the sibling finding: encoded event-stream header data (type/length-prefixed names like 'bytes', 'utf8') used as a parser test fixture. Legitimate test data.
-
b, b b blikely benign Event-stream framed sample response in a test file for decoding AWS-style eventstreams.Reasoning
The literal contains AWS event-stream framing with readable embedded XML and JSON, consistent with a test case for decoding eventstream responses. The escapes are protocol framing bytes, not an obfuscated payload.
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.
&&