Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Webauthn Emulator Laravel Package

pronin/webauthn-emulator

A PHP library that emulates WebAuthn authenticators for testing: generate attestation and assertion responses, simulate security keys, and exercise registration and login flows in Laravel and plain PHP test suites without hardware.

View on GitHub
Deep Wiki
Context7

Product Decisions This Supports

  • Passwordless / passkey roadmap feasibility. This library lets the team exercise real WebAuthn registration and authentication ceremonies from PHP, so you can validate that your relying-party implementation (challenge issuance, credential storage, attestation parsing, signature-counter handling, UV/UP flags) actually works before committing passkey support to the roadmap.
  • Test strategy and cost of quality. It replaces a rack of physical YubiKeys and manual Touch ID/Face ID/Windows Hello QA passes with deterministic, scriptable authenticator emulation inside PHPUnit. That directly informs the decision of whether passkey features can ship behind automated CI gates or need a manual device lab.
  • Build vs. buy on test tooling. Because it is a small MIT library, the realistic alternative is an internal emulator or a browser-driven approach. Use it to size the effort: if it covers most of your flows in a one-sprint spike, buy/borrow; if it leaves large gaps, budget for browser-level virtual authenticators instead.
  • Scope and edge-case prioritization. Emulators can be configured to vary authenticator behavior (attestation formats, counter behavior, user-verification presence), which helps the team decide which authenticator classes and failure modes are in scope for v1 versus later.
  • Integration surface discovery. Standing it up against your Laravel auth stack surfaces exactly which application layers need to change (routes, user model, credential model, session re-auth), improving estimation on the passkey epic.

When to Consider This Package

  • You are implementing or maintaining server-side WebAuthn/FIDO2 in PHP or Laravel and want automated coverage of registration and login ceremonies without hardware.
  • Your team already lives in PHPUnit/Pest and you want passkey tests to run in the same CI pipeline as everything else, with no browser or OS dependency.
  • You need to simulate many authenticator types or malformed/edge-case responses faster than manual QA allows.

Look elsewhere or treat with caution when:

  • Browser or platform behavior is the risk. This emulates the authenticator, not the browser, OS biometric prompt, or client-side navigator.credentials flow. For end-to-end coverage, the Chrome DevTools Protocol virtual authenticator (via Playwright/Puppeteer) is the stronger fit and worth comparing in the same spike.
  • Maturity matters. Five stars, zero dependents, and a single maintainer mean high bus-factor risk. It is acceptable as a test-only dependency you can fork (MIT), not something to build a strategy around unexamined.
  • You need real attestation trust. Emulated attestation will not validate against the FIDO Metadata Service or a production attestation policy. Device-lab testing is still required for those requirements.
  • You are not on PHP. If the backend is Node, Go, or Python, the value proposition largely disappears.

Recommended adoption shape: pin the version, confine it to require-dev, timebox a one-sprint evaluation against your real auth flow, and pre-agree a fallback to CDP virtual authenticators if coverage gaps appear.

How to Pitch It (Stakeholders)

For executives: This is a small, free, MIT-licensed development-time library that de-risks our passkey/passwordless plans. It lets us test biometric and security-key login flows automatically in CI instead of buying hardware and running manual QA cycles. It carries no production dependency and no customer exposure — the commitment is one evaluation sprint, and the downside if it does not fit is a few days of engineering time.

For engineering: It is a PHP authenticator emulator — we can script WebAuthn registration and authentication, including attestation and signature-counter behavior, directly in our existing test suite. It ships nothing to production, fits PHPUnit, and being MIT and small we can fork it if the maintainer goes quiet. Known gap: it does not cover browser or OS-level behavior, so we should pair it with Playwright/CDP virtual authenticators for end-to-end coverage and keep a device lab only for real attestation validation.

Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib
tacticmedia/scim-server-bundle
neika-ai/symfony-bundle
mattleads/agent-publishing-bundle
glavweb/framework-bundle