PyPI / google-auth / 2.62.0
google-auth 2.62.0
- Source
- https://github.com/googleapis/google-cloud-python
- Tag scanned
google-auth-v2.62.0- Directory
packages/google-auth- Compared with
google-auth-v2.61.0(0 signals introduced since)- Files
- 237 scanned, 44 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 39 info
- Scan time
- 24.9 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 37 of 37 warn and critical signals; 37 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-21 23:53
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
* -
- -
# e.g. --executable-command="/path/to/command --foo=bar" --executable-command= \ # Optional argument for the executable timeout. Defaults to 30s. # --executable-timeout-millis=$EXECUTABLE_TIMEOUT \likely benign RST docs showing an embedded bash example with a placeholder executable command for a Google auth config.Reasoning
Documentation example of a CLI flag whose value is a placeholder variable in an embedded shell snippet; the flagged 'dynamic execution' is the documented executable command the user configures. Not malicious.
-
# e.g. --executable-command="/path/to/command --foo=bar" --executable-command= \ # Optional argument for the executable timeout. Defaults to 30s. # --executable-timeout-millis=$EXECUTABLE_TIMEOUT \likely benign Duplicate embedded bash example in the user guide documenting executable-command configuration.Reasoning
Same documentation pattern repeated elsewhere in the guide; placeholder variable in a usage example, no concealment or malicious payload.
-
# --executable-output-file=$EXECUTABLE_OUTPUT_FILE \ --workforce-pool-user-project= \likely benign Docs example showing CLI flags for workforce pool configuration in an embedded bash block.Reasoning
Documentation example passing a workforce pool project variable to a CLI flag; the variable name is a configuration value, not dynamic execution of attacker-controlled code.
-
=likely benign setup.py executes the package's own version.py to read __version__ at build/import time.Reasoning
Standard setup.py idiom reading google/auth/version.py and exec'ing it to obtain __version__. It is a known pattern in Google client libraries, though exec on file contents is worth noting; the file is packaged source, not remote input.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/compute_engine/test__metadata.py:43:7b b b blikely benign Test fixture containing a PEM certificate encoded as byte-string lines.Reasoning
Lines are a PEM certificate fixture split into byte literals in a test file; the base64 is expected content, not obfuscation.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/test_agent_identity_utils.py:32:7b b b blikely benign Test fixture with a PEM certificate split across byte-string lines.Reasoning
Test certificate fixture in PEM format; base64 content is expected for certificate test data.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/test_agent_identity_utils.py:60:7b b b blikely benign Second PEM certificate test fixture in the agent identity tests.Reasoning
Another PEM certificate test fixture in a unit test; legitimate test data.
-
= # To avoid json.dumps() differing behavior from one version to other,likely benign AWS example session token string used as test data.Reasoning
AWS documentation example token (AQoEXAMPLE... pattern) used in tests for AWS signing; obviously placeholder credential material, not a live secret or obfuscation.
-
:likely benign AWS Signature V4 example header in a test fixture.Reasoning
AWS SigV4 example Authorization header from the AWS documentation test vectors (AKIDEXAMPLE); the hex signature is expected test data.
-
:likely benign Duplicate AWS SigV4 example Authorization header in tests.Reasoning
Repeated AWS SigV4 test vector with example credentials; legitimate test data.
-
:likely benign Third AWS SigV4 example Authorization header in tests.Reasoning
Repeated AWS SigV4 test vector with example credentials; legitimate test data.
-
:dismissed AWS Signature V4 test vector in an Authorization header, misflagged as base64.Reasoning
The flagged 74-byte value is the hex SigV4 Signature inside an AWS Authorization header. The AKIDEXAMPLE credential and host.foo.com are the standard AWS documentation test vectors, and the file is a test suite. A raw-pass base64 heuristic firing on a hex digest is a false positive.
-
:dismissed AWS SigV4 test-vector signature in a test file, misflagged as base64.Reasoning
Same pattern as the other findings: a hex SigV4 signature in an AWS documentation example inside a test file. The base64 signal is a false positive from a raw-byte heuristic.
-
:dismissed AWS SigV4 example signature in a test fixture, misflagged as base64.Reasoning
A hex SigV4 signature in a standard AWS example Authorization header, with AKIDEXAMPLE and host.foo.com placeholders. This is a legitimate test fixture and not an encoded payload.
-
:dismissed AWS SigV4 test-vector signature, misflagged as base64.Reasoning
The flagged blob is a 64-character hex signature in an AWS test vector. Placeholder credentials and host confirm it is a fixture, so the raw base64 heuristic is misfiring.
-
:dismissed AWS SigV4 test-vector signature, misflagged as base64.Reasoning
Hex SigV4 signature in an AWS documentation-style test header with example credentials. Not obfuscation; a false positive from the raw pass.
-
:dismissed AWS SigV4 test-vector signature in a test fixture, misflagged as base64.Reasoning
Hex SigV4 signature in a signed-headers test case using AKIDEXAMPLE and host.foo.com placeholders. Legitimate test fixture; the base64 signal is spurious.
-
:dismissed AWS SigV4 test-vector signature, misflagged as base64.Reasoning
A hex signature in an AWS SigV4 test header using placeholder credentials. The raw-pass base64 detection is a false positive on a hexadecimal digest.
-
:dismissed AWS SigV4 test-vector signature, misflagged as base64.Reasoning
Hex SigV4 signature in an AWS example Authorization header inside a test module. Benign fixture data flagged by a high-false-positive raw heuristic.
-
:dismissed AWS SigV4 test-vector signature, misflagged as base64.Reasoning
A 64-character hex signature in an AWS SigV4 test header with placeholder credentials and host. Not an encoded dropper or hidden payload.
-
:dismissed AWS SigV4 test-vector signature, misflagged as base64.Reasoning
Hex SigV4 signature in a standard AWS test vector with AKIDEXAMPLE and host.foo.com placeholders. Legitimate test data; the base64 finding is spurious.
-
+ + , : ,dismissed SigV4 signature generated in an EC2 signing test, misflagged as base64.Reasoning
The blob is a hex SigV4 signature built in a test that concatenates an access key ID into an EC2 credential scope. The host ec2.us-east-2.amazonaws.com is a real endpoint but the code is a signing test, not a payload. The base64 signal is a false positive.
-
+ + , : ,likely benign AWS SigV4 test Authorization header containing a hex signature.Reasoning
Raw-pass base64 heuristic hit on a hex signature string inside an AWS SigV4 Authorization header in a test file. Test fixture with no execution or concealment; the signature is a hex digest, not an obfuscated payload.
-
+ + , : , : ,likely benign AWS SigV4 test Authorization header with a hex signature.Reasoning
Same pattern as the other AWS test: a SigV4 Authorization header with a hex signature in a unit test. Raw-pass heuristic on a legitimate fixture value.
-
+ + , : ,likely benign DynamoDB SigV4 test Authorization header with a hex signature.Reasoning
DynamoDB SigV4 test header with a hex signature string. Legitimate test fixture flagged by a high-false-positive raw heuristic.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test__custom_tls_signer.py:82:44assertlikely benign Assertion comparing a base64-encoded signature to an expected value.Reasoning
Base64 encoding of a signature is compared to an expected literal inside an assert. This is ordinary test assertion code with no decoding or execution.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test__mtls_helper.py:36:1= blikely benign Encrypted EC private key PEM fixture in an mTLS helper test.Reasoning
Encrypted PEM private key literal used as a test fixture for mTLS helper code. Standard test data, not a dropper or hidden payload.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test__mtls_helper.py:45:1= blikely benign EC public key PEM fixture in a test.Reasoning
PEM public key constant in a test module. Standard fixture data flagged by the raw base64 heuristic.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test__mtls_helper.py:108:9= blikely benign Dummy PRIVATE KEY PEM fixture in a test.Reasoning
Dummy PEM private key literal used as test input for key-parsing code. Fixture data, not malicious.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test__mtls_helper.py:112:9= blikely benign Dummy RSA private key PEM fixture in a test.Reasoning
Dummy RSA private key PEM literal in a test file, used to exercise key handling. Ordinary test data.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test__mtls_helper.py:116:9= blikely benign Dummy EC private key PEM fixture in a test.Reasoning
Dummy EC private key PEM literal in a test file. Standard fixture; the repeated body reflects test data, not hidden code.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test_requests.py:73:47= blikely benign Mock certificate PEM constant in a requests transport test.Reasoning
Certificate PEM bytes used as a mock value in a transport test. Standard certificate test data flagged by the raw base64 heuristic.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test_requests.py:1076:50= blikely benign Old certificate PEM constant in a requests transport test.Reasoning
Old certificate PEM bytes assigned in a test for certificate handling. Fixture data with no execution or concealment.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test_requests.py:1200:50= blikely benign A PEM-encoded test certificate embedded as a bytes literal in a transport test.Reasoning
The snippet is a PEM certificate literal in a test file, with standard BEGIN CERTIFICATE framing and base64 rows. Certificates are base64 by design, and the raw pass flags them as encoded blobs with a low compression ratio that is expected for base64 of DER data. No decoding or execution is present.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test_urllib3.py:29:47= blikely benign A mock PEM certificate constant for urllib3 transport unit tests.Reasoning
This is a PEM certificate constant used as mock data in a urllib3 transport test. Base64 DER content inside a BEGIN CERTIFICATE block is the normal representation of certificates, and nothing decodes or executes it.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test_urllib3.py:458:50= blikely benign A test-fixture PEM certificate in the urllib3 transport tests.Reasoning
Same PEM certificate literal pattern as the other test certificates: a BEGIN CERTIFICATE block with base64 rows, used as test fixture data. The raw-pass base64 signal reflects normal certificate encoding, not obfuscation.
-
info
warn→ info by reviewencoding-base64packages/google-auth/tests/transport/test_urllib3.py:577:50= blikely benign A PEM certificate fixture in urllib3 transport tests.Reasoning
A PEM certificate bytes literal in a test file, with the same structure as the other flagged certificate fixtures. Base64 is the standard format for certificates, and the code only uses the value as test data.
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.
&&