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

boilpayment

v0.3.0

Published

boilpayment — CLI wizard: pick a provider, answer policy questions, get modules + Postgres schema + webhook + notifications

Readme

boilpayment

CLI wizard for boilpayment: answer a few questions about your provider (Stripe/Toss/PortOne/Polar) and billing policy, and it generates composed boilpayment-sdk modules, a Postgres migration set, a webhook handler, a POLICY.md describing the decisions you made, and a .env.example — in TS or Python.

Install

npx boilpayment init

or install it globally:

npm install -g boilpayment
boilpayment init

Usage

boilpayment init [--yes] [--out <dir>] [--config [file]] \
            [--providers stripe,toss,portone,polar] \
            [--models subscription,topup,usage] \
            [--languages ts,py] [--goods credits,usage_quota] [--cs]
boilpayment check [--out <dir>]     # validate config + (optional) DB connectivity, read-only
boilpayment live [--out <dir>] [--config <file>] [--env <file>] [--dry-run]
boilpayment --help

init writes paykit.config.json plus generated code into --out (default: the current directory); re-running with --config only asks the questions your existing config is missing.

--yes explicitly accepts the default rules. Refund requests, missing-grant recovery and dispute handling are included by default; --cs only enables optional usage reporting. Call initialize() to verify the schema and seed configured plans, then checkout() and registerCompletedCheckout() to retain immutable purchase evidence. Native Stripe/Polar price/product references must be configured before selling; check rejects incomplete drafts. A hosted AI support service and customer chat widget are not generated.

Programmatic use (scripting the wizard instead of the binary):

import { runWizard, generateAll } from 'boilpayment';

const config = await runWizard({
  yes: true, existingRaw: null,
  overrides: { providers: ['stripe'] },
});
await generateAll(config, './my-app');

Full wizard contract: docs/ARCHITECTURE.md §6.