awesomejev

Community project / Client libraries and integrations

Jev for Apple Foundation Models

Swift 6 bridge that translates Apple @Generable Boolean, enum, and bounded score fields into one Jev question set, then decodes the typed answers through LanguageModelSession; ships mock-transport tests and two demos, but requires iOS, macOS, or visionOS 27 and an API key kept on a backend or trusted machine rather than in a mobile app.

Open the original resource ↗ See it in the full directory Browse all Client libraries and integrations
Awesome Jev share card for Jev for Apple Foundation Models Download share card

Share this listing

Maintaining this project? Share its link, badge, or image. Listed means included, not endorsed.

Download share card

This is an independent community listing. Check the source, license, data handling, and evaluation caveats before relying on a project. Inclusion is not an endorsement or security review.

Found an outdated or inaccurate detail? Report a correction →

Explore more in Client libraries and integrations

  • jev-acp

    Standalone ACP agent for Jev Choice, Score, and Noul decisions, with guided input, reusable templates, and probability displays; requires a TypeSafe API key and sends decision inputs to TypeSafe.

    Read listing →

  • jevframe

    Early Python library adding async Jev Noul, Choice, Score, and multi-question evaluation to pandas and eager Polars, with full Choice and Score probability distributions, bounded row concurrency, and opt-in memory caching; each uncached row sends selected context to TypeSafe, and LazyFrame expressions are outside v0.

    Read listing →

  • jevql

    psql-shaped CLI and Go/TypeScript/Python SDKs that let you write WHERE jev(alias, 'condition'), jev_prob, jev_choice, and jev_score against a vanilla Postgres with no extension: it runs the plain SQL on the server, judges the surviving rows with Jev in batches (cached in local SQLite), and applies filter, sort, and group in the client; every row that survives the SQL filters is sent to TypeSafe and judged, so put cheap predicates in SQL first.

    Read listing →