Skip to main content
Forme 0.9.0 renames the signing API surface to better reflect the cryptographic nature of the operation (PKCS#7 certification, not e-signatures). Old names continue to work with deprecation warnings.

Breaking Changes

sign → certify rename

All signing API surfaces have been renamed: Old names still work — they are exported as deprecated aliases. No immediate code changes are required, but you should migrate before a future major version removes the aliases.

Migration Examples

React (<Document> prop)

Node.js (@formepdf/core)

API endpoint

The request body is identical. No field names changed.

Go SDK

Python SDK


New in 0.9.0

New API Endpoints

New Features

Bug Fixes

  • SVG children API — JSX children auto-serialized to SVG content
  • SVG opacity support (opacity, fill-opacity, stroke-opacity)
  • Page style prop inheritance fix
  • WASM time panic fix in certify and redact (browser WASM)
  • PKCS#1 private key auto-conversion to PKCS#8

Upgrade Checklist

  1. Update @formepdf/react, @formepdf/core, and @formepdf/cli to 0.9.0
  2. Search your codebase for signature prop, signPdf, SignatureConfig, /v1/sign
  3. Replace with certification, certifyPdf, CertificationConfig, /v1/certify
  4. Update Go/Python SDK method calls if applicable
  5. Test that existing certifications still verify correctly