[Security] Bump npm from 6.9.0 to 6.13.4

[dependabot-preview]

Bumps npm from 6.9.0 to 6.13.4.

Release notes

Sourced from npm's releases.

v6.13.4

6.13.4 (2019-12-11)

BUGFIXES

• 320ac9aee npm/bin-links#12 npm/gentle-fs#7 Do not remove global bin/man links inappropriately (@​isaacs)

DEPENDENCIES

• 52fd21061 gentle-fs@2.3.0 (@​isaacs)
• d06f5c0b0 bin-links@1.1.6 (@​isaacs)

v6.13.3

6.13.3 (2019-12-09)

DEPENDENCIES

• 19ce061a2 bin-links@1.1.5 Properly normalize, sanitize, and verify bin entries in package.json.
• 59c836aae npm-packlist@1.4.7
• fb4ecd7d2 pacote@9.5.11
  • 5f33040 #476 npm/pacote#22 npm/pacote#14 fix: Do not drop perms in git when not root (isaacs, @​darcyclarke)
  • 6f229f7 sanitize and normalize package bin field (isaacs)
• 1743cb339 read-package-json@2.1.1

v6.13.2

6.13.2 (2019-12-03)

BUG FIXES

• 4429645b3 #546 fix docs target typo (@​richardlau)
• 867642942 #142 fix(packageRelativePath): fix 'where' for file deps (@​larsgw)
• d480f2c17 #527 Revert "windows: Add preliminary WSL support for npm and npx" (@​craigloewen-msft)
• e4b97962e #504 remove unnecessary package.json read when reading shrinkwrap (@​Lighting-Jack)
• 1c65d26ac #501 fix(fund): open url for string shorthand (@​ruyadorno)
• ae7afe565 #263 Don't log error message if git tagging is disabled (@​woppa684)
• 4c1b16f6a #182 Warn the user that it is uninstalling npm-install (@​Hoidberg)

v6.13.1

6.13.1 (2019-11-18)

BUG FIXES

• 938d6124d #472 fix(fund): support funding string shorthand (@​ruyadorno)
• b49c5535b #471 should not publish tap-snapshot folder (@​ruyadorno)
• 3471d5200 #253 Add preliminary WSL support for npm and npx (@​infinnie)
• 3ef295f23 #486 print quick audit report for human output (@​isaacs)

TESTING

• dbbf977ac #278 added workflow to trigger and run benchmarks (@​mikemimik)

... (truncated)

Changelog

Sourced from npm's changelog.

6.13.4 (2019-12-11)

BUGFIXES

• 320ac9aee
  npm/bin-links#12
  npm/gentle-fs#7
  Do not remove global bin/man links inappropriately
  (@​isaacs)

DEPENDENCIES

• 52fd21061
gentle-fs@2.3.0
  (@​isaacs)
• d06f5c0b0
bin-links@1.1.6
  (@​isaacs)

6.13.3 (2019-12-09)

DEPENDENCIES

• 19ce061a2
bin-links@1.1.5 Properly normalize, sanitize, and verify bin entries
  in package.json.
• 59c836aae
npm-packlist@1.4.7
• fb4ecd7d2
pacote@9.5.11
  • 5f33040
    #476
    npm/pacote#22
    npm/pacote#14 fix: Do not
    drop perms in git when not root (isaacs,
    @​darcyclarke)
  • 6f229f7
    sanitize and normalize package bin field
    (isaacs)
• 1743cb339
read-package-json@2.1.1

6.13.2 (2019-12-03)

BUG FIXES

• 4429645b3
  #546
  fix docs target typo

... (truncated)

Commits

• fd29398 6.13.4
• f2aca36 docs: changelog for 6.13.4
• 320ac9a Do not remove global bin/man links inappropriately
• d06f5c0 bin-links@1.1.6
• 52fd210 gentle-fs@2.3.0
• 45482c2 6.13.3
• 118bc96 docs: changelog for 6.13.3
• 1743cb3 read-package-json@2.1.1
• fb4ecd7 pacote@9.5.11
• 59c836a npm-packlist@1.4.7
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

We've just been alerted that this update fixes a security vulnerability:

Sourced from The GitHub Security Advisory Database.

Low severity vulnerability that affects npm

Arbitrary File Overwrite

Versions of the npm CLI prior to 6.13.4 are vulnerable to an Arbitrary File Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a serve binary, any subsequent installs of packages that also create a serve binary would overwrite the previous serve binary.

This behavior is still allowed in local installations and also through install scripts. This vulnerability bypasses a user using the --ignore-scripts install option.

Thank you to Daniel Ruf for reporting the issue!

Further information: npm blog post

Affected versions: ["< 6.13.4"]

[gep13]

LGTM!