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

@cats-inc/cats-one

v0.2.0

Published

Bootstrap installer entrypoint for the Cats ecosystem.

Vulnerabilities

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

Links

Git

Maintainers

sammykenny2sammykenny2

Keywords

catsonebootstrapinstallerplatformruntime

Readme

@cats-inc/cats-one

Bootstrap installer entrypoint for the Cats ecosystem.

cats-one boots the whole Cats stack in one shot: it starts @cats-inc/cats-runtime (unless one is already serving), waits for its /health endpoint, then launches @cats-inc/cats-platform, forwarding Platform CLI options to the platform.

Status: published. @cats-inc/cats-one and its dependencies are live on npm. The unscoped cats-one package is a thin alias that forwards to this canonical package, so npx cats-one works too.

Both npm names are released at the same version. The alias pins that exact canonical version; npx cats-one displays the alias's own package version in its installation prompt. Maintainers must publish and verify both names using the npm release guide.

The cross-repository release guide covers independent Runtime/Platform npm releases, when cats-one needs a new version, Desktop official/preview publication, and individually versioned Apps and compatibility.

Requirements

  • Node.js 22+
  • npm 12+

Usage

npx @cats-inc/cats-one

Behavior

  • The runtime endpoint comes from CATS_RUNTIME_BASE_URL, or CATS_RUNTIME_HOST/CATS_RUNTIME_PORT, defaulting to http://127.0.0.1:3110. The same endpoint drives the health probe, the runtime cats-one starts, and the platform's runtime client, so they always agree (wildcard binds like 0.0.0.0 are probed via loopback).
  • When CATS_RUNTIME_API_KEY is set, health probes use it as a bearer token. The same environment is passed to runtime and platform.
  • If a runtime already answers there, it is reused instead of starting a second one.
  • Otherwise, for local endpoints cats-one starts cats-runtime, waits up to 60s for /health, then starts cats-platform; startup fails loudly if the runtime never becomes healthy. For non-local endpoints cats-one refuses to auto-start and exits with an error instead.
  • If a runtime that cats-one started dies while the platform is running, the launcher shuts the platform down and exits non-zero (automatic restart / supervision is future work).
  • --platform-only skips runtime orchestration entirely.
  • Once Platform is ready, an interactive terminal opens its page in the default browser and shows the URL. Press o to open it again, or q / Ctrl+C to stop.
  • --no-open skips the initial browser launch while keeping the o shortcut.
  • Shutdown waits for Platform cleanup, then stops only the Runtime this launcher started. An already running Runtime is left alone. SIGTERM follows the same cleanup path; unresponsive owned children have a 15-second fallback per child.
  • CI, non-TTY, app-managed, and JSON/silent sessions do not launch browsers or take over terminal input. --help exits without starting either service.

Standalone npx @cats-inc/cats-platform and npx @cats-inc/cats-runtime have the same browser and keyboard behavior. Runtime opens Setup when bootstrapping, otherwise its dashboard. Browser launch failure leaves the URL available for manual opening and the service running.

Developer Workspace

cats-one owns the development workspace definition for sibling cats-one, cats-runtime, cats-platform, and cats-apps checkouts. Their parent directory can remain outside Git. The checkout command inventories canonical maintenance skills and synchronizes root guidance and discovery copies.

Prepare developer dependencies once with npm ci --include=dev in cats-one, then use the helper for your OS from that checkout, with no parameters:

| OS | Command | | --- | --- | | Windows | .\scripts\windows\Sync-WorkspaceSkills.ps1 | | macOS | ./scripts/macos/sync-workspace-skills.sh | | Linux | ./scripts/linux/sync-workspace-skills.sh |

Each helper locates the parent workspace from its script path, synchronizes both .agents/skills and .claude/skills, then checks the result. Use -WhatIf on Windows or --dry-run on Bash to preview; -Check / --check only checks. Node.js and the four sibling checkouts are still required.

Sync copies complete skills, records their ownership, preserves local edits and unrelated files, and recovers interrupted operations on the next sync. Repeating an unchanged sync does not rewrite files or metadata. The underlying scripts/workspace.mjs interface remains available for selecting a single agent.

check and sync --dry-run stay read-only. Sync/preview exit 0 on success; a check with drift exits 1; invalid input or conflicts exit 2. See the setup guide for requirements, conflicts and recovery.

This developer command is available from a checkout, outside the published npm payload. App installation, version selection and Desktop packaging remain owned by cats-platform.

License

MIT