Keyring

Packages

The eight MIT packages that ship into your process, layered core, cache, sdk, adapter.

PackageWhat it is
@keyring/coreThe key format, verify(), hashing and the policy-store contract. Framework-free, I/O-free.
@keyring/cacheThe versioned snapshot, the 5-second delta poller, the bounded LRU and the disk snapshot.
@keyring/sdkThe runtime: the decision, the onUnavailable modes, resources, limits, idempotency, telemetry.
@keyring/expressExpress and Connect middleware.
@keyring/fastifyFastify plugin.
@keyring/nestNestJS module, guard, interceptor and decorators, on either platform adapter.
@keyring/nextNext.js App Router route-handler wrapper, Node runtime only.
@keyring/reactThe embeddable <KeyringKeys /> component.

Every adapter is a thin translation over @keyring/sdk. Anything an adapter is tempted to reimplement lives in the SDK instead, which is what keeps the adapters small and what will keep the Python and Go ports tractable.

Not publicly available yet

None of these is on the npm registry, and the repository they build from is private, so today they install only from tarballs someone with repository access builds. Access is granted by hand: ask the Keyring team. Start in 5 minutes has the build and the overrides block.