npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@substrate-system/crypto-stream

v0.1.1

Published

Streaming encryption for the browser

Readme

crypto stream

tests module types semantic versioning Common Changelog install size license

Streaming encryption for the browser, based on Encrypted Content-Encoding for HTTP (RFC 8188)

This uses the Web Crypto API.

Install

npm i -S @substrate-system/crypto-stream

Fork

This is a fork of SocketDev/wormhole-crypto. Thanks @SocketDev team for working in the world of open source.

Example

import { Keychain } from '@substrate-system/crypto-stream'

// Create a new keychain. Since no arguments are specified, the key and salt
// are generated.
const keychain = new Keychain()

// Get a WHATWG stream somehow, from fetch(), from a Blob(), etc.
const stream = getStream()

// Create an encrypted version of that stream
const encryptedStream = await keychain.encryptStream(stream)

// Normally you'd now use `encryptedStream`, e.g. in fetch(), etc.
// However, for this example, we'll just decrypt the stream immediately
const plaintextStream = await keychain.decryptStream(encryptedStream)

// Now, you can use `plaintextStream` and it will be identical
// to if you had used `stream`.

Example With Blobs

See ./example for a version that uses blobs + a local vite server.

import { Keychain } from '@substrate-system/crypto-stream'

// Decryption requires the same key and salt that encrypted the file.
const keychain = new Keychain(key, salt)

const response = await fetch(imgUrl)
const decryptedStream = await keychain.decryptStream(response.body)
const decryptedResponse = new Response(decryptedStream)
const blobUrl = window.URL.createObjectURL(await decryptedResponse.blob())

// ...

function Component () {
    return html`<img src="${blobUrl}" />`
}

Seek

crypto-stream can seek on both sides of the cipher.

Reads use decryptStreamRange, which decrypts an arbitrary byte range without reading the whole ciphertext.

Writes use reproducible, record-addressable encryption. The same plaintext always encrypts to identical bytes, and you can regenerate any single record on demand without re-encrypting the rest. That is what lets a peer seed a large file (for example, over WebRTC) without buffering the whole ciphertext. Hash the content once, then hand out individual records as they are requested.

import { Keychain } from '@substrate-system/crypto-stream'
import {
    recordPlaintextSize,
    recordCount
} from '@substrate-system/crypto-stream/ece'

const keychain = new Keychain()
const data = new TextEncoder().encode('the quick brown fox')
const rs = 1024  // record size; transport chunks line up with records

// 1. Hash pass. The salt is derived from this digest, so it is bound
//    to exactly this content (no AES-GCM nonce reuse).
const digest = await keychain.contentDigest(data)

// 2. Reproducible whole-stream encrypt. Re-encrypting `data` with the
//    same digest yields byte-identical output.
const encrypted = await keychain.encryptStream(new Response(data).body, {
    contentDigest: digest,
    recordSize: rs
})

// 3. Record-addressable: rebuild any single record on demand. The full
//    ciphertext is `header || rec0 || rec1 || ... || recLast`.
const head = await keychain.header({ contentDigest: digest, recordSize: rs })

const max = recordPlaintextSize(rs)  // plaintext bytes per record
const count = recordCount(data.length, rs)  // number of data records

const i = 0
const slice = data.subarray(i * max, (i + 1) * max)
const record = await keychain.encryptRecord(i, slice, {
    isLast: i === count - 1,
    contentDigest: digest,
    recordSize: rs
})
// `head || record` equals the first record of `encrypted`, byte for byte.

See Reproducible & record-addressable encryption for the safety model (why the salt is derived from the content) and the low-level building blocks.

API

new Keychain([key, [salt]])

constructor (key?:string|Uint8Array, salt?:string|Uint8Array)

Type: Class

Returns: Keychain

Create a new keychain object. The keychain can be used to create encryption streams, decryption streams, and to encrypt or decrypt a "metadata" buffer.

key

Type: Uint8Array | string | null

Default: null

The main key. This should be 16 bytes in length. If a string is given, then it should be a base64-encoded string. If the argument is null, then a key will be automatically generated.

salt

Type: Uint8Array | string | null

