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] Upgrade libp2p-crypto from 0.19.7 to 0.21.0 #4

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

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade libp2p-crypto from 0.19.7 to 0.21.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.
  • The recommended version was released a month ago, on 2021-12-01.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Open Redirect
SNYK-JS-NODEFORGE-2331910
663/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.4
Proof of Concept

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

Release notes
Package name: libp2p-crypto
  • 0.21.0 - 2021-12-01

    Features

    • replace keypair and ursa-optional with node crypto (#219) (759535c)

    BREAKING CHANGES

    • requires node 15+
  • 0.20.0 - 2021-10-21

    Bug Fixes

    Features

    • use noble-secp256k1 and noble-ed25519 (#202) (167eace)

    BREAKING CHANGES

    • keys function hashAndVerify returns boolean false when fail, instead of throwing error
  • 0.19.7 - 2021-08-18
    No content.
from libp2p-crypto GitHub release notes
Commit messages
Package name: libp2p-crypto

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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.

1 participant