joserfc 1.7.7
- Source
- https://github.com/authlib/joserfc
- Artifact scanned
joserfc-1.7.7-py3-none-any.whl- Compared with
joserfc-1.7.6-py3-none-any.whl(0 signals introduced since)- Files
- 56 scanned, 5 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 3 info
- Scan time
- 4.8 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 3 of 3 warn and critical signals; 3 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 10:12
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
= =likely benign JWE decompression of DEF/GZIP-compressed plaintext using zlib, as required by RFC 7516.Reasoning
This is the standard DEFLATE/gzip decompression path for JWE 'zip' header parameter (RFC 7516), using zlib.decompressobj with raw deflate window bits for DEF and gzip header detection for GZIP. Decompressing attacker-supplied payload is the expected function of a JWE decoder; the scanner flags the generic decompress call, not an obfuscated dropper.
-
-likely benign Base64url-looking sample string, likely an example JWE token or key value in a library file.Reasoning
Raw pass base64-like blob in a JOSE library docstring or test-vector style example; the text is a long base64url string with low compression ratio, typical of RFC example ciphertext or key material in documentation. Raw-pass findings have high false-positive rates and no code execution is involved.
-
. .likely benign Base64url-encoded example JWS payload (RFC 7515 sample claims) embedded in source.Reasoning
The snippet decodes to a JSON object with iss/exp/http claims, i.e. the RFC 7515 example JWS payload used in documentation or a docstring. It is a plain base64url-encoded example token with no execution path, so it is a legitimate pattern.
Reproduce This Scan
Run disclude locally to verify. These commands scan the published file; the "new in this release" marks come from comparing it with the previous release's file, which they don't repeat. Add --format sarif for SARIF output. Add --llm (with an API key in the environment) to include the LLM review.
|