Skip to Content
ZeroLeaksDocs
ZeroLeaks SDK

Changelog

Changes to the ZeroLeaks SDK.

0.5.0

  • Runtime scans contain tool calls by default. Side-effecting tools and calls to hosts outside your allowlist return a simulated result, and the call is still recorded as evidence.
  • Pass containment: false to run tools for real. See tools and side effects.
  • Upgrade with bun add @zeroleaks/sdk@^0.5.0.

0.4.0

  • The optional AI SDK adapter moves to AI SDK 7. It needs ai@^7, and aiSdk() accepts AI SDK 7's runtime-context type.
  • Projects still on AI SDK 6 should stay on 0.3.x.
  • Upgrade with bun add @zeroleaks/sdk@^0.4.0.

0.3.0

  • Adds types for the remaining agent report fields: component findings, the secrets-in-context summary, defense fingerprints, campaign state, and the attack-path search tree.
  • Adds plantedSecret to endpoint configurations.
  • Deprecates scans.create and scans.run. Both methods reject with PROMPT_SCANS_RETIRED because hosted prompt scans are retired.
  • components names its four components instead of using Record<string, unknown>, and boundaryAssurance is typed instead of unknown. Handwritten test reports must include all four components and every required boundaryAssurance field. To cast boundaryAssurance to your own interface, cast through unknown.
  • Upgrade with bun add @zeroleaks/sdk@^0.3.0.

0.2.2

  • The complete production probe catalog is the default for runtime scans.
  • Isolated sessions run concurrently.
  • The SDK detects stalled hosted workers.

On this page