StashJS

A zero-dependency, ephemeral, crypto-agnostic content store for Node.js - bytes in, ref out.

Every page in this reference is generated from the library's own source comments. You put bytes in and get a ref back - a 256-bit random capability, not a content address. You take the bytes out, and when the terms say once, they're gone.

Quick start

npm install @blamejs/stash

import { Stash } from "@blamejs/stash";
import { MemoryBackend } from "@blamejs/stash/backends/memory";

const stash = new Stash({ backend: new MemoryBackend() });
const ref = await stash.push(ciphertext);   // ref: 'v1_...' - a capability
const entry = await stash.show(ref);        // metadata only, never contents
const readable = await stash.apply(ref);    // digest-verified stream

Design tenets

• Crypto-agnostic by architecture. There is no key parameter on any method and no cipher import anywhere in the tree. A store with nowhere for a key to live survives compulsion; encryption belongs to the consumer.
• Refs are capabilities. A ref is 256 bits of randomness, never a content hash - a content hash is guessable by anyone holding the content, and dedup buys nothing on ciphertext.
• Fail closed. Every failure is a typed StashError with a stable code; no error message ever contains a ref, a meta value, or a path.
• Streaming-first. No method buffers a whole blob; size limits are enforced mid-stream, and reads are digest-verified as they drain.
• The lifecycle is monotone. Entries are write-once and every state change moves them closer to destruction - no touch(), no TTL extension, no metadata mutation.
• Zero dependencies. Node builtins only, at runtime and in development; the published dependency object is empty.

Namespaces