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

warden-landing

v0.3.0

Published

Warden - A sandbox runtime for MCP servers

Readme

warden-landing

Landing page for Warden, built with Next.js 14 (App Router), TypeScript, Tailwind CSS, and Framer Motion for the one animated moment on the page — the interactive sandbox demo in the hero.

Setup

npm install
npm run dev

Then open http://localhost:3000.

This was written without running npm install — it was built in an offline sandbox with no network access, so the code hasn't been through an actual build. It should work as-is with the versions pinned in package.json, but if you hit a version mismatch on first install, it's most likely Next/Tailwind needing a minor bump — run npm install and check the terminal output first.

Before you deploy

  1. Replace every yourname placeholder in components/Nav.tsx, components/Hero.tsx, components/Cta.tsx, and components/Footer.tsx with your real GitHub org/repo path and Go module path (should match whatever you set in the main repo's go.mod).
  2. components/Backends.tsx and components/Compatibility.tsx hardcode status values ("Ready", "In progress", "Verified", "Testing") — keep these in sync with ROADMAP.md as milestones land. Don't let the landing page claim something the repo hasn't shipped yet.
  3. Add a real OG image / favicon — currently there's just text metadata in app/layout.tsx.

Platform Support

| Platform | Backend | Status | |----------|---------|--------| | Linux | bubblewrap (unprivileged namespaces) | ✅ Ready | | macOS | sandbox-exec, with Docker fallback | ✅ Ready | | Windows | AppContainer + WFP + Job Objects + ETW audit | ✅ Ready | | Overall | — | ✅ Ready |

Compatibility Matrix

The Warden MCP compatibility matrix (18 servers) has been validated:

  • ✅ Pass (14): filesystem, github, slack, postgres, sqlite, brave-search, gdrive, git, memory, time, sequential-thinking, notion, linear, tavily
  • ⚠️ Conditional (2): fetch (was a Warden bug — ambiguous file access, now fixed via policy.Normalize), kubernetes (inherent — needs per-deployment cluster API host + kubeconfig)
  • ❌ Fail (2): docker (inherent — requires Docker daemon socket, cannot be sandboxed), playwright (schema-gap — missing wildcard hosts & unix-socket grants)

See docs/compatibility.md for the full matrix and testdata/compat/ for regression fixtures.

  • Reduced-motion is respected both globally (app/globals.css) and inside the visualizer specifically (useReducedMotion from Framer Motion).