[Snyk] Security upgrade ipfs-repo from 0.24.0 to 0.27.0

[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:
  • examples/custom-ipfs-repo/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	823/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 8.6	Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864	No	Proof of Concept

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

Commit messages

Package name: ipfs-repo

The new version differs by 41 commits.

• 62cc749 chore: release version v0.27.0
• 8b79982 chore: update contributors
• e6db5cf feat: refactor/async await ([Snyk] Security upgrade electron from 2.0.18 to 23.2.3 #199)
• 25cecd7 chore: release version v0.26.6
• 3af3c57 chore: update contributors
• 9c7cb0b chore: update cids dependency ([Snyk] Security upgrade electron from 2.0.18 to 22.3.23 #198)
• e8f658f chore: release version v0.26.5
• 1b011c6 chore: update contributors
• 99b13c1 chore: update datastore-level ([Snyk] Security upgrade aegir from 14.0.0 to 31.0.0 #196)
• 4e5ae79 chore: release version v0.26.4
• 2f3124d chore: update contributors
• 0aa9d77 fix: reduce bundle size ([Snyk] Security upgrade ipfs from 0.30.0 to 0.64.0 #186)
• ca31174 chore: release version v0.26.3
• 354ea54 chore: update contributors
• 73d95cd fix: update lock file package to fix compromised lock check ([Snyk] Security upgrade aegir from 14.0.0 to 17.0.0 #193)
• c018653 chore: release version v0.26.2
• bc9c656 chore: update contributors
• a33c5f0 chore: fix npm dist files
• c845011 chore: release version v0.26.2-rc.0
• ff7f068 chore: update contributors
• 14051c4 chore: update deps
• 23f49f2 chore: move to travis ([Snyk] Security upgrade electron-rebuild from 1.11.0 to 3.2.4 #190)
• 01a4737 chore: release version v0.26.1
• 8131dc0 chore: update contributors

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:

🦉 Server-side Request Forgery (SSRF)

[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 dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	Transitive: environment, filesystem	+76	12.7 MB

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
Native code	npm/[email protected]	Location: Package overview	examples/custom-ipfs-repo/package.json
Install scripts	npm/[email protected]	Install script: postinstall Source: opencollective-postinstall || exit 0	examples/custom-ipfs-repo/package.json

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]