Datasette 1.0a43 fixes leak of private stored query SQL
Original title: datasette 1.0a43
The issue can reveal a private query’s title and SQL but does not allow that query to run.
Simon Willison released datasette 1.0a43 and said the 1.0 milestone is 53% complete. The main 1.0 change is streaming for output renderers, now used by built-in TSV and CSV export and available to plugins through Response.stream(). The release also includes security fixes, including a GitHub advisory for exposure of private stored queries’ titles and SQL without allowing execution.
Unconfirmed: The post is truncated, so the other security fix and remaining changes are not fully described.
- The 1.0 milestone is reported 53% complete.
- Plugins can stream every row via Response.stream().
- Built-in TSV and CSV exports now stream.
- The advisory covers title and SQL, not execution.
- He used Claude Fable 5.2 while working toward 1.0.
Impact: private stored query titles and SQL exposed
| Product | Affected | Fixed in |
|---|---|---|
| datasette | — | 1.0a43 |
- 1.Upgrade to datasette 1.0a43
- Products
- datasette
- AI models
- Claude Fable 5.2
From the original article
Release: datasette 1. 0a43 I've been leaning hard into Claude Fable 5. 2 to help knock things off the 1.
simonwillison.net
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.