Skip to content

TScert v0.5

Choose a tag to compare

@cristianoc cristianoc released this 31 Oct 00:35
· 801 commits to main since this release

v0.5 is TScert's first tagged release, at commit 945fa802: a research verifier
for type safety of TypeScript functions. TScert accepts a function when its
certificate passes a checker whose soundness is proved in Lean.

The version number marks a coverage threshold: v0.N requires at least N×10% of
the named top-level function declarations with bodies in tools/, TScert's own
front end, to verify in the census on main. v0.5 meets the 50% threshold.

The census of 945fa802, measured on 2026-10-30 with a 300 s stage limit,
verifies 351 of 637 functions (55.1%). Within those function bodies, 3,300
of 15,319 counted statements are covered (21.5%); the
coverage definition
states what is counted.

What acceptance guarantees

For inputs meeting their types and a heap meeting its storage contracts, an
accepted function's translation into the calculus does not get stuck or return a
value outside its result type. It may throw or run forever. The acceptance
theorem,
SourceClaimJson.checkJson_safe,
establishes this guarantee for successful checking.

The guarantee relies on source translation and annotation interpretation,
library and host contracts, conforming inputs, and the trusted tools and runtime
assumptions listed in the
trust surface.

Scope

The supported subset includes control flow, objects, arrays, classes, closures
and generic functions; the
README
outlines it. Async support covers await of promises of primitives through
trusted intrinsic contracts;
the proof does not establish JavaScript async entry and resumption semantics.

The
fragment boundary
describes source restrictions. An unverified result means that search or
checking has not established the required derivation. The
work ledger
tracks remaining verification work.

Try it

Follow the
setup instructions,
then check the included example:

make check FILE=pipeline/examples/array-last-element.ts