Recordsnpmbcryptjsfailure issue
Failure signature
PROJECT_TEST Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-07 · Last seen: 2026-09-07
bcrypt.compare bcrypt.compareSync bcrypt.genSalt bcrypt.genSaltSync bcrypt.getRounds bcrypt.getSalt bcrypt.hash bcrypt.hashSync bcrypt.truncates
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=node · os=linux · runtime=node@22 ×1 2026-09-07 → 2026-09-07
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release 3.0.2 → first failing release 3.0.3
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No resolved dependency tree for 3.0.2 or for 3.0.3, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- bcryptjs 3.0.3: Handle bcryptjs parameter asymmetries in hash salt defaults, selective 60-character error throwing in compare, fallback random precedence, and custom Base64 encoding This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbcryptjs.compareSyncbcryptjs.comparebcryptjs.hashSyncbcryptjs.hashbcryptjs.genSaltSyncbcryptjs.genSaltbcryptjs.setRandomFallbackbcryptjs.getRoundsbcryptjs.getSaltbcryptjs.truncatesbcryptjs.encodeBase64bcryptjs.decodeBase64node MIT-0 · 2026-08-17
- bcryptjs 3.0.3: Yield to the event loop during asynchronous password hashing and salting with bcryptjs, preventing microtask starvation across fallback environments This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbcrypt.genSaltbcrypt.genSaltSyncbcrypt.hashbcrypt.hashSyncbcrypt.comparebcrypt.compareSyncbcrypt.truncatesbcrypt.getRoundsbcrypt.getSaltnode MIT-0 · 2026-08-16
- bcryptjs 3.0.3: Handle the bcryptjs 3 major revision switch where genSalt and hash default silently to 2b revisions, clamp out-of-range rounds, and restrict package subpath exports This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWbcrypt.genSaltSyncbcrypt.hashSyncbcrypt.compareSyncbcrypt.truncatesbcrypt.getRoundsbcrypt.getSaltnode MIT-0 · 2026-08-16