disclude.iobase64 0.23.1
- Source
- https://github.com/marshallpierce/rust-base64
- Artifact scanned
base64-0.23.1.crate- Compared with
base64-0.23.0.crate(0 signals introduced since)- Files
- 30 scanned, 9 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 9 info
- Scan time
- 6.6 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 9 of 9 warn and critical signals; 9 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-24 01:15
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
assert_eq!;likely benign Unit test asserting the chunked base64 encoder output for a fixed input.Reasoning
The snippet is an assert_eq comparing a known base64 string against chunked_encode_str output for a fixed plaintext. This is a standard encoder unit test with expected output, not obfuscation.
-
let alphabet = new_with_paddinglikely benign Test constructing a custom base64 alphabet with padding symbol.Reasoning
The literal is a custom 64-character alphabet passed to Alphabet::new_with_padding in a test. Custom alphabets are a normal feature of a base64 library and the file is a test module.
-
likely benign Test fixture containing a malformed base64 string to exercise invalid-suffix handling.
Reasoning
The high-entropy literal is test input for a test named detects_users_real_world_invalid_suffix, used to check decoding of a malformed base64 string. It is data for a decoder test, not a payload being executed.
-
likely benign Same malformed base64 test fixture, flagged for high complexity.
Reasoning
This is the same test fixture literal as the base64 finding on the same line, flagged for low compression. Random-looking test data is expected for a base64 decoder test.
-
compare_encodelikely benign Test vector of all byte values in base64 for an encode comparison.Reasoning
The literal is the sequential byte sequence 0x00 to 0xFF encoded in base64 with a padding character, used as an expected encoding vector in a conformance test.
-
"AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1Njc4OTo7P\ D0+P0BBQkNERUZHSElKS0xNTk9QUVJTVFVWV1hZWltcXV5fYGFiY2RlZmdoaWprbG1ub3BxcnN0dXZ3eHl6e3x9fn8\ =", &ascii,likely benign Continuation of the all-bytes base64 test vector.Reasoning
This is the continuation of the same all-bytes base64 test vector, split across string-continuation lines in a test file.
-
compare_encodelikely benign Multi-line base64 expected output in an encoding comparison test.Reasoning
The multi-line base64 literal is a sequential-byte encoding expected output in a compare_encode test. Its line layout is consistent with a test table.
-
assert_eq!likely benign URL-safe base64 expected output for the all-bytes vector in a test assertion.Reasoning
This is another expected base64 encoding of sequential bytes used in an assert_eq within a conformance test, using the URL-safe alphabet with '-' characters.
-
"AAECAwQFBgcICQoLDA0ODxAREhMUFRYXGBkaGxwdHh8gISIjJCUmJygpKissLS4vMDEyMzQ1Njc4OTo7PD0\ -P0BBQkNERUZHSElKS0xNTk9QUVJTVFVWV1hZWltcXV5fYGFiY2RlZmdoaWprbG1ub3BxcnN0dXZ3eHl6e3x9fn\ -AgYKDhIWGh4iJiouMjY6PkJGSk5SVlpeYmZqbnJ2en6ChoqOkpaanqKmqq6ytrq\likely benign Continuation of the URL-safe all-bytes base64 test vector.Reasoning
This is the continuation of the URL-safe all-bytes test vector in the same assertion, consistent with a standard encoding test.
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.
|
&&