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

@maintainer-pro/setup

v0.2.0

Published

One-command Maintainer Pro host-app setup

Readme

@maintainer-pro/setup

One-command onboarding for a host app. The sandbox page in Maintainer Pro admin generates a pinned npx command; this CLI asks where the UI and backend live, writes API keys, then uses the same coding agent as ai-cli (agent / claude / agy) to wire the real project.

A coding agent CLI must be installed and authenticated. Without one, setup stops — chat in the host app would not work anyway.

Happy path for an empty folder: a static HTML page plus a Node server.mjs that serves /api/chat and /embed-config.js (keys stay on the server, not in HTML). Existing apps are patched in place — the agent uses a setup brief and recipes instead of inventing a new framework app.

npx --yes @maintainer-pro/[email protected] --url http://localhost:4100 --token mp_setup_...

Local run (no publish — use this while iterating on setup itself):

node path/to/maintainer-pro/packages/setup/src/setup.mjs --url http://localhost:4100 --token mp_setup_...

It will:

  1. Fetch sandbox API keys from Maintainer Pro
  2. Ask for the UI project path and the backend project path
  3. Suggest installing @maintainer-pro/ai-cli in their parent so the coding agent can edit both
  4. Ask for the public app URL (port included, default http://localhost:3000)
  5. Write .env, then run the coding agent with a brief + recipes
  6. Run doctor (Node 22+, admin health, agent / claude / agy on PATH) and print the agent workspace

Flags

| Flag | Purpose | |------|---------| | --url | Maintainer Pro admin URL | | --token | mp_setup_… token from the sandbox page | | --ui | UI project directory | | --backend | Backend project directory | | --workspace | Directory where ai-cli is installed (agent edit root) | | --app-url | Public origin the browser will open (http://localhost:3000) | | --create | Allow scaffolding HTML + server.mjs without prompting | | --packages-from <sdk-repo> | Install ai-cli / ai-ui from a local checkout (file:…) | | --skip-install | Do not run npm install | | --dry-run | Log writes without touching the disk |

What it writes

  • .env on the backend (MAINTAINER_PRO_*, AI_CLI_WORKSPACE, PORT, CORS_ORIGIN)
  • Chat widget and /api/chat (via the coding agent)

Start the happy-path backend with npm run dev in the backend folder, then open the app URL you gave setup.