# tapid manifest validate

Source: https://tapid.dev/docs/commands/manifest-validate

Validate a package.json manifest before project work.

## Syntax

```text
tapid manifest validate [PATH]
```

`validate` is currently the only `tapid manifest` subcommand. The current client does not expose separate manifest edit, add, remove, or publish commands. [`tapid init`](https://tapid.dev/docs-markdown/commands/init/content.md) creates a new private manifest, and [`tapid install`](https://tapid.dev/docs-markdown/commands/install/content.md) can update `dependencies` when you pass a package argument.

Validate the selected manifest. The path defaults to `package.json` in the current directory. An explicit relative path is resolved from the directory where you run the command.

Validation covers the manifest shape and package identity used by the current project workflow. The root must be a JSON object with string `name` and `version` fields. tapid also checks the supported types for `private`, `description`, `license`, dependency maps, scripts, and `bin` entries, including package names and safe bin targets. Unknown fields are accepted as preserved package metadata.

## Example

```text
$ tapid manifest validate package.json
```

The command prints the manifest identity and does not modify the file:

```text
Valid manifest: demo@0.1.0
```

It validates project input only. It does not resolve dependencies, generate a lockfile, update `package.json`, or contact a registry.

## Common failures

* A missing or unreadable path stops validation.
* Invalid JSON or a non-object root is rejected.
* Missing or incorrectly typed `name`, `version`, or supported metadata fields is rejected.
* Invalid package names, dependency names, package versions, or unsafe `bin` targets are rejected.