build(deps-dev): bump vm2 from 3.9.11 to 3.10.0

[dependabot]

Bumps vm2 from 3.9.11 to 3.10.0.

Release notes

Sourced from vm2's releases.

v3.10.0

What's Changed

• Upstream security fixes @​netroy in patriksimek/vm2#540
• Modernization, added support for TypeScript compiler @​patriksimek in patriksimek/vm2#542

New Contributors

• @​netroy made their first contribution in patriksimek/vm2#540

Full Changelog: patriksimek/vm2@3.9.19...v3.10.0

3.9.19

Fixes

patriksimek/vm2@cfa3fc6: Fix resolver issue.

3.9.18

New Features

patriksimek/vm2@dd81ff6: Add resolver API to create a shared resolver for multiple NodeVM instances allowing to cache scripts and increase sandbox startup times. patriksimek/vm2@4d662e3: Allow to pass a function to require.context which is called with the filename allowing to specify the context pre file. (Thanks to @​blakebyrnes)

Fixes

patriksimek/vm2@d88105f: Fix issue leaking host array through Proxy. (Thanks to @​arkark (Takeshi Kaneko) of GMO Cybersecurity by Ierae, Inc.) patriksimek/vm2@5206ba2: Fix issue with inspect being writeable. (Thanks to @​arkark (Takeshi Kaneko) of GMO Cybersecurity by Ierae, Inc.)

3.9.17

Fixes

patriksimek/vm2@4b22e87: Fix issue in catch block protection. (Thanks to Xion (SeungHyun Lee) of KAIST Hacking Lab.) patriksimek/vm2@f3db4de: Fix issue with host exceptions thrown in async functions leaking though the Promise.

3.9.16

Fixes

patriksimek/vm2@24c724d: Fix issue in transformer issue by reworking replacement logic. (Thanky to Xion (SeungHyun Lee) of KAIST Hacking Lab.)

3.9.15

Fixes

patriksimek/vm2@d534e57: Ensure no host objects are passed through to Error.prepareStackTrace. (Thanky to Seongil Wi from KAIST WSP Lab)

3.9.14

Fixes

patriksimek/vm2@fe3ab68: Support conditional export resolution with custom resolver (thanks to nick-klaviyo).

3.9.13

Fixes

... (truncated)

Commits

• 96acb88 Resurrection (#542)
• d9a1fde Upstream security fixes, and update supported node.js versions (#540)
• b51d33c Update README.md
• 642b200 Discontinued
• 1663f23 Release 3.9.19
• cfa3fc6 Fix resolver issue
• 2f446e5 Release 3.9.18
• 587bb13 Add tests for past vulnerabilities
• f5a129a Merge branch 'master' of https://github.com/patriksimek/vm2
• dd81ff6 Merge pull request #519 from XmiliaH/resolver-api
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by patriksimek, a new releaser for vm2 since your current version.

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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

Warning

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Potential code anomaly (AI signal): npm acorn is 100.0% likely to have a medium risk anomaly Notes: Overall, the analyzed code is a legitimate, well-structured Acorn 8.x parser fragment with robust handling for ES2020+ features. There is no direct malicious payload, backdoor, or exfiltration mechanism within this fragment. The primary security considerations relate to safe handling of untrusted input to avoid DoS via complex/ pathological RegExp usage or verbose error reporting. In a typical extension usage, isolate parsing to a sandbox and limit resource usage to mitigate potential abuse. Confidence: 1.00 Severity: 0.60 From: ? → npm/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: 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 [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report