Skip to content
This repository has been archived by the owner on Apr 6, 2024. It is now read-only.

[Snyk] Security upgrade watchify from 3.11.1 to 4.0.0 #22

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

Conversation

CFenner
Copy link
Member

@CFenner CFenner commented Mar 7, 2021

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

Changes included in this PR

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

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 479/1000
Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS)
SNYK-JS-GLOBPARENT-1016905
Yes No Known Exploit

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

Commit messages
Package name: watchify The new version differs by 9 commits.
  • 7b27a3c 4.0.0
  • 5d4842a bump deps (#380)
  • b840f29 disable package-lock.json
  • bae5e02 update chokidar and anymatch (#378)
  • 3445775 ci: use github actions (#379)
  • f79e59f Change URLs from "Substack" (someones personal site & acc) to "browserify" (#369)
  • bd2f677 ci: run on more node versions
  • 563a90d Merge pull request #367 from Trott/update-readme-badge
  • bb2b429 chore: Fix Travis-CI badge in readme.markdown

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

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-GLOBPARENT-1016905
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants