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 npm-lifecycle from 2.1.0 to 2.1.1 #15

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

Conversation

snyk-bot
Copy link

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

merge advice

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
low severity 481/1000
Why? Recently disclosed, Has a fix available, CVSS 3.7
Regular Expression Denial of Service (ReDoS)
SNYK-JS-TAR-1536758
No No Known Exploit

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

Commit messages
Package name: npm-lifecycle The new version differs by 7 commits.
  • cf5f5ca chore(release): 2.1.1
  • dbbfe27 deps: bump deps to fix security advisories
  • e96f550 deps: update node-gyp to v4.0.0
  • f6cef1c chore: update CI for current Node LTS
  • c137ac7 deps: bump devDeps
  • 62c07d3 deps: bump deps
  • 220cd70 fix(test): update postinstall script for fixture

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

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