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

two80

v0.5.2

Published

Deploy and share your app. One verb: two80 push.

Readme

two80

https://280apps.com/setup.md - Agents start here

Commands

Every error prints a fix line with the exact command to run next.

| Command | Purpose | Options | | --- | --- | --- | | two80 | Show this directory's app state and next steps | | | two80 push | Build, deploy, and print the live URL | --name <slug>, --framework next\|static, --new | | two80 init | Detect the framework and write .280/config.json | --name <slug>, --framework next\|static | | two80 delete | Destroy this project's app, URL, content, and data | --yes <name> | | two80 whoami | Show authentication state | | | two80 login | Authenticate this machine | | | two80 setup | Install agent hooks and the skill | | | two80 version | Show the CLI version | --version, -v | | two80 help | Show all available commands and flags | --help, -h |

two80 push

Push initializes new projects automatically. Framework and name options only apply during the first initialization.

| Flag | Description | | --- | --- | | --name <slug> | Use this app name instead of the package.json name | | --framework next\|static | Skip framework detection | | --new | Create a fresh app instead of linking an existing one |

two80 push
two80 push --name my-app --framework next
two80 push --new

two80 delete

Deletion is permanent and requires the app's name as confirmation. Running the command without confirmation prints the required name and deletes nothing.

two80 delete
two80 delete --yes my-app

Agent integration

Two paths, install either or both:

  • Session hook (recommended): npx -y two80@latest setup registers a SessionStart hook for Claude Code, Codex, and OpenCode. Every session opens with this directory's app state already visible. Live state, small per-session token cost.
  • Skill: the same setup run installs the on-demand 280-deploy skill. Loads only when the agent recognizes a deploy task. No per-session cost, works in any agent supporting the skill format.

Both are opt-in, idempotent, and merge into your agent config without overwriting it.

Output contract

  • stdout is TOON, for agents. Progress goes to stderr.
  • Errors are structured on stdout and carry a runnable fix.
  • Exit codes: 0 ok (including no-ops), 1 failure (with a fix), 2 bad flags or args.