Default: null

The salt. This should be 16 bytes in length. If a string is given, then it should be a base64-encoded string. If this argument is null, then a salt will be automatically generated.

Keychain.AuthHeader(secretKey, salt)

static async AuthHeader (
    secretKey:string,
    salt:string|Uint8Array
):Promise<string>

Static equivalent of keychain.authHeader(), for callers that have a base64-encoded key and salt but no Keychain instance. Derives the auth token from secretKey and salt and returns the same Bearer sync-v1 ${authTokenB64} header value.

secretKey

Type: string

The main key, as a base64-encoded string.

salt

Type: string | Uint8Array

The salt used to derive the authentication token.

Keychain.Header(writeToken)

static Header (writeToken:string):string

Format a token as the HTTP header value: Bearer sync-v1 ${writeToken}. Used internally by Keychain.AuthHeader and keychain.authHeader, and useful on its own for formatting a server-issued writer token.

writeToken

Type: string

A base64-encoded token.

keychain.key

key:Uint8Array

The main key.

keychain.keyB64

keyB64:string

The main key as a base64url-encoded string.

keychain.salt

salt:Uint8Array

The salt.

Implementation note: The salt is used to derive the (internal) metadata key and authentication token.

keychain.saltB64

saltB64:string

The salt as a base64-encoded string.

keychain.authToken()

authToken ():Promise<Uint8Array>

Returns the authentication token. By default, the authentication token is automatically derived from the main key using HKDF SHA-256.

The authentication token can be used to communicate with the server and prove that the client has permission to fetch some data. Without a valid authentication token, the server can reject the request.

Since the authentication token is derived from the main key, the client would present it to the server as a "reader token" to prove that it is in possession of the main key without revealing the main key to the server.

For destructive operations, the client should instead present a "writer token", which is not derived from the main key but is provided by the server.

keychain.authTokenB64()

authTokenB64 ():Promise<string>

Returns the authentication token as a base64-encoded string.

keychain.authHeader([tokenString])

authHeader (tokenString?:string):Promise<string>
// => `Bearer sync-v1 ${tokenString ?? authTokenB64}`

Returns a Promise that resolves to the HTTP header value to be provided to the server, as a base64 string. It contains the authentication token.

tokenString

Type: string

Optional. A base64-encoded token to use instead of the keychain's own authTokenB64. Useful for presenting a server-issued "writer token" instead of the reader token derived from the main key.

keychain.setAuthToken(authToken)

setAuthToken (authToken:string|Uint8Array|null):void

Update the keychain authentication token to the given authToken.

authToken

Type: Uint8Array | string | null

Default: null

The authentication token. This should be 16 bytes in length. If a string is given, then it should be a base64-encoded string. If this argument is null, then an authentication token will be automatically generated.

keychain.encryptStream(stream[, opts])

encryptStream (
    stream:ReadableStream,
    opts?:{ contentDigest?, recordSize? }
):Promise<ReadableStream>

Type: Function

Returns: Promise<ReadableStream>

Returns a Promise that resolves to a ReadableStream encryption stream that consumes the data in stream and returns an encrypted version. Data is encrypted with Encrypted Content-Encoding for HTTP (RFC 8188).

If opts.contentDigest is provided, the salt is derived from the digest, making the output reproducible — the same plaintext always produces identical ciphertext. Without options, a fresh random salt is used (default behavior; not reproducible).

stream

Type: ReadableStream

A WHATWG readable stream used as a data source for the encrypted stream.

opts

Type: { contentDigest?, recordSize? }

Optional encryption options.

contentDigest

Type: Uint8Array

SHA-256 digest of the plaintext (from keychain.contentDigest()). When provided, enables reproducible encryption by deriving the salt from the digest internally.

recordSize

Type: number

ECE record size in bytes (default RECORD_SIZE = 65536). Record size affects output size and encryption granularity.

keychain.contentDigest(content)

contentDigest (
    content:ReadableStream<Uint8Array>|Uint8Array|Blob
):Promise<Uint8Array>

Type: Function

Returns: Promise<Uint8Array>

