Skip to content

Conversation

@snyk-bot
Copy link

Snyk has created this PR to upgrade jpm from 1.1.4 to 1.3.1.

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 5 versions ahead of your current version.
  • The recommended version was released 3 years ago, on 2017-03-29.

The recommended version fixes:

Severity Issue Exploit Maturity
Regular Expression Denial of Service (ReDoS)
npm:tough-cookie:20160722
No Known Exploit
Prototype Override Protection Bypass
npm:qs:20170213
No Known Exploit
Prototype Pollution
SNYK-JS-LODASHMERGE-173732
No Known Exploit
Regular Expression Denial of Service (ReDoS)
npm:tough-cookie:20170905
No Known Exploit
Regular Expression Denial of Service (ReDoS)
npm:semver:20150403
No Known Exploit
Remote Memory Exposure
npm:request:20160119
No Known Exploit
Prototype Pollution
SNYK-JS-LODASHMERGE-173733
No Known Exploit
Release notes
Package name: jpm from jpm GitHub release notes
Commit messages
Package name: jpm

Compare


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

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