SDKsVolume 1 · v0.1.0

Four SDKs.
One contract.

Rust, TypeScript, Python, and Go. All generated from the same OpenAPI spec. Identical feature surface. Identical retry semantics. Identical telemetry hooks. Choose your stack — get the same Zaps.

01Language matrixStatus · install · registry · repo
Rs
Rust
v0.1.0 · released 2026-04-08
GA
Ts
TypeScript
v0.1.0 · released 2026-04-08
GA
Py
Python
v0.1.0 · released 2026-04-08
GA
Go
Go
v0.1.0 · released 2026-04-08
GA

Last published: 2026-04-08 · Next release window: 2026-04-22 · Owner: @l1feai/zaps-devrel

02Feature parityIdentical surface across all four SDKs
API key auth
Ru
Ty
Py
Go
OAuth 2.0 client credentials
Ru
Ty
Py
Go
JWT bearer
Ru
Ty
Py
Go
mTLS
Ru
Ty
Py
Go
Server-Sent Events / streaming
Ru
Ty
Py
Go
Auto retries · exp backoff + jitter
Ru
Ty
Py
Go
Rate-limit headers + auto throttle
Ru
Ty
Py
Go
Cursor pagination
Ru
Ty
Py
Go
Auto-pagination iterators
Ru
Ty
Py
Go
Webhook signature verification
Ru
Ty
Py
Go
Multipart upload
Ru
Ty
Py
Go
Async / concurrent requests
Ru
Ty
Py
Go
Custom HTTP client / proxy
Ru
Ty
Py
Go
Fully-typed models
Ru
Ty
Py
Go
OpenTelemetry hooks
Ru
Ty
Py
Go
Request/response middleware
Ru
Ty
Py
Go
Idempotency key support
Ru
Ty
Py
Go

Source of truth · regenerated in CI on every release · owner @l1feai/zaps-devrel

03Security & complianceSigned, scanned, audited
In progress · ETA Q3 2026

SOC 2 Type II

Trust report and current control mapping available on request. Email security@l1fe.ai.

Sigstore · cosign-verifiable

Package signing

Every published artifact (cargo, npm, PyPI, pkg.go.dev) is signed and verifiable with cosign.

Hermetic CI builds

SLSA Level 3

All SDK builds run on isolated GitHub Actions runners with SLSA L3 provenance attestation.

SPDX 2.3 · per-release

SBOM

A complete SBOM ships with every SDK release at github.com/l1feai/zaps/releases.

Snyk + Dependabot

Dependency scanning

Critical CVEs block merge. High-severity findings ship a patch within one business day.

security.txt + bounty

Responsible disclosure

Email security@l1fe.ai or report via the program at hackerone.com/l1feai.

04Support & SLAWhat happens when something breaks

Issues are filed at github.com/l1feai/zaps/issues. Enterprise customers get a dedicated Slack channel and a named support engineer with response-time commitments below.

Response SLABolt + above
Sev-1SDK broken on stable language version, or causes data corruptionWithin 4 business hours
Sev-2Documented feature does not work as specifiedWithin 1 business day
Sev-3Non-blocking bug or quality regressionWithin 5 business days
Sev-4Improvements, suggestions, polishTriaged weekly