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

@getjack/jack

v0.1.36

Published

Ship before you forget why you started. The vibecoder's deployment CLI.

Readme



You're vibecoding. Ideas are flowing. You want to ship.

But first: config files, deployment setup, secret management, debugging infrastructure errors...

30 minutes later, the spark is gone.

jack removes the friction between your idea and a live URL.

curl -fsSL docs.getjack.org/install.sh | bash
jack new my-app   # → deployed. live. done.

That's it. Write code. Ship again with jack ship. Stay in flow.


Why jack

Instant deploymentjack new creates AND deploys. You have a live URL before your first commit.

Works with your agent — Claude Code, Cursor, Codex, whatever. Every project includes AI context files so your agent understands the stack from prompt one.

Roaming secrets — Configure once, use across all projects. No more per-project secret ceremony.

Project tracking — 100 experiments scattered everywhere? jack ls finds them all.

No lock-in — Standard config files, standard TypeScript. Your projects work without jack installed.


Quick Start

# Install (CLI + MCP for your AI editor)
curl -fsSL docs.getjack.org/install.sh | bash

# Create and deploy
jack new my-app

Or try without installing: npx -y @getjack/jack new my-app


Commands

| Command | What it does | |---------|--------------| | jack new <name> | Create and deploy a new project | | jack ship | Deploy current project | | jack ls | Show all your projects | | jack open | Open project in browser | | jack secrets | Manage project secrets | | jack feedback | Share feedback or report issues |

Full documentation at docs.getjack.org


Who This Is For

Builders who ship constantly. You spin up new projects all the time, and suddenly you have dozens scattered across your machine—each with its own env vars, secrets, and deploy setup you've already forgotten.

jack keeps you organized. One command to ship, one place to find everything, zero setup overhead. Stay creative, skip the ceremony.


Philosophy

In Gibson's Neuromancer, "jacking in" means plugging directly into cyberspace. The body becomes irrelevant—you're pure thought in the matrix.

jack handles the infrastructure so you stay in creative flow. The boring parts disappear. You just build.


License

Apache-2.0