You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
[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/.