Skip to main content

Package Ninja overview

Package Ninja is a hosted SaaS workspace plus a local CLI enforcement layer. It authenticates developers in the browser, resolves package policy from the control plane, and blocks or allows package-manager commands before install-time side effects happen. Use this guide when you need to install the CLI, understand the control model, or troubleshoot governed npm workflows.

The goal is simple: keep developer workflows fast while making package policy enforcement deterministic, auditable, and workspace-managed.

What does Package Ninja do?​

Package Ninja gives security, platform, and engineering teams one shared package-governance workflow:

  • developers keep using familiar package-manager commands
  • policy is checked before install, run, and publish side effects
  • audit visibility is captured in the hosted workspace

How is Package Ninja structured?​

  • Control plane (web + backend): authentication, workspace state, policy config, billing, and audit records.
  • Data plane (CLI runtime): executes package commands locally after policy preflight.
  • Policy timing: verdicts are resolved before package manager side effects.

Who should use Package Ninja?​

  • Security teams that need enforceable package policy without rewriting developer workflows.
  • Platform teams that need centralized governance and incident visibility.
  • Engineering orgs that need seat-based controls and predictable onboarding.

What does this guide cover?​

  • install and authenticate the CLI
  • workspace onboarding and first-run behavior
  • policy precedence and enforcement outcomes
  • team membership, roles, and session revocation
  • billing seats and checkout lifecycle
  • operational troubleshooting and recovery commands

What is the correct CLI package and command name?​

Package Ninja uses package-ninja as the canonical command name.

The canonical npm package is @packageninja/cli.

Some compatibility package channels may still expose the transitional executable name package-ninja-ee. If your machine does that, substitute package-ninja-ee for package-ninja in the command examples.

Where are the main product pages?​