Update template to v0.13

[AyushBherwani1998]

Note

Upgrade to Delegation Toolkit v0.13 and migrate permission flow to periodic transfers with updated APIs, types, and config (drop RPC env).

• Permissions flow (ERC-7715):
  • Replace grantPermissions with requestExecutionPermissions and switch to native-token-periodic (0.001 ETH/day) with isAdjustmentAllowed: false in src/components/GrantPermissionsButton.tsx.
  • Update types from GrantPermissionsReturnType to RequestExecutionPermissionsReturnType in PermissionProvider.
  • Adjust UI/schema handling (expiry source, remove start) in src/components/PermissionInfo.tsx.
• Redeem updates:
  • Remove accountMetadata usage; use only context/delegationManager in src/components/RedeemPermissionButton.tsx.
• Session account:
  • Rename signatory to signer in toMetaMaskSmartAccount call in SessionAccountProvider.
• Config:
  • publicClient now uses http() (drop NEXT_PUBLIC_RPC_URL).
  • Update .env.example/README to reflect only NEXT_PUBLIC_PIMLICO_API_KEY.
• Dependencies:
  • Bump @metamask/delegation-toolkit to ^0.13.0 and refresh lockfile.

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
templated-gator-7715	Ready	Preview	Comment	Oct 16, 2025 9:38pm

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​tailwindcss/​oxide-android-arm64@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-darwin-arm64@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-darwin-x64@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-freebsd-x64@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-linux-arm-gnueabihf@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-linux-arm64-gnu@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-linux-arm64-musl@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-linux-x64-gnu@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-linux-x64-musl@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-win32-arm64-msvc@​4.1.11 ⏵ 4.1.14
	@​tailwindcss/​oxide-win32-x64-msvc@​4.1.11 ⏵ 4.1.14
	@​unrs/​resolver-binding-android-arm-eabi@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-android-arm64@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-darwin-arm64@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-darwin-x64@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-freebsd-x64@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-arm-gnueabihf@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-arm-musleabihf@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-arm64-gnu@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-arm64-musl@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-ppc64-gnu@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-riscv64-gnu@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-riscv64-musl@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-s390x-gnu@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-x64-gnu@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-linux-x64-musl@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-win32-arm64-msvc@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-win32-ia32-msvc@​1.9.2 ⏵ 1.11.1
	@​unrs/​resolver-binding-win32-x64-msvc@​1.9.2 ⏵ 1.11.1
	node-releases@​2.0.19 ⏵ 2.0.23				-3
	@​img/​sharp-darwin-arm64@​0.34.3 ⏵ 0.34.4
	@​img/​sharp-darwin-x64@​0.34.3 ⏵ 0.34.4
See 107 more rows in the dashboard

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		[email protected] has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → 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.
Block		[email protected] has Network access. Module: http Location: Package overview From: yarn.lock → 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.
Block		[email protected] has Network access. Module: https Location: Package overview From: yarn.lock → 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		[email protected] has Install scripts. Install script: postinstall Source: napi-postinstall unrs-resolver 1.11.1 check From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is an install script? 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 not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. 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		@emnapi/[email protected] is a AI-detected potential code anomaly. Notes: This file implements a WASM/N-API runtime bridge (emnapi) exposing many napi_* functions, memory-view and buffer helpers, thread/worker management and threadsafe function queues. It uses dynamic function creation via new Function (with identifier validation), direct WebAssembly memory reads/writes (DataView/Uint8Array), Atomics/SharedArrayBuffer for cross-thread signaling, and postMessage transfers of ArrayBuffers. There is no evidence of malicious behavior (no network callbacks, no shell or file operations, no hard-coded secrets), but these powerful primitives can enable unexpected code execution or data movement if untrusted inputs reach them. Confidence: 1.00 Severity: 0.60 From: yarn.lock → npm/@emnapi/[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/@emnapi/[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		[email protected] is a AI-detected potential code anomaly. Notes: This is a legitimate template compiler implementation that uses dynamic code generation (Function constructor) and optional 'with' scope. It is not malicious by intent in the provided fragment, but it exposes typical high-risk behaviors: arbitrary code execution via evaluate delimiters, potential XSS from unescaped interpolation, and broader attack surface if untrusted templates or imports are used. Use only with trusted templates or ensure strict delimiter/escaping policies. No evidence of backdoor, exfiltration, or obfuscated malicious payloads found in the provided code. Confidence: 1.00 Severity: 0.60 From: yarn.lock → 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.
Warn		[email protected] is a AI-detected potential code anomaly. Notes: The code represents a legitimate and well-structured signing module for a multi-owner wallet with WebAuthn support. It implements standard flows for signing typed data and user operations, and encodes signatures for on-chain verification. No evidence of covert data leakage, backdoors, or malicious behavior is detected within this fragment. Potential risks stem from UI trust boundaries and signer implementation integrity, not from the fragment itself. Confidence: 1.00 Severity: 0.60 From: package.json → 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.
Warn		[email protected] is a AI-detected potential code anomaly. Notes: The provided ABI fragment represents a standard account abstraction/smart account interface, exposing high-privilege operations (execute, executeBatch) and user operation validation. There is no explicit malicious behavior visible in the ABI itself, but the architectural pattern inherently carries security risk if access control and operation authorization are lax in the implementation. The fragment should be audited alongside the concrete contract to verify proper authorization, nonce management, and safe external calls. Confidence: 1.00 Severity: 0.60 From: package.json → 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