Fix random bound validation and harden CI - #25
Merged
Conversation
rblake2320
marked this pull request as ready for review
July 30, 2026 18:48
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
secureRandomIntbounds before entering rejection samplingWhy
The random integer helper used a 32-bit entropy source but accepted arbitrary JavaScript numbers. A bound above
2^32made the rejection limit zero, causing a non-terminating loop. Invalid fractional and non-finite inputs were also not rejected explicitly.Validation
npm run buildnpm run typechecknpm testnpm run test:hanpm run test:packnpm auditgit diff --check