# v0.0.7

Source: https://tapid.dev/docs/releases/v0.0.7

Archived Tapid v0.0.7 development release documentation.

Tapid v0.0.7 was a source-built development target. It connected the consumer path to supported npm registry metadata and artifacts, resolved supported transitive dependencies deterministically, required registry-declared SHA-512 integrity by default, wrote a schema-6 `tapid.lock`, stored verified trees, and materialized managed `node_modules` without running dependency lifecycle scripts.

The v0.0.7 release did not include an asset-backed stable installer. Production support was not available for that release.

## Evaluate the source-built alpha

Follow [Contributor](https://tapid.dev/docs-markdown/contributor/content.md) to build a source checkout. For the current public install path, use [Getting started](https://tapid.dev/docs-markdown/getting-started/content.md). The shortest supported package path is:

```text
$ mkdir demo
$ cd demo
$ tapid init
$ tapid i is-char
```

## Lockfile migration

Schema 5 lockfiles must be regenerated online because schema 6 records whether package integrity came from registry metadata. Schema 4 remains a controlled compatibility path with narrower identity and replay rules.

```text
$ tapid install
$ tapid lock verify
```

## Current limits

tapid implements an npm-compatible subset rather than complete npm behavior. Tags, aliases, peer resolution, workspaces, private-registry authentication, lifecycle-script approval, and several package-management commands remain incomplete. Dependency lifecycle scripts stay disabled by default.

Use [Getting started](https://tapid.dev/docs-markdown/getting-started/content.md) for the current public installer path. This archived page describes the v0.0.7 client.

See the [v0.0.7 release on GitHub](https://github.com/LimeTip/tapid/releases/tag/v0.0.7) for the canonical release record.