oauthlib 4.0.0
- Source
- https://github.com/oauthlib/oauthlib
- Tag scanned
v4.0.0- Compared with
v3.3.1(0 signals introduced since)- Files
- 229 scanned, 21 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 10 info
- Scan time
- 7.4 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 10 of 10 warn and critical signals; 10 demoted to info.
- Disclude version
- 4.1.0
- Scanned (UTC)
- 2026-10-22 02:40
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
= \ =likely benign Expected HMAC-SHA256 signature value in an OAuth1 test vector.Reasoning
The blob is an expected HMAC-SHA256 signature constant in a unit test for an OAuth1 library. Test vectors like this are normal, and the raw base64 pattern alone is not evidence of obfuscation.
-
=likely benign Expected HMAC-SHA512 signature value in an OAuth1 test vector.Reasoning
The split string is an expected HMAC-SHA512 signature constant used for assertions in an OAuth1 signature test suite. This is ordinary test data.
-
----- ----- //4rEKJopeQRRKKpZI4s5i+ 5IYGhBi2E9ycNS329W27nJPWNCbESTu7snVlG8V8mfvGGg3xNjTMO7IdrwIDAQABlikely benign Embedded RSA private key used as a test fixture.Reasoning
This is a PEM-encoded RSA private key in a test file for an OAuth library, consistent with published RFC 5849 test vectors. It is a known test key, not a live credential or an obfuscated payload.
-
----- ----- // / +8YaDfE2NMw7sh2vAgMBAAE=likely benign Embedded RSA public key used as a test fixture.Reasoning
This is a PEM-encoded RSA public key in a test fixture for an OAuth library. Public keys in tests are routine and carry no malicious signal.
-
=likely benign Expected RSA-SHA1 signature value in an OAuth1 test vector.Reasoning
The split lines form an expected RSA-SHA1 signature constant in an OAuth1 test. This is standard test data in a signature-verification suite.
-
----- ----- /1OZNJJ6Y3QZM16Z+ +/ //+7DP01OWMfWS99S7eQIDAQABlikely benign Embedded RSA private key used as a test fixture.Reasoning
This is another PEM-encoded RSA private key in an OAuth test file, the same kind of fixture as the other key blocks. The context points to test data, not an attack payload.
-
info
warn→ info by reviewencoding-base64tests/oauth2/rfc6749/clients/test_service_application.py:20:1----- ----- //4rEKJopeQRRKKpZI4s5i+ 5IYGhBi2E9ycNS329W27nJPWNCbESTu7snVlG8V8mfvGGg3xNjTMO7IdrwIDAQABlikely benign Embedded RSA private key in an OAuth2 client test.Reasoning
This PEM RSA private key appears in an OAuth2 client test file. Test keys like this are common in authentication library test suites.
-
info
warn→ info by reviewencoding-base64tests/oauth2/rfc6749/clients/test_service_application.py:38:1----- ----- //4rEKJ +likely benign Embedded PEM public key in an OAuth2 client test.Reasoning
This is a PEM public key block in an OAuth2 client test, consistent with a fixture for JWT or service-application testing. It is not an encoded dropper or obfuscated code.
-
----- ----- / /+likely benign Embedded RSA private key in an OAuth2 server test.Reasoning
This PEM RSA private key sits in an OAuth2 server test file. It is a conventional test fixture and the base64 pattern is expected for PEM data.
-
----- ----- / 5laMGbj1pPyCPxlVi9LK82HQNX0BYK7tZtVfDHElQA7F4v3j9d3rad4O9/+likely benign Embedded PEM public key in an OAuth2 server test.Reasoning
This is a PEM public key in an OAuth2 server test file, a routine fixture. The raw base64 detection reflects PEM formatting, not hidden code.
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.
&&