Menu / packages / valet

valetas of 5.1.0 · `246baf6b`

What it serves, where

Capability	iOS	macOS	watchOS	tvOS	visionOS	Linux	Catalyst
Keychain storage	✓ serves it · confidence 0.90 · as of 5.1.0 `Valet` Sources/Valet/Valet.swift:21 View the line on GitHub → Core class, doc: 'Reads and writes keychain elements.' Unconditional, no platform gaps. `Valet.setObject` Sources/Valet/Valet.swift:248 View the line on GitHub → Keychain write API, present on all platforms per surface digest. `Valet.object` Sources/Valet/Valet.swift:270 View the line on GitHub → Keychain read API, present on all platforms per surface digest.	✓ serves it · confidence 0.90 · as of 5.1.0 `Valet` Sources/Valet/Valet.swift:21 View the line on GitHub → Core class, unconditional, no platform gaps. `Valet.setObject` Sources/Valet/Valet.swift:248 View the line on GitHub → Keychain write API, present on all platforms per surface digest. `Valet.migrateObjectsFromPreCatalina` `#if os(macOS)` Sources/Valet/Valet.swift:525 View the line on GitHub → macOS-only keychain migration API corroborates first-class macOS keychain support.	✓ serves it · confidence 0.90 · as of 5.1.0 `Valet` Sources/Valet/Valet.swift:21 View the line on GitHub → Core class, unconditional, no platform gaps. `Valet.setObject` Sources/Valet/Valet.swift:248 View the line on GitHub → Keychain write API, present on all platforms per surface digest. Package.swift:11 View the line on GitHub → Manifest declares .watchOS(.v4).	✓ serves it · confidence 0.90 · as of 5.1.0 `Valet` Sources/Valet/Valet.swift:21 View the line on GitHub → Core class, unconditional, no platform gaps. Secure Enclave variants are tvOS-gapped, but plain Valet keychain access is not. `Valet.setObject` Sources/Valet/Valet.swift:248 View the line on GitHub → Keychain write API, present on all platforms per surface digest. Package.swift:10 View the line on GitHub → Manifest declares .tvOS(.v12).	✓ serves it · confidence 0.80 · as of 5.1.0 `Valet` Sources/Valet/Valet.swift:21 View the line on GitHub → Core class resolves PRESENT on visionOS (no gap). The extractor models visionOS explicitly (conditional decls elsewhere list it), so absence of a gap here is meaningful. `Valet.setObject` Sources/Valet/Valet.swift:248 View the line on GitHub → Keychain write API, present on all platforms per surface digest. Package.swift:8 View the line on GitHub → No visionOS floor declared in Package.swift; confidence lowered accordingly.	? not verified yet · confidence 0.20 · as of 5.1.0 Package.swift:8 View the line on GitHub → Linux is not declared in the manifest (not absence evidence per rules). Core decls carry no os() guards so they resolve textually present on linux, but the Keychain depends on Apple's Security framework and Swift-parse extraction cannot establish Linux compilability. No guard/availability evidence of absence exists, so status stays unknown.	✓ serves it · confidence 0.85 · as of 5.1.0 `Valet` Sources/Valet/Valet.swift:21 View the line on GitHub → Core class resolves PRESENT on macCatalyst (no gap); Catalyst builds from the unguarded iOS surface. `Valet.setObject` Sources/Valet/Valet.swift:248 View the line on GitHub → Keychain write API, present on all platforms per surface digest. Package.swift:9 View the line on GitHub → No explicit macCatalyst floor; iOS 12 floor covers Catalyst builds.

✓ serves it · ◐ with conditions · ✕ not served (proven) · ? not verified yet — hover any verdict for the receipt, click to pin it

Notes

Keychain storage: Core capability of the package. Extraction blind spot: 2 ObjC files unparsed (Swift-only extraction), so confidence is held below the 0.95 cap. SecureEnclaveValet/SinglePromptSecureEnclaveValet variants carry tvOS/watchOS gaps, but plain Valet keychain read/write is unconditional across the surface.

Badges for your README

Maintainer of valet? These are yours — verified claims, linked to the receipts. Wrong verdict? That's a fix we want; see contribute.

valetas of 5.1.0 · 246baf6b

What it serves, where

Notes

Badges for your README

valetas of 5.1.0 · `246baf6b`