Skip to content

chore(deps): bump the npm-production group across 1 directory with 4 updates - #92

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-production-448cb22a88
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/npm-production-448cb22a88

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 16, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the npm-production group with 4 updates in the / directory: accounts, mppx, typebox and viem.

Updates accounts from 0.15.5 to 0.21.1

Release notes

Sourced from accounts's releases.

accounts@0.21.1

Patch Changes

  • b2535d3: Reclaim expired in-memory KV entries on writes and propagate finite cache TTLs to backing storage. Capacity remains unlimited by default; opt in with Kv.memory({ maxEntries }) to reject new keys at a chosen capacity without evicting live authentication state. Deployments must size an explicit cap and apply admission controls to avoid blocking legitimate writes.

    Validate the current adapter account before local access-key transaction paths and discard keys belonging to accounts omitted by a new wallet selection. Privy revocation now waits for successful execution before deleting local key state, retaining keys on pending or failed revocations.

    Upgrade Hono to 4.13.11 to fix double-decoding of static paths that could bypass middleware.

  • 00b6ee3: Updated viem to 2.57.12 and ox to 0.14.59, which derive configurable account addresses from the hash of the initial config. The viem peer range now starts at 2.57.12, since an earlier Viem derives other addresses.

  • 80bdb13: Handler.relay no longer signs as its own fee payer when a request names an app's fee payer URL and that relay returns an unsigned fill. It answers with an invalid-params error instead, so an app's URL can no longer make the relay's fee payer pay without its validate.

  • b38af80: Treat a retried eth_sendRawTransaction or eth_sendRawTransactionSync that the node rejects with already known or nonce too low as successful when the node knows the transaction's hash. viem's transports retry a submission after a timeout, a network error or a 5xx response, so a transaction that landed on the first attempt could previously fail the send.

    An access-key send that times out or loses its response no longer falls back to signing the same calls with the root account, which could send them twice.

  • 581bf10: Fixed Handler listeners to respond with a 400 to requests with an unparseable Host header or request target.

  • 9c6dee1: Fixed Node request listeners to safely cancel oversized uploads and close unfinished connections after sending the response.

  • 51f3b65: Added handoff to the postMessage tempoWallet() adapter and Handoff.read(). Tempo Wallet shows a QR code so someone without a passkey on the computer can approve the request with their phone. By default the requesting tab receives the result. With handoff.url, the phone's browser opens that page on the app's origin instead, and it receives the result and an access key the phone generated, which Handoff.read() returns. handoff: false hides the QR code.

  • 5fa1ac9: Close the postMessage popup session when its popup closes. A request sent within 250 ms after the previous popup closed (for example eth_sendTransaction right after wallet_connect) no longer reaches the closed window and fails; it opens a new popup instead.

  • afddb6d: Handler.relay answers eth_fillTransaction in fewer sequential RPC rounds. It simulates the requested calls alongside the fill instead of after it, and reuses that simulation unless a swap was prepended. It skips tempo_simulateV1 for 10 minutes after the node reports it unsupported. The autoSwap balance check reuses the fee-token balance already read during fee-token resolution.

  • 2c059cb: Removed the applePay deposit intent from wallet_deposit, wallet_connect and wallet_authorizeAccessKey. Tempo Wallet no longer offers fiat or card onramps; use mach for MACH checkout.

  • 85642db: Invalidate cached Privy accounts and access keys when the authenticated user changes. Preserve local access keys until shared revocation confirms successful execution.

  • 7b24e3e: Added WebAuthnCeremony.deferred, a WebAuthnCeremony.server variant that answers registration as soon as the passkey is created and verifies it with the server in the background, retrying requests that fail in transit. The webAuthn adapter makes logins and disconnects wait for that verification for up to 10 s, then cancels it, so it can't replace the session that follows. A registration whose server-parsed public key differs from the client's is refused, and one acknowledged without its session ends the session in place. If the server rejects the registration while the page is open, the adapter removes the account and its access keys and keeps the public key in storage; a later login with the passkey restores the account. WebAuthnCeremony.server now also ends its session on wallet_disconnect when passed as ceremony. WebAuthnCeremony.server's logout now fails on an error response other than 404. Handler.webAuthn's /register revokes the session presented with it when it issues a new one, and answers a retry after a stored registration with Credential already exists even when the challenge was already used.

  • 904e9b0: WebAuthnCeremony.deferred now also answers a login with a known passkey as soon as its signature checks out against the stored public key, and verifies it with the server (POST /login) in the background. verifyAuthentication takes an optional credential (the signed challenge, public key and RP ID) and signal, and may return verified, which resolves { session }. The webAuthn adapter passes its stored credential and makes later logins, sign-ups and disconnects wait for the verification. A login the server refuses (it doesn't know the credential, the signature fails, or a hook denies it with 401 or 403) ends the session in place and drops the account. A login whose outcome stays unknown (it failed in transit, a retry found its challenge consumed, or the server failed for another reason) ends the session in place (retrying the logout until it succeeds or a later login, sign-up or disconnect cancels it) and keeps the account. WebAuthnCeremony.server's verifyAuthentication now returns only its declared fields. Signing a digest with the latest registration's own credential (e.g. an access key authorized right after sign-up) no longer waits for that registration to land, since it needs no server login. verifyAuthentication also takes ready, a promise a server-backed ceremony waits for before sending /login: the adapter passes its wait for earlier registrations, so a deferred login answers at once and only its background /login waits. verifyRegistration takes ready too: a sign-up answers at once, and its background /register waits for logins and registrations still verifying, so it still sets the session last.

  • 84d2087: Added prefetch to WebAuthnCeremony.server and WebAuthnCeremony.deferred. It fetches a login and a registration challenge ahead of the ceremonies that use them, so their options are built locally instead of waiting for the server to store a challenge. Each challenge taken is replaced in the background. The webAuthn adapter's login with a known passkey uses a prefetched challenge (takeChallenge) instead of registering a random one. Handler.webAuthn's /register/options issues a challenge without a name, and /register then takes the name sent with the credential. It binds a random userId when none is sent, so Provider no longer generates one for wallet_connect sign-ups; WebAuthnCeremony.local, and WebAuthnCeremony.server when it requests its own options, generate a random one instead. The webAuthn adapter still passes a random one to ceremonies that don't prefetch.

    Handler.webAuthn's /register/options and /login/options now return the challenge ttl (seconds) alongside options, and /register rejects a login challenge.

  • 6a163eb: Handler.webAuthn: /register reads the challenge and checks for a duplicate credential in parallel, and deletes the challenge after responding when the runtime exposes waitUntil (pass the execution context to handler.fetch). Stores with take (e.g. Kv.memory, Kv.durableObject) now consume register and login challenges atomically, so each is single-use.

accounts@0.21.0

Minor Changes

  • a60b2c6: Added provider.ready(), which resolves once the provider has loaded its stored state and rejects with Store.HydrationError when the storage read fails or takes longer than the new hydrationTimeout option (default 10 seconds). request now waits for the load instead of continuing with an empty store after 100ms, and rejects with an RpcResponse.InternalError caused by the Store.HydrationError when the load fails. getAccount throws Store.HydrationError until the load finishes instead of reporting no accounts.

    The default storage now uses IndexedDB only where indexedDB exists, so React Native gets memory storage, and keeps state in memory when IndexedDB fails.

  • 4008d21: Add an optional chainId to wallet_revokeAccessKey so callers can revoke an access key on a specific chain. The provider rejects a chain it is not configured for. Local, Privy, dialog, device-code (including CLI), postMessage and mobile web auth revocations target that chain and remove the local key for it only after the revocation succeeds. Other JSON-RPC adapters reject a chainId other than the active chain. Omitting chainId keeps revoking on the active chain.

Patch Changes

  • 0488591: Limit the WebAuthn adapter's post-registration signing shortcut to the most recent registration, for 5 minutes, so it only applies while that registration still owns the server session. Any later registration, server login or disconnect falls back to server authentication.
  • 0488591: Prompt for the passkey while the WebAuthn ceremony registers the login challenge when the credential is already known (stored account or this session's registration), instead of after the /login/options round trip. Falls back to the ceremony's options if they differ from the locally built ones.
  • 6ec2640: Apply retryCount to wallet_revokeAccessKey in request-based adapters (device code, CLI, postMessage, mobile web auth), which now send revocations through the same transport as other wallet requests. Device-code and CLI revocations are still sent once by default, on the chain named in the request context.
  • af5e9b8: Send device-code wallet requests once by default. A failed or timed-out request such as eth_sendTransactionSync or wallet_revokeAccessKey was retried up to three times, starting a new approval (and possibly a second transaction) on each attempt. Added retryCount to deviceCode, cli, and the CLI Provider.create to opt back into retries. Chain reads still retry.
  • 6b06ace: Route wallet_updateAccessKey to the requested chainId for dialog, device-code, postMessage and mobile web auth adapters by carrying it in the request context, as wallet_revokeAccessKey does, instead of sending it only in params while the context names the active chain. Request-based updates honor retryCount like revocations. Mobile web auth now forwards the request context (account and chain) to the wallet like the other Wata transports, which also fixes chain routing for its revocations. Other JSON-RPC adapters reject a chainId other than the active chain instead of updating on it. wallet_revokeAccessKey and wallet_updateAccessKey reject an address that is not a connected account before any adapter runs, instead of opening the wallet for it.
  • 2a088fc: Reject wallet_updateAccessKey with UnsupportedChainIdError when chainId is not one of the provider's configured chains, instead of updating the key on the default chain. The request fails before any adapter or wallet approval runs and leaves local access-key state unchanged.

accounts@0.19.1

Patch Changes

  • 9cf6d39: Updated mppx to 0.12.0 and raised the viem peer dependency to >=2.57.1.
  • f06dd91: Updated wata to 0.4.2. This fixes device-code /token polls overwriting the user's approval on eventually-consistent stores like Cloudflare KV.
  • bdf2170: Check fee AMM liquidity before automatically selecting a transaction fee token, falling back to another funded token when the preferred or highest-balance token cannot settle the fee.

... (truncated)

Changelog

Sourced from accounts's changelog.

0.21.1

Patch Changes

  • b2535d3: Reclaim expired in-memory KV entries on writes and propagate finite cache TTLs to backing storage. Capacity remains unlimited by default; opt in with Kv.memory({ maxEntries }) to reject new keys at a chosen capacity without evicting live authentication state. Deployments must size an explicit cap and apply admission controls to avoid blocking legitimate writes.

    Validate the current adapter account before local access-key transaction paths and discard keys belonging to accounts omitted by a new wallet selection. Privy revocation now waits for successful execution before deleting local key state, retaining keys on pending or failed revocations.

    Upgrade Hono to 4.13.11 to fix double-decoding of static paths that could bypass middleware.

  • 00b6ee3: Updated viem to 2.57.12 and ox to 0.14.59, which derive configurable account addresses from the hash of the initial config. The viem peer range now starts at 2.57.12, since an earlier Viem derives other addresses.

  • 80bdb13: Handler.relay no longer signs as its own fee payer when a request names an app's fee payer URL and that relay returns an unsigned fill. It answers with an invalid-params error instead, so an app's URL can no longer make the relay's fee payer pay without its validate.

  • b38af80: Treat a retried eth_sendRawTransaction or eth_sendRawTransactionSync that the node rejects with already known or nonce too low as successful when the node knows the transaction's hash. viem's transports retry a submission after a timeout, a network error or a 5xx response, so a transaction that landed on the first attempt could previously fail the send.

    An access-key send that times out or loses its response no longer falls back to signing the same calls with the root account, which could send them twice.

  • 581bf10: Fixed Handler listeners to respond with a 400 to requests with an unparseable Host header or request target.

  • 9c6dee1: Fixed Node request listeners to safely cancel oversized uploads and close unfinished connections after sending the response.

  • 51f3b65: Added handoff to the postMessage tempoWallet() adapter and Handoff.read(). Tempo Wallet shows a QR code so someone without a passkey on the computer can approve the request with their phone. By default the requesting tab receives the result. With handoff.url, the phone's browser opens that page on the app's origin instead, and it receives the result and an access key the phone generated, which Handoff.read() returns. handoff: false hides the QR code.

  • 5fa1ac9: Close the postMessage popup session when its popup closes. A request sent within 250 ms after the previous popup closed (for example eth_sendTransaction right after wallet_connect) no longer reaches the closed window and fails; it opens a new popup instead.

  • afddb6d: Handler.relay answers eth_fillTransaction in fewer sequential RPC rounds. It simulates the requested calls alongside the fill instead of after it, and reuses that simulation unless a swap was prepended. It skips tempo_simulateV1 for 10 minutes after the node reports it unsupported. The autoSwap balance check reuses the fee-token balance already read during fee-token resolution.

  • 2c059cb: Removed the applePay deposit intent from wallet_deposit, wallet_connect and wallet_authorizeAccessKey. Tempo Wallet no longer offers fiat or card onramps; use mach for MACH checkout.

  • 85642db: Invalidate cached Privy accounts and access keys when the authenticated user changes. Preserve local access keys until shared revocation confirms successful execution.

  • 7b24e3e: Added WebAuthnCeremony.deferred, a WebAuthnCeremony.server variant that answers registration as soon as the passkey is created and verifies it with the server in the background, retrying requests that fail in transit. The webAuthn adapter makes logins and disconnects wait for that verification for up to 10 s, then cancels it, so it can't replace the session that follows. A registration whose server-parsed public key differs from the client's is refused, and one acknowledged without its session ends the session in place. If the server rejects the registration while the page is open, the adapter removes the account and its access keys and keeps the public key in storage; a later login with the passkey restores the account. WebAuthnCeremony.server now also ends its session on wallet_disconnect when passed as ceremony. WebAuthnCeremony.server's logout now fails on an error response other than 404. Handler.webAuthn's /register revokes the session presented with it when it issues a new one, and answers a retry after a stored registration with Credential already exists even when the challenge was already used.

  • 904e9b0: WebAuthnCeremony.deferred now also answers a login with a known passkey as soon as its signature checks out against the stored public key, and verifies it with the server (POST /login) in the background. verifyAuthentication takes an optional credential (the signed challenge, public key and RP ID) and signal, and may return verified, which resolves { session }. The webAuthn adapter passes its stored credential and makes later logins, sign-ups and disconnects wait for the verification. A login the server refuses (it doesn't know the credential, the signature fails, or a hook denies it with 401 or 403) ends the session in place and drops the account. A login whose outcome stays unknown (it failed in transit, a retry found its challenge consumed, or the server failed for another reason) ends the session in place (retrying the logout until it succeeds or a later login, sign-up or disconnect cancels it) and keeps the account. WebAuthnCeremony.server's verifyAuthentication now returns only its declared fields. Signing a digest with the latest registration's own credential (e.g. an access key authorized right after sign-up) no longer waits for that registration to land, since it needs no server login. verifyAuthentication also takes ready, a promise a server-backed ceremony waits for before sending /login: the adapter passes its wait for earlier registrations, so a deferred login answers at once and only its background /login waits. verifyRegistration takes ready too: a sign-up answers at once, and its background /register waits for logins and registrations still verifying, so it still sets the session last.

  • 84d2087: Added prefetch to WebAuthnCeremony.server and WebAuthnCeremony.deferred. It fetches a login and a registration challenge ahead of the ceremonies that use them, so their options are built locally instead of waiting for the server to store a challenge. Each challenge taken is replaced in the background. The webAuthn adapter's login with a known passkey uses a prefetched challenge (takeChallenge) instead of registering a random one. Handler.webAuthn's /register/options issues a challenge without a name, and /register then takes the name sent with the credential. It binds a random userId when none is sent, so Provider no longer generates one for wallet_connect sign-ups; WebAuthnCeremony.local, and WebAuthnCeremony.server when it requests its own options, generate a random one instead. The webAuthn adapter still passes a random one to ceremonies that don't prefetch.

    Handler.webAuthn's /register/options and /login/options now return the challenge ttl (seconds) alongside options, and /register rejects a login challenge.

  • 6a163eb: Handler.webAuthn: /register reads the challenge and checks for a duplicate credential in parallel, and deletes the challenge after responding when the runtime exposes waitUntil (pass the execution context to handler.fetch). Stores with take (e.g. Kv.memory, Kv.durableObject) now consume register and login challenges atomically, so each is single-use.

0.21.0

Minor Changes

  • a60b2c6: Added provider.ready(), which resolves once the provider has loaded its stored state and rejects with Store.HydrationError when the storage read fails or takes longer than the new hydrationTimeout option (default 10 seconds). request now waits for the load instead of continuing with an empty store after 100ms, and rejects with an RpcResponse.InternalError caused by the Store.HydrationError when the load fails. getAccount throws Store.HydrationError until the load finishes instead of reporting no accounts.

    The default storage now uses IndexedDB only where indexedDB exists, so React Native gets memory storage, and keeps state in memory when IndexedDB fails.

  • 4008d21: Add an optional chainId to wallet_revokeAccessKey so callers can revoke an access key on a specific chain. The provider rejects a chain it is not configured for. Local, Privy, dialog, device-code (including CLI), postMessage and mobile web auth revocations target that chain and remove the local key for it only after the revocation succeeds. Other JSON-RPC adapters reject a chainId other than the active chain. Omitting chainId keeps revoking on the active chain.

Patch Changes

  • 0488591: Limit the WebAuthn adapter's post-registration signing shortcut to the most recent registration, for 5 minutes, so it only applies while that registration still owns the server session. Any later registration, server login or disconnect falls back to server authentication.
  • 0488591: Prompt for the passkey while the WebAuthn ceremony registers the login challenge when the credential is already known (stored account or this session's registration), instead of after the /login/options round trip. Falls back to the ceremony's options if they differ from the locally built ones.
  • 6ec2640: Apply retryCount to wallet_revokeAccessKey in request-based adapters (device code, CLI, postMessage, mobile web auth), which now send revocations through the same transport as other wallet requests. Device-code and CLI revocations are still sent once by default, on the chain named in the request context.
  • af5e9b8: Send device-code wallet requests once by default. A failed or timed-out request such as eth_sendTransactionSync or wallet_revokeAccessKey was retried up to three times, starting a new approval (and possibly a second transaction) on each attempt. Added retryCount to deviceCode, cli, and the CLI Provider.create to opt back into retries. Chain reads still retry.
  • 6b06ace: Route wallet_updateAccessKey to the requested chainId for dialog, device-code, postMessage and mobile web auth adapters by carrying it in the request context, as wallet_revokeAccessKey does, instead of sending it only in params while the context names the active chain. Request-based updates honor retryCount like revocations. Mobile web auth now forwards the request context (account and chain) to the wallet like the other Wata transports, which also fixes chain routing for its revocations. Other JSON-RPC adapters reject a chainId other than the active chain instead of updating on it. wallet_revokeAccessKey and wallet_updateAccessKey reject an address that is not a connected account before any adapter runs, instead of opening the wallet for it.
  • 2a088fc: Reject wallet_updateAccessKey with UnsupportedChainIdError when chainId is not one of the provider's configured chains, instead of updating the key on the default chain. The request fails before any adapter or wallet approval runs and leaves local access-key state unchanged.

0.20.0

Minor Changes

... (truncated)

Commits
  • d307e33 chore: version packages (#897)
  • 51f3b65 feat(postMessage): add phone handoff option to tempoWallet (#931)
  • c15f5c6 chore: update viem to 0.0.0-9a2b41b1 (#930)
  • 7a2feb9 chore: update viem to 0.0.0-de39e106 for configurable account message signing...
  • 9c6dee1 fix(server): handle canceled Node request bodies (#927)
  • 9207c7f chore(site): upgrade vocs to 2.12.0 (#923)
  • 00b6ee3 chore: update viem to 2.57.12 and ox to 0.14.59 (#925)
  • 5a66fa0 fix(deps): patch SDK and tooling vulnerabilities (#915)
  • 2c059cb feat: remove applePay deposit intent (#922)
  • 581bf10 fix(server): respond 400 to an unparseable host or request target (#921)
  • Additional commits viewable in compare view

Updates mppx from 0.12.0 to 0.17.3

Release notes

Sourced from mppx's releases.

mppx@0.17.3

Patch Changes

  • f8852c3: Removed the eventsource-parser dependency. The MCP client protocol now reads the first event of a text/event-stream response with a small internal SSE parser.

mppx@0.17.1

Patch Changes

  • 95dd056: Fixed closing a Tempo session paid with a Viem Tempo access key account. signCloseAuthorization now signs the close authorization hash raw with the access key, as vouchers already do, instead of returning a keychain signature that TIP-1034 rejects.
  • ed76e8e: Accepted the RFC 9530 byte-sequence form (sha-256=:base64:) in BodyDigest.verify, alongside the existing bare form. BodyDigest.compute still emits the bare form.
  • 20eca32: Added feeToken to the Tempo charge client, so an access key whose spending limits exclude the default fee token can pay an unsponsored charge's fee in a token it may spend.
  • 2b747bf: Fixed Tempo charge settlement returning a fresh 402 after a paid transaction was mined: a broadcast rejected with ExpiringNonceReplay (for example, a retried send) now recovers the transaction's receipt instead of failing.
  • cd6a2a7: Fixed payment retries losing Request-carried HTTP methods and bodies, including valid body overrides. Rejected automatic payment after redirects with ambiguous method rewriting before creating credentials.
  • 807376f: Fixed cooperative HTTP session close inheriting the resource Request's body and abort signal while preserving its transport settings and the same resource URL.
  • 2ca12d1: Charged request-priced SSE-enabled content before invoking application handlers, including POST requests that return plain responses. Marked the receipt prepaid to avoid charging the first stream unit twice. Per-item pricing remained stream-driven. Applications must refund request charges when they cannot serve the accepted request.
  • 3fca0d6: Added an opt-in replay option to Proxy.create, so a payer who loses the connection during a long paid request can collect the response. The paid upstream request runs detached from the client, and a retry with the same credential and request gets the stored response, 202 while it runs, or a new upstream attempt after a failed delivery, without paying again.
  • afb9924: Fixed rejected WebSocket payments leaving sockets open when detailed error messages exceeded the close-frame reason limit.
  • 3c2bc84: Bound each session manager to its first HTTP origin and persisted that binding with reusable channels. Rejected cross-origin HTTP, SSE, and WebSocket reuse before disclosing channel hints or payment credentials, and prevented redirects from forwarding session requests. Existing unbound channel entries acquired an origin on their next validated reuse.
  • 9957b10: Applied the currencies, maxAmount, maxAtomicAmount and expectedRecipients client options to Tempo session payments. tempo() passed them only to its charge method; its session method, and tempo.session() given them directly, now skip offers in other currencies, to other recipients or above the cap during selection and reject them before signing or topping up a channel. An explicit close passed to Mppx.createCredential, fetch or the MCP client stays available for any offer: canHandleChallenge now receives the caller's credential context when it is known before selection.
  • 5d353bb: Prevented validation probes from authorizing payments through an installed global Mppx fetch wrapper.

mppx@0.17.0

Minor Changes

  • 25c8468: Simplified payment-stage identity. Breaking changes to mppx/identity:

    • Every payment offer in one 402 now carries the same HMAC-bound identity nonce, passed to verifiers as context.nonce. Bind payment-stage proofs to it instead of the challenge id. Routes may combine several offers with payment-stage identity (for example tempo()'s default currencies, or Tempo and Stripe), as long as they require the same verifiers; previously a route allowed only one such offer.
    • Verifiers issue their 402 challenge headers through a new optional challenge(request, { nonce }) hook, which runs once per 402, instead of returning them from verify as missing. verify only checks proofs.
    • Prover.retry is split: prepare(response, { challenge }) runs on a 402 before the payment retry, and retry(response) runs on other rejections and returns whether to resend.

Patch Changes

  • b149237: Raised the @​hono/node-server override to 2.1.5 to resolve a dependency audit advisory.
  • faa4735: Fixed the client throwing No Payment schemes found. on a 402 whose WWW-Authenticate has no Payment challenge, so other protocols such as x402 now handle it.
  • 73b464f: Fixed the Tempo charge client signing a sponsored transaction whose validBefore had fewer than 15 seconds left after slow preparation: the pre-sign check now measures validBefore as well as the challenge expiry.
  • a0d54fd: Enforced the fee payer's 15-second remaining-validity minimum for Tempo charges: clients refused to sign a sponsored pull transaction for a challenge expiring in under 15 seconds, checking again right before signing, and servers refused to issue a sponsored challenge with a paid amount and pull mode that expires that soon. Push and zero-amount challenges were exempt. Request hooks received the expiry echoed by the credential when verifying it.
  • 7a68c55: Fixed focused tests failing in a clean checkout by generating the HTML modules on demand, and the package check's cleanup reinstalling dependencies with the publish manifest.
  • 443ad6d: Improved mppx validate SSE receipt scanning to search only newly received text for event boundaries, so long events no longer cost quadratic time.

mppx@0.16.0

Minor Changes

  • 793aa2b: Replaced request attestation with per-route identity. Breaking changes:

    • mppx/attestation became mppx/identity. Server Mppx.create({ attestation }) was removed (passing it now throws); routes take identity: [verifier, ...] (all required), for example mppx.charge({ amount, identity: [tap] }), and the result exposes result.identity.get(verifier).
    • Added Identity.anyOf(...) to accept one of several protocols. Every member runs, so each presented proof is consumed.
    • Verifiers return missing, invalid or valid (unverified became invalid with code 403), may set their own status code and headers, and declare a stage: request (checked before any 402) or payment (adds headers to the 402 and is checked against the answered challenge and credential before settlement). Identity rejections are returned on the non-200 branch as a 401/403 response.
    • A composed route can include at most one offer with payment-stage identity. Payment-stage identity is not supported on methods with a preflight hook.
    • Client attestation signer maps became identity: [prover, ...]. Provers have a required origin scope, receive the payment challenge in prove(request, context), and can prepare proofs or request one resend with retry(response, context). Requests that carry proofs do not follow redirects.
    • TAP and Web Bot Auth moved to mppx/extensions/identity/tap and mppx/extensions/identity/web-bot-auth; Client.signer became Client.prover.

... (truncated)

Changelog

Sourced from mppx's changelog.

0.17.3

Patch Changes

  • f8852c3: Removed the eventsource-parser dependency. The MCP client protocol now reads the first event of a text/event-stream response with a small internal SSE parser.

0.17.2

Patch Changes

  • 247dc02: Rendered nested problem-details fields (such as details) as JSON in the CLI's Payment Rejected output instead of [object Object].

  • d87c8bb: Removed @stripe/stripe-js from dependencies. The Stripe HTML payment page bundles Stripe.js at build time, and the Stripe Elements option types in stripe.charge's html.elements are now inlined, so the published types no longer import @stripe/stripe-js.

  • a384733: Added Store.durableObject() and Store.DurableObjectStore, an atomic store backed by Cloudflare Durable Objects (one object per key, compare-and-swap with jittered retries), for running tempo.session() and replay protection on Cloudflare Workers.

  • adaeef7: Fixed Tempo and Stripe server bundles always including their HTML payment page: the page now loads with a dynamic import() the first time it is rendered, and html.content also accepts an async loader.

  • 2060c5f: Bound automatic session signatures and stored channel reuse to the authorized HTTP origin. Applied trustedTempoProofRealms to session challenges and forwarded manager pins. Added session({ origin }) for direct credentials that will be reused over HTTP; originless stored channels must be explicitly migrated or closed rather than silently rebound. Use separate channel stores per HTTP origin because each payment scope retains a single channel.

    Preserved request swap policies for automatic session top-ups and payment suppression through identity wrappers. Kept MCP adapter approval and payer selection authoritative when global payment fetch is installed. Limited proxy request bodies, including free routes, to 10 MiB by default with a configurable maxRequestBodySize.

    Required explicit origin trust for remote snapshot recovery and rejected opaque origins. Preserved explicit CLI closing of legacy channels through validated origin migration. Returned payment challenges before buffering unpaid uploads and rejected oversized tee branches without waiting for sibling cancellation.

  • 55a7b62: Credited prepaid SSE items that failed before delivery when their spend remained unsettled. Added an idempotent merchant reconciliation hook for declined or uncertain credits, preserving settled funds and delivered-item charges.

    Automatic prepaid credits are opt-in with sse: { autoCreditPrepaid: true, onRefundRequired }; existing merchant refund handlers remain unchanged. Delivery obligations persist in channel state before a managed stream starts, with bounded records and idempotent credit retries. Refund jobs distinguish uncertain writes from definite failures and expose only finalized captured funds as externally refundable. HTTP close receipts accept spend reduced by credits while retaining authorization and scope validation.

  • 7a18dac: Fixed sponsored preflight simulation billing the sender's fee token. Tempo nodes recover the fee payer of an eth_call only from feePayerSignature and ignore a bare feePayer address, so the final simulation charged the sender, and payments failed with "insufficient fee token balance" when the sponsor picked a fee token the sender did not hold. The simulation now carries the sponsor's signature: hosted sponsors return it from eth_fillTransaction (fillHostedFeePayerTransaction now returns feePayerSignature), and local fee-payer accounts sign a simulation-only copy with the new signFeePayerSimulation, only after the sender simulation passes. The sender simulation now runs at the transaction's exact gas limit with zero fee fields and the fields that set its intrinsic gas, so a transaction whose gas is too low is rejected before broadcast without needing a sender fee balance. The local simulation-only copy adds up to sponsoredSimulationGasBuffer (10,000) gas, because a sponsored eth_call charges more gas than the mined transaction uses, clamped to the fee payer policy's maxGas and maxTotalFee (sponsoredSimulationGas). When the sponsored simulation runs without the full buffer (hosted signatures, or clamped padding), a failure that is only out of gas no longer rejects the payment; fee balance errors and reverts still do.

  • a4d7a8e: Added Store.sql(), an atomic store on SQL databases (single-statement compare-and-swap, no transactions needed, and replay claims in one statement), with Store.postgres() for pg, Neon, Vercel Postgres, Supabase and PGlite, Store.sqlite() for node:sqlite, better-sqlite3 and bun:sqlite, and Store.d1() for Cloudflare D1.

  • 8be5d55: Fixed esbuild bundles including all of zod/mini by importing it as a namespace in mppx's zod helpers, so unused validators tree-shake.

0.17.1

Patch Changes

  • 95dd056: Fixed closing a Tempo session paid with a Viem Tempo access key account. signCloseAuthorization now signs the close authorization hash raw with the access key, as vouchers already do, instead of returning a keychain signature that TIP-1034 rejects.
  • ed76e8e: Accepted the RFC 9530 byte-sequence form (sha-256=:base64:) in BodyDigest.verify, alongside the existing bare form. BodyDigest.compute still emits the bare form.
  • 20eca32: Added feeToken to the Tempo charge client, so an access key whose spending limits exclude the default fee token can pay an unsponsored charge's fee in a token it may spend.
  • 2b747bf: Fixed Tempo charge settlement returning a fresh 402 after a paid transaction was mined: a broadcast rejected with ExpiringNonceReplay (for example, a retried send) now recovers the transaction's receipt instead of failing.
  • cd6a2a7: Fixed payment retries losing Request-carried HTTP methods and bodies, including valid body overrides. Rejected automatic payment after redirects with ambiguous method rewriting before creating credentials.
  • 807376f: Fixed cooperative HTTP session close inheriting the resource Request's body and abort signal while preserving its transport settings and the same resource URL.
  • 2ca12d1: Charged request-priced SSE-enabled content before invoking application handlers, including POST requests that return plain responses. Marked the receipt prepaid to avoid charging the first stream unit twice. Per-item pricing remained stream-driven. Applications must refund request charges when they cannot serve the accepted request.
  • 3fca0d6: Added an opt-in replay option to Proxy.create, so a payer who loses the connection during a long paid request can collect the response. The paid upstream request runs detached from the client, and a retry with the same credential and request gets the stored response, 202 while it runs, or a new upstream attempt after a failed delivery, without paying again.
  • afb9924: Fixed rejected WebSocket payments leaving sockets open when detailed error messages exceeded the close-frame reason limit.
  • 3c2bc84: Bound each session manager to its first HTTP origin and persisted that binding with reusable channels. Rejected cross-origin HTTP, SSE, and WebSocket reuse before disclosing channel hints or payment credentials, and prevented redirects from forwarding session requests. Existing unbound channel entries acquired an origin on their next validated reuse.
  • 9957b10: Applied the currencies, maxAmount, maxAtomicAmount and expectedRecipients client options to Tempo session payments. tempo() passed them only to its charge method; its session method, and tempo.session() given them directly, now skip offers in other currencies, to other recipients or above the cap during selection and reject them before signing or topping up a channel. An explicit close passed to Mppx.createCredential, fetch or the MCP client stays available for any offer: canHandleChallenge now receives the caller's credential context when it is known before selection.
  • 5d353bb: Prevented validation probes from authorizing payments through an installed global Mppx fetch wrapper.

0.17.0

Minor Changes

  • 25c8468: Simplified payment-stage identity. Breaking changes to mppx/identity:

... (truncated)

Commits
  • cf9cf65 chore: version packages (#1193)
  • f8852c3 refactor: replace eventsource-parser with an internal SSE parser (#1192)
  • e17dac3 chore: version packages (#1171)
  • 4f176c4 docs(store): fix libSQL guidance in Store.sqlite JSDoc (#1191)
  • fdc8a21 fix(examples): serve content for session POSTs mppx bills as content (#1190)
  • a4d7a8e feat(store): add SQL store for Postgres, SQLite and D1 (#1187)
  • 3ce0231 feat(examples): run examples as Cloudflare Workers in workerd (#1188)
  • a384733 feat(store): add Durable Object store with workerd integration tests (#1182)
  • 7a18dac fix(tempo): simulate sponsored transactions with the fee payer signature (#1179)
  • adaeef7 fix: load the Tempo and Stripe payment pages lazily (#1178)
  • Additional commits viewable in compare view

Updates typebox from 1.3.6 to 1.4.5

Commits

Updates viem from 2.57.1 to 2.57.16

Release notes

Sourced from viem's releases.

viem@2.57.16

Patch Changes

  • #5395 c60ca26e030706610bcf61689331008a30a3db2a Thanks @​jxom! - viem/tempo: gatewayActions paid in the Gateway currency the Client account held most of, threw Gateway.InsufficientFundsError (with the account's balances) when it couldn't pay, and explained how to pay in Gateway.PaymentRequiredError.

  • #5392 9348d386a9f62fd6713124e25360d6040e4a34cf Thanks @​gakonst! - Stopped retrying JSON-RPC method-not-found (-32601) and method-not-supported (-32004) errors from non-2xx HTTP responses, since a retry gets the same refusal.

  • #5392 9348d386a9f62fd6713124e25360d6040e4a34cf Thanks @​gakonst! - Reduced per-request overhead of the http, webSocket and ipc transports by building the onFetchRequest Request only when the hook is set and the TimeoutError only when a request times out, and fetched the withdrawal receipt once in the ZKsync finalizeWithdrawal and isWithdrawalFinalized actions.

  • #5392 9348d386a9f62fd6713124e25360d6040e4a34cf Thanks @​gakonst! - Cached signature hashes in toSignatureHash, so selector lookups in decodeFunctionData, decodeEventLog, decodeErrorResult and encodeFunctionData no longer hash every ABI item on each call.

  • #5391 721d6824516514195c0a98971731c6d81b2f9032 Thanks @​jxom! - viem/tempo: Added experimental Gateway and gatewayActions (client.ai, client.bucket, client.compute, client.kv), with standalone Actions.ai, Actions.bucket, Actions.compute, and Actions.kv, with client.gateway.getCapabilities, Actions.gateway.getCapabilities and defaults for every option (gatewayActions()), for wallet-paid inference (including streamed text), object storage, metered and streamed CPU and GPU compute, and key-value state on a Tempo Gateway paid with a local Client account through the optional mppx peer dependency, with Tempo Wallet through the Accounts SDK, or with an app-supplied payment-aware fetch.

viem@2.57.15

Patch Changes

  • #5339 a864b864b8b9031d970910fb8247471924d09280 Thanks @​mortezashojaei! - Fixed getAbiItem to throw AbiItemAmbiguityError for overloads that JavaScript cannot distinguish, such as bytes vs bytes32, uint256 vs int256, and uint256[] vs uint256[2], while resolving distinguishable values by byte length and integer range.

  • #5321 af062571382ec3631cf1901aeda9b58a87c8fad5 Thanks @​evanaronson! - Removed a trailing slash to the ZKsync explorer URL.

  • #5358 179a53682d9bf2ac2b7a65a86ec312fca0c7c9a8 Thanks @​Turkchain1919! - Added Turkchain Mainnet (Chain ID: 1919) to the supported chains.

  • #5375 bb12b94649962cd7f03c339c226399c614b49805 Thanks @​jxom! - Fixed decodeEventLog and parseEventLogs to decode anonymous event logs when eventName names the event or every event in abi is anonymous, as with getLogs and watchEvent given a single anonymous event.

  • #5364 8f2a79ba8b4d235a24c4c101f4ef04a824c3e429 Thanks @​jxom! - ccip: Applied the HTTP transport timeout (including its override) and 10 MiB response cap to CCIP-Read gateway requests, refused non-HTTP(S) gateway URLs (including data: URLs, which previously worked), and limited one lookup to 4 nested callbacks, 4 nested local batches, 256 gateway requests and 16 concurrent requests.

  • #5372 f32ef6c41e623683b99989422eac7ac6cea5c107 Thanks @​jxom! - Fixed estimateGas and estimateContractGas returning a gas limit filled by eth_fillTransaction that ignored blockNumber, blockTag, and stateOverride.

  • #5360 41801d827e339b96d1b4dd775f4dd379f17cc610 Thanks @​jxom! - Raised the default expiring nonce validBefore from 25 to 270 seconds, capped Relay.feePayer expiring nonce windows at 300 seconds, added Transaction.expiringNonceMaxExpiry, and replaced the random expiring nonce validAfter with a random nonce discriminator.

  • #5360 41801d827e339b96d1b4dd775f4dd379f17cc610 Thanks @​jxom! - Fixed sponsored prepareTransactionRequest fills keeping a requested feeToken that the fee payer did not sign, which made the fee payer signature invalid.

  • #5378 cbdd61078378012368464c9b0e4a76804a5ea987 Thanks @​mmv08! - Fixed fillTransaction and prepareTransactionRequest returning gasPrice next to EIP-1559 fees on Anvil, which made estimateGas and sendTransaction fail on Anvil 1.8.5 and later with "both gasPrice and (maxFeePerGas or maxPriorityFeePerGas) specified".

  • #5346 7156f80f77c47c0a3f9df479b0a6e856029edb3b Thanks @​KieranAltman! - Updated HashKey Chain and HashKey Chain Testnet display names, native currency name, and block explorer URLs.

  • #5373 ddc2d365d093793f9d8f5818743f169c98eed8d7 Thanks @​jxom! - Added an optional nonce to NonceManager reset parameters, which sendTransaction and sendTransactionSync now set to the consumed nonce when a send fails after consume returned.

  • #5371 035c519b6b6b3f179fa741953751a501f05132a2 Thanks @​jxom! - Fixed parseTransaction to accept an EIP-7702 authorization yParity from 2 to 255 so a serialized transaction parses back, and made recoverAuthorizationAddress throw InvalidYParityError (and verifyAuthorization return false) for a yParity other than 0 or 1, which EIP-7702 treats as having no authority.

  • #5318 57db085e896dfee3a3387fb7573bf7f7ebc6170d Thanks @​jxom! - Fixed parseTransaction not raising TipAboveFeeCapError when the encoded maxFeePerGas is zero.

  • #5377 42c41ca3c42792e56a2e1f64d3007c28adc9fbba Thanks @​mmv08! - Fixed sendTransactionSync and writeContractSync failing at once and freeing the nonce when the node had accepted the transaction but stopped waiting for its receipt (eth_sendRawTransactionSync error code 4), even if the error had no transaction hash, and stopped fallback from sending that transaction to the next node.

  • #5388 141f8c0ed7f5fdeafbfc514131781638e9340bd9 Thanks @​jxom! - Added Account.serialize and Account.deserialize to viem/tempo, which store a configurable account (TIP-1107) as JSON and rebuild it with passkey owners that sign, and Account.AddressMismatchError for a version-zero config that does not derive the stored address. Added a keyAuthorization option to access key accounts, which attaches a signed key authorization to the account's transactions until the chain registers the access ke...

    Description has been truncated

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 16, 2026
@socket-security

socket-security Bot commented Oct 16, 2026 •

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedaccounts@​0.15.5 ⏵ 0.21.196100100 +1100 +2100
Updatedtypebox@​1.3.6 ⏵ 1.4.510010099 +196 +2100
Updatedviem@​2.57.1 ⏵ 2.57.1697100100 +198 +1100
Updatedmppx@​0.8.15 ⏵ 0.17.39910010098100

View full report

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review found no issues

No high-confidence issues detected in this change.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/npm-production-448cb22a88 branch from b47cfd0 to 98e07b0 Compare October 22, 2026 14:47

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review found no issues

No high-confidence issues detected in this change.

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/npm-production-448cb22a88 branch 2 times, most recently from 4e630b4 to fb6291a Compare October 23, 2026 23:34

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reviewed the latest push and didn't find any bugs. The accounts bump crosses six pre-1.0 minor versions that change provider behavior, and the code that depends on it can't be type-checked or tested here, so a human should run the tests before merging.

What was reviewed:

  • The package.json range changes (accounts ^0.21.0, mppx ^0.13.5) and the regenerated pnpm-lock.yaml. Only resolutions and transitive packages change, plus @ cfworker/json-schema and @ modelcontextprotocol/server are dropped.
  • How src/mpp.ts uses accounts/cli. createTempoProvider calls store.persist.rehydrate() by hand, and resolveWalletSource then calls provider.getAccount(). According to the 0.21.0 notes, getAccount now throws Store.HydrationError until the provider finishes loading, and provider.ready() is the new way to wait for that. I couldn't confirm that a manual rehydrate counts as finished loading.
  • The device-code and CLI requests used during wallet setup now send only once by default (retryCount). That is safer, but it changes how setup behaves.
Extended reasoning...

This automated dependency bump changes only package.json and pnpm-lock.yaml. The packages it bumps (accounts, mppx, viem) handle wallet access keys and payment signing in src/mpp.ts. Since my earlier reviews, a new commit regenerated the bump to accounts 0.21.0, which changes provider hydration and getAccount semantics. src/mpp.ts calls those APIs directly, and node_modules isn't installed here, so compatibility couldn't be checked. The jump across several pre-1.0 versions in payment-related code decided defer over approve.

…updates

Bumps the npm-production group with 4 updates in the / directory: [accounts](https://github.com/tempoxyz/accounts), [mppx](https://github.com/wevm/mppx), [typebox](https://github.com/sinclairzx81/typebox) and [viem](https://github.com/wevm/viem).


Updates `accounts` from 0.15.5 to 0.21.1
- [Release notes](https://github.com/tempoxyz/accounts/releases)
- [Changelog](https://github.com/tempoxyz/accounts/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tempoxyz/accounts/compare/accounts@0.15.5...accounts@0.21.1)

Updates `mppx` from 0.12.0 to 0.17.3
- [Release notes](https://github.com/wevm/mppx/releases)
- [Changelog](https://github.com/wevm/mppx/blob/main/CHANGELOG.md)
- [Commits](https://github.com/wevm/mppx/compare/mppx@0.12.0...mppx@0.17.3)

Updates `typebox` from 1.3.6 to 1.4.5
- [Commits](sinclairzx81/typebox@1.3.6...1.4.5)

Updates `viem` from 2.57.1 to 2.57.16
- [Release notes](https://github.com/wevm/viem/releases)
- [Commits](https://github.com/wevm/viem/compare/viem@2.57.1...viem@2.57.16)

---
updated-dependencies:
- dependency-name: accounts
  dependency-version: 0.19.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-production
- dependency-name: mppx
  dependency-version: 0.13.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-production
- dependency-name: typebox
  dependency-version: 1.3.36
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-production
- dependency-name: viem
  dependency-version: 2.57.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/npm-production-448cb22a88 branch from fb6291a to 5555b5d Compare November 14, 2026 01:36

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review found no issues

No high-confidence issues detected in this change.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants