Skip to content

[Snyk] Upgrade safe-buffer from 5.1.2 to 5.2.1 - #10

Open
Linkcar13 wants to merge 1 commit into
masterfrom
snyk-upgrade-51d16179a7a583a2dac79a7dcf4d5459
Open

[Snyk] Upgrade safe-buffer from 5.1.2 to 5.2.1#10
Linkcar13 wants to merge 1 commit into
masterfrom
snyk-upgrade-51d16179a7a583a2dac79a7dcf4d5459

Conversation

@Linkcar13

Copy link
Copy Markdown
Collaborator

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


Snyk has created this PR to upgrade safe-buffer from 5.1.2 to 5.2.1.

ℹ️ 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 3 years ago, on 2020-05-10.
Release notes
Package name: safe-buffer from safe-buffer GitHub release notes
Commit messages
Package name: safe-buffer
  • 89d3d5b package metadata
  • e4d9032 5.2.1
  • 1f19817 Merge pull request #28 from feross/greenkeeper/tape-5.0.0
  • 09eb337 chore(package): update tape to version 5.0.0
  • 7d54474 Update README.md
  • 94d0401 standard *
  • 4c90fcc Merge pull request #27 from feross/greenkeeper/standard-14.0.1
  • ac31863 chore(package): update standard to version 14.0.1
  • 2e8e6b4 Pin standard to workaround npm bug
  • da591f1 Update FUNDING.yml
  • ae53d5b 5.2.0
  • a43206b Merge pull request #23 from vkarpov15/patch-1
  • 4463582 add FUNDING.yml
  • 9be9ce7 add tidelift link
  • 4a4f75d Make SafeBuffer's prototype inherit from Buffer

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.

2 participants