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

jfl

v0.1.0

Published

Just Fucking Launch - CLI for AI-powered GTM and development

Readme

JFL - Just Fucking Launch

Your team's context layer for shipping products. Any AI. Any task.

JFL is a CLI toolkit that powers go-to-market campaigns from zero to launch. It creates structured GTM workspaces where product code, strategy, brand, and content all work together.

What JFL Does

  • Initialize GTM workspaces with proper architecture
  • Manage your launch dashboard with countdown, phases, and tasks
  • Authenticate and manage billing ($5/day per person, crypto-first)
  • Deploy to platform for team collaboration
  • Orchestrate parallel agents for Pro tier
  • Track feedback and iterate

Installation

npm install -g jfl

JFL automatically installs all required dependencies, including:

  • httpcat-cli - For gasless USDC transfers via x402 (bundled, no separate install needed)
  • @x402/evm - x402 payment protocol for Day Pass payments

Quick Start

# Create a new GTM workspace
jfl init my-project-gtm

# Check status
cd my-project-gtm
jfl status

# View launch dashboard
jfl hud

# Or just type. It will walk you through it
jfl

Architecture

JFL creates GTM workspaces that are separate from your product code:

my-project-gtm/              ← GTM workspace (strategy, content, brand)
├── product/                 ← SUBMODULE → your-product-repo
├── knowledge/               ← Strategy, vision, narrative
├── content/                 ← Marketing content
├── suggestions/             ← Contributor work
├── skills/                  ← JFL skills (updated via jfl update)
└── CLAUDE.md                ← AI instructions

your-product-repo/           ← SEPARATE REPO (all code lives here)
├── src/
├── cli/
└── ...

Why?

  • Clean separation of concerns
  • Product can be worked on independently
  • GTM context doesn't pollute product repo
  • Multiple GTMs can reference same product
  • jfl update updates GTM toolkit without touching product

Commands

Core Commands

jfl                          # Start interactive session (with optional --update)
jfl init [template]          # Initialize new GTM workspace
jfl status                   # Show project status
jfl hud                      # Show campaign dashboard
jfl hud --compact            # One-line status
jfl update                   # Pull latest JFL updates
jfl update --dry             # Preview updates without applying

Platform Commands

jfl login                    # Authenticate to JFL platform
jfl login --x402             # Use x402 Day Pass ($5/day, crypto)
jfl login --solo             # Use Solo plan ($49/mo)
jfl login --team             # Use Team plan ($199/mo)
jfl login --free             # Stay on trial
jfl logout                   # Logout from platform
jfl wallet                   # Show wallet and day pass status
jfl deploy                   # Deploy to JFL platform
jfl deploy --force           # Force deploy even if no changes
jfl agents [action]          # Manage parallel agents (list, create, start, stop)
jfl feedback                 # Rate your session

Skill Shortcuts

These skills run in your Claude Code session:

jfl brand [subcommand]       # Run /brand-architect skill
jfl content <type> [topic]   # Run /content skill (thread, post, article, one-pager)

Authentication

JFL supports two authentication methods:

GitHub OAuth

jfl login

x402 Crypto Wallet (with httpcat-cli bundled)

jfl login --x402

This enables:

  • Gasless USDC transfers (no ETH needed for gas)
  • $5/day payments via x402 protocol
  • httpcat-cli automatically installed and configured

View your auth status:

jfl wallet

Pricing

Trial - $0

  • Full JFL toolkit
  • Foundation + brand setup
  • Use Claude Code or Codex CLI - download Claude Pro or Max at claude.ai
  • Ends when you add teammates (context is more fun when you shape it together)

Day Pass - $5/day per person

  • Only pay the days you use it
  • AI included (no API key needed)
  • Chat in Telegram, Slack, Discord
  • Dashboard + Deploy at [TBD]
  • Pay with USDC (gasless via x402)

Solo - $49/mo

  • Just you (1 seat)
  • AI included
  • Everything in Day Pass
  • Best if you use it most days

