Skip to content

fix(security): use unbiased cryptographic randomness - #54

Merged
SMAKSS merged 10 commits into
masterfrom
security/secure-randomness
Nov 3, 2026
Merged

SMAKSS merged 10 commits into
masterfrom
security/secure-randomness

Conversation

@SMAKSS

@SMAKSS SMAKSS commented Nov 2, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Generate strings with Web Crypto and rejection sampling, including the default length.

  • Validate requested length and character sets; throw when secure randomness is unavailable.

  • Require Node.js 20 or later and document the runtime requirement.

  • Migrate package tooling to pnpm 12 and Vite, and update pinned CI actions.

  • Add focused regression and package export/type tests.

  • Add local Vite playgrounds, updated README examples, and repository-specific AGENTS.md and Copilot instructions.

Validation

  • All five playground production builds pass; playground typechecks are included in the package typecheck.

  • Local pnpm test, typecheck, lint, and format:check pass.

  • pnpm audit and git diff --check pass.

  • ESM/CJS runtime exports and NodeNext consumer types pass.

  • Latest GitHub PR checks pass, including tests, type checks, lint/format, security audit, and artifact upload.

This PR does not publish an npm release.

@SMAKSS
SMAKSS merged commit 6451715 into master Nov 3, 2026
2 checks passed
@SMAKSS
SMAKSS deleted the security/secure-randomness branch November 3, 2026 01:44
@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown

🎉 This PR is included in version 2.0.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant