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

@madewithremy/admin

v0.1.38

Published

Admin SDK + CLI for managing production Remy apps

Readme

@madewithremy/admin

Admin SDK + CLI for managing production Remy apps: request logs, analytics, releases, users, secrets, database, files, email (including custom sending/receiving domains), scheduled jobs, QA replays, and more. Almost every operation wraps the same management API the dashboard uses, so anything answerable in the console is answerable here — from the terminal or from code. The exception is qa-recordings export, which renders a video on the dev box and therefore only runs inside a sandbox.

One surface, two skins: every CLI command (remy-admin <group> <sub>) is also a typed client method (admin.<group>.<sub>()). Both are thin layers over the same ops core.

Install

npm install -g @madewithremy/admin    # CLI on PATH
npm install @madewithremy/admin      # import layer in a project

CLI

remy-admin --help              # all command groups
remy-admin <group> --help      # per-group commands, flags, examples

All output is JSON (one value, compact when piped, pretty on a TTY). Unknown flags are rejected rather than ignored. Exit codes: 0 success, 10 any error (releases wait additionally uses 1–4 for build outcomes).

Configuration is read from the environment and the workspace — there are no config commands:

| Source | Meaning | |---|---| | MINDSTUDIO_API_KEY | Org-scoped sk_ API key (required) | | MINDSTUDIO_BASE_URL | API origin (default https://v1.mindstudio-api.com) | | WORKSPACE_DIR | Workspace root (default /home/vercel-sandbox/workspace) | | ${WORKSPACE_DIR}/mindstudio.json | appId — which app the CLI manages | | REMY_SIDECAR_URL | Sandbox sidecar for qa-recordings export (default http://127.0.0.1:4388) |

Import layer

// Lazy, environment-configured (same resolution as the CLI):
import admin from '@madewithremy/admin';
const { jobs } = await admin.cron.list({});

// Explicit — one client is bound to one app:
import { createAdminClient, AdminApiError } from '@madewithremy/admin';
const client = createAdminClient({ apiKey: 'sk_…', appId: 'app_…' });

const { releases } = await client.releases.list({ limit: 5 });
const { url } = await client.files.put({
  content: buffer,
  store: 'assets',
  access: 'public',
  filename: 'hero.jpg',
});
const domains = await client.email.listDomains('sending'); // typed per direction
const other = client.forApp('app_other');                  // sibling client, same credentials

try {
  await client.requests.get('req_missing');
} catch (err) {
  if (err instanceof AdminApiError) console.log(err.status, err.body);
}

Every response is fully typed (the shapes are hand-transcribed from the platform API). Failures throw AdminApiError (method/path/status/body) or AdminTimeoutError. Long-running composites take an onProgress callback (releases.waitForCommit, dataSources.addDocument / waitForIngest, files.put). The SSE/NDJSON streaming paths (methods invoke --stream, jewels export --file) are CLI-only.

Development

npm install
npm run typecheck
npm run build        # tsup → dist/index.js (+ d.ts) and dist/prod.js (bin)
node dist/prod.js --help

Layout: src/ops/ is the pure core (one module per group: (ctx, params) → typed result, no printing/exiting), src/commands/ the CLI skins (spec + Args→params + output), src/client.ts the import layer binding a context over the ops, src/types/ the response types. See CLAUDE.md for the conventions.