bcrypt 5.0.0
- Source
- https://github.com/pyca/bcrypt
- Artifact scanned
bcrypt-5.0.0.tar.gz- Compared with
bcrypt-4.3.0.tar.gz(0 signals introduced since)- Files
- 10 scanned, 11 skipped (binary, oversized, or unrecognised)
- Signals
- 0 critical · 0 warn · 22 info
- Scan time
- 14.3 s
- LLM review
- Reviewed by claude-haiku-5-5 (Anthropic): 22 of 22 warn and critical signals; 22 demoted to info.
- Disclude version
- 4.3.0
- Scanned (UTC)
- 2026-10-23 08:36
Signals
Ordered by severity, then signals introduced in this release. Hidden characters are shown as ⟨U+…⟩.
-
likely benign Binary test-vector bytes literal in the bcrypt test suite.
Reasoning
The file is a bcrypt test suite, and this bytes literal of 40 \xNN escapes is a binary known-answer test vector (a hash or key-derivation output). Byte-heavy literals are expected in such tests, and nothing in the snippet executes or decodes anything.
-
likely benign Binary test-vector bytes literal in the bcrypt test suite.
Reasoning
Same file and pattern as the other test vectors: a concatenated bytes literal of expected binary output for a bcrypt test. It is data, not code that runs a payload.
-
b, b b, ],likely benign Expected binary digest in a parametrized bcrypt test case.Reasoning
A bytes literal of 32 escapes sits inside a parametrized list of password, salt and expected-output tuples, which is the standard form of known-answer test data in a crypto library's tests.
-
b, b b, ],dismissed Hex escapes forming a random-looking expected digest in a test vector.Reasoning
Raw-pass hex-escape hit on the same expected-digest literal as the adjacent finding. The entropy is what random digest bytes would show, and the surrounding code is a test-vector table, so this is a false positive.
-
b b, ],dismissed Hex escapes forming a random-looking expected digest in a test vector.Reasoning
Raw-pass hit on another expected-output byte literal in the bcrypt test table. Random-looking bytes are normal for hash test vectors, and the file context explains them.
-
b, b, ],dismissed Hex escapes forming a random-looking derived key in a test vector.Reasoning
Raw-pass hit on a 16-byte expected-output literal inside a bcrypt test case list. The entropy is consistent with a derived key, and no decoding or execution is involved.
-
b, b, ],dismissed Hex escapes forming a random-looking expected digest in a test vector.Reasoning
Raw-pass hit on a 16-byte expected-output literal in a bcrypt test table. This is test data with the entropy expected of a hash, not an obfuscated payload.
-
b, b b, ],likely benign Binary test-vector bytes literal in the bcrypt test suite.Reasoning
A 32-byte bytes literal of expected output in a bcrypt known-answer test with a salt that contains a NUL byte. It is a standard test vector with no executable behaviour.
-
b, b b, ],dismissed Hex escapes forming a random-looking expected digest in a test vector.Reasoning
Raw-pass hit on the same expected-output literal as the adjacent finding. The high entropy is what a hash output looks like, so this is a false positive from the raw pass.
-
b b, ],dismissed Hex escapes forming a random-looking expected digest in a test vector.Reasoning
Raw-pass hit on a 16-byte fragment of a bcrypt test vector. The bytes are expected hash output inside the test data, so the finding does not reflect malicious intent.
-
b, b, ],dismissed Hex escapes forming a random-looking expected digest in a test vector.Reasoning
Raw-pass hit on a bytes literal in a bcrypt test case that uses a salt with an embedded NUL. The high-entropy expected output is what a derived key looks like in test data.
-
b, b, ],dismissed Hex escapes forming a random-looking expected digest in a test vector.Reasoning
Raw-pass hit on an expected-output byte literal in the bcrypt test table. It is test data, and the raw pass is known to over-flag this kind of literal.
-
b, b b blikely benign Binary test-vector bytes literal in the bcrypt test suite.Reasoning
A 64-byte bytes literal of expected output in the bcrypt test vectors, using a salt in the surrounding tuple. It is standard known-answer test data in a crypto library and has no executable behaviour.
-
b, b b blikely benign Binary bcrypt test vector bytes written as hex escapes in a test file.Reasoning
The hex escape runs are bcrypt test vectors (salt and hash byte arrays) in a test file for a bcrypt library. Raw byte escapes of this shape are expected for cryptographic test data.
-
b, b, ],likely benign 16-byte bcrypt known-answer test vector as hex escapes.Reasoning
Same test-vector table in a bcrypt test suite; 16-byte hex escape rows are the expected representation of known-answer data.
-
b, b, ],likely benign Test vector bytes in a bcrypt test case.Reasoning
Known-answer test data for bcrypt hashing with a salt string and byte output; no execution or decoding of hidden content.
-
8, b, b, b,likely benign Test vector rows in a bcrypt test file.Reasoning
Consecutive rows of hex-escaped bytes forming a bcrypt test vector, consistent with the rest of the test table.
-
b, b, b, ],likely benign Test vector rows in a bcrypt test file.Reasoning
Continuation of the same bcrypt test-vector table; the bytes are fixed expected outputs for hashing tests.
-
b, b, ],likely benign Test vector rows in a bcrypt test file.Reasoning
Same known-answer test table pattern; nothing in the snippet decodes or executes the bytes.
-
8, b, b, blikely benign Eighteen rows of bcrypt test vector bytes.Reasoning
Large block of test vectors for bcrypt in a test module. The escapes are literal test data, the same style as the other findings in this file.
-
b, b b blikely benign Concatenated bytes literal of bcrypt test vector data.Reasoning
The AST pass flags a concatenated bytes literal as a payload shape, but in a bcrypt test file this is the expected expected-output table for hash comparisons. No dynamic execution, decoding or network use is present in the snippet.
-
b, b, ], ],likely benign Bytes test vector for bcrypt tests with non-ASCII input.Reasoning
Test vector bytes in a bcrypt test suite, including UTF-8-like byte sequences for non-ASCII password tests; legitimate test data.
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.
|
&&