mlua-batteries
Batteries-included standard library modules for mlua.
Lua 5.4 scripts gain access to JSON, environment variables, filesystem, HTTP, hashing, LLM chat completion, structured async tasks, and SQLite-backed storage — all behind a configurable policy layer that can sandbox untrusted code.
Core modules (json, env, path, time, fs, http, hash, llm, string, regex, validate, log, uuid, base64, schema, sandbox) are synchronous (blocking) and require no async runtime. The optional task module requires a tokio current-thread runtime driving a LocalSet (see the Async modules section), as do the std.sql / std.kv bridges in the companion mlua-batteries-sqlite crate.
Modules
| Module | Feature flag | Description |
|---|---|---|
json |
json |
JSON encode / decode (serde_json) |
env |
env |
Environment variable access (overlay-safe set) |
path |
path |
Path manipulation (pure computation + absolute) |
time |
time |
Timestamps, sleep, measure |
string |
string |
String utilities beyond Lua's built-ins |
regex |
regex |
Regex match / replace (regex crate) |
validate |
validate |
Lightweight value validation helpers |
log |
log |
Bridge to the host's log facade |
uuid |
uuid |
UUID v4 / v7 generation |
base64 |
base64 |
Base64 encode / decode |
fs |
fs |
File I/O, walk, glob, rename, symlink (Unix) (walkdir + globset) |
http |
http |
HTTP client (ureq) |
hash |
hash |
SHA-256 hashing (sha2) |
llm |
llm |
Chat completion — OpenAI, Anthropic, Ollama |
schema |
schema |
JSON Schema validation (schema-bridge) |
sandbox |
sandbox |
Capability-based filesystem sandbox (cap-std) |
proc |
proc |
Typed argv pipeline spawn — no shell involved |
watch |
watch |
Filesystem versioning watcher — content-addressed store + JSONL journal (notify) |
task |
task |
Structured async tasks with cooperative cancellation (requires tokio) |
std.sql / std.kv moved to the mlua-batteries-sqlite crate in 0.5.0 — see SQLite below.
Default features: json, env, path, time, string, validate.
Enable everything: full.
Quick start
[]
= "0.3"
use *;
let lua = new;
register_all.unwrap;
lua.load.exec.unwrap;
Per-module registration
For integration with mlua-pkg or custom loaders:
for in module_entries
Sandboxing
The default configuration uses Unrestricted policies — Lua scripts can access any file, URL, and env var. For untrusted scripts, use Sandboxed (requires the sandbox feature):
[]
= { = "0.3", = ["full"] }
use *;
use Config;
use Sandboxed;
let lua = new;
let config = builder
.path_policy
.max_walk_depth
.build
.expect;
register_all_with.unwrap;
Policy layers
| Policy | Controls | Built-in options |
|---|---|---|
PathPolicy |
Filesystem access | Unrestricted, Sandboxed (cap-std) |
HttpPolicy |
Outbound URLs | Unrestricted |
EnvPolicy |
Env var read/write | Unrestricted |
LlmPolicy |
LLM provider/model access | Unrestricted |
All policies are trait objects — implement the trait to create custom policies.
LLM module
Built-in providers: OpenAI, Anthropic, Ollama. API keys are read from environment variables (OPENAI_API_KEY, ANTHROPIC_API_KEY).
local resp = std..
print
-- Batch parallel requests
local results = std..
Custom providers can be registered via mlua_batteries::llm::register_provider.
Async modules
task is async-first and requires a tokio current-thread runtime driving a LocalSet. It is not part of the default feature set — opt in explicitly.
[]
= { = "0.5", = ["task"] }
= { = "1", = ["rt", "macros"] }
task provides structured concurrency primitives (spawn, scope, with_timeout, sleep, checkpoint) with cooperative, level-triggered cancellation. with_timeout applies a 3-stage graceful-abort pattern (deadline → drain under grace_ms → hard-abort).
See the module-level rustdoc on src/task/mod.rs for the full API.
SQLite: std.sql / std.kv
The SQLite bridges live in a companion crate, mlua-batteries-sqlite (crates/mlua-batteries-sqlite in this repo). They were part of this crate up to 0.4.0 and moved out in 0.5.0.
[]
= { = "0.5", = ["task"] }
= "0.5" # pick the line matching your rusqlite cluster
The reason for the split is the SQLite stack, not the code. libsqlite3-sys declares links = "sqlite3", so a build graph holds exactly one of its major versions, and cargo enforces that while resolving dependencies — meaning no crate can offer several clusters behind mutually exclusive features. Serving more than one cluster requires more than one published version line. Keeping that constraint on the small bridge crate leaves this crate's version line free for its own features, and leaves consumers who do not need SQLite free of a C library.
The companion crate's README carries the cluster table and the wiring contract.
Configuration
Config::builder() exposes all tunable limits:
| Setting | Default | Description |
|---|---|---|
max_walk_depth |
256 | Max directory depth for fs.walk |
max_walk_entries |
10,000 | Max entries from fs.walk / fs.glob |
max_json_depth |
128 | Max nesting depth for JSON |
http_timeout |
30s | Default HTTP request timeout |
max_response_bytes |
10 MiB | Max HTTP response body size |
max_sleep_secs |
86,400 | Max time.sleep duration |
llm_default_timeout_secs |
120 | Default LLM request timeout |
llm_max_response_bytes |
10 MiB | Max LLM response body size |
llm_max_batch_concurrency |
8 | Max threads for llm.batch |
Platform support
Unix only (Linux, macOS). Windows is not a supported target.
All path arguments are UTF-8. Non-UTF-8 Lua strings are rejected at the FromLua boundary.
MSRV
Rust 1.77 or later.
Contributing
Bug reports and feature requests are welcome — please open an issue. Pull requests are also appreciated.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT License (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.