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 @oclif/command from 1.8.0 to 1.8.16 #2026

Merged
merged 1 commit into from
Aug 2, 2022

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented Aug 2, 2022

Snyk has created this PR to upgrade @oclif/command from 1.8.0 to 1.8.16.

merge advice
ℹ️ 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 16 versions ahead of your current version.
  • The recommended version was released 8 months ago, on 2021-12-17.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Regular Expression Denial of Service (ReDoS)
SNYK-JS-NODEFETCH-2964180
554/1000
Why? Proof of Concept exploit, Recently disclosed, CVSS 7.5
Proof of Concept

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

Release notes
Package name: @oclif/command from @oclif/command GitHub release notes

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

@snyk-bot snyk-bot requested a review from a team as a code owner August 2, 2022 03:42
@jheikes515 jheikes515 merged commit cbfdb0c into master Aug 2, 2022
@jheikes515 jheikes515 deleted the snyk-upgrade-5a35c263b25155e2020b9151b9fc1bd6 branch August 2, 2022 15:31
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.

None yet

2 participants