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

@intutic/cli-control-plane

v3.2.3

Published

The intutic commands that only work against a control plane (login, connect, guardrails, keys, org, ...). @intutic/cli loads this package at startup when it is installed next to it.

Readme

@intutic/cli-control-plane

The intutic commands that only work against a control plane: login, logout, whoami, connect, sync-context, decisions-log-refresh, sops, guardrails, keys, attenuate, org, team, gateway, credentials, settings, mcp, notifications, siem, tasks, compliance, usage, github, inventory, gate-liveness, findings, incidents, integrity, routing, predict-cost, optimizer, loop, decision, enterprise, judge, and the subcommands budget set|keys|key|members|member, policy snapshot|replay and enforce report.

Install it next to the CLI, with the same version:

npm install -g @intutic/cli @intutic/cli-control-plane

The public @intutic/cli does not contain any of this code: it loads this package at startup when it is installed next to it, and without it prints where a control-plane command comes from.

This package is proprietary: see LICENSE. It is a client. What it can do is decided by the control plane it signs in to, so it holds no entitlement and no secret.

How it is loaded

tools/cli/src/lib/controlPlanePlugin.ts (shared with the public repository) does await import('@intutic/cli-control-plane') at startup, by a variable specifier, and calls this package's register(program, ctx) (src/index.ts) before the command line is parsed. If the package is not installed the CLI has no such commands; any other failure to load it is an error.

  • In this repository the root package.json lists the package as a devDependency, so the workspace link puts it where tools/cli finds it. The CLI's own tests then load it, so turbo.json makes @intutic/cli#test wait for this package's build; running vitest in tools/cli directly needs it built first.
  • Installed from npm. publish.yml's publish-plugin-npm job publishes the tarball each v* release of this repository carries, after the public release, whose packages it depends on. npm install -g puts it in the same node_modules as the CLI, so Node resolves it from there.

What it builds on

The plugin imports the CLI's internals (credentials, the API client, paths, ...) from @intutic/cli/<subpath>. The subpaths are the explicit exports of tools/cli/package.json: add one only for a module a plugin command needs. The plugin API version (PLUGIN_API_VERSION in controlPlanePlugin.ts) is checked on register; bump both sides when the contract changes.

Keeping the CLI's list of names in step

A CLI without this package answers a control-plane command from a list of names (CONTROL_PLANE_COMMANDS in controlPlanePlugin.ts). src/registration.test.ts holds that list to what register adds, and the CLI's cliReference.test.ts holds it to apps/docs/reference/cli.md. Adding a command here means adding its name there, in the public repository first.

Tests

pnpm --filter @intutic/cli-control-plane run test

src/cli.plugin.test.ts runs the real CLI entrypoint with the plugin loaded. The rest are the tests that moved with the commands.

Enterprise-edition binary

pnpm turbo build --filter=@intutic/cli-control-plane
pnpm --filter @intutic/cli-control-plane run build:binary -- --targets node22-linux-x64,node22-macos-arm64

scripts/build-binary.mjs bundles the CLI and this package into one module with esbuild and packages it with pkg; see the script for why a plain pkg of tools/cli cannot include a plugin. The public release job (tools/cli alone) is unchanged and produces a binary without these commands.