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

@sowdb/cli

v0.2.2

Published

Stop letting Claude touch your prod database. PII-safe local Postgres sandbox for coding agents.

Readme

@sowdb/cli

Stop letting Claude touch your prod database.

You're using Claude Code or Cursor against a real codebase with a real database. Every time the agent is about to do something database-adjacent, you feel that quiet pang of "wait, should I let it do that?"

sow is the safety layer. One command points it at your prod Postgres, samples the data, scrubs every PII column with realistic fakes, and gives your coding agent a sandboxed local copy to hammer. Prod never gets touched. The sandbox runs in seconds, resets in under one. 100% local. Zero API calls. Zero cost. Never writes to your source database.

Install & First Use

npm install -g @sowdb/cli
cd your-project
sow sandbox

sow sandbox auto-detects your database from your project's env files, samples it, sanitizes PII, and patches .env.local with a safe DATABASE_URL. Now any coding agent on your laptop talks to the sandbox instead of prod.

Why sow

  • Built for coding agents. MCP server with 22 tools, --json mode for every command, deterministic seeds so bugs reproduce across sessions.
  • PII-safe by default. Detects emails, phones, names, addresses, SSNs, JSONB-embedded fields. Fail-closed: aborts if it sees a Postgres type it can't verify, with --allow-unsafe to override explicitly.
  • Reset in under 1 second. Postgres template-database backed. Your agent can try a destructive change, verify the result, reset, try again — 50 iterations in a minute.
  • Zero config. Auto-detects env files, Prisma, Drizzle, Knex, TypeORM, Sequelize, Docker Compose. Identifies Supabase, Neon, Vercel Postgres, and Railway projects.
  • Read-only on the source. sow never writes to your production database. Parameterized queries, identifier escaping, and a security-audited code path.
  • 100% local. No cloud round-trip, no third party holding your sanitized data, no account, no API key.

Quick Start

# Zero-config: detect your DB, sample, sanitize, patch .env.local
sow sandbox

# Or do it explicitly
sow connect postgresql://user:pass@host:5432/mydb   # analyze, sample, sanitize
sow branch create my-feature                         # isolated Postgres in ~5s
DATABASE_URL=postgresql://sow:sow@localhost:54320/sow_my_feature npm run dev
sow branch reset my-feature                          # back to seed state in <1s
sow branch diff my-feature                           # see what your agent changed
sow branch delete my-feature                         # clean up

For AI Agents

npm install -g @sowdb/mcp
sow mcp --agent claude-code          # or cursor, windsurf, codex

Or add to your MCP config manually:

{
  "mcpServers": {
    "sow": { "command": "sow-mcp" }
  }
}

The MCP server exposes 22 tools covering the full sample → branch → exec → diff → reset loop. See @sowdb/mcp for the tool list.

Documentation

Full docs, cookbook, and sanitization details: github.com/Bugsterapp/sow

Run sow --help for the full command reference.

License

MIT