[Snyk] Fix for 2 vulnerabilities

[adamlaska]

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
  • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	586/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 5.3	Regular Expression Denial of Service (ReDoS) SNYK-JS-HTTPCACHESEMANTICS-3248783	No	Proof of Concept
	751/1000 Why? Proof of Concept exploit, Has a fix available, CVSS 8.6	Prototype Pollution SNYK-JS-PROTOBUFJS-5756498	Yes	Proof of Concept

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

Commit messages

Package name: go-ipfs

The new version differs by 38 commits.

• 807ce2b 0.22.0
• 4441b8a feat: add KUBO_BINARY env to allow overriding the path used ([Snyk] Security upgrade ts-standard from 11.0.0 to 12.0.0 #62)
• f8af841 fix: update path to TS types ([Snyk] Security upgrade electron from 19.0.9 to 27.3.11 #58)
• 4da0b7b 0.22.0-rc1
• 517ad00 0.21.0
• 3459f9d chore: Update .github/workflows/stale.yml [skip ci]
• cdf1088 build(deps): bump gozala/typescript-error-reporter-action ([Snyk] Security upgrade electron from 19.0.9 to 29.3.3 #60)
• b7cac3d build(deps): bump actions/checkout from 2 to 3 ([Snyk] Security upgrade electron from 19.0.9 to 29.3.3 #61)
• 43135d3 0.21.0-rc3
• 101bd81 build(deps): bump actions/setup-node from 1 to 3 ([Snyk] Security upgrade electron from 19.0.9 to 27.3.10 #59)
• f1a5174 0.21.0-rc2
• bb8e590 chore: Update .github/dependabot.yml [skip ci]
• d098ca9 chore: Update .github/workflows/stale.yml [skip ci]
• 30d1ebc 0.21.0-rc1
• ff80133 0.20.0
• 634a82c 0.19.2
• edfb99a 0.20.0-rc2
• a6a1a31 0.20.0-rc1
• 79157ea 0.19.1
• abfc2f7 0.19.0
• 8513f17 0.19.0-rc1
• 567233b Update entrypoint.sh
• 2e47003 0.18.1
• 64a7dfe 0.18.0

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/go-ipfs@0.22.0	Transitive: environment, filesystem, network	+84	4.18 MB
npm/ipfs-http-client@60.0.1	Transitive: environment, filesystem, network, unsafe	+111	15.3 MB	npm-service-account-ipfs

🚮 Removed packages: npm/go-ipfs@0.14.0, npm/ipfs-http-client@56.0.2

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/protobufjs@7.2.6	Install script: postinstall Source: node scripts/postinstall	package-lock.json package.json

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/protobufjs@7.2.6