Skip to content

Releases

v1.6.4

Choose a tag to compare

@github-actions github-actions released this 14 Nov 00:54
37afd9d

[1.6.4] - 2026-11-13

Changed

  • package.json reads 1.6.4. v1.6.3 is already tagged and is not moved. The next tag should be v1.6.4 so it matches this version.

Security

  • Pushing a v* tag builds lightdrawer-<tag>.tar.gz and the npm pack tarball (lightdrawer-receipts-<version>.tgz) and attaches both, plus verify.html and SHA256SUMS.txt, to the GitHub Release. SHA256SUMS.txt lists those three files and not the provenance files. The SLSA GitHub generator (generator_generic_slsa3.yml at tag v2.1.0, commit f7dd8c54c2067bafc12ca7a55595d5ee9b75204a) signs one SLSA Build Level 3 provenance file, lightdrawer-<tag>.intoto.jsonl, and attaches it to that release. Check it with slsa-verifier verify-artifact. GitHub's native attestation is still produced with actions/attest-build-provenance and checked with gh attestation verify. The generator is referenced by its release tag because a commit SHA is rejected by the generator and by slsa-verifier. Verifying a release.

v1.6.3

Choose a tag to compare

@github-actions github-actions released this 13 Nov 21:28
c3df7e5

[1.6.3] - 2026-11-13

Changed

  • How we keep LightDrawer trustworthy now says the main ruleset requires the automated tests to pass, and that v1.6.2 is the first release with signed build provenance. Formatting in its settings list is restored.
  • package.json reads 1.6.3, and this tag matches it. The v1.6.2 tag itself still reads 1.6.1 there, because the version was not bumped before tagging. Tags are never moved.

