[Snyk] Fix for 6 vulnerabilities

[anaconda-security-bot]

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

Snyk changed the following file(s):

• packages/_metapackage/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
	Prototype Pollution SNYK-JS-MERMAID-18592329	611
	Arbitrary Code Injection SNYK-JS-MERMAID-18592305	551
	Use of Blocking Code in Single-threaded, Non-blocking Context SNYK-JS-MERMAID-18592314	551
	Improperly Controlled Sequential Memory Allocation SNYK-JS-MERMAID-18592327	551
	Cross-site Scripting (XSS) SNYK-JS-DOMPURIFY-18593782	541
	Cross-site Scripting (XSS) SNYK-JS-JUPYTERLABRENDERMIMEINTERFACES-16438959	529

Breaking Change Risk

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:

🦉 Cross-site Scripting (XSS)
🦉 Arbitrary Code Injection
🦉 Prototype Pollution

[anaconda-security-bot]

The upgrade to version 7.0.0 of @jupyter-notebook/notebook-extension and @jupyter-notebook/ui-components represents a complete architectural overhaul. Jupyter Notebook v7 is now built on top of JupyterLab components, which fundamentally changes the extension system.

Key Breaking Changes:

• New Extension System: Classic Notebook v6 extensions are incompatible with Notebook v7. Any custom extensions you rely on must be migrated to the new JupyterLab extension system. The packages @jupyter-notebook/notebook-extension and @jupyter-notebook/ui-components are part of this new architecture.
• API Incompatibility: The underlying APIs for extensions have completely changed. Code interacting with the classic notebook frontend will be broken.
• Underlying Technology: The frontend has moved from a traditional HTML/jQuery stack to a modern system based on JupyterLab, Lumino, and React. The text editor was upgraded from CodeMirror 5 to CodeMirror 6, which has a different API.

Recommendation:
This is a major migration effort. Treat this as a rewrite of any custom frontend extensions or integrations. Developers must port existing classic notebook extensions to the new JupyterLab-based framework. For users who cannot immediately migrate, the nbclassic package can be used to provide the old Notebook v6 interface as a temporary solution.

Source: Jupyter Notebook 7 Migration Guide, Jupyter Blog

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