§ CHANGELOG
What's new in Execlave
Governance policy types, SIEM exporters, SDK releases, and platform hardening — the latest changes to the Execlave AI agent governance platform.
- July 2026sdk-js / sdk-python v1.6.0
Stronger enforcement, broader prompt-injection coverage, and signed compliance reports
- ▸Prompt-injection detection now covers encoded payloads (base64, hex, leetspeak, reversed text), cross-script look-alike characters, and non-Latin languages including Chinese, Japanese, Korean, Hindi, and Arabic — plus system-prompt-extraction attempts and attacks split across multiple conversation turns.
- ▸Kill-switch and fail-closed behavior hardened: a paused agent stops immediately, and 'fail closed' now blocks on the very first enforcement outage as documented.
- ▸Framework adapters (LangChain, OpenAI Agents) now enforce policy on direct model calls and agent input, not only wrapped chains — closing gaps on the most common integration paths.
- ▸New SDK APIs: scan a tool's output before it reaches the model (enforceToolOutput / enforce_tool_output), and pass conversation history for multi-turn injection scanning.
- ▸Compliance reports are now digitally signed (RSA-SHA256-PSS) and carry an enforcement-decision summary — allowed and blocked counts, not just violations — so coverage is provable to an auditor.
- ▸Opt-in redaction of PII in stored trace payloads, and clearer, more reliable AI policy generation from plain English.
- ▸Upgrade note: the SDK enforcement call now rejects unknown fields with a clear error instead of ignoring them — use the documented option names.
- July 2026sdk-js / sdk-python v1.5.0
Approval certificates now bind to the full request, not a hand-picked field list
- ▸The OpenAI Chat adapter sealed only { model, messages } into the approval certificate's digest — tools, tool_choice, temperature, and response_format could drift from what a human approved without invalidating the certificate. It now seals the full request.
- ▸Fixed a serialization gap shared by both SDKs: one non-serializable field anywhere in a payload used to collapse the entire sealed value to a placeholder, silently making certificate verification a no-op for everything else in it. Now isolated per field instead.
- ▸CrewAI's Python integration previously enforced tool-call policy with no sealed metadata at all — brought in line with every other adapter.
- ▸A new structural test blocks any adapter from hand-picking fields into a certificate's sealed metadata going forward.
- June 2026i18n · security
Execlave is now available in German
- ▸The full product — every marketing page and the entire dashboard — is now localized in German (de), with locale-aware routing and hreflang alternates for search.
- ▸Approval and violation history now preserves a policy's name after it is deleted, so audit trails stay readable after cleanup.
- ▸Richer search presence: JSON-LD structured data, x-default / hreflang alternates, and on-page FAQs across key pages.
- ▸Security hardening: next-intl upgraded to v4, plus nodemailer and form-data CVE patches.
- June 2026
SIEM exporters + compliance PDF export
- ▸New OpenTelemetry (OTLP), Splunk HEC, and Microsoft Sentinel trace exporters — stream every agent trace to your SIEM, off the enforcement path.
- ▸SIEM credentials are envelope-encrypted (AES-256-GCM) at rest, never stored as plaintext.
- ▸Compliance evidence packages now export as signed PDF, alongside HTML and JSON.
- ▸New public EU AI Act overview mapping Execlave to the high-risk (Annex III) obligations — dated 2 August 2026, with a proposed Omnibus postponement to December 2027.
- June 2026sdk-js / sdk-python v1.4.0 · cli v1.1.0
HMAC request signing + federated policy export
- ▸Optional HMAC request signing across the JS and Python SDKs — replay-safe, opt-in request authentication.
- ▸Signed, portable policy export/verify and a federation export endpoint for multi-environment policy sync.
- ▸Built-in policy types expanded to 19, covering tool integrity, response groundedness, OPA Rego, and agent lineage.
- May–June 2026
Enforcement hardening
- ▸Audit-log atomicity and hash-chain hardening; append-only immutability enforced at the database trigger level.
- ▸Prompt-injection ReDoS guards and a semantic-classifier circuit breaker.
- ▸Approval-workflow TOCTOU fix and per-namespace enforcement rate limiting.
- ▸Multilingual prompt-injection and PII detection across 13 languages.
- May 2026sdk-js / sdk-python v1.2.0
Framework integrations + tool-integrity governance
- ▸SDK integrations for LlamaIndex, MCP, OpenAI, and AutoGen.
- ▸Tool-integrity governance: baseline expected tools and detect drift in agent tool usage.
- ▸Per-evaluator enforcement modes (monitor / warn / require approval / block) with configurable failure modes.
§ DETAILS
Per-package release notes
The SDKs and CLI ship their own versioned CHANGELOGs in the repository; this page summarizes platform-level changes.