[Snyk] Security upgrade npm from 2.15.12 to 5.6.0

[isp1r0]

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

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
	584/1000 Why? Has a fix available, CVSS 7.4	Regular Expression Denial of Service (ReDoS) SNYK-JS-HAWK-2808852	Yes	No Known Exploit

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

Commit messages

Package name: npm

The new version differs by 250 commits.

• 5e426a7 5.6.0
• e1ab2d1 update AUTHORS
• 87cc9ed doc: update changelog for npm@5.6.0
• 7ae3c4c Revert tar@4.1.0
• 14f3be4 gentle-fs@2.0.1: fixes global force issues
• 114d518 pack: stop including mtime so tarball packing usually results in the same sha
• 39ba4aa tar@4.1.0
• 2906bc6 test: fix some standard failures
• a0be6ba pacote@7.0.2
• 829893d config: Switch to find-npm-prefix module
• 876f0c8 find-npm-prefix@1.0.1
• 5dfe1c9 test: shrinkwrap-_auth: ditch hock
• b80d650 pack/publish/install: fix git and tarball specs and checksum errors (#19163)
• 66d1828 config: expose "node-options" passthrough for lifecycle scripts
• 6003b41 npmrc: we can use ^ now‼
• 72cad8c copy-concurrently@1.0.5
• 798428b bin-links@1.1.0
• c930e98 npm-lifecycle@2.0.0
• 7793394 docs: Remove trailing white space from npm-access docs
• dbc7e5b doc: use valid JSON in example for bundledDependencies
• 8a0fe71 diff-trees: Fix package comparison when integrity is unavailable
• 391ebcc test: add-remote-git for new cache.add internals
• c3e1ec7 test: cleanup during setup of install-shrinkwrapped-git
• 2e2ac03 test: bearer-token-check standard fixes

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

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.