tapid docs

Commands

Tapid commands, their effects, and the supported release scope.

Version scope

These examples target v0.0.13, published on 2026-10-10. Release changes records its reviewed source and implementation limits.

Check your installed binary before choosing a command:

$ tapid --version
$ tapid --help
$ tapid install --help

Published commands

CommandPurpose
tapid initCreate a private manifest in an existing directory.
tapid manifest validateValidate a manifest without changing it.
tapid lock verifyCheck the structure of tapid.lock.
tapid installResolve dependencies or replay a verified lockfile. i is an alias.
tapid runLaunch an explicit Node.js root script under its configured execution policy.
tapid upgradeVerify a release and replace the Tapid executable. Available starting with 0.0.10.
tapid addAdd packages to a dependency section and install the resulting graph.
tapid removeRemove declared dependencies and reinstall the remaining graph.
tapid updateResolve the graph again, preserving declared ranges unless --latest is selected.
tapid outdatedCompare direct requirements and locked versions with registry versions.
tapid pruneRebuild managed node_modules from the lockfile without network access.
tapid licensePrint the embedded Apache-2.0 license and attribution offline. Available starting with 0.0.12.
tapid ciInstall exact ordinary locked dependencies, fetching missing verified artifacts without resolution.
tapid import-package-lockImport the supported npm lockfile v3 subset offline.

Global JSON results and approved dependency scripts are available in v0.0.13. Their command coverage and execution prerequisites differ.

Typical project flow

$ mkdir demo
$ cd demo
$ tapid init
$ tapid i is-char
$ tapid lock verify
$ tapid install --offline --frozen

lock verify checks lockfile structure. Offline/frozen installation also checks the root manifest digest and verified store before activation. Neither result proves that dependency code is safe. Dependency lifecycle scripts are denied by default. Exactly approved hooks require supported Linux ManagedTree execution; offline/frozen replay and ci never execute hooks.

Read Getting started for installation and Using Tapid with AI agents for version checks, command effects, and Markdown access. Native publishing, package audits, one-shot execution, and store garbage collection are not exposed commands in this CLI.