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

sealmetrics

v0.1.3

Published

SealMetrics setup CLI — provision a free analytics account, place the tracker, and auto-configure the MCP server in one turn

Downloads

563

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

sealmetricsssealmetricssricardpuntiricardpunti

Keywords

sealmetricsanalyticsclisetupwizardmcpprivacy-firstcookieless

Readme

sealmetrics

Set up SealMetrics analytics in one command: provision a free account, get the tracker snippet placed, and auto-configure the SealMetrics MCP server in your editor so you can read your analytics in natural language.

npx sealmetrics init

Privacy-first, cookieless, GDPR-compliant by design — no card required for the free tier.

What it does

  1. Detects your framework (Next.js, Astro, Remix, Nuxt, SvelteKit, Vite, plain HTML) or CMS (WordPress, WooCommerce, PrestaShop, …).
  2. Provisions a free account headless (POST /provision) and stores the read-only API key in .env (gitignored — never printed).
  3. Hands off the snippet — the CLI never edits your source. It tells you exactly where the snippet goes and writes .sealmetrics/INSTALL.md; you (or your agent) paste it.
  4. Auto-configures the MCP server for Claude Code, Cursor, Windsurf or VS Code (unknown clients get the standard block to paste).
  5. Verifies the install by polling pixel status.

Agent mode

npx sealmetrics init --agent --email [email protected] --accept-tos \
  --site-name "My Shop" --domain myshop.com --install-source claude-code

In --agent mode all stdout is versioned NDJSON with structured exit codes — see PROTOCOL.md. Built for AI orchestrators (Claude Code, Cursor, Codex) to drive in one turn.

Common flags

| Flag | Purpose | |------|---------| | --agent | Machine mode (NDJSON + auto-approve, no prompts) | | -y, --yes | Non-interactive (use flags/defaults) | | --dry-run | Detect only — no provisioning, no writes | | --resume | Resume from the last checkpoint (no re-provision) | | --no-inject | Provision only — don't emit placement guidance | | --no-mcp | Skip MCP auto-config | | --region <prod\|pre\|local> / --base-url <url> | Target a backend | | --editor <id> | Force an MCP client | | --verify-timeout <secs> | Pixel verify timeout (0 = skip) |

Run npx sealmetrics init --help for the full list.

What it writes

Only its own artefacts, always atomically and idempotently: .env, seal.config.json, .sealmetrics/INSTALL.md, .sealmetrics/INSTRUMENTATION.md, .sealmetrics/checkpoint.json, the MCP config file, and .gitignore entries. It never touches your application source.

License

MIT