Repositories
Everything Is Public - Here Is Where to Look
Apps, SDKs and tooling are published on GitHub under AGPLv3. This page maps each repository to the problem it solves, so you can go straight to the one you need instead of browsing an organisation.
Applications
Complete, shipping applications. Usually the fastest way to understand how something is done, because they show real usage rather than an isolated snippet.
Seedkeeper-Manager-iOS
The native iOS management app for Seedkeeper PRO.
Read it for: NFC session lifecycle on iOS, PIN entry flows, credential enumeration, OTP management, and how the Apple entitlements and Info.plist declarations are set up.
Seedkeeper-flutter
The Flutter application covering Android, Windows, macOS and Linux from a single codebase.
Read it for: cross-platform structure, how the same operations are expressed over NFC and over a contact reader, and desktop smartcard handling.
Tooling
seedkeeper-manager
Python library and command line tool for configuring the FIDO2 and OTP applets.
Read it for: provisioning, automation, scripted PIN and credential management, and reading authenticatorGetInfo from a device you hold. Full context in Python Library and CLI.
Mobile SDKs
Forks of the Yubico Mobile SDKs, adapted for this device's applets and transports.
yubikit-ios
iOS SDK: NFC transport, smartcard connection handling, CTAP2 layer.
yubikit-android
Android SDK, same scope.
Both are covered in Mobile SDKs. If you have used the Yubico SDKs, the API will be familiar.
Which One Do I Need?
| Problem | Repository |
|---|---|
| Accept passkeys on my website | None - see WebAuthn Quickstart |
| Provision devices before distribution | seedkeeper-manager |
| Script PIN or credential setup | seedkeeper-manager |
| Build an iOS app that manages the device | yubikit-ios + Seedkeeper-Manager-iOS |
| Build an Android app that manages the device | yubikit-android + Seedkeeper-flutter |
| Support desktop as well as mobile | Seedkeeper-flutter |
| Verify a capability claim | Any of them - it is all readable |
About the Licence
Everything is AGPLv3. Two consequences worth understanding before you build on it.
You can read and verify everything. Any claim in this documentation - the extensions supported, the storage limits, what happens on a reset - can be checked against the source rather than trusted. That is the whole argument for open-source security, and it only holds if the source is genuinely there.
AGPL is copyleft, including over a network. If you distribute a derivative work, or make one available as a network service, the AGPL requires you to publish your modifications under the same licence. Consider that before forking for a commercial product, and get advice if your situation is not obvious.
Using the device, or integrating with it over standard WebAuthn, carries no licensing obligation at all. WebAuthn is a standard, not our code.
Reporting a Security Issue
Open an issue for a bug. For a security vulnerability, use the repository's private reporting channel rather than a public issue, so a fix can ship before the details do.
FAQ
Is Seedkeeper open source?
Yes, everything is published under AGPLv3 - the applications, the mobile SDKs and the Python tooling.
Which repository do I need to accept passkeys on my site?
None. Standard WebAuthn is sufficient, and your code never communicates with the device directly.
Are the mobile SDKs forks of Yubico's?
Yes, adapted for this device's applets and transports. Experience with the Yubico Mobile SDKs transfers directly.
Can I fork Seedkeeper code for a commercial product?
The AGPL permits it, provided you publish your modifications under the same licence - including when the derivative work is offered as a network service. Take advice if your case is unclear.
How do I verify a claim in this documentation?
Read the source, or read authenticatorGetInfo from a device you hold. Both are authoritative in a way documentation is not.