---
public-agent: true
id: package-manifests
title: Package Manifest Standard
status: current
classification: public-agent-standard
safety: reviewed-public
---

# Package Manifest Standard

This standard covers the intent and ownership of Node.js `package.json` files.
It does not prescribe every npm or Node field. The package manager and other
tools define their own field semantics; this document records Meridian policy
and the boundaries between those authorities.

## Identity and runtime compatibility

Give each package a stable identity appropriate to its publication boundary.
Use `private: true` when the package must not be published. For publishable
packages, review the packed file set and public entry points as part of the
release contract; a package name or `private` flag alone does not prove that
the intended files or API are published.

Declare the package module format and supported runtime range when they affect
consumers or execution. In Meridian, `engines` communicates compatibility and
`packageManager` records the expected package-manager version. The repository's
toolchain and package-manager standards own the actual version lines and
workspace-wide package-manager settings. Do not copy those values into a
second policy source.

Node.js defines the meaning of fields such as `type`, `exports`, `imports` and
`engines`; package managers and build tools may define additional fields. See
the [Node.js package documentation](https://nodejs.org/api/packages.html) and
[npm package.json documentation](https://docs.npmjs.com/cli/v11/configuring-npm/package-json).

## Scripts and dependencies

Scripts are the package's explicit task interface. Keep them named for stable
package capabilities and have them delegate to maintained implementations.
Repository-wide aliases, CI-facing commands and provider-facing command
surfaces belong to repository and deployment owners, not duplicated package
policy.

Put a dependency in the scope where it is used. Runtime dependencies must be
available to consumers at runtime; build, test and lint tools generally belong
in development dependencies. Workspace catalogue selection, lockfile
authority, dependency updates, build-script trust and package authentication
are owned by [`pnpm-workspace.md`](pnpm-workspace.md),
[`dependency-automation.md`](dependency-automation.md) and
[`pnpm-hosted-builds.md`](pnpm-hosted-builds.md). This standard deliberately
does not restate their rules.

Meridian presentation metadata, when useful, follows
[`package-presentation-metadata.md`](package-presentation-metadata.md). It is
optional and does not define architecture, release status or dependency
ownership.

## Exceptions and review

Package shape varies with runtime, publication model and tool requirements.
An exception is justified by an observable consumer or execution constraint;
record its owner and removal condition when it is temporary. Do not add fields
solely to make unrelated packages look alike.

When changing a manifest, validate the owning package's scripts, type checks
and tests. For publishable packages, also inspect the packed contents and
consumer-facing entry points. Exact validation commands belong to the package
and release contract.
