Type Safe
Back to home

JEV and TypeSafe Ecosystem Updates | Type Safe

How to follow new listings, verification reviews, corrections, and methodology changes.

Last updated: 2026-10-19

TypeSafe Python SDK 0.7.5

The release adds experimental image and Box support, asset attachment, and default zstd request compression while reorganizing the documentation. Review version boundaries and compatibility notes on the Python SDK 0.7.5 update page.

TypeSafe JavaScript SDK 0.7.0

This breaking release raises the minimum runtime to Node.js 22, adds experimental image and Box support, and changes request compression behavior. Read the migration boundaries and fixes on the JavaScript SDK 0.7.0 update page.

jev-mcp 0.13.0

The historical 0.13.0 release tightened subject-aware contradiction handling and added a bounded deny-only coding-agent hook example. Review the exact behavior and version status on the jev-mcp 0.13.0 update page.

jev-secrets 1.1.0

Review the verified package metadata, Python requirements, and the boundary between reversible pseudonymisation and anonymisation on the jev-secrets 1.1.0 update page.

TypeSafe Python SDK 0.7.2

HTTP/2 support is now available through an optional dependency group. Read the installation commands, compatibility checks, and source notes on the Python SDK 0.7.2 update page.

Follow directory changes

The Type Safe RSS feed publishes available blog articles and the directory update hub. Add it to any RSS reader to follow changes without creating an account.

What counts as a material update

  • A new model, workflow, integration, template, or comparison.
  • A changed access method, license, availability, or verified version.
  • A correction to a factual statement or source.
  • A new reproducible benchmark result.
  • A material change to the editorial or benchmark methodology.

Small spelling and layout fixes may be made without a separate notice. Every catalog detail page carries its own last-verified date.

Request an update

Use the submission form and choose correction. Add the affected resource, a concise explanation, and a first-party source when one exists. The request becomes a private ticket for editorial review.

For account or privacy questions, open a support ticket.