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

@mirage-cli/radar-cli

v0.2.3

Published

ViewEngine Radar CLI — org-scoped AI visibility (projects, queries, game-plans, results, jobs, credits). Mirage-compatible command shape.

Readme

@mirage-cli/radar-cli

ViewEngine Radar CLI — org-scoped access to the ViewEngine AI Visibility API at radar.viewengine.ai. Read projects, queries, query-results, execution-jobs, and credits; manage game plans; switch between organizations.

bun add -g @mirage-cli/radar-cli
radar login                    # Clerk OAuth (browser)
radar login --api-key sk_...   # headless / CI

radar orgs list                # orgs you belong to
radar orgs use <id-or-slug>    # set the active org (persisted)

radar projects list --search acme
radar queries list --project-id <id>
radar game-plans list --status open
radar game-plans complete-action <planId> <actionIndex>
radar results list --provider perplexity --query-id <id>
radar jobs list --status running
radar credits list
radar export game-plans > game-plans.json

Commands

  • projects {list, get}
  • queries {list}
  • game-plans {list, get, update, complete-action}
  • results {list, get} (query-results)
  • jobs {list} (execution-jobs)
  • credits {list}
  • export <entity> — page through every row of an entity
  • orgs {list, use, current, clear} — multi-tenant switching
  • login / whoami / logout

All list commands accept --page, --limit, --sort <field>, --dir <asc|desc>. Output is JSON (ideal for piping / bot consumption).

Auth & org scoping

  • radar login — Clerk OAuth (PKCE + RFC 7591 DCR + loopback). Persists to ~/.config/radar/session.json (0600).
  • radar login --api-key sk_... — Clerk machine API key for headless use.
  • Env override: RADAR_API_KEY (preferred) or RADAR_OAUTH_ACCESS_TOKEN. RADAR_API_BASE_URL overrides the base URL.
  • Active org: radar orgs use <id-or-slug> persists it; override per-command with --org <id-or-slug> or the RADAR_ACTIVE_ORG_ID env var. It rides on every request as the X-Active-Org-Id header, which the API resolves by id or slug server-side.
  • Shared projects: projects, queries, results, and game-plans scoped to the active org include projects shared into it (agency access), not just ones it owns. Each project row carries an access field — "owner" (your org owns/pays) or "shared" (shared in for view/run/edit; billing hidden). Jobs and credits stay owner-org-only.

Programmatic use

import { buildProgram, ApiClient, loadSession } from "@mirage-cli/radar-cli";

// As a Commander program (drives the same CLI surface):
const program = buildProgram();
await program.parseAsync(["node", "radar", "projects", "list"]);

// As a typed API client:
const session = loadSession();
if (session) {
  const client = new ApiClient(session);
  const { rows, total } = await client.list("projects", { search: "acme" });
  const plan = await client.get("game-plans", "<id>");
}

Drop-in for mirage: see @mirage-cli/radar.