@ende/http/unstable-message-signatures

ende add jsr:@ende/http

Version 2026.10.15 on JSR.

Utilities for creating and verifying RFC 9421 HTTP Message Signatures.

HTTP Message Signatures provide end-to-end integrity and authenticity for components of an HTTP message by using detached digital signatures or MACs. The Signature-Input and Signature headers are serialized as Structured Fields Dictionaries (RFC 9651).

Exports

  • ComponentIdentifier — A component identifier consisting of a name and optional parameters.
  • ComponentInput — Convenience type accepting either a plain string or a full ComponentIdentifier. Known derived component names are autocompleted.
  • ComponentParameters — Parameters that can be attached to a component identifier.
  • createSignatureBase — Construct the signature base string for a message per RFC 9421 section 2.5.
  • CreateSignatureBaseOptions — Options for createSignatureBase.
  • DerivedComponent — Known derived component names per RFC 9421 section 2.2.
  • ParsedSignatureParams — Parsed signature parameters returned from verification. Components are always fully resolved ComponentIdentifier objects.
  • SignatureAlgorithm — Algorithm identifiers per RFC 9421 section 3.3.
  • SignatureParams — Signature parameters used when signing a message.
  • signMessage — Sign an HTTP message per RFC 9421.
  • SignOptions — Options for signMessage.
  • Uint8Array_ — Proxy type of {@code Uint8Array<ArrayBuffer>} or {@code Uint8Array} in TypeScript 5.7 or below respectively.
  • verifyMessage — Verify one or more signatures on an HTTP message per RFC 9421.
  • VerifyOptions — Options for verifyMessage.
  • VerifyResult — Result of a successful signature verification.