Skip to content

Bump js-yaml from 4.1.0 to 4.1.1 in /ui#7

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/ui/js-yaml-4.1.1
Open

Bump js-yaml from 4.1.0 to 4.1.1 in /ui#7
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/ui/js-yaml-4.1.1

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot bot commented on behalf of github Nov 14, 2025

Bumps js-yaml from 4.1.0 to 4.1.1.

Changelog

Sourced from js-yaml's changelog.

[4.1.1] - 2025-11-12

Security

  • Fix prototype pollution issue in yaml merge (<<) operator.
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [js-yaml](https://github.com/nodeca/js-yaml) from 4.1.0 to 4.1.1.
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.0...4.1.1)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 4.1.1
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 14, 2025
@fossabot
Copy link
Copy Markdown

fossabot bot commented Nov 14, 2025

fossabot is Thinking

@fossabot
Copy link
Copy Markdown

fossabot bot commented Nov 14, 2025

✓ Safe to upgrade

I recommend merging this upgrade because js-yaml is only used as a dev dependency (likely for Cypress testing configuration) with no direct code imports found in the codebase. The upgrade patches a prototype pollution security vulnerability while maintaining full backward compatibility with no breaking changes. The security fix strengthens protection against proto key manipulation attacks.

What we checked

  • js-yaml declared as devDependency only (not production dependency), limiting exposure [1]
  • Upgrade from 4.1.0 to 4.1.1 - patch version with security fix for prototype pollution (GHSA-mh29-5h37-fv8m) [2]
  • Searched for 'js-yaml', 'jsyaml', require/import statements, and yaml.load/dump usage patterns across all .js/.jsx/.ts files - no direct usage found in application code [3]

Dependency Usage

Changes

js-yaml upgraded with a critical security fix that blocks prototype pollution attacks by preventing proto key manipulation in the YAML merge operator. The update strengthens object construction safeguards across both mergeObjects() and constructMapping() functions.

  • Enhanced prototype pollution protection by extracting setProperty() helper function and applying it consistently in both mergeObjects() and constructMapping() to prevent proto key manipulation (v4.1.1, other)
  • Fix prototype pollution issue in yaml merge (<<) operator. (v4.1.1, changelog)
  • Updated documentation URLs from HTTP to HTTPS for yaml.org and pyyaml.org references in README (v4.1.1, other)
View 3 more changes
References (3)

[1]: js-yaml declared as devDependency only (not production dependency), limiting exposure

"js-yaml": "4.1.1",

[2]: Upgrade from 4.1.0 to 4.1.1 - patch version with security fix for prototype pollution (GHSA-mh29-5h37-fv8m)

js-yaml@4.1.1, js-yaml@^4.1.0:

[3]: Searched for 'js-yaml', 'jsyaml', require/import statements, and yaml.load/dump usage patterns across all .js/.jsx/.ts files - no direct usage found in application code
https://github.com/UchihaCortez/conductor/blob/69f30fc15d0935ac33143ccad5430490b039ff8b/ui


fossabot analyzed this PR using dependency research. View this analysis on the web

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

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants