Skip to content

[Snyk] Security upgrade js-cookie from 2.2.1 to 3.0.7 - #159

Open
fredex42 wants to merge 1 commit into
mainfrom
snyk-fix-117195a0082aed8bdc21a9c882251873
Open

[Snyk] Security upgrade js-cookie from 2.2.1 to 3.0.7#159
fredex42 wants to merge 1 commit into
mainfrom
snyk-fix-117195a0082aed8bdc21a9c882251873

Conversation

@fredex42

@fredex42 fredex42 commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

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

Snyk changed the following file(s):

  • frontend/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
high severity Prototype Pollution
SNYK-JS-JSCOOKIE-17816999
  721  

Breaking Change Risk

Merge Risk: High

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:

🦉 Prototype Pollution

@fredex42

fredex42 commented Jul 5, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This major version upgrade from js-cookie v2 to v3 introduces significant breaking changes that require developer action.

Key Breaking Changes:

  • JSON Handling Removed: The Cookies.getJSON() method and automatic JSON stringification in Cookies.set() have been removed. Developers must now manually stringify and parse JSON objects.
    • Before: Cookies.set('foo', { bar: 'baz' })
    • After: Cookies.set('foo', JSON.stringify({ bar: 'baz' }))
  • Configuration API Changed: The Cookies.defaults property has been removed. To set default attributes for cookies, you must now use the Cookies.withAttributes() method to create a new instance.
  • ES Module Support: The package now provides an ES module build, which may affect bundlers and import statements.
  • Browser Support: Support for Internet Explorer versions older than 10 has been dropped.

Recommendation:
Code using Cookies.getJSON() or setting objects directly with Cookies.set() must be refactored to handle JSON manually. Any global default configurations must be updated to use the new Cookies.withAttributes() API.

Source: GitHub Releases

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

@github-actions

github-actions Bot commented Jul 5, 2026

Copy link
Copy Markdown

Unit Test Results

0 tests   - 185   0 ✔️  - 185   0s ⏱️ -45s
0 suites  -   52   0 💤 ±    0 
0 files    -   52   0 ±    0 

Results for commit 98b21e3. ± Comparison against base commit 1ef4054.

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.

2 participants