deps(dev): bump @bytecodealliance/jco from 1.5.0 to 1.6.0

[dependabot]

Bumps @bytecodealliance/jco from 1.5.0 to 1.6.0.

Release notes

Sourced from @​bytecodealliance/jco's releases.

1.6.0

What's Changed

• use require.resolve shim instead of hard-coded paths by @​OmarTawfik in bytecodealliance/jco#493
• fix: pass open flags to getChildEntry in statAt by @​kateinoigakukun in bytecodealliance/jco#496
• feat: support --aot flag for jco componentize by @​guybedford in bytecodealliance/jco#498

New Contributors

• @​OmarTawfik made their first contribution in bytecodealliance/jco#493

Full Changelog: bytecodealliance/jco@1.5.0...1.6.0

Commits

• 059acf8 1.6.0
• 881aca0 feat: support --aot flag for jco componentize (#498)
• 33e6192 fix: pass open flags to getChildEntry in statAt (#496)
• 046f337 use import.meta.resolve instead of hard-coded paths (#493)
• 9ae2fef try adding write permission
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@bytecodealliance/jco@1.6.0	Transitive: environment, eval, filesystem, network, shell	+84	451 MB	guybedford

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	CI
Trivial Package	npm/pinkie-promise@2.0.1	Location: Package overview	analyze/package.json package-lock.json redact-wasm/package.json	🚫
New author	npm/fd-slicer@1.1.0	New Author: thejoshwolfe Previous Author: superjoe	analyze/package.json package-lock.json redact-wasm/package.json	🚫
Network access	npm/@tybys/wasm-util@0.9.0	Module: globalThis["fetch"] Location: Package overview	analyze/package.json package-lock.json redact-wasm/package.json	🚫
Network access	npm/@emnapi/core@1.2.0	Module: globalThis["fetch"] Location: Package overview	analyze/package.json package-lock.json redact-wasm/package.json	🚫
Network access	npm/@cfallin/weval@0.2.14	Module: globalThis["fetch"] Location: Package overview	analyze/package.json package-lock.json redact-wasm/package.json	🚫
Shell access	npm/@napi-rs/lzma@1.4.0	Module: child_process Location: Package overview	analyze/package.json package-lock.json redact-wasm/package.json	🚫

View full report↗︎

Next steps

What are trivial packages?

Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.

Removing this package as a dependency and implementing its logic will reduce supply chain risk.

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

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/pinkie-promise@2.0.1
• @SocketSecurity ignore npm/fd-slicer@1.1.0
• @SocketSecurity ignore npm/@tybys/wasm-util@0.9.0
• @SocketSecurity ignore npm/@emnapi/core@1.2.0
• @SocketSecurity ignore npm/@cfallin/weval@0.2.14
• @SocketSecurity ignore npm/@napi-rs/lzma@1.4.0

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[blaine-arcjet]

I really don't want to take on so many deps for a feature we don't use, so I've opened bytecodealliance/jco#500

[dependabot]

Superseded by #1745.