npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@glideco/paymaster

v0.1.0

Published

Vendor-neutral EIP-4337 paymaster interface with Pimlico impl. PaymasterProvider abstraction pluggable across Pimlico / Alchemy Gas Manager / Biconomy. Cancel-vs-treasury-fallback race documented; nonce serialization via NonceClaimAdapter callback.

Downloads

122

Readme

@glideco/paymaster

Vendor-neutral EIP-4337 paymaster interface for EVM gas sponsorship.

import {
  resolvePaymasterProvider,
  registerPaymasterProvider,
  type PaymasterProvider,
  type SponsoredUserOp,
} from '@glideco/paymaster';

// Operator-supplied: Pimlico, Alchemy, Biconomy, mock, etc.
registerPaymasterProvider(myProvider);

const sponsored = await resolvePaymasterProvider('pimlico').sponsorUserOp({
  safeAddress: '0x...',
  calldata: '0x...',
  chain: 'base',
  policyId: 'policy_xyz',
  safeNonce: 5n,
});

Why an interface

Past gas-sponsorship vendors have shifted (Octane shut down April 2026). Locking to one vendor in code is a load-bearing assumption. Future vendor swap = add a new file behind this interface + flip the discriminator column in your DB. No router/orchestrator code changes.

Cancel vs treasury fallback

After a 30s no-receipt timeout + 60s additional poll, the operator's orchestrator should attempt cancelUserOp (if supported) before falling back to treasury-pays. This package defines the interface; the double-spend-prevention nonce-claim state machine lives in your application layer (see apps/web/src/server/lib/gas-sponsorship/safe-nonce-claim.ts in the Glide repo for an example Postgres-advisory-lock impl).

SemVer policy (D18)

@glideco/paymaster is the interface package. Concrete impl packages (@glideco/paymaster-pimlico, @glideco/paymaster-alchemy-solana, future @glideco/paymaster-biconomy, etc.) declare a peer-dep on it using a caret major range:

{
  "peerDependencies": {
    "@glideco/paymaster": "^1.0.0"
  }
}

Major-bump contract. A breaking change to the PaymasterProvider interface (added required method, removed/renamed type, changed signature, etc.) requires a coordinated major bump of every impl package in the same release. The interface package never bumps major in isolation — that would silently strand impls on incompatible versions.

Compatible additions. Adding an optional method (like cancelUserOp? or getReceipt?), a new error code variant, or a new optional field is a minor bump on the interface. Impls don't need to move; ones that implement the new optional surface ship a minor of their own.

Status of v0.13.0.0 packages. All ship at 0.1.0. The first incompatible interface change after publish gates the 1.0.0 release.

License

MIT