Skip to content

v0.94

Latest

Choose a tag to compare

@cristianoc cristianoc released this 04 Nov 09:00
· 421 commits to main since this release

TScert is a research verifier for type claims about TypeScript functions. A function is accepted only with a certificate that passes an independent checker whose soundness is proved in Lean.

v0.94: 643 of 686 functions of tools/ verify (93.7%), against 628 of 684 (91.8%) at v0.9. Counted statement coverage is separately 10,097 of 17,790 (56.8%). None of v0.9's verified functions is lost, and 15 are gained.

The measurement is the census of ae20a6c6, the tagged commit, taken on 2026-11-04 with a 1,800-second stage limit and a 4 GiB memory limit per stage. The metric changed with this release.

  • v0.94, shallow function coverage: each module is checked once, unit by unit. A function counts as verified when its own unit (the function, a group of functions that reach each other, or the initialization) is accepted, with what it calls read at its stated signature.
  • v0.9: each function was sliced into its own file with the bodies of the same-file functions it calls.

Unsupported, unverified and timed-out functions remain in the denominator. See the function and release metric and work ledger.

Changes:

  • Per-unit acceptance. One acceptance path and one headline theorem, checkUnitJson_safe: a unit's accepted verdict gives safety for every function of that unit. A file is read once into one shared front, and its evidence is written and checked one unit at a time. A full census of tools/ takes about 15 minutes with each stage under 4 GiB.
  • Omission. A refused function, with its recursive group, or a refused top-level statement, is omitted, and the rest of its file is checked without it. A constant holding only functions with written signatures is read at its signature.
  • Library support: Math.abs, Object.freeze of a fresh object literal, generic overloaded declarations, a program's own overloaded functions checked at each overload, and o[n.toString()] read as o[n].
  • ReScript. These support the experimental TypeScript backend of the ReScript compiler (rescript-lang/rescript#9211 and #9213).
  • Re-exports are read as module declarations that run nothing.
  • Documentation. Each top-level document states its subject once, as it currently is.

The supported fragment, audited host boundaries and the trust surface remain explicit.