Crypto Edge
    Preparing search index...

    Crypto Edge

    crypto-edge logo

    @sebastienrousseau/crypto-edge

    Edge-runtime cryptographic operations using the Web Crypto API, optimized for Cloudflare Workers, Vercel Edge, and Deno.

    Build Coverage Registry Docs OpenSSF Scorecard License: Apache-2.0 OR MIT Node.js 22 or newer


    Getting started

    • Install — installation via pnpm, npm, or yarn
    • Requirements — runtime floor and environment prerequisites
    • Quick Start — minimal working usage sample

    The Crypto Service ecosystem

    Package reference

    Operational


    pnpm add @sebastienrousseau/crypto-edge
    # or
    npm install @sebastienrousseau/crypto-edge
    # or
    yarn add @sebastienrousseau/crypto-edge

    Back to Top


    • Node.js: ^22.0.0 or >=24.0.0 (active and maintenance LTS releases)
    • Package Manager: pnpm >=9 (recommended) or npm >=10
    • TypeScript: >=5.0 (when compiling with TypeScript)

    Back to Top


    import { hash, detectRuntime } from "@sebastienrousseau/crypto-edge";

    console.log("Running on:", detectRuntime());

    const digest = await hash("SHA-256", "hello world");
    console.log(digest);
    // b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9

    Back to Top


    Crypto Service provides a complete cryptography stack across 14 specialized packages:

    Package Role Description
    @sebastienrousseau/crypto-api API docs Postman collection types and a Postman-to-Markdown converter; the server's API contract is its OpenAPI document.
    @sebastienrousseau/crypto-benchmarks Benchmarks Benchmarks comparing classical and post-quantum cryptography: ops/sec, latency and throughput.
    @sebastienrousseau/crypto-cbom CBOM Cryptographic Bill of Materials generator and auditor (CycloneDX 1.6, SPDX 3.0).
    @sebastienrousseau/crypto-cli Terminal CLI Command-line interface: hashing, key generation, encryption, signing, HPKE, Argon2id and CBOM scans, with an interactive menu.
    @sebastienrousseau/crypto-edge (this package) Edge Runtime Edge-runtime cryptographic operations using the Web Crypto API, optimized for Cloudflare Workers, Vercel Edge, and Deno.
    @sebastienrousseau/crypto-kms Cloud KMS Unified KMS interface: AWS KMS, Google Cloud KMS, Vault Transit and local providers; Azure is a stub.
    @sebastienrousseau/crypto-lib Core Library Core library: post-quantum ML-KEM, ML-DSA and SLH-DSA, plus classical, modern and OpenPGP cryptography for TypeScript.
    @sebastienrousseau/crypto-lsp IDE Analysis Language server that flags weak and quantum-vulnerable cryptography in the editor, with quick fixes.
    @sebastienrousseau/crypto-mcp AI Agents Model Context Protocol server exposing cryptography tools to AI assistants and agents.
    @sebastienrousseau/crypto-middleware Middleware Cryptographic middleware for Express and Fastify: decrypt requests, encrypt responses, verify HMAC signatures and JWTs.
    @sebastienrousseau/crypto-prisma ORM Adapter Transparent field-level encryption extension for Prisma Client, using XChaCha20-Poly1305.
    @sebastienrousseau/crypto-react React Hooks React hooks and context provider for client-side cryptographic operations with zero boilerplate.
    @sebastienrousseau/crypto-sdk Client SDK A zero-dependency, typed HTTP client for the Crypto Service REST API, with full post-quantum support.
    @sebastienrousseau/crypto-server HTTP API A hardened Fastify REST API for cryptographic operations, with rate limiting, OpenAPI schemas, and post-quantum endpoints.
    @sebastienrousseau/crypto-testing Test Support Deterministic keys, fast mocks, and test fixtures for crypto-lib
    @sebastienrousseau/crypto-typeorm ORM Adapter TypeORM column-level encryption with a single decorator, powered by crypto-lib.
    @sebastienrousseau/crypto-vue Vue Composables Vue 3 composables for client-side cryptography
    @sebastienrousseau/crypto-wasm Acceleration Placeholder for a WebAssembly accelerator; no WebAssembly module ships yet.

    Back to Top


    crypto-edge adapts the Crypto Service Suite for edge and serverless runtimes. It provides runtime detection, a Web Crypto wrapper for hashing, AES-GCM encryption, HMAC signing, and key generation, plus polyfills for minimal environments. All functions use only the standard Web Crypto API -- no Node.js built-ins are imported.

    Back to Top

    Runtime Identifier Web Crypto Notes
    Cloudflare Workers cloudflare-workers Yes Full support
    Vercel Edge vercel-edge Yes Full support
    Deno deno Yes Full support
    Bun bun Yes Full support
    Browsers browser Yes Modern browsers (Chrome 37+)
    Node.js node Yes Node >= 15 (globalThis.crypto)
    Unknown unknown Varies Use getCapabilities() to check

    Back to Top

    import {
    detectRuntime,
    getCapabilities,
    isEdgeCryptoAvailable,
    } from "@sebastienrousseau/crypto-edge";

    const runtime = detectRuntime();
    const caps = getCapabilities();
    if (isEdgeCryptoAvailable()) {
    // Safe to call hash(), encrypt(), etc.
    }
    import {
    hash,
    generateKey,
    encrypt,
    decrypt,
    } from "@sebastienrousseau/crypto-edge";

    // Hashing
    const sha256 = await hash("SHA-256", "hello");

    // Encryption / Decryption (AES-GCM)
    const key = await generateKey({ algorithm: "AES-GCM", length: 256 });
    const { ciphertext } = await encrypt({
    key,
    plaintext: new TextEncoder().encode("secret"),
    });
    const plaintext = await decrypt({ key, ciphertext });

    Call installPolyfills() once at startup for minimal runtimes missing standard globals:

    import { installPolyfills } from "@sebastienrousseau/crypto-edge";

    const installed = installPolyfills();

    Polyfills provided: TextEncoder, TextDecoder, btoa, and atob. crypto.getRandomValues is never polyfilled: without a native CSPRNG, randomBytes() throws rather than fall back to predictable output.

    Back to Top

    All examples are self-contained TypeScript files in the examples/ directory. Run any example with:

    npx ts-node examples/<name>.ts
    
    Category Example Purpose
    Detection detect.ts Runtime detection
    Hashing hash.ts Edge-compatible hashing
    Encryption encrypt.ts AES-GCM encrypt and decrypt
    Workers workers.ts Cloudflare Workers usage
    Vercel vercel.ts Vercel Edge Function usage
    Browser browser.ts Browser usage
    Polyfills polyfill.ts Polyfill installation

    Back to Top

    Back to Top


    pnpm --filter @sebastienrousseau/crypto-edge run build
    pnpm --filter @sebastienrousseau/crypto-edge run test
    pnpm --filter @sebastienrousseau/crypto-edge run lint
    pnpm --filter @sebastienrousseau/crypto-edge run format

    All 18 packages in the Crypto Service workspace maintain a 100% coverage floor across statements, branches, functions, and lines.

    Back to Top


    Report vulnerabilities privately via GitHub Security Advisories or according to SECURITY.md. Never report security issues publicly.

    Cryptographic operations use the @noble/* libraries, Node.js crypto and OpenPGP.js. @noble/post-quantum has not been independently audited and does not guarantee constant-time execution, and no module in this suite is FIPS 140-3 validated. Key zeroization is limited: JavaScript strings and garbage-collected buffers cannot be reliably wiped. See SECURITY.md.

    Back to Top


    Back to Top


    Versions advance strictly one step at a time on the 0.0.x line (v0.0.1 → v0.0.2 → v0.0.3 ... → v0.0.999 → v0.1.0). Work for every release iteration begins on a dedicated feat/v<version> branch.

    All 18 packages in the workspace move in lockstep. Public API signatures, cipher output formats, and serialization schemas are strictly versioned. Breaking changes to serialized formats or algorithm defaults are considered major breaking changes. Minimum toolchain upgrades (e.g. Node.js LTS floor) are governed by POLICIES.md.

    Back to Top


    Dual-licensed under Apache 2.0 or MIT, at your option.

    Copyright (c) 2022-2026 Sebastien Rousseau and The Crypto Service Suite contributors.

    Back to Top