Returns a 32-byte SHA-256 digest of the plaintext. Use this digest as the input to encryptStream, header, and encryptRecord to enable reproducible encryption. Accepts a stream, byte array, or Blob; streams and Blobs are drained into memory before hashing.

content

Type: ReadableStream<Uint8Array> | Uint8Array | Blob

The plaintext to hash.

keychain.header(opts)

header (opts:{ contentDigest, recordSize? }):Promise<Uint8Array>

Type: Function

Returns: Promise<Uint8Array>

Returns the 21-byte ECE header for content identified by the digest. The salt is derived internally from the content digest, so this never exposes a raw salt. The header is byte-identical to the header that encryptStream with the same options emits.

opts

Type: { contentDigest, recordSize? }

Required options.

contentDigest

Type: Uint8Array

SHA-256 digest of the plaintext (from keychain.contentDigest()).

recordSize

Type: number

ECE record size in bytes (default RECORD_SIZE = 65536).

keychain.encryptRecord(seq, plaintext, opts)

encryptRecord (
    seq:number,
    plaintext:Uint8Array,
    opts:{
        isLast:boolean,
        contentDigest:Uint8Array,
        recordSize?:number
    }
):Promise<Uint8Array>

Type: Function

Returns: Promise<Uint8Array>

Encrypts a single ECE record by index. The result is byte-identical to record seq of encryptStream with the same content and options. The salt is derived from the content digest internally.

Non-final records must be exactly recordPlaintextSize(recordSize) bytes; the final record must be less than or equal to that. The low-level ECE functions throw if violated.

seq

Type: number

Zero-based record index (0, 1, 2, ...).

plaintext

Type: Uint8Array

The record's plaintext data.

opts

Type: { isLast, contentDigest, recordSize? }

Required options.

isLast

Type: boolean

Whether this is the final record of the content.

contentDigest

Type: Uint8Array

SHA-256 digest of the entire plaintext (from keychain.contentDigest()).

recordSize

Type: number

ECE record size in bytes (default RECORD_SIZE = 65536). Must match the record size used for the header and other records.

keychain.decryptStream(encryptedStream[, opts])

decryptStream (
    encryptedStream:ReadableStream<Uint8Array>,
    opts?:{ recordSize?:number }
):Promise<ReadableStream<Uint8Array>>

Type: Function

Returns: Promise<ReadableStream>

Returns a Promise that resolves to a ReadableStream decryption stream that consumes the data in encryptedStream and returns a plaintext version.

encryptedStream

Type: ReadableStream

A WHATWG readable stream used as a data source for the plaintext stream.

opts

Type: { recordSize? }

Pass the same recordSize that was used to encrypt the stream; defaults to RECORD_SIZE (65536).

keychain.decryptStreamRange(offset, length, totalEncryptedLength[, opts])

decryptStreamRange (
    offset:number,
    length:number,
    totalEncryptedLength:number,
    opts?:{ recordSize?:number }
):Promise<{
    ranges:{ offset:number, length:number }[],
    decrypt:(streams:ReadableStream[])=>ReadableStream
}>

Returns a Promise that resolves to a object containing ranges, which is an array of objects containing offset and length integers specifying the encrypted byte ranges that are needed to decrypt the client's specified range, and a decrypt function.

Once the client has gathered a stream for each byte range in ranges, the client should call decrypt(streams), where streams is an array of ReadableStream objects, one for each of the requested ranges. decrypt will then return a ReadableStream containing the plaintext data for the client's desired byte range.

offset

Type: number

Byte offset into the plaintext to start reading from.

length

Type: number

Number of plaintext bytes to read.

totalEncryptedLength

Type: number

Total length, in bytes, of the encrypted stream.

opts

Type: { recordSize? }

Pass the same recordSize that was used to encrypt the stream; defaults to RECORD_SIZE (65536).

keychain.encryptMeta(meta)

encryptMeta (meta:Uint8Array):Promise<Uint8Array>

Returns a Promise that resolves to an encrypted version of meta. The metadata is encrypted with AES-GCM.

Implementation note: The metadata key is automatically derived from the main key using HKDF SHA-256. The value is not user-controlled.

