Skip to content

SDKs

szl-python and szl-ts are planned unified client interfaces. They are not published package releases in this documentation snapshot. Do not run an install command for a package name until its exact registry version, integrity, source revision, and release provenance are published.

What is available today

NeedSupported pathEvidence boundary
Lean source/proof reproductionClone the pinned lutar-lean source snapshotSource contract, not runtime evidence.
a11oy developmentClone/build the a11oy source workspaceSource-local; public readiness currently unavailable.
killinchu public readinessGET /api/killinchu/healthz after checking /statusHTTP 200 observed on 2026-08-11 only.
Receipt integrityRecompute the documented hash/self-digest when bytes are availableIntegrity is not signer authentication.

The standalone Provenance Anchor, Operator, and Policy roles remain roadmap/not deployed. Their names are not registry-package or cloneable-repository promises in this page.

Planned clients

SDKStateInstallation rule
szl-pythonPlannedNo PyPI command is published.
szl-tsPlannedNo npm/pnpm command is published.
Agentic Mesh SDKRoadmapNo JavaScript, Python, or Go registry package is published.

See Python, TypeScript, and Source-local packages. Current runtime availability belongs on /status, not in an SDK package claim.

Public claims link to source and evidence. SLSA L1 is the current stated supply-chain posture.