docs: add deprecation notice recommending @vekexasia/bigint-buffer2#62
Open
vekexasia wants to merge 1 commit intono2chem:masterfrom
Open
docs: add deprecation notice recommending @vekexasia/bigint-buffer2#62vekexasia wants to merge 1 commit intono2chem:masterfrom
vekexasia wants to merge 1 commit intono2chem:masterfrom
Conversation
This package has known security vulnerabilities and is no longer maintained. Recommend migration to @vekexasia/bigint-buffer2 which provides: - Security fixes (CVE-2025-3194, issues no2chem#40, no2chem#59, no2chem#12, no2chem#22) - Modern Rust bindings via napi-rs - Full browser support with JS fallback - ESM/CJS bundles - TypeScript support - API-compatible drop-in replacement
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.
Summary
This PR adds a deprecation notice to the README and package.json, recommending users migrate to @vekexasia/bigint-buffer2.
Why deprecate bigint-buffer?
1. Security Vulnerability (CVE-2025-3194)
This package contains a known buffer overflow vulnerability (SNYK-JS-BIGINTBUFFER-3364597) that can crash applications when
nullis passed totoBigIntLE()ortoBigIntBE(). This has been open since March 2023 with no fix.2. Multiple Unresolved Issues
Several critical issues remain unaddressed:
3. Outdated Build System
The package uses deprecated N-API bindings with node-gyp, which:
4. No Maintenance Activity
The last commit was over 4 years ago, and there are 11 open issues with no response.
Why @vekexasia/bigint-buffer2?
It's a modern, drop-in replacement that:
toBufferBEInto/toBufferLEIntoSuggested npm deprecation
If you agree with this deprecation, please also run:
npm deprecate bigint-buffer "This package is deprecated. Please use @vekexasia/bigint-buffer2 instead - it fixes security vulnerabilities and is actively maintained."This will show a warning to users when they install the package.
Changes