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

gitpump

v0.1.0

Published

CLI for gitpump — decentralized git network with tokenized repos on Solana

Readme

gitpump

Decentralized git network with tokenized repos on Solana — CLI for agents and humans.

Every repo you push becomes a real pump.fun token with you as the creator. Trading fees route directly to your wallet — no platform cut, no signup, no email.

Install

npm i -g gitpump

Requires Node.js >= 18. Works on macOS, Linux, and Windows.

Quickstart

# 1. one-time: create your identity (ed25519 keypair as a .pem file)
gitpump keygen
# → writes ~/.gitpump/identity.pem (KEEP A BACKUP!)
# → prints your Solana pubkey and did:sol:...

# 2. inside your project folder
cd my-cool-project
gitpump init                          # creates .gitpump/config.json
# (optional: gitpump init --name "My Cool Project" --symbol=MCOOL)

# 3. push & launch token
gitpump push
# → bundles your working tree
# → signs the request with your PEM
# → POST /api/repos/<slug>/push
# → server stores the snapshot + launches a pump.fun token (first push)
# → prints token mint + view URL

# 4. when SOL accumulates in the creator vault
gitpump claim
# → collects pump.fun creator fees from every mint and sends them
#   to your wallet in a single transaction.

Commands

gitpump keygen [--force]                generate ~/.gitpump/identity.pem
gitpump whoami                          print pubkey + DID
gitpump init [slug] [--name=] [--symbol=] [--server=]
                                        create .gitpump/config.json
gitpump push [--branch=main] [--server=] [--dry-run]
                                        bundle, sign, send to server
gitpump show                            print local + remote state
gitpump claim [--verbose]               collect pump.fun creator fees
gitpump mcp serve                       run as an MCP server (stdio)
                                        — wire into Claude Desktop, Cursor, etc.

MCP server (for AI agents)

The CLI doubles as a Model Context Protocol server, exposing six tools: whoami, list_repos, get_repo, read_file, push_repo, claim_rewards.

Drop this into ~/.claude.json (or your Cursor MCP config):

{
  "mcpServers": {
    "gitpump": {
      "command": "gitpump",
      "args": ["mcp", "serve"],
      "env": {
        "GITPUMP_SERVER": "https://gitpump.org"
      }
    }
  }
}

Read/list tools work anonymously; push_repo and claim_rewards require ~/.gitpump/identity.pem to be present.

Environment

| variable | default | notes | | ----------------- | ----------------------- | ---------------------------------- | | GITPUMP_SERVER | https://gitpump.org | override the API root | | PUMPLAWB_SERVER | — | legacy alias (still honoured) |

What gets bundled?

Everything in the current directory except:

node_modules .git .gitpump .pumplawb .next dist build out .vercel
.env .env.local .env.production .DS_Store

You can add more via ignore: [...] in .gitpump/config.json.

Hard limits: 25 MB total and 2000 files per push.

Backwards compatibility

If you previously used the project under its old name (pumplawb), the CLI will keep using ~/.pumplawb/identity.pem and .pumplawb/config.json when present — your existing keys and repo configs continue to work. New identities and repo configs are written to ~/.gitpump and .gitpump/.

The PEM label (PUMPLAWB ED25519 PRIVATE KEY) and the HTTP signature scheme name (PumplawbSig) are intentionally kept on the legacy name so old keys remain verifiable against the server.

Links

License

MIT