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

@beinfi/cli

v0.2.7

Published

Infi CLI — init/scaffold, login, API keys, sandbox provisioning, and billing sync

Readme

@beinfi/cli

Operator CLI for Infi — port of the Go beinfi-cli, built on @beinfi/sdk.

npm install -g @beinfi/cli
# or
bunx @beinfi/cli sandbox create

Commands

| Command | Description | |---------|-------------| | infi login --token <session> | Exchange dashboard session for API key (saved to ~/.config/infi/config.json) | | infi keys list | List tenant API keys | | infi keys create | Create a new secret key | | infi keys revoke <id> | Revoke a key | | infi sandbox create | Provision claimable sandbox (ref=cli) | | infi sandbox get <id> | Poll public sandbox status | | infi sync [file] | Apply infi.company.ts (--plan for dry-run) | | infi pull [file] | Backend → infi.company.ts + lock | | infi providers [list] | BYOP connection status (provider, webhook, publishable key) | | infi providers verify <p> | Re-check a stored credential after a key rotation | | infi doctor | Setup health: products, payment provider, env | | infi go-live | Claim → connect provider → webhook → live key | | infi deploy --url <url> | Register webhook + write INFI_WEBHOOK_SECRET | | infi deploy vercel [--prod] | Vercel deploy + env sync + webhook |

Global flags

  • --key sk_... or INFI_SECRET_KEY
  • --profile <name> — config profile (default: default)
  • --localhttp://localhost:8088
  • --json — machine-readable output

Scaffold

Use the separate scaffolder (not a subcommand):

npm create infi-app my-app

Config

~/.config/infi/config.json stores profiles after infi login.

Development

bun run --filter @beinfi/cli build
bun run --filter @beinfi/cli dev -- sandbox create --json --local

Connecting a payment provider

There is no infi providers connect, on purpose. Connecting decides which account a merchant's money lands in, so the backend gates it behind fresh MFA — and a step-up token is only ever minted for a dashboard session, so an API key can neither obtain nor replay one. Connect at app.beinfi.com/go-live; the CLI reports and verifies.

What this CLI does not do

Beinfi does not handle your end users' login — bring your own auth (Clerk, Supabase, NextAuth, your own) and pass that user's id as externalId.