# tapid lock verify

Source: https://tapid.dev/docs/commands/lock-verify

Validate tapid.lock before replay.

## Syntax

```text
tapid lock verify
```

`verify` is currently the only `tapid lock` subcommand. The current client does not expose separate lockfile create, update, or repair commands. Online [`tapid install`](https://tapid.dev/docs-markdown/commands/install/content.md) writes the lockfile as part of a successful dependency install.

Validate `tapid.lock` in the current project. The command reads the fixed `tapid.lock` path, parses the JSON, and checks the lockfile's supported schema, package identities, roots, dependency edges, URLs, integrity values, and required provenance fields.

## When to use it

Run this before an offline or frozen install when you want a separate validation step:

```text
$ tapid lock verify
```

The successful output is:

```text
Valid lockfile: tapid.lock
```

`tapid lock verify` does not fetch registry metadata, compare the lockfile with the current `package.json`, inspect the verified store, or create a missing lockfile. Use [`tapid install --offline --frozen`](https://tapid.dev/docs-markdown/commands/install/content.md) when you need the full replay check before activation.

## Common failures

* A missing `tapid.lock` cannot be verified.
* Invalid JSON or an unsupported lockfile version is rejected.
* Non-canonical roots, dangling dependencies, mismatched package keys, invalid URLs, or invalid integrity values are rejected.
* A schema-5 file may parse, but replay still requires online regeneration because it lacks the current integrity-provenance contract.