swift-typesafe

Checked, not fully reviewed. It needs Swift 6.4, and the package supports Linux through its AsyncHTTPClient trait, so we built and ran it there rather than only reading it. No Jev calls.

It is a port of TypeSafe’s Python SDK 0.7.2, which it vendors and pins; UPSTREAM.md records the exact Python and JS commits it was checked against. The Swift side is the @QuestionSet macro: a struct of @Choice, @Noul and @Score properties becomes a request whose answers come back as those types, and a result builder does the same ad hoc. Its README says retries follow upstream — 408, 429 and 5xx, honouring Retry-After; we did not exercise them. All 66 tests pass on Linux once python3 is installed for the HTTP tests’ helper server; without it, five fail, which was our image and not the package.

Against a stand-in the example decoded every answer and read /v1/models in TypeSafe’s shape. An answer naming a choice outside the enum is rejected with Invalid response data at 'answers.category.choice' rather than decoded into something wrong.

The finding is order. Choice criteria are a Swift Dictionary throughout the public API, so options go out unordered and reshuffle per process: five runs of the example sent its billing, technical, other enum in two different orders, neither of them the declared one. Jev’s answer can change with option order, and the Python SDK this ports keeps the order you wrote. We reported it. MIT, 16 stars.

See how it compares with other tools in Best Jev tools, tested hands-on.

Review updated Oct 4, 2026. Numbers quoted from the project are its author's own; we don't publish our own measurements of Jev.