chore: Bump @lavamoat/allow-scripts from 3.4.0 to 3.4.1

[dependabot[bot]]

Bumps @lavamoat/allow-scripts from 3.4.0 to 3.4.1.

Release notes

Sourced from @​lavamoat/allow-scripts's releases.

allow-scripts: v3.4.1

3.4.1 (2025-11-19)

Bug Fixes

• deps: fix npm audit issues (#1853) (5ba0f2d)

Changelog

Sourced from @​lavamoat/allow-scripts's changelog.

3.4.1 (2025-11-19)

Bug Fixes

• deps: fix npm audit issues (#1853) (5ba0f2d)

Commits

• 3a2edd4 chore: release main (#1849)
• 5ba0f2d fix(deps): fix npm audit issues (#1853)
• 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)

---

[!NOTE] Updates @lavamoat/allow-scripts from 3.4.0 to 3.4.1 in root and all packages, refreshing yarn.lock with related transitive dependency upgrades.

• Dependencies:
  • Bump @lavamoat/allow-scripts devDependency from ^3.4.0 to ^3.4.1 across the monorepo (root and all workspaces).
  • Refresh yarn.lock, updating transitive packages (e.g., @npmcli/*, make-fetch-happen, cacache, node-gyp, tar, which, etc.).

^{Written by Cursor Bugbot for commit ffb78924c9c23085efd5de11bcd0f9ab17aff30d. This will update automatically on new commits. Configure here.}

[socket-security[bot]]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​lavamoat/​allow-scripts@​3.4.0 ⏵ 3.4.1

View full report

[socket-security[bot]]

[!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		Network access: npm lru-cache in module globalThis["fetch"] Module: globalThis["fetch"] Location: Package overview From: ? → npm/@lavamoat/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is network access? 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: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. 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.
Warn		Potential code anomaly (AI signal): npm node-gyp is 100.0% likely to have a medium risk anomaly Notes: The code is a legitimate Windows registry query and filesystem readability utility, with no inherent malware or backdoors. Primary security concerns are data exposure through verbose logging and the potential misuse of reg.exe with untrusted inputs. Mitigations include restricting input sources, redacting sensitive outputs in logs, and ensuring callers handle registry data securely. Overall security risk is moderate due to sensitive operations and logging exposure, but no active malicious behavior detected. Confidence: 1.00 Severity: 0.60 From: ? → npm/@lavamoat/[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

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 98.28%. Comparing base (fc9ab36) to head (0b4d0d6).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3744   +/-   ##
=======================================
  Coverage   98.28%   98.28%           
=======================================
  Files         420      420           
  Lines       12211    12211           
  Branches     1889     1889           
=======================================
  Hits        12002    12002           
  Misses        209      209           

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:rocket: New features to boost your workflow:

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