Skip to content

[Snyk] Fix for 1 vulnerabilities#888

Closed
MelvinBot wants to merge 2 commits intomainfrom
snyk-fix-b04677028250e66fe978dfca37a0db80
Closed

[Snyk] Fix for 1 vulnerabilities#888
MelvinBot wants to merge 2 commits intomainfrom
snyk-fix-b04677028250e66fe978dfca37a0db80

Conversation

@MelvinBot
Copy link

snyk-top-banner

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 Score
medium severity Prototype Pollution
SNYK-JS-JSYAML-13961110
  631  

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:

🦉 Prototype Pollution

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-JSYAML-13961110
@MelvinBot MelvinBot requested a review from a team as a code owner November 18, 2025 10:27
@melvin-bot melvin-bot bot requested review from neil-marcellini and removed request for a team November 18, 2025 10:27
@neil-marcellini
Copy link
Contributor

It's a ton of work to get this working, and a lot of changes that would be hard to test.

While js-yaml (CVE-2025-64718 / SNYK-JS-JSYAML-13961110) appears in the dependency tree, this repository does not process untrusted YAML input. The js-yaml package is only used as a transitive dependency by ESLint, Grunt, and Jest for parsing trusted configuration files that are part of the repository itself. Therefore, this repository is not vulnerable to this attack vector.

So I'm going to close this.

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.

3 participants