Skip to content

[Snyk] Security upgrade payload from 2.30.3 to 3.44.0#477

Open
finkinfridom wants to merge 1 commit into
mainfrom
snyk-fix-710f7afe20fee844497e301b9631f74c
Open

[Snyk] Security upgrade payload from 2.30.3 to 3.44.0#477
finkinfridom wants to merge 1 commit into
mainfrom
snyk-fix-710f7afe20fee844497e301b9631f74c

Conversation

@finkinfridom

Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
  • yarn.lock

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.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Insufficient Session Expiration
SNYK-JS-PAYLOAD-12239898
  601  
medium severity Insufficient Session Expiration
SNYK-JS-PAYLOAD-12239899
  551  

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:

🦉 Insufficient Session Expiration

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