open-standards/jouleclaw/jouleclaw-rs
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Transaction Science fc67077fca
All checks were successful
jouleclaw public surface must stay documented / Public-surface audit (jouleclaw-rs) (push) Successful in 1m38s
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (push) Successful in 4m34s
sec: rusqlite 0.41 for RUSTSEC-2026-0459, SQLite reading uninitialised page-cache memory through a sibling -wal
jouleclaw-context-store bundles SQLite through rusqlite 0.32, whose
libsqlite3-sys 0.30.1 carries CVE-2026-119375. SQLite before 3.54.0 can
return uninitialised page-cache memory when it opens a database beside
a -wal file whose page size differs. The patched libsqlite3-sys is
0.39, which rusqlite 0.41 takes.

The store uses Connection, OpenFlags, params and rusqlite::Error, which
rusqlite 0.41 keeps. Its 12 tests pass, its clippy is clean, and the
jouleclaw workspace checks with every target. check-advisories: 67
lockfiles, nothing outside the allow list. The lockfile also moves
hashlink to 0.12 and adds foldhash, and the wasm-only rsqlite-vfs and
sqlite-wasm-rs that rusqlite 0.41 declares.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-11-09 09:08:09 -05:00
..
crates sec: rusqlite 0.41 for RUSTSEC-2026-0459, SQLite reading uninitialised page-cache memory through a sibling -wal 2026-11-09 09:08:09 -05:00
Cargo.lock sec: rusqlite 0.41 for RUSTSEC-2026-0459, SQLite reading uninitialised page-cache memory through a sibling -wal 2026-11-09 09:08:09 -05:00
Cargo.toml Cargo: no minimum-supported-version floor, because the policy is latest stable 2026-11-03 17:42:20 -05:00