chore: Bump @metamask/permission-controller from 13.1.1 to 14.0.0

[dependabot]

Bumps @metamask/permission-controller from 13.1.1 to 14.0.0.

Commits

• e12dae8 Release 1247.0.0 (#10160)
• 6ccd29b Revert "Release 1247.0.0" (#10159)
• 6b9bd13 ci: remove partial build logic (#10158)
• 4dfae94 Fix dev-only lint errors in delegation packages (#10153)
• f1c8f6c Release 1247.0.0 (#10155)
• 55df130 Fix partial build step in CI to pass correct args to tsc (#10156)
• 1cf2689 chore!: bump TypeScript target and lib to ES2022 (#10019)
• 2a20a22 chore: bump TypeScript from 5 to 7, and add TypeScript 6 side by side (#9518)
• 4acf0d1 feat!: replace hybrid CJS/ESM build with ESM-only (#9536)
• 98d0eb1 chore!: Drop Node 18 and 20 (#9976)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​metamask/permission-controller since your current version.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​permission-controller@​14.0.0

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

Priority	Alert  (click "▶" to expand/collapse)	Action
	Potential security risk (AI signal): npm lodash-es is 80.0% likely risky Notes: No overt malware/backdoor/IO/exfiltration behavior is present in this module itself. However, it is a high-risk template compiler because it dynamically generates and compiles JavaScript via Function(...) using template-derived fragments and caller-supplied configuration. In particular, the evaluate directive inserts raw JavaScript into the generated source, and with (obj) broadens scope when variable is unset. Treat template strings and especially evaluate/interpolate content and options as fully trusted or strictly controlled; otherwise, this can enable arbitrary code execution in the context of the application. Confidence: 0.80 Severity: 0.70 From: packages/snaps-controllers/package.json → npm/@metamask/permission-controller@14.0.0 → npm/lodash-es@4.18.1 ℹ Read more on: This package | This alert | What are AI-detected potential security risks? 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 identified potential security problems in this package. It is advised to review the package thoroughly and assess the potential risks before installation. You may also consider reporting the issue to the package maintainer or seeking alternative solutions with a stronger security posture. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/lodash-es@4.18.1. 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

View full report