[Snyk] Security upgrade aegir from 14.0.0 to 37.0.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/circuit-relaying/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	768/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.5	Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795	Yes	Proof of Concept

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

Commit messages

Package name: aegir

The new version differs by 250 commits.

• 5d448e7 chore(release): 37.0.0 [skip ci]
• bc62524 chore: add missing dep
• e3a4b45 feat: update build and release commands (#946)
• 585b004 chore(release): 36.2.3 [skip ci]
• a4123d5 chore(deps): bump simple-git from 2.37.0 to 3.3.0 (#944)
• 045ee8a chore(release): 36.2.2 [skip ci]
• cdd0ad1 chore: fix linting
• 677efd7 chore: slow ci is slow
• 2f88c95 fix: restore typesversions for ts config file
• 512e594 chore(release): 36.2.1 [skip ci]
• d03bb03 fix: types for test utils
• 539f597 fix: update config
• a849765 fix: publish utils dir
• 9b45b4b chore(release): 36.2.0 [skip ci]
• 3defb4f chore: add auto-release
• 3fec2e3 chore: remove unused dep
• dcb5be6 chore: add path dep
• feeeb54 fix: tsc receives forward args (#939)
• d3dc7cd fix: cache types dir
• 6136719 chore: add install browser deps action
• d8111a2 fix: remove playwright
• 7f83b6c fix: run playwright install-deps
• 40a49f6 fix: cache playwright browsers
• ad2f33b chore: change if clause

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)

[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]

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
aegir	14.0.0...37.12.1	network, environment	+691/-45	599 MB	npm-service-account-ipfs

[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.

Issue	Package	Version	Note	Source
HTTP dependency	aegir	37.12.1	Dependency: @semantic-release/github@https://registry.npmjs.org/@achingbrain/semantic-release-github/-/semantic-release-github-0.0.0.tgz Location: package.json	examples/circuit-relaying/package.json
Install scripts	esbuild	0.16.17	Install script: postinstall Source: node install.js	[email protected] via examples/circuit-relaying/package.json
Install scripts	esbuild	0.17.18	Install script: postinstall Source: node install.js	[email protected] via examples/circuit-relaying/package.json

Next steps

What are http dependencies?

Contains a dependency which resolves to a remote HTTP URL which could be used to inject untrusted code and reduce overall package reliability.

Publish the HTTP URL dependency to npm or a private package repository and consume it from there.

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 package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

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