Security

  • How we keep LightDrawer trustworthy now says CodeQL code scanning is on. GitHub's default setup runs it on pushes and pull requests to main, and on a weekly schedule. Required approving reviews are still not required.
  • POST /api/ct/tick no longer returns exception text. An unexpected failure is logged on the server, the JSON body says the tick failed, and D1 last_error can still keep the detail for the operator. The mock certificate directory name uses a random UUID instead of Math.random(), and the stamp-key script escapes backslashes before quotes in the printed wrangler command.
  • The README shows the OpenSSF Best Practices badge (passing). (#15)
  • minimatch, used only by the lint tool and never shipped, is pinned to 11.0.8 to clear a moderate advisory (GHSA-g3hv-75wg-m249). npm audit reports 0 vulnerabilities. (#16)
  • GitHub Releases now also attach *.intoto.jsonl provenance bundles for the tarball, verify.html, and SHA256SUMS.txt. Those files are the signed provenance the release workflow already creates. SHA256SUMS.txt still lists only the tarball and verify.html. The security policy now says we acknowledge a report within 14 days and aim to fix a confirmed vulnerability within 60 days. npm test includes property-based parser tests, and npm run lint checks src/, scripts/, and test/.

v1.6.2

Choose a tag to compare

@github-actions github-actions released this 13 Nov 17:34
1dc898c

Release v1.6.2.

No matching section in CHANGELOG.md.

1.4.0

Choose a tag to compare

@desynced desynced released this 11 Nov 03:42

1.4.0 — November 10, 2026 (US Central)

Added
An open stamp lane at POST /api/mcp/stamp for the LightDrawer MCP server and similar local tools. It accepts the same hash-only body as /api/stamp (digest and optional tsq), with no human check and no API key. Website stamping and API-key stamping are unchanged.

The lane can be switched off with the MCP_LANE variable (HTTP 404, so MCP clients fall back to the browser) or immediately, without a redeploy, by setting mcp_lane=off in the ct_meta table.

Optional hourly and daily caps (MCP_LIMIT_IP_HOUR and MCP_LIMIT_GLOBAL_DAY). 0 means that cap is off (unlimited); a positive number turns it on. When a cap is off, no counter row is written for it, so no hashed-IP data is stored. The hosted site starts with both caps off. A short burst limit (5 requests per 10 seconds) sits in front to protect the public calendars and FreeTSA. If a cap or the burst guard is hit, the response is HTTP 429 with Retry-After.

When an hourly cap is on, addresses are stored only as a keyed hash for the current UTC day, never as raw IPs. Those counters are removed by the existing 15-minute cron once they expire.

1.3.1

Choose a tag to compare

@desynced desynced released this 10 Nov 23:27

1.3.1 — November 10, 2026 (US Central)

Fixed
The offline verifier now checks Let's Encrypt's embedded precertificate SCTs against bundled Certificate Transparency log keys, instead of warning that the signature did not match. The bundled list also includes current static-ct-api (tiled) logs such as IPng Gouda, which the previous snapshot skipped.

Changed
The three example receipts in examples/ were remade with the current LightDrawer. Each now includes the finished Bitcoin proof, the FreeTSA timestamp, and the certificate-log proof, and the README links to each one's public receipt page.

LightDrawer 1.3.0

Choose a tag to compare

@desynced desynced released this 10 Nov 19:28

Added

  • Websites can add a free “Stamp this with LightDrawer” link or a small helper they host themselves. A plain-language guide is at /button, with a standalone demo in examples/stamp-button/. The usual version is a normal HTML link. An optional ?expect= query (the file’s SHA-256) makes LightDrawer warn if a different file is dropped; an optional helper can pass that same file hash in the URL fragment (#digest=…) so it never reaches a server log. Visitors still confirm the file and complete the human check on LightDrawer. Embedded pages do not call /api/stamp, and API keys stay on site servers only.

LightDrawer 1.2.2

Choose a tag to compare

@desynced desynced released this 10 Nov 17:53

Changed

  • Stamp requests now cap the request body by counting the bytes actually read, even if Content-Length is missing.
  • JSON API responses now send a tight Content-Security-Policy (default-src 'none'), X-Content-Type-Options: nosniff, Referrer-Policy: no-referrer, and frame-ancestors 'none'.
  • The on-demand certificate-log tick endpoint compares its secret in constant time (by hashing both values first) and is rate-limited per address, using an existing limiter with its own key.
  • Stamp error lists no longer include raw messages from OpenTimestamps, FreeTSA, or the database. Those details stay in Worker logs.
  • A leftover certificate-issuance error note in the database is cleared after a certificate is issued successfully.

Added

  • A /.well-known/security.txt file that points vulnerability reports at this repository's GitHub security advisories.

Operations

  • The Worker's default workers.dev address was turned off, so the production site is only reached through lightdrawer.org (and www).
  • The site's minimum TLS version was raised to 1.2.
  • The site's SSL mode was set to Full (strict).
  • www.lightdrawer.org now redirects permanently to lightdrawer.org.

LightDrawer 1.2.1

Choose a tag to compare

@desynced desynced released this 10 Nov 17:53

Added

  • A plain-language "Why would I use this?" section on the homepage, with three everyday examples: showing you made something first, recording a rental's condition before a repair or move-out, and keeping the exact version of an agreement.

LightDrawer 1.2.0

Choose a tag to compare

@desynced desynced released this 10 Nov 17:53

Added

  • A shareable receipt page at https://lightdrawer.org/r/<fingerprint>. Anyone with the link can see whether a fingerprint was stamped and when, without trusting LightDrawer. The page shows only the fingerprint and its timestamps, never a file.
  • /?digest=<fingerprint> now redirects to the receipt page. The same lookup is available as JSON.

Notes

  • While a stamp waits to be batched, the page shows its exact received time. After it's sealed into a Certificate Transparency batch, the page says "Stamped no later than" the batch's closing time, because the exact time isn't kept after batching.

LightDrawer 1.1.0

Choose a tag to compare

@desynced desynced released this 10 Nov 17:53

Added

  • An optional API key for trusted servers, so another service can stamp fingerprints without a browser human check. Only a hash of each key is stored. Each key has its own rate limit and can be revoked on its own. Receipts never name the caller, and requests without a key work exactly as before.

Operations

  • HTTP Strict Transport Security (HSTS) turned on, so browsers always use a secure connection.
  • "Always Use HTTPS" turned on, so plain-http links redirect to https.
  • A firewall rate limit added on the stamping endpoint (at most 5 requests per 10 seconds from one address), on top of the Worker's own limits.

Changed

  • Commit history was rewritten once to replace a personal email address in the commit author field with a private GitHub address. The code was unchanged.