Changelog

Check out what's new in the latest major version and read what we think about it. You can find our releases on GitHub for more technical details here. You can find our release candidates here.

v1.5.5 (latest)

Released 6th May 2024

This release contains 20 fixes

✅ Show Completed Fields

Fields completed by other recipients are not visible to everyone to better communicate the state of the document and allow users an informed decision on what they are signing.

⬇️ Download Completed Documents via API

Completed documents can now be downloaded via the API using this new endpoint:

GET /API/V1//DOCUMENTS/{ID}/DOWNLOAD

Check out the full Open API docs here: https://documen.so/openapi

➕ Adding Yourself as a Signer

Adding yourself as a signer is now just one click away.

v1.5.4

Released 11th April 2024

This release contains 21 fixes

🔑 Passkeys

To improve security and usability for high-security setups, we added passkeys with this release. Passkeys can now be used to log in or re-authenticate each signature for high-compliance cases.

📄 Signing Certificate & Audit Log

On the security/ compliance side, we also added Signing Certificates and Audit Logs. Every signed document now has a certificate attached, showing technical details of the signature to improve transparency and security. Further, every action on a document from creation to completion is now logged in the audit log to guarantee the integrity of the process.

🔏🦀 @documenso/pdf-sign

We are pretty hyped about this one: Since version 0.9, we relied on https://github.com/vbuch/node-signpdf to add the digital signatures to our documents. Since signing is at the heart of Documenso, we created our own rust-based library for signing. As of 1.5.4, Documenso's signing runs on @documenso/pdf-sign. The library offers a better architecture to enable signing with private keys that are not stored locally (e.g. via HSM). We are in the process of cleaning up the library to open source it like the rest of Documenso 🌱 The library will also help us to offer Long Term Validation (LTV) for signatures soon. While we are currently limited to signing with PKCS7-B, eventually, we plan to support all common signing standards like PAdES, CAdES, and XAdES.