Datasette's 1.0 push lands sandbox runtime and stored-query advisory in one tag
Every URL the pipeline pulled into ranking for this issue — primary sources plus the supporting and contradicting findings each Researcher returned. Inline citations in the issue point back here.
Sources
datasette 1.0a43 simonwillison.net
Release: datasette 1.0a43 I’ve been leaning hard into Claude Fable 5.2 to help knock things off the 1.0 milestone , which is now 53% complete. The biggest 1.0 item in this release is streaming support for output renderers - the built-in TSV and CSV export mechanisms now use this as well, and plugins can register themselves as capable of streaming every row in a table in one go via the new Response.stream() method. There are a couple of security fixes, one of which I deemed deserving of a GitHub…
datasette 0.65.6 simonwillison.net
Release: datasette 0.65.6 I backported a minor security fix from 1.0a43: Fixed a security issue where a database registered using add_database(db, name=…, route=…) with a route that differs from its name could be downloaded from /
.db by actors who were denied access to it. […] Tags: security , datasette
datasette-agent 0.6a0 simonwillison.net
Release: datasette-agent 0.6a0 Accumulated small fixes for Datasette Agent, my agent plugin for Datasette that lets you ask questions about your data. Most notably, it now adds an agent prompt directly to the Datasette homepage, with support for hash-mentions of tables and queries: Tags: datasette-agent , llm , datasette , llms , ai , generative-ai
datasette-apps 0.4a0 simonwillison.net
Release: datasette-apps 0.4a0 Datasette Apps are sandboxed HTML and JavaScript applications that live inside Datasette - think Claude Artifacts, but these ones can run SQL queries against your data. 0.4a0 adds support for linking: you can link to an app with #fragments in the URL and the app can see and use those, plus supported URL schemes are reported back to Datasette Agent so it can help write apps that link to each other. This means you can have e.g. an app that shows details about a speci…
datasette-maplibre 0.1a0 simonwillison.net
Release: datasette-maplibre 0.1a0 The first new Datasette geospatial plugin in quite a while! This one combines the excellent MapLibre GL library with OpenFreeMap , the free vector map server operated by Zsolt Ero (you should sponsor Zsolt on GitHub .) I built most of this with a single prompt to Claude Fable 5.2: Look at datasette-cluster-map and datasette-leaflet-geojson plugins, then look at ~/dev/tools/openfreemap-demo.html - then build a brand new Datasette plugin that uses maplibreGL and…
References
Datasette official documentation docs.datasette.io
Response.stream() lets plugins register as capable of streaming every row in a table in one go, which the built-in CSV and TSV exporters now use to avoid memory bottlenecks on large exports.
Simon Willison — ‘Introducing Datasette Apps’ (June 2026) simonwillison.net
Datasette Apps hosts sandboxed HTML/JS inside iframes with a restrictive Content Security Policy, exposing a datasette.query() JavaScript API for read-only SQL — effectively turning the server into a backend-as-a-service for small, ‘baked data’ applications.
datasette/datasette-apps GitHub repository github.com
Apps run inside iframes with sandbox=“allow-scripts allow-forms” and are prevented from accessing host cookies or storage; network egress is blocked by default via CSP, enabling multi-tenant hosting of untrusted apps within a shared Datasette instance.
Simon Willison monthly newsletter (Oct 2025) simonwillison.net
Agentic coding with Claude Code and Codex has changed what counts as a ‘reasonable’ plugin to build — small ideas that were previously too small to justify the overhead are now worth doing in an afternoon.
newly.app — ‘Vibe Coding Limitations’ newly.app
Statistical analyses suggest 40–62% of AI-generated code contains security vulnerabilities such as XSS, and ‘vibe debugging’ can turn a two-hour feature into twenty days of remediation.
codeculture.store — ‘Is Vibe Coding Bad?’ codeculture.store
Cognitive debt accumulates when maintainers must reason about systems they didn’t personally author; the risk is not the code itself but the loss of long-term architectural understanding.