Skip to content

Releases

SignuDoc 0.5.0

Choose a tag to compare

@kropdx kropdx released this 18 Nov 21:32
f8a07f7

Administrators can now see every member's envelopes and delete finished ones after a 14-day notice, plus six outside bug fixes and a security update. This release changes the database: see the end of these notes.

Administrators

  • An "Everyone's" view on the dashboard lists every member's sent and finished envelopes, with the sender on each card. Administrators can open them and download their files, and a download of another member's file is recorded in the site audit trail. Drafts stay private to their sender.
  • The dashboard is split into pages of 48, and its search box searches the whole list on the server, including the sender's name and email in "Everyone's".
  • "Delete envelope" on a completed, declined or voided envelope schedules it for deletion 14 days later. The sender gets an email naming who asked, and any administrator can cancel within the 14 days, in which case the sender is told it will not be deleted. Nothing is deleted before the sender has been emailed. In Part 11 mode a reason is required. The request, a cancellation and the deletion itself are all in the site audit trail, with the record's hashes kept after the files are gone.
  • A deleted envelope's files are queued and retried by the daily job until they are gone, so a storage hiccup cannot leave orphaned files behind.
  • The retention sweep does not delete an envelope with a deletion scheduled, so the retention period cannot cut the 14-day notice short.

