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

@arbitrum/mpp

v0.1.0

Published

Make payments using MPP (Machine Payments Protocol) on Arbitrum

Downloads

100

Readme

arbitrum-mpp

Make payments using MPP (Machine Payments Protocol) on Arbitrum.

package structure

arbitrum-mpp/
├── src/
│   ├── index.ts              # Re-export shared schemas
│   ├── Methods.ts            # Shared Method.from() definitions
│   ├── default.ts            # Default shared values
│   ├── client/
│   │   ├── index.ts          # ./client entry point
│   │   └── Charge.ts         # Client charge implementation
│   └── server/
│       ├── index.ts          # ./server entry point
│       └── Charge.ts         # Server charge implementation
└── test/
│   ├── client.ts             # example client implementation
│   └── server.ts             # example server implementation
├── package.json
└── tsconfig.json

client/Charge.ts is responsible for taking a servers Challenge and creating a Credential which contains a signature and information about how the client wants to pay, what they want to pay for, etc

server/Charge.ts is responsible for both defining the Challenge along with taking in a clients Credential and checking its validity. If valid, the server will submit the transaction and verify the payment went through.

Useful documentation references:

Running the test

To try it out locally, start the server in one terminal:

npm run server

Then, in a separate terminal, run the client:

npm run client

Make sure the server has eth and the client has a compatible ERC-20 (Currently only USDC)