mylofi/webauthn-local-client

monitor webcrypto ed25519 support, potentially moving away from libsodium

Open

#19 opened on Dec 15, 2025

View on GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (9 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (179 stars)
PR merge metrics
 (PR metrics pending)

Description

it would be a HUGE win to move away from libsodium (giant size, not ESM capable).

it seems support for ed25519/x25519 keys (import, export, sign, verify) landed "recently" (e.g., chrome 137 6 months ago, firefox 130 14 months ago, safari 17 1-2 years ago).

we're probably nearing the point where we could safely assume to move support for these key curves into native web crypto and basically drop libsodium. would need to verify if the encryption/decryption (used by local-vault) also works in those places, but I assume it does if the key management does.

I think maybe once we pass a full year of chrome support, it's probably safe to make this move.

Contributor guide

Research direction
Check the browser compatibility table for SubtleCrypto.importKey ed25519 support (Chrome, Firefox, Safari). Verify that encryption/decryption functions in local vault use these curves. Set a target date after a full year of Chrome support and evaluate if libsodium can be dropped.
Tech stack
javascript
Domain
securityauthenticationfrontend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitBrowser
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85