CodeVetter · Repo Unpack · Feature catalog
pnpm/pnpm
The inspected Rust command table covers dependency management, workspace execution, package inspection, publishing, configuration, runtime management, and release intents. Installation exposes dependency-group and linker choices, with optional Cargo and Python participation. pnpr combines compatible registry APIs with resolution, artifact, compiler-cache, and pipeline-record surfaces. This catalog groups the inspected public surfaces; command registration alone does not establish complete implementation or successful operation.
- Dependency commands include add, install, install-test, update, remove, link/unlink, import, dedupe, prune, fetch, deploy, and patch/patch-commit/patch-remove; install accepts production, development, and optional dependency selection plus isolated, hoisted, or PnP linkers.
- Execution surfaces include recursive, run, exec, dlx, create, test/start/stop/restart shortcuts, tasks, and pipeline. Pipeline's declared contract includes frozen installation, affected-project selection, dependency ordering, and cached task restoration.
- Inspection and security commands include list/ll, why, outdated, audit, peers, licenses, sbom, doctor, ignored-builds, approve-builds, cat-file, cat-index, and find-hash.
- Publishing and account commands include pack, publish, stage, access, deprecate/undeprecate, unpublish, dist-tag, login/logout, owner, team, whoami, and star/unstar/stars; change, version, and lane manage release intents and lanes.
- Configuration and environment surfaces include config/get/set, pkg, set-script, runtime, deprecated env, shim, with, setup, self-update, completion, clean/purge, ci, store, and cache. edit/profile/token/xmas are explicitly registered as unimplemented commands directing users to npm.
- When cargo.enabled or python.enabled is set, ecosystem_install::plan adds Cargo or Python tasks to an InstallPlan; Python selection follows workspace scope and production/development dependency groups.
- pnpr mounts npm metadata, version, tarball, search, dist-tag, publish, unpublish, and staged-publish routes, including named registry prefixes; configured Cargo and PyPI ecosystems add their own route sets.
- Optional pnpr surfaces provide resolve/verify-lockfile, artifact publication/resolution/blob retrieval, compiler-cache reads and writes, and pipeline-run storage plus a viewer. NAPI separately exposes install, rebuild, pack, dependency resolution, peer checks, configuration, and lockfile APIs to Node hosts.