Artifact catalog¶

Start with the recommended mobile or backend setup. Use this catalog when you need to replace a default layer or adopt a lower-level protocol component.

Recommended mobile setup

Use webauthn-client-flow and webauthn-client-ktor-kotlinx in shared code, then webauthn-client-defaults in Android and iOS source sets.

Mobile and client¶

webauthn-client-compose ¶

Compose helpers for lifecycle-aware platform clients and the generic PasskeyFlow API, which owns no product UI state.

webauthn-client-core ¶

Platform-neutral passkey operations and result and error contracts at the raw platform boundary.

webauthn-client-defaults ¶

Batteries-included platform-client composition over the same replaceable seams exposed by the lower-level modules.

webauthn-client-flow ¶

Generic passkey ceremony orchestration over PasskeyClient and application-owned backend contracts, without library-owned product state.

webauthn-client-json-core ¶

JSON interoperability layer on top of raw-response client orchestration.

webauthn-client-ktor ¶

Codec-neutral Ktor transport for the generic webauthn-client-flow backend contracts.

webauthn-client-ktor-kotlinx ¶

Opt-in Kotlinx Serialization implementation of this repository's default /webauthn/* client contract.

webauthn-client-platform ¶

Kotlin Multiplatform platform bridge for passkey operations. Its Android source set uses Credential Manager; its iOS source set uses Authentication Services.

webauthn-client-prf-crypto ¶

Audience: teams implementing client-side encryption flows derived from WebAuthn PRF assertion outputs.

Protocol foundation¶

webauthn-cbor-core ¶

Audience: maintainers and advanced integrators needing strict CBOR byte-scanning primitives shared by parser modules.

webauthn-core ¶

Audience: teams validating WebAuthn ceremonies before cryptographic verification and persistence updates.

webauthn-crypto-api ¶

Contract layer for cryptographic and trust operations used by validation and ceremony services.

webauthn-json-api ¶

Audience: applications and adapters that need a replaceable JSON boundary for WebAuthn ceremony values.

webauthn-json-kotlinx ¶

Serialization and mapping helpers between wire DTOs and typed WebAuthn domain models.

webauthn-model ¶

Audience: teams that need typed WebAuthn values and protocol models as the shared contract between transport, validation, and service layers.

webauthn-protocol ¶

Audience: integrators and adapters that need strict WebAuthn binary protocol interpretation without selecting a JSON or CBOR object codec.

webauthn-runtime-core ¶

Audience: module authors who need consistent coroutine-safe failure handling helpers across client and network adapters.

JVM backend¶

webauthn-attestation-mds ¶

Optional FIDO Metadata Service trust-source integration for attestation verification.

webauthn-server-core-jvm ¶

Typed JVM ceremony services and store contracts for WebAuthn registration and authentication.

webauthn-server-jvm-crypto ¶

Default JVM crypto backend for the server stack.

webauthn-server-ktor ¶

Ktor route adapters for the JVM ceremony services.

webauthn-server-store-exposed ¶

Exposed-backed persistence adapters for server-core store contracts.

Coordinated versions¶

webauthn-bom ¶

This BOM aligns versions across published WebAuthn Kotlin Multiplatform artifacts so mixed-module apps stay on one tested release train.

Release alignment¶

The latest stable coordinated release is v0.4.0. JVM builds can use webauthn-bom; Kotlin Multiplatform source sets must keep explicit artifact versions aligned.