dsh-util-crypto

English | 中文

Summary

Zero-dependency browser-safe UUID and byte-encoding helpers. UUID minting uses crypto.getRandomValues, the one random primitive every shipped context provides. crypto.randomUUID is a secure-context Web API: a page or worker served over plain HTTP on a LAN address (the browser preview deployment) has no such method, so code that must run there cannot call it. The repository-wide no-restricted-properties lint rule points crypto.randomUUID callers here; Node-only code importing randomUUID from node:crypto stays as it is.

Table of Contents

• Use this package
• API
• Model Experience
• Known Limitations and Deferred Work
• Dev Note

---

Use this package

It is a library, not a service or plugin: no ctx, registers nothing, holds no state.

---

API

import { bytesToBase64, randomUUID, type Uuid } from '@deepseek-ai/dsh-util-crypto'

Export	Role
bytesToBase64(data)	Canonical base64 for a byte array, encoded in bounded chunks.
randomUUID()	Random RFC 9562 v4 UUID string, minted from crypto.getRandomValues. Drop-in for crypto.randomUUID().
Uuid	The five-group UUID string type, matching crypto.randomUUID's declared return shape.

Model Experience

Indirectly, through consumers that mint request, session, and attachment identifiers with it, none of which enter prompts as semantic content.

KV Cache effect

No direct invalidation; identifier-minting consumers own any request changes.

Known Limitations and Deferred Work

• v4 only — no other UUID versions, namespaces, or parsing; consumers needing more should take a real UUID dependency.
• Uniqueness is probabilistic — 122 random bits, the same guarantee crypto.randomUUID gives; nothing here detects collisions.

Dev Note

Working context for maintainers — click to expand

None.

Runtime invariant: No companion is published. This pure utility owns no event stream or mutable runtime data; its value algebra is enforced by unit tests.