chore: Bump lavamoat from 11.0.0 to 11.1.1

[dependabot]

Bumps lavamoat from 11.0.0 to 11.1.1.

Release notes

Sourced from lavamoat's releases.

lavamoat: v11.1.1

11.1.1 (2026-04-16)

Bug Fixes

• deps: update dependency resolve to v1.22.12 (#1951) (4a06108)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​lavamoat/aa bumped from ^5.0.0 to ^5.0.1

lavamoat: v11.1.0

11.1.0 (2026-04-15)

Features

• lavamoat-node: modernize resolve in lavamoat classic, opt-in only (#1928) (21f8d97)

Bug Fixes

• deps: update babel monorepo (#1680) (9739051)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • lavamoat-core bumped from ^18.0.1 to ^18.0.2
    • lavamoat-tofu bumped from ^9.0.0 to ^9.0.1

lavamoat: v11.0.1

11.0.1 (2026-04-02)

Bug Fixes

• deps: update dependency resolve to v1.22.11 (#1920) (5ed6202)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • lavamoat-core bumped from ^18.0.0 to ^18.0.1

Changelog

Sourced from lavamoat's changelog.

11.1.1 (2026-04-16)

Bug Fixes

• deps: update dependency resolve to v1.22.12 (#1951) (4a06108)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​lavamoat/aa bumped from ^5.0.0 to ^5.0.1

11.1.0 (2026-04-15)

Features

• lavamoat-node: modernize resolve in lavamoat classic, opt-in only (#1928) (21f8d97)

Bug Fixes

• deps: update babel monorepo (#1680) (9739051)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • lavamoat-core bumped from ^18.0.1 to ^18.0.2
    • lavamoat-tofu bumped from ^9.0.0 to ^9.0.1

11.0.1 (2026-04-02)

Bug Fixes

• deps: update dependency resolve to v1.22.11 (#1920) (5ed6202)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • lavamoat-core bumped from ^18.0.0 to ^18.0.1

Commits

• d4da884 chore: release main (#1957)
• 4a06108 fix(deps): update dependency resolve to v1.22.12 (#1951)
• 1f023d3 chore: release main (#1939)
• 21f8d97 feat(lavamoat-node): modernize resolve in lavamoat classic, opt-in only (#1928)
• 9739051 fix(deps): update babel monorepo (#1680)
• 8ccf3ad chore: release main (#1912)
• 5ed6202 fix(deps): update dependency resolve to v1.22.11 (#1920)
• See full diff in compare view

[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.28.4 ⏵ 7.29.0	+1		+1
	lavamoat@​11.0.0 ⏵ 11.1.1				+2

View full report

[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 resolve is 100.0% likely to have a medium risk anomaly Notes: This manifest uses a non-registry, relative-path dependency ('resolve': '../../../') which is a significant supply-chain risk because it allows arbitrary local code to be pulled in and executed without registry protections. Combined with the 'lerna bootstrap' postinstall script (which can trigger other lifecycle scripts across the monorepo), this setup increases the chance of untrusted code execution and other malicious behavior. Inspect the target of the relative path, all bootstrap-linked packages, and any lifecycle scripts before running npm install in an untrusted environment. Confidence: 1.00 Severity: 0.60 From: ? → npm/@lavamoat/allow-scripts@4.0.0 → npm/@lavamoat/webpack@2.1.1 → npm/lavamoat@11.1.1 → npm/depcheck@1.4.7 → npm/@emotion/react@11.14.0 → npm/eslint-plugin-import-x@4.6.1 → npm/vite-plugin-node-polyfills@0.23.0 → npm/jest@29.5.0 → npm/@babel/preset-env@7.23.2 → npm/webpack-cli@5.1.4 → npm/@rollup/plugin-node-resolve@15.1.0 → npm/resolve@1.22.12 ℹ 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/resolve@1.22.12. 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

[FrederikBolding]

@dependabot recreate

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.56%. Comparing base (31f2c55) to head (16bf866).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3978   +/-   ##
=======================================
  Coverage   98.56%   98.56%           
=======================================
  Files         429      429           
  Lines       12365    12365           
  Branches     1944     1944           
=======================================
  Hits        12187    12187           
  Misses        178      178           

☔ View full report in Codecov by Sentry.
📢 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.