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 laravel-elixir from 4.2.1 to 5.0.0 #7

Open
wants to merge 1 commit into
base: master
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.

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 Issue Breaking Change Exploit Maturity
medium severity Prototype Pollution
SNYK-JS-LODASH-567746
Yes Proof of Concept
Commit messages
Package name: laravel-elixir The new version differs by 11 commits.
  • 2def8c9 v5.0.0
  • b0bfaf6 Merge pull request #434 from SethTompkins/master
  • 4442316 add cache and package cache browserify options keys by default
  • cc5cab9 Remove some duplication
  • f0491ba Remove gulp-phpspec plugin
  • 5fa4b86 Remove gulp-phpunit - closes #418
  • e2b2a0f Bump gulp-uglify
  • 1a26399 Ignore bang when asserting files exist - closes #429
  • 7881b51 Wrote a test for the scripts to test if my changes broke anything.
  • 589f56c Moved Uglify Config to the Config.js
  • a95c787 Add 4.2.1 notes

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-LODASH-567746
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