[Snyk] Security upgrade js-yaml from 3.14.1 to 5.2.2

[bio-boris]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json

⚠️ Warning

Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Inefficient Algorithmic Complexity SNYK-JS-JSYAML-18313070

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:

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

[bio-boris]

This is a major upgrade from version 3 to 5, which includes numerous significant breaking changes across two major releases (v4 and v5). Direct upgrade without code modification will likely cause application failure.

Key Breaking Changes in v4.0.0:

• safeLoad and safeDump Removed: The safeLoad(), safeLoadAll(), and safeDump() functions have been removed. The main functions (load(), loadAll(), dump()) are now safe by default. All calls to the safe* methods must be renamed.
• Unsafe Tags Moved: Deserialization of unsafe tags like !!js/function and !!js/regexp is no longer supported by default and has been moved to a separate package (js-yaml-js-types).
• Number Parsing: The library now parses numbers according to the YAML 1.2 specification, which means octal numbers like 01234 are now interpreted as decimal. This can lead to silent data corruption if your application relies on the old behavior.

Key Breaking Changes in v5.0.0:

• Empty Input: load('') will now throw an error instead of returning undefined. Code that checks for an undefined return value must be updated to use a try...catch block.
• Custom Types API: The Type class and Schema.extend() have been removed and replaced with a new tags API. Any custom type definitions must be completely rewritten.
• Dumper Options: Several dumper options like replacer, quotingType, and styles have been removed or replaced.

Recommendation: Due to the extensive and impactful nature of these breaking changes, a direct upgrade is not recommended. A thorough code review and refactoring are required to align with the new APIs for loading, dumping, and defining custom types. Please consult the migration guide for detailed instructions.

Source: GitHub CHANGELOG, v5 Migration Guide

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

[Copilot]

Pull request overview

This PR updates the project’s npm dependency on js-yaml to address a reported security vulnerability (SNYK-JS-JSYAML-18313070).

Changes:

• Bumps js-yaml from 3.14.1 to 5.2.2 in package.json.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud