
Company News
Free Business Plan Upgrades for Open Source Maintainers
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.
@dotit/pades
Advanced tools
PAdES (PDF Advanced Electronic Signatures) for IntentText — export a sealed .it as a digitally-signed PDF (ECDSA P-256 + X.509 + CMS) that Adobe/readers recognize. The standards bridge on top of @dotit/sign's native Ed25519 trust.
PAdES (PDF Advanced Electronic Signatures) for IntentText — export a sealed
.it document as a digitally-signed PDF that Adobe Reader, courts, banks, and
government portals recognize.
It's the standards bridge on top of IntentText's native trust: a .it stays
Ed25519-signed and queryable (@dotit/sign); the exported PDF carries an
X.509 / CMS PAdES signature the outside world auto-accepts. The two coexist.
ETSI.CAdES.detached).
(Adobe doesn't validate Ed25519 PDF signatures — hence X.509 here.)npm i @dotit/pades
The easiest path is via @dotit/pdf, which renders the .it then signs the PDF:
import { renderSignedPDF } from "@dotit/pdf";
import { generateSelfSignedCert } from "@dotit/pades";
const id = await generateSelfSignedCert({
commonName: "Dalil Technology",
organization: "Dalil",
});
const signedPdf = await renderSignedPDF(sealedItSource, {
executablePath: process.env.CHROME_PATH, // puppeteer-core needs a Chrome
signer: {
certPem: id.certPem,
privateKeyPem: id.privateKeyPem,
name: "Dalil Technology",
reason: "Issued invoice",
tsaUrl: "http://timestamp.digicert.com", // optional → PAdES-T
},
});
// signedPdf: Uint8Array — opens in Adobe as a digitally-signed document.
import { signPdfWithPem, verifyPdfSignature } from "@dotit/pades";
const signed = await signPdfWithPem(pdfBytes, {
certPem,
privateKeyPem,
name: "Sarah Al-Ahmad",
tsaUrl: "http://timestamp.digicert.com", // optional
});
const info = await verifyPdfSignature(signed);
// { present, valid, coversWholeFile, signerCommonName, signedAt,
// timestamped, timestampTime, chainValid }
generateSelfSignedCert returns PEM strings — store them securely (e.g. the OS
keychain) and reload with signerFromPem:
const id = await generateSelfSignedCert({ commonName: "Acme Corp" });
// keep id.certPem + id.privateKeyPem (private key → keychain / KMS)
const signer = await signerFromPem(id.certPem, id.privateKeyPem);
A self-signed cert is cryptographically valid but shows as "identity not trusted" until installed. Issue signer certs from a CA whose root verifiers trust:
import { createCertificateAuthority, issueCertificate, signPdf, verifyPdfSignature } from "@dotit/pades";
const root = await createCertificateAuthority({ commonName: "UTS Root CA", organization: "UTS" });
// keep root.privateKeyPem OFFLINE
const signer = await issueCertificate({
issuer: { certificate: root.certificate, privateKey: root.privateKey },
commonName: "Dalil Technology",
});
const signed = await signPdf(pdfBytes, {
certificate: signer.certificate,
privateKey: signer.privateKey,
chain: signer.chain, // embeds the CA cert(s) in the signature
});
const info = await verifyPdfSignature(signed, { trustedRoots: [root.certificate] });
// info.chainValid === true
For production, keep the root key offline and issue an intermediate
(issueCertificate({ ..., isCa: true })) for online signing.
| Function | Purpose |
|---|---|
generateSelfSignedCert(opts) | ECDSA P-256 self-signed cert + key (PEM/DER) |
createCertificateAuthority(opts) | a CA root/intermediate (cA:true) |
issueCertificate({ issuer, commonName, isCa? }) | CA-signed cert + chain |
signerFromPem(certPem, keyPem) | load a signer from PEM |
signPdf(pdf, { certificate, privateKey, chain?, tsaUrl? }) | PAdES-sign a PDF |
signPdfWithPem(pdf, { certPem, privateKeyPem, tsaUrl? }) | sign via PEM identity |
verifyPdfSignature(pdf, { trustedRoots? }) | verify (signature, whole-file, timestamp, chain) |
requestTimestampToken(data, tsaUrl) | low-level RFC-3161 timestamp |
signDetachedCms / verifyDetachedCms | low-level CMS over arbitrary bytes |
PUBLIC_TSA | { digicert, sectigo, swisssign } free TSA URLs |
PAdES-B-B / PAdES-B-T (ETSI EN 319 142), CMS (RFC 5652) with ESS
signing-certificate-v2 (RFC 5035), RFC-3161 timestamps, X.509 (RFC 5280),
ECDSA P-256 (FIPS 186-4). Built on pkijs + @signpdf + Node WebCrypto.
MIT
FAQs
PAdES (PDF Advanced Electronic Signatures) for IntentText — export a sealed .it as a digitally-signed PDF (ECDSA P-256 + X.509 + CMS) that Adobe/readers recognize. The standards bridge on top of @dotit/sign's native Ed25519 trust.
The npm package @dotit/pades receives a total of 25 weekly downloads. As such, @dotit/pades popularity was classified as not popular.
We found that @dotit/pades demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Company News
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.

Security News
The supply chain control that delays freshly published gems now covers lockfile generation and gem vendoring in Ruby projects.

Security News
During a UK cyber test, a Mythos 5 agent used sockpuppets, social engineering, and prompt injection to try to get a maintainer to merge malware.