bcrypt 5.0.0
- Source
- https://github.com/pyca/bcrypt
- Tag scanned
5.0.0- Compared with
4.3.0(0 signals introduced since)- Files
- 8 scanned, 6 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 22 info
- Scan time
- 12.7 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 22 of 22 warn and critical signals; 22 demoted to info.
- Disclude version
- 4.0.0
- Scanned (UTC)
- 2026-10-14 18:48
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
likely benign Binary test vector bytes literal in bcrypt test suite.
Reasoning
This is a bcrypt test file containing binary test vectors (hashes/salts) written as bytes literals. Binary test vectors in a crypto library test suite are expected, not a payload.
-
likely benign Binary known-answer test vector in bcrypt tests.
Reasoning
Same pattern: binary known-answer test data in a bcrypt test file, consistent with legitimate cryptographic test vectors.
-
b, b b, ],likely benign 16-byte salt/hash test vector in test parameter list.Reasoning
Bytes literal of 16-byte values adjacent to b"salt" in a test parameter list is a typical KDF/bcrypt test vector layout.
-
b, b b, ],likely benign Hex-escaped test vector bytes in bcrypt test.Reasoning
Raw-pass hex escape run is just the same test vector bytes; high-entropy binary data is expected for salts and hashes in crypto tests.
-
b b, ],likely benign Hex-escaped test vector bytes in bcrypt test.Reasoning
Continuation of the same test vector list; expected binary test data in a bcrypt test file.
-
b, b, ],likely benign Hex-escaped test vector bytes in bcrypt test.Reasoning
Test vector data alongside b"\x00" and other salts in a parameterized bcrypt test; benign.
-
b, b, ],likely benign Hex-escaped test vector bytes in bcrypt test.Reasoning
Hex-escaped 16-byte test vector in a bcrypt test case; expected for cryptographic known-answer tests.
-
b, b b, ],likely benign 32-byte binary test vector in bcrypt tests.Reasoning
Binary test vector in bcrypt test file with salt bytes; no execution or decoding of a payload.
-
b, b b, ],likely benign Hex-escaped test vector bytes in bcrypt test.Reasoning
Hex-escaped test vector bytes as part of the same expected-output data in the bcrypt test suite.
-
b b, ],likely benign Hex-escaped test vector bytes in bcrypt test.Reasoning
Continuation of the test vector list; benign binary test data.
-
b, b, ],likely benign Hex-escaped test vector bytes with NUL-containing salt.Reasoning
Test vector with a salt containing an escaped NUL in a bcrypt test; benign test data.
-
b, b, ],likely benign Hex-escaped test vector bytes in bcrypt test.Reasoning
Same kind of binary test vector in bcrypt tests; no decoding or execution path.
-
b, b b blikely benign Concatenated binary salt and hash test vector in the bcrypt test suite.Reasoning
The bytes literal is a run of 64 escaped bytes spread over concatenated string lines, a standard way to write fixed binary test vectors. The file is a bcrypt test suite with salt and hash-like byte arrays, and the file context points to a legitimate test fixture, not a payload.
-
b, b b bdismissed Rows of hex-escaped bytes forming bcrypt test vector salts and digests.Reasoning
Hex escape runs are how binary test vectors are written in Python. The surrounding code is a bcrypt test file that passes salts and expected digests as bytes, so the entropy is expected for cryptographic test data.
-
b, b, ],dismissed A 16-byte binary test vector in the bcrypt test data.Reasoning
A 16-byte escape run in a bcrypt test case. Random-looking bytes are expected for a cryptographic test vector, and the raw pass has a high false-positive rate for this shape.
-
b, b, ],dismissed A 16-byte binary value in a bcrypt test vector list.Reasoning
A 16-byte hex-escaped value in a list of bcrypt test inputs and expected outputs. This is binary fixture data in a test file.
-
8, b, b, b,dismissed Binary test vector bytes inside a bcrypt test case table.Reasoning
Consecutive hex escapes in a list of bcrypt test vectors. Nothing in the snippet suggests execution or decoding of a payload.
-
b, b, b, ],dismissed A 16-byte binary test vector row in the bcrypt test fixtures.Reasoning
Same pattern as the neighbouring test vector rows: a 16-byte binary literal in a bcrypt test fixture with no decoding or execution.
-
b, b, ],dismissed A 16-byte binary row in the bcrypt test vector table.Reasoning
A 16-byte hex-escaped test vector row in a bcrypt test table, consistent with the other fixture rows in the file.
-
8, b, b, bdismissed Many rows of binary bcrypt test vectors in a test file.Reasoning
A block of 18 escape-run rows in the bcrypt test vector table. The data is cryptographic test material, and the file is a test suite, not shipped code that decodes or runs anything.
-
b, b b blikely benign Long concatenated binary test vector in the bcrypt test suite.Reasoning
A concatenated bytes literal of 256 escapes forms a long binary test vector. The shape matches a payload, but the file is a bcrypt test suite where such vectors are expected, and there is no execution or decoding in the snippet.
-
b, b, ], ],dismissed A 16-byte binary row closing a bcrypt test vector list.Reasoning
A 16-byte hex-escaped row at the end of a bcrypt test vector table. It is test data with no decoding, execution, or network activity.
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.
&&