DocsRelease seals
Docs · Guides

Release seals

Each release has a seal, a picture of its tarball hash. Two releases with the same bytes have the same seal.

Updated Oct 14, 2026docs/public/seals.md

Release seal of empathic@2.0.0 Release seal of empathic@2.1.0

Release Integrity
empathic@2.0.0 sha512-i6UzDscO/XfAcNYD…
empathic@2.1.0 sha512-AnfC1ATldl49/cvZ…

How the registry draws it#

The registry reads the SHA-512 integrity of the tarball, the dist.integrity field of the version. It draws 48 rays around a ring. Each ray starts just outside the ring, and one byte of the hash sets its length. The version is in the center.

What it tells you#

The same tarball always gives the same seal. A change to one byte of the tarball gives a new hash, and so a different seal. Use it to see at a glance if two releases, or two registries, serve the same bytes.

What it does not do#

The seal is not a security check. npm, Bun, and other clients check the integrity hash when they install. To see where and how a release was built, look for the verified provenance badge.