[Snyk] Fix for 3 vulnerabilities

[posit-snyk-bot]

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

Snyk changed the following file(s):

• packages/editor/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
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-17900054	225
	Infinite loop SNYK-JS-TAR-17909068	169
	Allocation of Resources Without Limits or Throttling SNYK-JS-TAR-17909152	169

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:

🦉 Allocation of Resources Without Limits or Throttling

[posit-snyk-bot]

This update includes a major version upgrade for pinyin which introduces significant breaking changes. The upgrade for js-yaml is minor and considered low-risk.

pinyin@2.11.2 → pinyin@4.0.0

Risk: High

This is a major version upgrade with significant breaking changes due to a complete rewrite of the library in TypeScript and a move to ES Modules (ESM).

• ES Module Transition: The package was rewritten and now primarily exports ES modules. You may need to update require() statements to import or use dynamic import(). This is a common breaking change that can affect how the module is loaded in your project. [4]
• Segmentation: The new version uses Intl.Segmenter for word segmentation and may require optional peer dependencies like @node-rs/jieba or segmentit for advanced use cases, which may have previously been bundled. [4, 11]
• API Rewrite: The library was completely rewritten in TypeScript, which could introduce subtle API and behavioral differences from the previous JavaScript implementation. [4]

Recommendation: Developers must carefully review their project's module system (CommonJS vs. ESM) and update import statements for pinyin. Test any functionality that relies on word segmentation to ensure it works as expected with the new implementation.

js-yaml@4.1.0 → js-yaml@4.3.0

Risk: Low

This is a minor version upgrade that includes security enhancements and bug fixes without any documented breaking API changes. [1]

• Security Fixes: The updates include patches for a potential prototype pollution issue and a denial-of-service (DoS) vulnerability related to the merge (<<) operator. [1]
• New Features: Safety features like a maxDepth loader option have been added with safe defaults. [1]

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]

✅ 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.