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

@leadpulse/pseo-bootstrap

v0.1.0

Published

Scaffold programmatic SEO (pSEO) drafts for any product. Interactive by default, non-interactive for agents/harnesses via JSON or flags. Stdlib-only — no runtime dependencies.

Readme

@leadpulse/pseo-bootstrap

Scaffold programmatic SEO (pSEO) drafts for any product. Interactive by default, non-interactive for agents/harnesses via JSON or flags. Stdlib-only — no runtime dependencies.

What it does

Takes a product config (name, tagline, pricing, lead sources, destinations, competitors, ...) and scaffolds a starter set of draft pages that fit the LeadPulse landing-page templates:

  • Integration pages (sources × destinations)
  • "X vs Y" comparisons (product vs competitor)
  • "Alternatives to X" (competitor alternatives hubs)
  • "Best of" roundups (category roundups)
  • Head-to-head pages (competitor A vs competitor B)

Drafts are scaffolding. Review, fact-check, and merge them into the target app's live data files before deploying (see the generated NEXT-STEPS.md).

Usage

# Interactive — guided questions, defaults shown in [brackets], Enter keeps them
pnpm --filter @leadpulse/pseo-bootstrap start

# Non-interactive from a JSON file (reuse the emitted pseo.config.json)
pnpm --filter @leadpulse/pseo-bootstrap start --config ./pseo.config.json

# From stdin (harness-friendly)
cat cfg.json | pnpm --filter @leadpulse/pseo-bootstrap start --config -

# From individual flags (merged over the selected preset)
pnpm --filter @leadpulse/pseo-bootstrap start \
  --name Foo --key foo --domain https://foo.app \
  --sources "Webhooks,API" --destinations "CRM,Sheet" \
  --roundups "Cool Stuff: cool tools" --head-to-head "Foo vs Zapier"

# Start from a reference preset
pnpm --filter @leadpulse/pseo-bootstrap start --preset gitshoutout

Output (default ./generated, override with --out <dir>):

  • pseo.config.json — resolved product config (reuse with --config)
  • pseo-drafts.ts — scaffolded draft page data
  • NEXT-STEPS.md — agent-facing implementation checklist

Flags, --config, and the --preset base merge in that order (flags win). Interactive mode starts from the selected preset (default leadpulse) so pressing Enter throughout reproduces that product's draft set.

Presets

src/presets.ts ships leadpulse and gitshoutout reference configs. Add more for your own products.

Library usage

The same builders drive the landing app's pseo:generate script — types and render logic live here so there is a single source of truth:

import { generateDrafts, countDrafts, renderDraftsTS } from '@leadpulse/pseo-bootstrap';

const drafts = generateDrafts(config);
const counts = countDrafts(drafts);
const ts = renderDraftsTS(config, { regenerateHint: 'pnpm --filter @leadpulse/landing pseo:generate' });

See src/index.ts for the full export list.

Development

pnpm --filter @leadpulse/pseo-bootstrap lint   # tsc --noEmit
pnpm --filter @leadpulse/pseo-bootstrap build  # emit declarations to dist