PyPI / google-cloud-storage / 3.17.1
google-cloud-storage 3.17.1
- Source
- https://github.com/googleapis/google-cloud-python
- Tag scanned
google-cloud-storage-v3.17.1- Directory
packages/google-cloud-storage- Compared with
google-cloud-storage-v3.17.0(0 signals introduced since)- Files
- 274 scanned, 22 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 14 info
- Scan time
- 12.4 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 14 of 14 warn and critical signals; 14 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-20 11:26
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
info
warn→ info by reviewdynamic-importpackages/google-cloud-storage/cloudbuild/run_benchmark_tests.sh:79:1fi # Check and install all dependencies into virtual environmentlikely benign Shell script sources the activate script of its benchmark virtualenv.Reasoning
Sourcing a virtualenv activate script from a path built from a variable is a standard pattern for a CI build script; BENCH_VENV is a local venv directory the script itself creates, so this is not a malicious dropper.
-
info
warn→ info by reviewdynamic-attributepackages/google-cloud-storage/tests/conformance/test_conformance.py:1003:21= f =likely benign Generates test case functions and registers them in module globals via a name-keyed assignment.Reasoning
Dynamically assigning generated test functions into globals() is a common pytest/unittest parameterization technique; the names are built from test IDs and method names, not from untrusted input.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_blob.py:397:29= b = = =likely benign Base64-encoded test fixture for an encryption key header in a unit test.Reasoning
The value is a base64 encoding of the hex key shown on the previous line (YWE0MjYxOTU0MDVhZGVlMmM4MDgxYmI5ZTdlNzRiMTk= decodes to aa426195405adee2c8081bb9e7e74b19), i.e. a test fixture for customer-supplied encryption headers, not obfuscation.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_blob.py:398:34= = = =likely benign Base64-encoded key hash test fixture for request headers.Reasoning
A base64 SHA-256 hash of the key used as a test header value in a storage client unit test; it is expected test data.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_blob.py:2676:29, , = = =likely benign Base64 encryption key header fixture in a blob unit test.Reasoning
Base64 header key value in a unit test for encryption headers, paired with a matching hash constant; standard fixture data.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_blob.py:2677:34= =likely benign Base64 key hash fixture used in a mocked unit test.Reasoning
Base64 SHA-256 key hash fixture used in a patch context in a test; expected test data with no execution of the decoded content.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_client.py:2918:28=likely benign Base64-encoded JSON policy document expected in a signed-URL test.Reasoning
The string starts with eyJ (base64 of a JSON object) and decodes to a signed URL policy document with conditions like bucket and acl; it is a test expectation for a signed policy, not hidden code.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_client.py:2958:28=likely benign Base64-encoded JSON policy expectation in a client unit test.Reasoning
Base64-encoded JSON policy fixture for a signed URL test; decodes to readable policy conditions and is only compared against output.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_client.py:2998:28=likely benign Base64-encoded JSON policy expectation for a signed upload test.Reasoning
Base64 JSON policy with field and date conditions, used as an expected value in a signed-policy test; benign test data.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_client.py:3115:28=likely benign Base64-encoded JSON policy expectation in a client unit test.Reasoning
Base64 JSON policy fixture with algorithm and credential fields, a standard expected value in signed URL tests.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_client.py:3141:28=likely benign Base64-encoded JSON policy expectation in a signed-policy test.Reasoning
Base64 JSON policy string matching the pattern of other expected signed-policy fixtures; no executable payload is decoded or run.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_client.py:3186:28=likely benign A base64-encoded JSON upload policy string used as an expected value in a unit test for a cloud storage client.Reasoning
The blob is a base64-encoded JSON policy document (decodes to conditions with bucket, acl, starts-with, x-goog-date fields), which is a typical signed-upload policy fixture in a Google Cloud storage client unit test. Raw pass has a high false-positive rate for base64 test fixtures, and the content is benign test data.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_transfer_manager.py:1225:39: , : , : , : ,likely benign A base64-encoded dummy AES encryption key used in a transfer manager unit test header fixture.Reasoning
The value is a base64 encryption key header in a test for customer-supplied encryption headers (X-Goog-Encryption-Key), which is an expected, legitimate fixture. Its decoded form is a plain ASCII string, consistent with a dummy test key.
-
info
warn→ info by reviewencoding-base64packages/google-cloud-storage/tests/unit/test_transfer_manager.py:1226:46: , : , : , : ,likely benign A base64-encoded SHA256 key digest header value used in a transfer manager unit test.Reasoning
This is the SHA256 digest header paired with the test encryption key in a unit test fixture for encrypted transfers. Raw base64 match in a test file with expected header values is a common false positive with no obfuscation or malicious behavior.
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.
&&