Team - $199/mo

  • Up to 5 seats (+$25/seat after)
  • AI included for everyone
  • Team dashboard + analytics
  • Parallel agents
  • Priority support

Project Setup Types

When initializing a project, JFL asks about your setup:

Building a product

  • You're writing code
  • Product repo linked as submodule at product/
  • Code changes go to product repo

GTM only

  • Team handles code
  • You focus on content, brand, outreach
  • No code changes, just marketing

Contributor

  • Working on specific tasks
  • Changes go to suggestions/{name}.md
  • Owner reviews and merges

Skills Available

JFL includes powerful skills for Claude Code:

| Skill | Description | |-------|-------------| | /hud | Campaign dashboard with countdown and tasks | | /brand-architect | Generate brand identity (marks, colors, typography) | | /web-architect | Implement assets (SVG, favicon, OG images) | | /content | Create content (threads, posts, articles, one-pagers) | | /x-algorithm | Optimize tweets for X For You feed using the open-sourced algorithm | | /video | Founder video scripts (viral short-form) | | /startup | Startup journey guidance (idea to scale) | | /agent-browser | Headless browser automation - navigate, screenshot, scrape | | /search | Semantic search across GTM knowledge base using qmd | | /spec | Multi-agent adversarial spec refinement | | /react-best-practices | React/Next.js performance optimization | | /remotion-best-practices | Remotion video creation in React |

Run these in Claude Code after initializing your project. Easy to add more skills, it has a sklls factory just ask it or copy your favorite skills repos

Knowledge Layer

JFL structures your GTM knowledge:

knowledge/
├── VISION.md              # What you're building
├── NARRATIVE.md           # How you tell the story
├── THESIS.md              # Why you'll win
├── ROADMAP.md             # What ships when
├── BRAND_BRIEF.md         # Brand inputs
├── BRAND_DECISIONS.md     # Finalized brand choices
├── VOICE_AND_TONE.md      # How the brand speaks
├── TASKS.md               # Master task list
└── CRM.md                 # Contact database

These docs are the source of truth that AI reads to generate content, make decisions, and maintain consistency.

Updating JFL

JFL updates independently of your project:

jfl update                   # Pull latest skills and CLAUDE.md
jfl update --dry             # Preview changes first

This updates:

  • skills/ - Latest skill implementations
  • CLAUDE.md - Latest AI instructions
  • Templates for new docs

Your project content (knowledge/, content/, product/) is never touched.

Session Management

Default: Single session, direct in repo.

Advanced: For parallel work across multiple sessions, use worktrees:

./scripts/worktree-session.sh create [username]    # Create isolated session
./scripts/worktree-session.sh list                 # List active sessions
./scripts/worktree-session.sh end [session-name]   # End session

Each worktree session has:

  • Isolated git worktree
  • Auto-commit (every 5 min)
  • Auto-merge to main (every 15 min)
  • Own branch for changes

Development

Contributing to JFL itself:

# Clone through GTM structure
jfl init my-jfl-gtm
# During setup, add: https://github.com/402goose/just-fucking-launch.git

# Run dev setup
cd my-jfl-gtm/product
./scripts/dev-setup.sh

# Work in the submodule
cd product/cli
npm install
npm run build

# Link globally for testing
npm link

Environment Variables

CRM_SHEET_ID=your-sheet-id   # Google Sheets CRM integration

Files You'll Work With

.jfl/config.json              # Project configuration
knowledge/                    # Strategy docs (you fill these)
content/                      # Generated content
suggestions/{name}.md         # Per-person working space
previews/                     # Generated assets

Help

jfl help                      # Show all commands
jfl --version                 # Show version

For issues or feedback:

  • GitHub: https://github.com/402goose/just-fucking-launch
  • Docs: https://jfl.run

License

MIT License - see LICENSE file for details.

Credits

Built by @tagga (Alec Taggart)

Powered by:

  • Claude (Anthropic)
  • x402 (crypto micropayments)
  • Commander.js, Inquirer, Chalk, and more