Changelog

What we shipped

Releases, launches, and milestones for the Zansn assurance toolkit. The open-source packages are the developer entry point to the broader assurance control plane.

  1. Release

    Framework adapters: LangChain and OpenAI Agents

    Two more drop-in adapters that turn an agent run in a popular framework into a portable Zansn evidence pack.

    • @zansn/langchain: a LangChain BaseCallbackHandler that records tool calls, usage, and spans; finalize() returns an evidence pack.
    • @zansn/openai-agents: fromRunResult() turns a completed Agents SDK run into an evidence pack in one call.
    • Both reuse the local zansn assurance engine (policy, privacy, cost, latency, readiness) with no new logic, and ship as peer-dependency-only packages.
    @zansn/langchain@zansn/openai-agents
  2. Release

    Vercel AI SDK adapter

    The first framework adapter: capture a Vercel AI SDK run as a Zansn evidence pack with one hook.

    • @zansn/ai-sdk: createZansnCollector().onStepFinish captures the AI SDK per-step trail; finalize() seals the evidence pack.
    • Maps AI SDK step, tool-call, tool-result, and usage shapes to Zansn types; usage field names line up exactly.
    • Includes a runnable example and a pull-request-gate GitHub Action recipe.
    @zansn/ai-sdk
  3. Launch

    zansn: the open-source developer starter kit

    The local-first entry point to Zansn assurance is live on npm. Run an agent workflow, get a reviewable evidence pack.

    • Local evaluation runner with task, scorer, trace, finding, policy, and readiness types.
    • Tool allow/block policy checks, configurable sensitive-data pattern checks, and cost and latency checks.
    • JSON and Markdown evidence-pack exporters, pack validation, and OpenTelemetry-compatible attribute mapping.
    • Runs locally with no account; produces portable evidence that later ingests into hosted Zansn.
    npm: zansn

Follow along at npm.