Build on the supported package contract
Use @absolutejs/key-transparency-memory through its supported public entry points.
@absolutejs/key-transparency-memoryv0.2.0betaMessagingDevelopment-only in-memory key transparency provider for AbsoluteJS.
bun add @absolutejs/key-transparency-memoryDevelopment-only, process-local provider for @absolutejs/key-transparency.
It maintains an append-only log view, signs every tree head with an ephemeral Ed25519 key, requires host-supplied update authorization, clones all sensitive byte inputs, and rejects prior views it did not issue. It is useful for tests, examples, and provider-neutral conformance.
It is intentionally not an implementation of the IETF KEYTRANS draft. It has no durable history, combined tree, VRF, commitments, private remote queries, independent monitor, or third-party auditor. Its manifest therefore uses the distinct absolute-memory-key-transparency-v1 protocol and does not claim split-view detection.
Never use this provider for production identities.
The package publishes a version-bound Bun certification report for its limited conformance and adversarial lifecycle. It deliberately claims no official IETF vectors, cross-implementation behavior, split-view drill, or independent audit.
Outcomes
Use @absolutejs/key-transparency-memory through its supported public entry points.
Hardening checklist
Follow in order
# @absolutejs/key-transparency-memory
import { createMemoryKeyTransparencyProvider } from "@absolutejs/key-transparency-memory";
const provider = await createMemoryKeyTransparencyProvider({
logId: "local-development-log",
verifyUpdateAuthorization: ({ authorization }) => authorization.length === 32,
});Supported entry points declared by this package manifest.
Package entry point declared in package.json.
Scripts declared by this package manifest.
Search the declarations exported by the current package type files. Expand a symbol to inspect its source-backed signature.