tapid docs

tapid outdated

Compare declared and locked dependencies with registry versions.

Status

Available starting with published v0.0.11. This page targets v0.0.13. Read Compatibility for the supported subset and Release changes for the reviewed release changes.

Syntax

tapid outdated [OPTIONS]
$ tapid outdated

Requires package.json and tapid.lock. Reports each direct dependency's declared requirement, locked version, newest compatible version, and newest available version. Aliases query their actual target package. Ordinary unaliased local workspace dependencies report member versions; aliased or prefixed workspace declarations are not fully reported. Imported schema-8 locks are rejected.

The command reads registry metadata unless a fixture is supplied. Normal operation does not change dependency declarations or install packages. It may recover an interrupted lifecycle transaction before reporting. --store-dir and --allow-unverified-registry-artifacts have no effect on this command.

Shared options

  • --project-dir PATH selects the project, defaulting to the current directory.
  • --workspace NAME selects a workspace member by name. The root owns the lockfile and managed activation. See Workspaces for member selection and local-link limits.
  • --store-dir PATH selects the verified store where applicable.
  • --registry-fixture PATH supplies local metadata for tests where applicable.
  • --allow-unverified-registry-artifacts permits the explicit online integrity exception where applicable. Resulting installs cannot use offline/frozen replay.

Use tapid --json outdated --json-limit 0 for all machine-readable entries. A partial report can exit successfully, so inspect outcome and entry errors. Read JSON results for coverage and limits.

This command does not execute dependency lifecycle scripts. Check tapid outdated --help on your installed binary before execution. The command does not provide a package safety verdict.