Fixes

  • Fields placed on rotated pages (typical of landscape scans), and on pages whose crop box differs from the page size, are stamped where they were placed in the signed PDF instead of shifted or sideways. This includes envelopes uploaded before this release (#69, PR #116).
  • A void or decline that races another void, decline or the last signature no longer deletes the winner's certificate (#68).
  • After switching signature tabs, the Draw tab shows the drawing that will be applied, instead of an empty canvas (#70).
  • A client that sends an empty User-Agent header can sign, verify, consent and decline, instead of getting an error (#71).
  • Exporting the audit trail of an envelope whose title has a dash, curly quote or non-Latin characters works, instead of failing with a server error (#72).
  • An envelope's timeline lists events in the order they were recorded, so "completed" no longer shows before "signed" (#73).

Security

  • node-forge updated to 1.4.3, which fixes four moderate advisories (#80).

Thanks to @njarrar for the six fixes, and to @jasonhaggart for the node-forge update.

This release changes the database (20261118100000_pending_file_deletions.sql, 20261118110000_scheduled_envelope_deletions.sql). On Vercel the production build applies them. On other hosts, run npm run db:migrate as on every deploy.

SignuDoc 0.4.0

Choose a tag to compare

@kropdx kropdx released this 17 Nov 18:16
6c0528e

A name field, and fixes for nine reported bugs. This release changes the database: see the end of this entry.

Envelopes

  • A name field. Place it where the signer's printed name belongs, and it is filled in with the name the sender gave that signer when they sign, the way a date field is filled in with the day. It is always required, and the signer does not type it. Contributed by @sumnerboy12 (#49, PR #50).

Fixes

  • The certificate's "sent" and reminder rows name the sender, not the first signer next to the sender's email address (#52).
  • Sending or reminding when email is not set up says so, instead of failing with a generic server error. A manual reminder no longer retires the signer's link before finding there is no email to send it with (#53).
  • A password-locked PDF is named as locked on upload, instead of being reported as a file that could not be rendered (#54).
  • After a signer declines, the page says the decline was recorded, instead of "This link has expired" (#55).
  • Setup refuses a password over 128 characters instead of silently cutting it short, which made the next sign-in fail (#56).
  • Sign-in and sign-up say a password is too long, instead of "too short" or "something went wrong" (#57).
  • Typed signatures in the script font keep every letter when the text is copied or searched, and no longer show gaps inside names where the font joins letters (#58, #59).

Documentation

  • The agent deploy guide checks Vercel's rule that the free Hobby plan is for non-commercial use before choosing free plans for a company (#47).

Thanks to @coygeek for the detailed bug reports, and to @sumnerboy12 for the name field.

This release changes the database (20261118090000_name_field.sql). On Vercel the production build applies it. On other hosts, run npm run db:migrate as on every deploy.

Full changelog: CHANGELOG.md

SignuDoc 0.3.0

Choose a tag to compare

@kropdx kropdx released this 17 Nov 00:45
1df503d

Sign-in security and audit features for organizations that need them, and two new ways to fix a sent envelope. This release changes the database: see the end of this entry.

Envelopes

  • A sender can correct a signer's email address after sending. The old signing link stops working, the new address gets a fresh invitation, and the audit trail records the correction.
  • A finished envelope can be copied into a new draft with the same document, recipients and fields, and nothing that was filled in.

Sign-in security

  • Two-step sign-in: anyone with an account can add an authenticator app under Settings, with ten single-use backup codes. Signing in then asks for a code after the password.
  • Administrators can require two-step sign-in of everyone (Settings, Organization, Sign-in security), and reset it for someone who lost their phone (People).
  • Session limits: administrators can sign people out after a time without use (15 minutes to 8 hours) and at the latest a set time after sign-in (8 hours to 3 days). Anyone can sign out on every device at once.
  • A session that was ended (signed out everywhere, or reset by an administrator) stops working at once, not when the short-lived session cookie runs out.
  • Ten wrong passwords for one email address within 15 minutes stop sign-in for that address for 15 minutes.
  • The site audit trail now records sign-ins, failed sign-ins, lockouts, sign-outs, password changes and resets, two-step sign-in changes, logo changes and the email domain being added. It moved from the Part 11 panel to the new Sign-in security panel, and is there whether or not Part 11 mode is on.
  • Single sign-on over OpenID Connect (Okta, Microsoft Entra ID, Google Workspace and others), set up with SSO_ISSUER, SSO_CLIENT_ID and SSO_CLIENT_SECRET. New people get an account under the install's sign-up rule. PASSWORD_SIGN_IN=off then turns password sign-in off, except for the addresses in PASSWORD_SIGN_IN_ALLOWED_EMAILS.
  • Audit rows (site and document trails) and security events are written to the function logs as JSON lines once saved, so a Vercel log drain can deliver them to a SIEM. AUDIT_LOG=off stops the audit lines.
  • A daily backup of the database and files to a second, private Blob store, turned on with BACKUP_BLOB_READ_WRITE_TOKEN, and npm run restore-backup to restore it into a new database and store. See docs/backup-and-restore.md. vercel.json has a second daily cron job, which does nothing until the token is set.
  • Account closure requests and account deletions are recorded in the site audit trail.
  • docs/soc2: a SOC 2 pack for organizations that put an install in their audit: a control map to the Trust Services Criteria, vendor duties, questionnaire answers and sample policies.

Project security

  • CodeQL, dependency review, a weekly npm audit and OpenSSF Scorecard run on the SignuDoc repository (skipped in a copy made by the Deploy button).
  • Each release gets a CycloneDX SBOM, a source archive and signed build provenance attached. SECURITY.md says how to verify them.

This release changes the database (20261115100000_copied_audit_event.sql, 20261116100000_signer_corrected.sql, 20261117090000_sign_in_security.sql, 20261117100000_session_controls.sql). On Vercel the production build applies them, so nothing is needed by hand. On other hosts, run npm run db:migrate as on every deploy.

Full changelog: CHANGELOG.md

SignuDoc 0.2.1

Choose a tag to compare

@kropdx kropdx released this 16 Nov 04:56
8d607a6

A smoother first deploy. No database change: this release needs no migration step.

Deploying

  • The Deploy button now adds Resend first, then Neon and Blob, so Resend's sending domain has longer to be ready before the first deployment starts.
  • If Vercel stops the first deployment with "One or more integration resources failed to provision", the README and the self-hosting guide say what to do: wait a minute or two, refresh, and redeploy. Nothing is wrong with your copy.
  • New guide for AI agents: give it to an agent that can use your browser, and it deploys and sets up SignuDoc for you, with clear retry rules.
  • The README's button now reads "Deploy to Vercel", with "or copy this to your LLM" under it, linking to that guide.

Updating an existing install: nothing to do beyond taking the release (Settings, SignuDoc, Check for updates). These changes only affect new deploys and the docs.

Full changelog: CHANGELOG.md

SignuDoc 0.2.0

Choose a tag to compare

@kropdx kropdx released this 15 Nov 22:19
4324ec7

Installs can now find and take new releases without using git. No database change: this release needs no migration step.

The same list is in CHANGELOG.md. How updating works is in Keep your install up to date.

Keeping an install up to date

  • Check for updates in Settings, SignuDoc (administrators only): shows the version the site runs, asks GitHub for the latest release, and shows what is new in it.
  • Update SignuDoc workflow (.github/workflows/update-signudoc.yml) in each copy: runs every Monday or by hand, merges the new release with the copy on a signudoc-update/<version> branch and opens a pull request, so Vercel builds a preview first. Changes you made to the code are kept; where you and SignuDoc changed the same lines it stops and lists the files. It never force-pushes.
  • Optional settings for the workflow: a SIGNUDOC_UPDATE_TOKEN secret so it can update workflow files too, SIGNUDOC_AUTO_MERGE=1 to merge clean updates straight into production, and SIGNUDOC_PRODUCTION_BRANCH when Vercel deploys from a branch other than the default one.
  • The self-hosting guide explains the workflow and a by-hand update for a Deploy-button copy, which shares no history with this project.

Upgrading from 0.1.0

A copy made from 0.1.0 does not have the update workflow yet. Add .github/workflows/update-signudoc.yml to it once (Settings in SignuDoc links to the right page, and the self-hosting guide has the steps), then run it. If it asks which version you deployed, use v0.1.0.

Other changes

  • The Code of Conduct file is removed.

Not yet verified

  • The update workflow is tested in CI against stand-in repositories. A real run in a Deploy-button copy has not been done yet.
  • Everything listed under 0.1.0 as not yet verified still is.

SignuDoc is software, not legal advice. See the README's legal disclaimer.

SignuDoc 0.1.0

Choose a tag to compare

@kropdx kropdx released this 14 Nov 20:59
c08b777

The first open-source release. SignuDoc is an e-signature platform that an organization deploys to its own Vercel account and runs on free plans.

Deploy it in one click from the README. The same list is in CHANGELOG.md.

Deploy and run it yourself

  • One-click Deploy to Vercel button that provisions Neon Postgres, Vercel Blob and Resend from the Vercel Marketplace, all on their free plans. Vercel keeps its free Hobby plan for personal, non-commercial use, so a company belongs on Vercel Pro ($20 a month, whatever its size).
  • Setup wizard on first visit: creates the first administrator, asks for the install's own support email, and fills in the email sending domain (with a sign. subdomain by default).
  • Daily Vercel cron for reminders, deadlines and retention, rate limits kept in Postgres, and optional Vercel BotID (BOTID=1).
  • Runs locally with no outside services for development and tests.
  • Copyright Nyllon Software, released under the license in LICENSE.

Sending and signing

  • Soft Studio interface for the dashboard, field placement, envelopes and the signing page, with first-page thumbnails and a phone layout.
  • Signers sign without an account. A signer's extra check is one choice: an emailed code or an access code.
  • Text, date, number, checkbox, dropdown and radio fields; signing order; CC recipients; deadlines with expiry; optional reminders.
  • Templates for documents sent often ("Save as template", "Use template").
  • Branding with your own name, logo and color, and an administrators panel.

Records you can rely on

  • Electronic-records consent disclosure and a permitted-use list, both versioned, to meet US ESIGN/UETA and EU eIDAS expectations for simple electronic signatures.
  • Hash-chained audit trail and a completion certificate on every envelope.
  • Finished documents sealed with a PAdES signature (an install's own key, or your certificate through SEAL_P12_BASE64), with an RFC 3161 timestamp when SEAL_TIMESTAMP_URL is set.
  • PAdES B-LT and B-LTA: revocation data and a document timestamp are added after the seal so it stays checkable for years.
  • Retention settings with a warning before anything is deleted, and signer erasure requests.

Regulated use

  • Part 11 mode for FDA 21 CFR Part 11 records: signers sign from a verified account and enter their password at signing, each signature carries its meaning, and settings changes go to their own audit chain with CSV export. A validation pack in docs/part11/ gives an install a start on its own validation.
  • Signer advanced and qualified signatures (AdES/QES): a signer can sign in their own name through eID Easy or any Cloud Signature Consortium (CSC v2) provider, with the result embedded in the PDF.

Not yet verified

These parts are built and tested against stand-ins in CI, but have not been checked against the real services:

  • A full Deploy-button pass on a clean Vercel account, step by step against the README. A first run surfaced Vercel's "Needs Attention" badge on Neon variables, which docs/self-hosting.md now explains.
  • Live eID Easy and CSC providers for signer AdES/QES.
  • A real timestamp authority and certificate authority for the seal and for B-LT/B-LTA.
  • Part 11 mode and the validation pack are a starting point: each organization still has to validate its own install.

SignuDoc is software, not legal advice. See the README's legal disclaimer.