Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade kea from 0.28.7 to 1.0.0 #607

Open
wants to merge 1 commit into
base: canary
Choose a base branch
from

Conversation

MaxMood96
Copy link

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • examples/with-kea/package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908
Yes Proof of Concept
low severity 506/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Prototype Pollution
SNYK-JS-MINIMIST-2429795
Yes Proof of Concept
medium severity 601/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 5.6
Prototype Pollution
SNYK-JS-MINIMIST-559764
Yes Proof of Concept
medium severity 539/1000
Why? Has a fix available, CVSS 6.5
Information Exposure
SNYK-JS-NODEFETCH-2342118
Yes No Known Exploit
medium severity 520/1000
Why? Has a fix available, CVSS 5.9
Denial of Service
SNYK-JS-NODEFETCH-674311
Yes No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Commit messages
Package name: kea The new version differs by 250 commits.
  • 6008f55 1.0.0
  • 022be13 Update README.md
  • f03c57a Update README.md
  • 83af1c0 readme for 1.0
  • 6aed05e small cleanup
  • 96e58b4 1.0.0-rc.10.2
  • c22b28f can access constants on logic before mounting
  • 8876165 1.0.0-rc.10.1
  • d0b872c remove proxy that throws custom errors in dev mode due to react-hot-router agressively accessing ".displayName" on exported logic
  • 750104a 1.0.0-rc.10
  • a79507d different approach
  • fbbf44d connect: { logic: [] }
  • 2a1825c throw error if accesing logic.actions and other fields when not yet mounted
  • 0f6969c 1.0.0-rc.9
  • 3078fb3 run selectors just once
  • bd79ac7 1.0.0-rc.8
  • 5d024cc support for build step order
  • ab2bfaa 1.0.0-rc.7
  • 8ea90a2 1.0.0.rc-7 changes
  • 0115ea6 simplify plugin.afterMount and others, make events work with connected logic
  • e08933b plugin context, logic.cache, mount events in logic
  • 0800456 1.0.0-rc.6
  • b29ef54 leak with clearing build cache
  • 7a4557d 1.0.0-rc.5

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

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