readystack/docuseal repository overview

⁠DocuSeal

readystack/docuseal:3.3.3-CE-alpine-r3

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/docuseal/recipe⁠
• Upstream source at this release's pinned commit (3.3.3): https://github.com/docusealco/docuseal/tree/8f8f69f0bc6ac2e59746cd6efac54a852289bec3⁠
• Product page: https://readystack.dev/products/docuseal⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/docuseal⁠
• Release history (JSON): https://readystack.dev/api/releases/docuseal⁠
• Defect record: https://readystack.dev/defects.html?product=docuseal⁠
• Today's scan: https://readystack.dev/products/docuseal#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=docuseal⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠

A cosign-signed build of github.com/docusealco/docuseal 3.3.3 (AGPL-3.0 — open-source document signing), built clean-room from official upstream source, with the source changes listed below by ReadyStack⁠.

⁠Who uses it and why

Who: Businesses and teams, such as HR and sales, who send documents for signature and keep them on their own server.

Why: DocuSeal turns a PDF into a form with signature, date and other fields, sends it to one or more signers by email, and signs the completed PDF electronically so the signature can be verified.

Use case: An HR team sends each new hire a contract to sign. They place signature, date and checkbox fields on the PDF once in the form builder, then send it; each hire fills it in and signs on a phone or laptop, and the signed PDFs are stored on the company's own server.

About the upstream project, written from its own description: https://github.com/docusealco/docuseal⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:afcee3f4cbd55c6e9f58a5cca766757e56b04c29d214084082f2164d2eaf84b4 on 2026-10-28.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/docuseal⁠
• ReadyStack release check — passed at release on 2026-10-27: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:afcee3f4cbd55c6e9f58a5cca766757e56b04c29d214084082f2164d2eaf84b4; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/docuseal:3.3.3-CE-alpine-r3.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (docuseal).
• Built from source by ReadyStack; the PDFium library (docusealco/pdfium-binaries, sha256-checked) and the field-detection ONNX model (docusealco/fields-detection) are DocuSeal's own prebuilt releases, downloaded by the vendor stage; the WordCraft library that converts Word documents to PDF (libwordcraft.so) is the prebuilt x86_64-linux-musl build inside DocuSeal's wordcraft gem (MIT, docusealco/wordcraft-ruby; the engine is storytold/wordcraft, Apache-2.0 or MIT), installed by Bundler from the version upstream's Gemfile.lock pins (0.8.0).

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is 3.3.3-CE-alpine-r3 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/docuseal:3.3.3-CE-alpine-r3

# ✗ unsupported (do not pull)
docker pull readystack/docuseal:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/docuseal:3.3.3-CE-alpine-r3 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

Single container, Ruby on Rails (Puma) with embedded Redis+Sidekiq — NO sidecars. Default DB is embedded SQLite at /data/docuseal/db.sqlite3 (mount /data/docuseal to persist). Optional external Postgres/MySQL via DATABASE_URL (not used in the CE demo). HTTP on :3000.

docker run -d --name docuseal -p 3000:3000 -v docuseal-data:/data/docuseal readystack/docuseal:3.3.3-CE-alpine-r3

⁠Source changes (AGPL)

This software is licensed under the GNU Affero General Public License, and the releases below are built from a modified copy of its source. Each line names a release, what ReadyStack changed and where the diff is published. From 2026-10-27 a release's diff carries every upstream file its build changes, the dependency manifests and lockfiles included, so its complete corresponding source is the upstream tag with that diff applied; the diff of an earlier release carries the source edits its line names, and the dependency files that release's build changed are in its release archive (vendored/). If you let users interact with the server over a network, AGPL-3.0 section 13 asks you to offer them its source; for a release from 2026-10-27 on, a link to its diff and the upstream tag does that.

• 3.3.3-CE-alpine-r3 — the build writes the release version (3.3.3) into .version, which upstream's tag ships empty and upstream's own release workflow fills the same way; full diff of every upstream file the build changes at https://readystack.dev/source/docuseal/3.3.3/docuseal-3.3.3-readystack.patch⁠

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/docuseal⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:170e4c988261fc9c066f02094fb0060885450920ba28aa8f78ad7cd81d257c5a on 2026-10-27.

— ReadyStack · readystack.dev