base64 0.23.1
- Source
- https://github.com/marshallpierce/rust-base64
- Tag scanned
v0.23.1- Compared with
v0.23.0(0 signals introduced since)- Files
- 33 scanned, 8 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 9 info
- Scan time
- 7.8 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 9 of 9 warn and critical signals; 9 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-14 20:13
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
assert_eq!;likely benign A base64 test vector asserted against chunked_encode_str output in a base64 library's test suite.Reasoning
The raw-pass base64 hit is a plain expected-output string in an assert_eq! inside a base64 encoder's unit tests. It is a known test vector, not an obfuscated payload.
-
let alphabet = new_with_paddinglikely benign A custom base64 alphabet literal used to construct an Alphabet in engine tests.Reasoning
The string is a custom 64-character alphabet passed to Alphabet::new_with_padding in a test. This is a configuration fixture for an encoding library, with no execution or exfiltration behavior.
-
likely benign A base64 sample string used as test input for invalid-suffix detection.
Reasoning
The literal is a sample base64 input inside a test named detects_users_real_world_invalid_suffix. It exists to exercise decoder error handling on a suffix, which is ordinary test data.
-
likely benign The same base64 test-input literal, flagged for high string complexity.
Reasoning
This high-complexity hit is the same test-data literal as the base64 finding on the same line. Its high entropy is expected for random-looking encoded sample data in a decoder test.
-
compare_encodelikely benign A sequential-bytes base64 test vector in an encode integration test.Reasoning
This is a sequential byte-range base64 vector (AAEC... through ...fn8=) passed to compare_encode in an encoder integration test. It is a standard exhaustive-alphabet test input.
-
"AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1Njc4OTo7P\ D0+P0BBQkNERUZHSElKS0xNTk9QUVJTVFVWV1hZWltcXV5fYGFiY2RlZmdoaWprbG1ub3BxcnN0dXZ3eHl6e3x9fn8\ =", &ascii,likely benign Continuation of the sequential-bytes base64 test vector in an encode integration test.Reasoning
This continuation line of the same sequential-bytes base64 test vector completes the string in compare_encode. It is test data with no executable or hidden behavior.
-
compare_encodelikely benign Multi-line sequential-bytes base64 test vector in an encode integration test.Reasoning
Rows 26-29 are the same sequential-byte base64 test vector split across lines with backslash continuations. The multi-row pattern is a formatting artifact of a long literal in a test, not a dropper.
-
assert_eq!likely benign Sequential-bytes base64 expected value in an assert_eq! encoder test.Reasoning
This is another line of the sequential-bytes base64 test vector used as an assert_eq! expectation. The context is clearly an encoder correctness test.
-
"AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1Njc4OTo7PD0\ -P0BBQkNERUZHSElKS0xNTk9QUVJTVFVWV1hZWltcXV5fYGFiY2RlZmdoaWprbG1ub3BxcnN0dXZ3eHl6e3x9fn\ -AgYKDhIWGh4iJiouMjY6PkJGSk5SVlpeYmZqbnJ2en6ChoqOkpaanqKmqq6ytrq\likely benign Continuation of the sequential-bytes base64 expected value in an encoder test.Reasoning
This line continues the same sequential-bytes base64 test vector in an encoder test. The repetition of the alphabet bytes is expected for exhaustive encoding coverage.
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.
&&