fix(deps): update dependency nanoid to v3 [security]#71
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
fea2d30 to
db51af7
Compare
db51af7 to
d74b5e5
Compare
d74b5e5 to
c349904
Compare
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.
This PR contains the following updates:
^2.1.11→^3.0.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Predictable results in nanoid generation when given non-integer values
CVE-2024-55565 / GHSA-mwcw-c2x4-8c55
More information
Details
When nanoid is called with a fractional value, there were a number of undesirable effects:
Version 3.3.8 and 5.0.9 are fixed.
Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
ai/nanoid (nanoid)
v3.3.8Compare Source
v3.3.7Compare Source
node16TypeScript support (by Saadi Myftija).v3.3.6Compare Source
v3.3.5Compare Source
v3.3.4Compare Source
--helpin CLI (by @Lete114).v3.3.3Compare Source
v3.3.2Compare Source
enhanced-resolvesupport.v3.3.1Compare Source
v3.3.0Compare Source
v3.2.0Compare Source
v3.1.32Compare Source
asyncexports size (by Artyom Arutyunyan).v3.1.31Compare Source
size(by Artyom Arutyunyan).v3.1.30Compare Source
brotlicompression (by Anton Khlynovskiy).v3.1.29Compare Source
v3.1.28Compare Source
v3.1.27Compare Source
dependenciesfrom development tools.v3.1.26Compare Source
v3.1.25Compare Source
browserifysupport.v3.1.24Compare Source
browserifysupport (by Artur Paikin).v3.1.23Compare Source
esbuildsupport.v3.1.22Compare Source
defaultandbrowser.defaulttopackage.exports.v3.1.21Compare Source
v3.1.20Compare Source
v3.1.19Compare Source
customAlphabetsize (by Enrico Scherlies).v3.1.18Compare Source
package.exports.v3.1.17Compare Source
process.v3.1.16Compare Source
v3.1.15Compare Source
package.typespath.v3.1.14Compare Source
package.types.v3.1.13Compare Source
randomFillSyncregression fromengines.node.v3.1.12Compare Source
v3.1.11Compare Source
customAlphabetin browser (by @LoneRifle).v3.1.10Compare Source
v3.1.9Compare Source
v3.1.8Compare Source
v3.1.7Compare Source
v3.1.6Compare Source
selfusing.v3.1.5Compare Source
v3.1.4engines.node(by Cansin Yildiz).v3.1.3asyncexports size (by Artyom Arutyunyan).v3.1.2Compare Source
v3.1.1Compare Source
customAlphabetsize (by Enrico Scherlies).v3.1.0Compare Source
v3.0.2Compare Source
v3.0.1Compare Source
non-secureimport (by Jia Huang).v3.0.0: 3.0 Migration GuideCompare Source
Nano ID 3.0 is the biggest release in the project history. Unfortunately, you will need to change the code of your application. But the changes are very small in most cases. In return, you will have better performance, smaller size, ES modules and TypeScript support.
Known Issues
Simple Case
In simple cases, you just need to change default import to named import.
If you support IE, you need to transpile
node_modulesby Babel.Non-secure and asynchronous Nano ID need only import changes as well.
TypeScript
Remove
@types/nanoidif you have it. Nano ID now have built-in types.React Native
For Expo you need to load the file by direct path:
For the non-Expo environment:
Change polyfill for hardware random generator from
expo-randomtoreact-native-get-random-values.Use sync Nano ID instead of async.
URL-Safe Alphabet
Our default URL-safe alphabet was moved as named export to
nanoidpath:Custom Alphabet
Now we use the currying API to change the alphabet. It improves performance by pre-calculating some caches for a new alphabet.
We hope the new API will be more readable compare to the old unclear “generate” word.
Non-secure and asynchronous APIs were also changed:
Custom Random Generator
Custom random generator API now is based on currying as well.
We removed a custom random generator from asynchronous API because we didn’t see that somebody used it.
New Features
A few good reasons, why you should migrate to Nano ID 3.0:
.d.tsfiles.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.