Tapid documentation

Tapid is a package manager and registry project in design and planning. These docs follow one question from beginning to end: how can a JavaScript or TypeScript project understand the exact code it is about to run, and the policy decision that governs it?

The pages describe the problem, the intended model, and the current implementation boundary. Planned behavior is labeled as planned. Nothing here should be read as proof that the client, resolver, verification store, or execution controls already exist.

Start with the problem

Begin with Getting started to understand what Tapid is trying to answer, what exists today, and what is planned next. Then read Package identity to see why a package name alone is not enough to identify code.

That gives the request a concrete target: a package, version, registry, and artifact digest that another person or system can inspect.

Follow one package decision

Once the target is clear, Evidence and policy explains the difference between facts and decisions, and how those ideas remain partly planned in the current client.

The Commands reference then collects the implemented command surface and its intended safeguards.

Look up the system boundaries

Use Evidence and policy when the question involves registry routing, credentials, publishing context, release history, execution boundaries, or independent verification.

Where to go next

If you are evaluating direction, use the current-status table in Getting started. If you are reviewing the trust model, start with Evidence and policy.