Implementation note: The initialization vector (IV) is automatically generated and included in the encrypted output. No need to generate it or to manage it separately from the encrypted output.

meta

Type: Uint8Array

The metadata buffer to encrypt.

keychain.decryptMeta(ivEncryptedMeta)

decryptMeta (ivEncryptedMeta:Uint8Array):Promise<Uint8Array>

Returns: Promise<Uint8Array>

Returns a Promise that resolves to a decrypted version of encryptedMeta.

ivEncryptedMeta

Type: Uint8Array

The encrypted metadata buffer to decrypt.

keychain.encryptBytes(bytes[, opts])

async function encryptBytes (
    bytes:ArrayBuffer|Uint8Array,
    opts?:{ iv?:Uint8Array, size?:number },
):Promise<Uint8Array>

Encrypt and return the given data in-memory, not using streams. The key is derived deterministically from the main key, so decryptBytes can re-derive it and decrypt the result.

opts

Type: { iv?, size? }

Optional. size is the derived key length in bytes (default 16); pass the same size to decryptBytes to re-derive a matching key. iv is a 12-byte initialization vector, randomly generated if omitted.

SAFETY: reusing a caller-supplied iv across two calls with different plaintexts is AES-GCM nonce reuse under the same derived key, and breaks confidentiality. Omit iv to get a random one per call.

keychain.decryptBytes(bytes[, opts])

async function decryptBytes (
    bytes:Uint8Array,
    opts?:{ size?:number },
):Promise<ArrayBuffer>

Decrypt the given data in-memory, without streaming.

opts

Type: { size? }

Optional. Pass the same size that was given to encryptBytes, so the same-length key is re-derived.

plaintextSize(encryptedSize)

function plaintextSize (
  encryptedSize:number,
  rs:number = RECORD_SIZE
):number

Given an encrypted size, return the corresponding plaintext size.

encryptedSize(plaintextSize)

function encryptedSize (
  plaintextSize:number,
  rs:number = RECORD_SIZE
):number

Given a plaintext size, return the corresponding encrypted size.

Reproducible & record-addressable encryption

By default, encryptStream uses a fresh random salt for each call. This provides strong privacy (identical plaintexts don't leak through repeated ciphertext), but the same input encrypted twice produces different output.

For use cases like deduplication and content-addressed storage, you need reproducible encryption: the same plaintext always produces identical ciphertext. This is safe only if the salt is bound to the plaintext, preventing a single salt from encrypting two different contents (which would break AES-GCM).

The Keychain API enforces this binding automatically. The salt is never chosen by the caller; it's derived from a content digest (SHA-256 hash of the plaintext) via HKDF. This guarantees: a fixed salt pairs with exactly one plaintext.

Two-pass flow: hash, then encrypt

To encrypt reproducibly, first compute the content digest, then pass it to the encrypt functions:

// 1. Hash pass
const digest = await keychain.contentDigest(file.stream())

// 2. Encrypt pass — reproducible: same input -> identical ciphertext
const encrypted = await keychain.encryptStream(file.stream(), {
    contentDigest: digest,
    recordSize: rs
})

// On demand: regenerate record i byte-identically
const rec = await keychain.encryptRecord(i, sliceI, {
    isLast,
    contentDigest: digest,
    recordSize: rs
})
// Full ciphertext = header(21) || rec0 || rec1 || ... || recLast
const head = await keychain.header({
    contentDigest: digest,
    recordSize: rs
})

Note that encryptStream with no options keeps the original random-salt behavior and is a single pass.

Low-level ECE building blocks

The package exports low-level ECE functions at @substrate-system/crypto-stream/ece. These include RECORD_SIZE, HEADER_LENGTH, recordPlaintextSize, recordCount, header, deriveContentSalt, and encryptRecord. They take a raw salt directly and are footgun-prone: passing the same raw salt with two different plaintexts breaks AES-GCM (nonce-reuse catastrophe). Prefer the Keychain API, which derives the salt from the content digest and is nonce-reuse-safe by construction.

credits

Thank you Feross and SocketDev team for writing and publishing the original, wormhole-crypto.