Skip to content

[Snyk] Security upgrade nanoid from 4.0.0 to 5.1.16 - #1074

Closed
posit-snyk-bot wants to merge 1 commit into
mainfrom
snyk-fix-9fc21c087f3487fc5789cb9e9283846d
Closed

[Snyk] Security upgrade nanoid from 4.0.0 to 5.1.16#1074
posit-snyk-bot wants to merge 1 commit into
mainfrom
snyk-fix-9fc21c087f3487fc5789cb9e9283846d

Conversation

@posit-snyk-bot

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • apps/vscode/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Infinite loop
SNYK-JS-NANOID-18506894
  148  
high severity Infinite loop
SNYK-JS-NANOID-18506897
  148  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

@posit-snyk-bot

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

The upgrade from nanoid v4 to v5 is a major version jump with significant breaking changes, primarily centered around the removal of the asynchronous API and updated Node.js version support.

Key Breaking Changes:

  • Asynchronous API Removed: The entire async API (nanoid/async) has been removed. The library now exclusively uses the synchronous Web Crypto API for random number generation. Any code using await nanoid() or importing from nanoid/async will break and must be refactored to use the synchronous nanoid() function. [1]
  • Node.js Support: Support for Node.js versions 14 and 16 has been dropped. [1]

Recommendation:
This is a high-risk upgrade. Before merging, you must audit your codebase to ensure you are not using the asynchronous version of nanoid. All calls must be converted to the synchronous API. You must also ensure your production environment runs on Node.js 18 or newer.

Source: nanoid CHANGELOG

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@posit-snyk-bot

posit-snyk-bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants