botocore 1.43.116
- Source
- https://github.com/boto/botocore
- Tag scanned
1.43.116- Compared with
1.43.115(0 signals introduced since)- Files
- 331 scanned, 3148 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 30 info
- Scan time
- 23.1 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 30 of 30 warn and critical signals; 30 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-21 00:56
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
"""Import module, returning the module after the last dot.""" returnlikely benign Vendored six compatibility helper that dynamically imports a module by name.Reasoning
six.py's import_module helper is the standard compatibility shim calling __import__ on a parameter; this is a known legitimate pattern in the vendored six library, not a dropper.
-
= =likely benign Vendored six exec_ helper fetching caller frame globals for default execution scope.Reasoning
sys._getframe(1) inside six's exec_ wrapper is used to default globals/locals for exec when caller does not supply them; standard six code, the anti-analysis label is a false association.
-
editor = env.get('VISUAL', env.get('EDITOR', 'vim')) p = subprocess.Popen(f'{editor} {f.name}', shell=True) p.communicate() with open(f.name) as f:likely benign Developer script opening the user's editor on a temporary file via shell=True.Reasoning
Launches the user's $VISUAL/$EDITOR via shell with a temp file name; a common editor-invocation pattern in a dev script. Minor injection surface but not malicious.
-
= f = assert ==likely benign Functional test decompressing a gzip request body to check its contents.Reasoning
Test code decompressing a gzip request body captured by a stubber to verify serialization; ordinary test assertion, no embedded payload executed.
-
: , : , }, ),likely benign Expected x-amz-checksum-sha256 header value in an HTTP checksum test.Reasoning
Base64 SHA256 checksum expected value in an AWS SDK test fixture; test data, not obfuscation.
-
: , : , }, ),likely benign Expected x-amz-checksum-sha512 header value in an HTTP checksum test.Reasoning
Base64 SHA512 checksum value in test fixture for AWS checksum headers.
-
, ),likely benign Expected SHA256 checksum header in a test case.Reasoning
Same SHA256 checksum test fixture repeated; legitimate test data.
-
, ),likely benign Expected SHA512 checksum header in a test case.Reasoning
Same SHA512 checksum test fixture; legitimate test data.
-
, ),likely benign Expected SHA256 checksum header in a test case.Reasoning
Repeated SHA256 checksum test fixture; legitimate test data.
-
, ),likely benign Expected SHA512 checksum header in a test case.Reasoning
Repeated SHA512 checksum test fixture; legitimate test data.
-
, , ),likely benign Parametrized test expected SHA256 checksum value.Reasoning
Checksum expected-value tuple in parametrized test; base64 of known digest, benign.
-
, , ), ]likely benign Parametrized test expected SHA512 checksum value.Reasoning
Checksum expected-value tuple in parametrized test; benign test data.
-
info
warn→ info by reviewencoding-base64tests/unit/auth/aws4_testsuite/post-sts-token/readme.txt:15:1AQoDYXdzEPT//////////wEXAMPLEtc764bNrC9SAPBSM22wDOk4x4HIZ8j4FZTwdQWLWsKWHGBuFqwAeMicRXmxfpSPfIeoIYRqTflfKD8YUuwthAx7mSEI/qkPpKPi/kMcGdQrmGdeehM4IC1NtBmUpp2wUE8phUZampKsburEDy0KPkyQDYwT7WZ0wq5VSXDvp75YU9HFvlRd8Tx6q6fE8YQcHNVXAkiY9q6d+xo0rKwT38xVqr7ZD0u0iPPkUL64lIZbqBAz+scqKmlzm8FDrypNC9Yjc8fPOLn9FX9KSYvKTr4rvx3iSIlTJabIlikely benign Sample AWS STS session token in SigV4 test suite documentation.Reasoning
AWS Signature V4 test-suite readme containing an example session token (EXAMPLE-marked sample credential); documentation data, not obfuscation.
-
, , )likely benign Expected base64 value in a signer test case.Reasoning
Expected base64 digest in a signer unit test for URL-encoded input; test fixture.
-
, , )likely benign Expected AWS request signature constant in a signer unit test.Reasoning
The blob is an expected HMAC-SHA256 signature value in a unit test assertion, compared against computed output. Raw-pass base64 heuristics fire on any 44-char base64 string, and this one sits in a test fixture.
-
: , : , } =likely benign Test-fixture signature value passed into a signer test.Reasoning
The value is the 'Signature' entry of a test params dict used as input to calc_signature. It is a fixture with no decoding or execution path.
-
, , )likely benign Expected signature in a tuple assertion in a signer test.Reasoning
The base64 string is an expected-result tuple member in an assertEqual against signer output. It is a test expectation, not a payload.
-
, , )likely benign Expected signature constant in a signer test assertion.Reasoning
This is an expected signature value compared with assertEqual in a test of request params. It is a fixture constant.
-
), )likely benign Expected AWS3-HTTPS Authorization header value in a test.Reasoning
The string is a fixture Authorization header signature inside a test expectation for the AWS3-HTTPS scheme. No runtime decode or execution is present.
-
: , : , :likely benign Dummy bearer token fixture used in an auth header test.Reasoning
The token decodes to the joke string "you're not supposed to decode this!". It is a dummy bearer token in a test case with no decoding or execution behavior in the snippet.
-
: , },likely benign Expected Bearer Authorization header with a dummy token.Reasoning
This is the same dummy token appearing in the expectedHeaders of the test case. It is test data.
-
=likely benign Gzip-compressed request body fixture in a compression test.Reasoning
The bytes literal begins with the gzip magic header (\x1f\x8b) and is a recorded compressed request body fixture for a compression test. Binary escapes are the expected form for such data.
-
likely benign Binary event-stream header fixture for an eventstream parser test.
Reasoning
The bytes are AWS event-stream binary header encoding (type/length-prefixed headers) in a parser test fixture. The escape density matches binary protocol data written in test code.
-
=likely benign Serialized event-stream headers fixture in an eventstream test.Reasoning
This is a binary header-encoding fixture ('bytes', 'utf8' header names and types) in an eventstream test. It is a serialized protocol sample, not a payload that executes.
-
, ,likely benign Known-answer checksum digests in an HTTP checksum test table.Reasoning
These are expected base64 digests for SHA-1 and SHA-256 test vectors paired with checksum classes. They are known-answer test data.
-
, , ), ]likely benign Expected SHA-512 checksum vector in a parametrized test.Reasoning
This is the expected SHA-512 base64 digest in a parametrized checksum test table. It is a known-answer test vector.
-
= =likely benign Encoded pagination token fixture for a paginator test.Reasoning
The string is a base64 pagination token encoding JSON with bytes-encoded keys, provided as test input to a paginator decode test. It is application test data.
-
=likely benign Multi-line base64 pagination token fixture in a paginator test.Reasoning
This is a multi-part base64 pagination token fixture used to exercise paginator token decoding. The content is ordinary test data.
-
=likely benign A base64-encoded pagination token fixture (boto-style continuation token) in a Python unit test.Reasoning
The raw pass flagged a base64 blob in a unit test. It decodes to JSON with a 'boto_encoded_keys' field and nested 'foo'/'bar'/'bin' keys, which is the format of a pagination continuation token. The test expects a dict with b'baz' and b'bam' values, so this is a test fixture for encoded pagination tokens, not a payload. Raw-pass findings have a high false-positive rate, and nothing here is executed or hidden.
-
) =likely benign Continuation of the same base64-encoded pagination token fixture in the unit test.Reasoning
This is the second half of the same base64 string split across adjacent literals, flagged again by the raw pass. It is the continuation of the pagination token fixture that the test decodes and compares against the expected dict. No decoding or execution of the blob occurs in the snippet, and the surrounding code is a test assertion.
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.
&&