disclude.iobotocore 1.43.117
- Source
- https://github.com/boto/botocore
- Tag scanned
1.43.117- Compared with
1.43.116(0 signals introduced since)- Files
- 339 scanned, 3127 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 32 info
- Scan time
- 20.2 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 31 of 31 warn and critical signals; 31 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 00:59
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
This is the standard six.py import_module helper, where __import__ on a caller-supplied module name is the documented purpose. Vendored library code, so the dynamic import is legitimate, though it is a generic pattern a scanner would flag.
-
= =likely benign Vendored six exec_ shim using sys._getframe to default to the caller's globals.Reasoning
This is the well-known six.exec_ wrapper that reads the caller's frame globals when none are given, a standard compatibility shim. The flagged sys.exit/exec co-occurrence is a generic heuristic match in a vendored utility, not an anti-analysis technique.
-
likely benign Long inline SVG path data in a docs HTML template.
Reasoning
The long line is an inline SVG path with numeric coordinate data in a documentation template. It is ordinary vector graphics, not hidden content or obfuscated code.
-
-
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 launching the user's editor through a shell on a temp file.Reasoning
The script opens the user's configured VISUAL or EDITOR in a temp file via shell=True. The command is built from environment variables, which is a common and expected pattern for launching an editor, and the file path is a temp file the script created. Low risk, though shell=True with an env-derived string is worth noting.
-
= f = assert ==likely benign Test decompresses a captured gzip request body to validate its contents.Reasoning
This is a test verifying gzip-compressed request bodies sent by the SDK. Decompressing the captured request body in the test is the expected check, not a hidden payload.
-
: , : , }, ),likely benign Base64 SHA256 checksum fixture in an HTTP checksum test.Reasoning
This is a base64-encoded SHA256 checksum value used as a test fixture for an x-amz-checksum header. Checksum strings are expected in AWS SDK test data.
-
: , : , }, ),likely benign Base64 SHA512 checksum fixture in an HTTP checksum test.Reasoning
This is a base64-encoded SHA512 checksum value used as a test fixture for an x-amz-checksum header, consistent with the surrounding test cases.
-
, ),likely benign Base64 SHA256 checksum fixture in an HTTP checksum test.Reasoning
Repeated SHA256 checksum fixture value in a test parametrization, expected test data.
-
, ),likely benign Base64 SHA512 checksum fixture in an HTTP checksum test.Reasoning
Repeated SHA512 checksum fixture value in a test parametrization, expected test data.
-
, ),likely benign Base64 SHA256 checksum fixture in an HTTP checksum test.Reasoning
Repeated SHA256 checksum fixture value in a test parametrization, expected test data.
-
, ),likely benign Base64 SHA512 checksum fixture in an HTTP checksum test.Reasoning
Repeated SHA512 checksum fixture value in a test parametrization, expected test data.
-
, , ),likely benign Base64 SHA256 checksum fixture in a checksum validation test case.Reasoning
Base64 SHA256 checksum fixture alongside a plain-text test value 'bm90LWEtY2hlY2tzdW0=' (not-a-checksum), consistent with test parametrization of checksum validation.
-
, , ), ]likely benign Base64 SHA512 checksum fixture in a checksum validation test case.Reasoning
Base64 SHA512 checksum fixture in a checksum validation test case, matching the surrounding 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 Base64-like AWS STS session token sample from a SigV4 test suite readme.Reasoning
The blob is the AWS SigV4 test-suite example session token (the EXAMPLE string is embedded), a documented public test vector in a readme, not a payload.
-
, , )likely benign Expected base64 HMAC signature constant in signer unit test.Reasoning
Base64 HMAC signature expected value in a unit test asserting signer output; standard test fixture.
-
, , )likely benign Expected HMAC signature string in a signer unit test assertion.Reasoning
Expected signature value compared with assertEqual in a signer test; ordinary test data.
-
: , : , } =likely benign Signature fixture value in a signer unit test.Reasoning
Signature fixture in a test dict for calc_signature; ordinary test data.
-
, , )likely benign Expected signature tuple value in a signer unit test.Reasoning
Expected signature tuple in a signer test; benign fixture.
-
, , )likely benign Expected HMAC signature assertion value in a signer test.Reasoning
Expected signature in an assertion within a signer test; benign.
-
), )likely benign Signature value in an expected auth header in a signer test.Reasoning
Expected Signature value embedded in an Authorization header string in a test; benign.
-
: , : , :likely benign Base64 bearer token test value with a joking plaintext.Reasoning
The decoded text 'you're not supposed to decode this!' is a deliberate test string for bearer token handling; the blob is test data, not hidden payload.
-
: , },likely benign Expected Authorization header bearer token in a test.Reasoning
Same bearer token test fixture repeated in expectedHeaders; benign test data.
-
=likely benign Gzip-compressed request body bytes literal in a compression unit test.Reasoning
A gzip byte stream literal used as a compressed request body fixture in a compression test; binary test data is expected here.
-
likely benign Eventstream binary header bytes literal in a unit test.
Reasoning
Binary eventstream header encoding bytes in a protocol parser test; expected for this format.
-
=likely benign Eventstream header bytes fixture in a unit test.Reasoning
Binary eventstream header fixture data for parser tests; expected for the protocol.
-
, ,likely benign Expected base64 checksum digest values in a checksum test.Reasoning
Expected base64 checksum digests for SHA1/SHA256 in a checksum test table; standard fixture.
-
, , ), ]likely benign Expected base64 SHA512 checksum value in a checksum test.Reasoning
Expected base64 SHA512 checksum value in the same checksum test table; benign fixture.
-
= =likely benign Base64-encoded pagination token used as test input in a paginator unit test.Reasoning
Raw-pass base64 signal in a unit test. The blob decodes to JSON resembling a pagination token ({"boto_encoded_keys": [["foo"]], "foo": "YmFy"}), and the test asserts the decoded value is {'foo': b'bar'}. This is a deliberate test fixture for a pagination round-trip, not a hidden payload.
-
=likely benign Split base64 pagination token fixture in a paginator test.Reasoning
The string is a multi-part base64 pagination token that decodes to structured JSON with nested keys and values. It sits in a test file alongside expected decoded values, which is the normal way to test token parsing. The raw-pass base64 heuristic fires on the length and shape alone.
-
=likely benign Multi-line base64 pagination token fixture for a paginator test.Reasoning
Concatenated base64 literal that decodes to a JSON pagination token with nested lists and dicts. The test's expected value is built from the same content. No execution, no dropper pipeline, and no obfuscated identifiers are present, so this is a test fixture.
-
) =likely benign Continuation of a base64 pagination token fixture in a paginator test.Reasoning
Continuation of the same multi-line base64 pagination token fixture, with the expected decoded structure asserted on the following line. The content is benign test data that the raw-pass heuristic flags only because it looks like base64.
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.
&&