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

@atlaslabsnpm/cli

v0.2.0

Published

Atlas CLI - drive Atlas machines: cloud VMs you and your agents work in together.

Readme

@atlaslabsnpm/cli

The Atlas CLI. Drive Atlas machines — cloud VMs attached to a workspace that you and your agents work in together, with a public URL for anything you serve.

npm install -g @atlaslabsnpm/cli
atlas login

Or without npm — one self-contained file, no dependencies beyond Node 20+:

curl -fsSL https://www.atlaslabs.id/install.sh | sh

Quick start

atlas machine create my-app                       # provision a VM
atlas put my-app ./server.js server.js            # push files
atlas exec my-app -- 'npm install && npm test'    # run work (exit code is mirrored)
atlas ports my-app                                # public HTTPS URL
atlas machine rm my-app                           # stop billing

Paths are relative to /workspace. Bind servers to 0.0.0.0 on port 3000 or 8000 — those are the ports routed from outside, and they are fixed when the machine is created.

Asking the user a question

ping_user reaches the human and blocks for their reply, so an agent can get an answer inline instead of stalling. Only their reply goes to stdout:

DB=$(atlas ping_user my-app "Postgres or SQLite for the todo store?")
atlas ping log my-app        # the full question/answer log for this machine

On timeout it exits 2 with the reply link still live — proceed on your default rather than waiting.

Commands

| Command | Purpose | |---|---| | atlas login / whoami / logout | Auth (device flow; token goes to your keychain) | | atlas machine create\|list\|status\|rm | Machine lifecycle | | atlas exec <slug> -- <cmd…> | Run a command; mirrors its exit code | | atlas put / get | Upload / download workspace files | | atlas ports <slug> | Public URLs | | atlas ping_user / ping log | Ask the user; read the log | | atlas open <slug> | Open in Atlas Browser | | atlas device list / rm | Signed-in devices; revoke one | | atlas source / specialist / group | Workspace, source and specialist management |

Full docs: https://www.atlaslabs.id/docs/cli

Configuration

| Variable | Purpose | |---|---| | ATLAS_BASE_URL | Point at a different Atlas server (default: production) | | XDG_CONFIG_HOME | Where config lives (default ~/.config/atlas) |

Requires Node.js 20 or newer.