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

aidevsandbox

v0.1.0

Published

Provision a hardened DigitalOcean dev environment (Terraform + cloud-init) ready for Claude Code, locked to your IP.

Readme

aidevsandbox

Spin up a hardened DigitalOcean dev box — Docker-ready, with Claude Code preinstalled — using one command. Networking is locked down so only your current public IP can reach the droplet, on every port. Terraform state stays local, in a folder you own.

npx aidevsandbox@latest

What it does

  1. Scaffolds a Terraform project (local state) into ./aidevsandbox.
  2. Auto-detects your public IP and locks the droplet's cloud firewall to it.
  3. Installs your SSH public key (key-only login; root login & passwords disabled).
  4. Provisions an Ubuntu 24.04 droplet (default 2 vCPU / 4 GB, region sgp1) with Docker, Node.js LTS, Claude Code, and your git identity configured.
  5. Runs terraform init / plan / apply and prints your ssh command.

You finish by SSHing in and running claude to log in (no secrets are stored in Terraform state).

Requirements

  • Terraform ≥ 1.5 on your PATH
  • A DigitalOcean API token (read/write)
  • An SSH key pair (~/.ssh/id_ed25519 recommended)

Usage

# token via env (recommended) — never written to disk:
export DIGITALOCEAN_TOKEN=dop_v1_xxx
npx aidevsandbox@latest

Options:

| Flag | Description | | --- | --- | | --dir <path> | Target directory (default ./aidevsandbox) | | --force | Overwrite templates if the dir already has *.tf | | --dry-run | Scaffold + detect IP/key, but don't run terraform | | -h, --help | Show help |

Security model

  • Cloud firewall (network edge): inbound tcp/udp/icmp allowed only from your <ip>/32; everything else denied. Outbound is open so the box can pull packages and reach the Anthropic API.
  • Host firewall (ufw) mirrors the same rule as defense-in-depth, plus fail2ban and unattended-upgrades.
  • SSH is key-only: PermitRootLogin no, PasswordAuthentication no.
  • The DO token is passed to Terraform via the environment and is never written to terraform.tfvars. State files are git-ignored.

When your IP changes

Re-run the CLI (or terraform apply inside the project folder) — it re-detects your IP and updates just the firewall rule. The droplet is left untouched.

Tear down

cd aidevsandbox
terraform destroy

License

MIT