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 lockfile-lint from 3.0.18 to 4.10.6 #256

Closed
wants to merge 1 commit into from

Conversation

lirantal
Copy link
Owner

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


Snyk has created this PR to upgrade lockfile-lint from 3.0.18 to 4.10.6.

ℹ️ 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.


Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 34 versions ahead of your current version.
  • The recommended version was released a month ago, on 2023-07-01.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Prototype Pollution
SNYK-JS-Y18N-1021887
472/1000
Why? Proof of Concept exploit, CVSS 7.3
Proof of Concept
Prototype Pollution
SNYK-JS-YARGSPARSER-560381
472/1000
Why? Proof of Concept exploit, CVSS 7.3
Proof of Concept

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


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 has created this PR to upgrade lockfile-lint from 3.0.18 to 4.10.6.

See this package in npm:


See this project in Snyk:
https://app.snyk.io/org/lirantal/project/f67650ab-646c-4345-90a4-62a090b90128?utm_source=github&utm_medium=referral&page=upgrade-pr
@lirantal lirantal closed this Aug 2, 2023
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