chore: Bump lavamoat from 11.1.2 to 11.1.4

[dependabot]

Bumps lavamoat from 11.1.2 to 11.1.4.

Release notes

Sourced from lavamoat's releases.

lavamoat: v11.1.4

11.1.4 (2026-06-25)

Bug Fixes

• Bump yargs (#2027) (affd672)
• deps: update babel monorepo to v7.29.7 (#2010) (9627a86)
• deps: update dependency corepack to v0.35.0 (#1988) (22b874a)
• lavamoat-node: remove corepack as prod dep (#2030) (18d7e88)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • lavamoat-core bumped from ^18.0.4 to ^18.0.5
    • lavamoat-tofu bumped from ^9.0.2 to ^9.0.3

lavamoat: v11.1.3

11.1.3 (2026-05-28)

Bug Fixes

• lavamoat-node: fix old resolution bug where paths containing # were misinterpreted (#1971) (494f852)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • lavamoat-core bumped from ^18.0.3 to ^18.0.4
    • lavamoat-tofu bumped from ^9.0.1 to ^9.0.2

Changelog

Sourced from lavamoat's changelog.

11.1.4 (2026-06-25)

Bug Fixes

• Bump yargs (#2027) (affd672)
• deps: update babel monorepo to v7.29.7 (#2010) (9627a86)
• deps: update dependency corepack to v0.35.0 (#1988) (22b874a)
• lavamoat-node: remove corepack as prod dep (#2030) (18d7e88)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • lavamoat-core bumped from ^18.0.4 to ^18.0.5
    • lavamoat-tofu bumped from ^9.0.2 to ^9.0.3

11.1.3 (2026-05-28)

Bug Fixes

• lavamoat-node: fix old resolution bug where paths containing # were misinterpreted (#1971) (494f852)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • lavamoat-core bumped from ^18.0.3 to ^18.0.4
    • lavamoat-tofu bumped from ^9.0.1 to ^9.0.2

Commits

• 40cfd1c chore: release main (#2015)
• 18d7e88 fix(lavamoat-node): remove corepack as prod dep (#2030)
• affd672 fix: Bump yargs (#2027)
• 22b874a fix(deps): update dependency corepack to v0.35.0 (#1988)
• 9627a86 fix(deps): update babel monorepo to v7.29.7 (#2010)
• d1c0b4f chore: release main
• 494f852 fix(lavamoat-node): fix old resolution bug where paths containing # were misi...
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for lavamoat 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 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)

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​babel/​types@​7.29.0 ⏵ 7.29.7
	yargs@​17.7.3
	lavamoat@​11.1.2 ⏵ 11.1.4	+3			+5

View full report

[socket-security]

Caution

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)
Block		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is obfuscated code? 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 support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. 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.
Block		Publisher changed: npm yargs is now published by shadowspawn Author: shadowspawn From: package.json → npm/yargs@17.7.3 ℹ Read more on: This package | This alert | What is unstable ownership? 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 support@socket.dev. Suggestion: Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/yargs@17.7.3. 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.
Warn		Potential code anomaly (AI signal): npm @babel/helper-string-parser is 78.0% likely to have a medium risk anomaly Notes: The analyzed code is a standard, well-structured parsing utility for JavaScript string literals and escapes (consistent with Babel’s helper-string-parser). It includes thorough validation, proper Unicode handling, and defensive error reporting. There is no evidence of malicious behavior, data leakage, or network activity within this fragment. The security risk is low when used as part of a trusted toolchain; the code otherwise poses no evident supply-chain threat based on the provided snippet. Confidence: 0.78 Severity: 0.55 From: ? → npm/@babel/types@7.29.7 → npm/@babel/helper-string-parser@7.29.7 ℹ 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 support@socket.dev. 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/@babel/helper-string-parser@7.29.7. 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.
Warn		Potential code anomaly (AI signal): npm yargs is 65.0% likely to have a medium risk anomaly Notes: The code fragment serves as a standard CLI command-definition utility with a notable security consideration: if an untrusted builder function is supplied, it can execute arbitrary code via the builder callback. There is no evidence of malware, exfiltration, or obfuscated techniques in this fragment. In trusted use, risk remains low; in contexts allowing untrusted inputs, this fragment requires strict input validation or sandboxing to mitigate arbitrary code execution. The recommended security posture is to avoid invoking untrusted builder callbacks or to constrain them to benign shapes and to sanitize or restrict what those builders can access. Confidence: 0.65 Severity: 0.60 From: package.json → npm/yargs@17.7.3 ℹ 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 support@socket.dev. 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/yargs@17.7.3. 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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.59%. Comparing base (52d3c27) to head (936ee60).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4053   +/-   ##
=======================================
  Coverage   98.59%   98.59%           
=======================================
  Files         425      425           
  Lines       12413    12413           
  Branches     1969     1969           
=======================================
  Hits        12238    12238           
  Misses        175      175           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.