Security
Passkey sign-in in PHP or Node with no cryptography of our own, bot protection that needs no third party, and a security.txt served from the same registry as your robots.txt. Every piece works behind the same React UI whichever backend runs it.
Passkeys
fancy-passkeys is passkey (WebAuthn) sign-in for PHP and for Node, as thin wrappers over web-auth/webauthn-lib and @simplewebauthn/server. The two share one four-endpoint wire contract, pinned by shared fixtures, so fancy-passkeys-ui works against either.
- Laptop fingerprint
- Security key
Seeded data. Enrolling opens nothing, because a real ceremony needs a gesture this page cannot fake.
Rename a passkey, then revoke one: the revoke is staged until you confirm it, and revoking the last one says it locks you out. An agent driving this list through registerPasskeyBridge can list, rename, open an enrollment prompt and propose a revoke, and nothing else: no tool completes a sign-in ceremony.
What ships today
Each claim is checkable in the packages' READMEs and changelogs.
Passkeys, end to end
Registration and sign-in ceremonies, discoverable (usernameless) credentials, single-use server-side challenges, and clone detection through the signature counter. The Laravel bridge augments Fortify rather than replacing it, so password login, reset and 2FA stay as they are.
No cryptography of our own
Verification is web-auth/webauthn-lib in PHP and @simplewebauthn/server in Node. What the libraries leave to you is what fancy-passkeys owns: challenge issuance, single-use expiry, credential persistence and counter replay detection.
Answers that leak nothing
Since 0.3.0 a response from the wrong origin is refused as origin_not_allowed in PHP and Node alike, decided before the credential is looked up, so the answer is the same whether or not the credential exists.
Optional login certificates
Off by default. Turned on, each sign-in and enrollment yields a canonical record with your own claims and a token both backends compute identically. Known-sensitive claim keys are stripped, and the package stores nothing.
Bot protection without a third party
fancy-captcha checks a form behind one Verifier contract. Its built-in mode needs no keys and no network: a honeypot, a signed render time and, when enabled, a single-use proof-of-work. Turnstile, reCAPTCHA and hCaptcha drivers talk plain HTTP with no SDK, and a configured provider fails closed.
security.txt from one registry
fancy-x-files serves security.txt (RFC 9116) in Laravel from the same declarative registry as robots.txt, humans.txt, llms.txt and the sitemap, and its protect() guard keeps private paths disallowed for every bot group. The Node port has the same model, builders and validators, and fancy-x-files-ui is an editor for each file with a live preview.
Bot protection for forms
fancy-captcha-ui is one React component for every fancy-captcha driver. It takes anything with allows(category), which fancy-compliance-ui's useConsent() returns, so a third-party captcha can wait for consent.
Send within three seconds of loading the page and the signed timing refuses it; wait, and it passes. The honeypot is hidden from keyboards and screen readers (aria-hidden, inert, tabindex -1). An agent may read the status attributes, and nothing lets it solve the check.
What these packages do not do
fancy-passkeys completes a ceremony only with the person present: no agent tool can sign in or enroll for them. Turnstile, reCAPTCHA and hCaptcha render their own widgets, with their own accessibility; the built-in captcha mode is the one held to AAA. Rate limits stay yours. Consent lives on the Compliance feature.
How it fits
Passkeys and security.txt each ship as a PHP and Node pair with one React UI; the captcha is a Laravel package and a React component.
Human+ bridge
An agent drives this surface over MCP, through the same state a person sees, never the DOM.
import { registerPasskeyBridge } from "@particle-academy/agent-integrations/bridges/passkeys";tools: passkey_*
Install
composer require particle-academy/fancy-passkeysnpm install @particle-academy/fancy-passkeysnpm install @particle-academy/fancy-passkeys-uicomposer require particle-academy/fancy-captchanpm install @particle-academy/fancy-captcha-uicomposer require particle-academy/fancy-x-filesnpm install @particle-academy/fancy-x-filesnpm install @particle-academy/fancy-x-files-uicomposer require particle-academy/fancy-service-tokennpm install @particle-academy/fancy-service-tokenpip install fancy-service-tokenpip install fancy-http-guardnpm install @particle-academy/fancy-http-errors
The packages
Passkey (WebAuthn) login for PHP — registration + authentication ceremonies, discoverable (usernameless) credentials, single-use server-side challenges, clone detection via the signature counter, and a Laravel bridge that augments Fortify rather than replacing it. A thin wrapper over web-auth/webauthn-lib: no cryptography of our own. Headless; pairs with @particle-academy/fancy-passkeys-ui.
Node/TS mirror of particle-academy/fancy-passkeys — the same four-endpoint wire contract, byte-compatible options payloads (pinned by shared fixtures), and the same challenge / counter / redaction policy, so one React UI works against either backend. Wraps @simplewebauthn/server. Headless; framework-free with a dependency-free HTTP adapter.
React surfaces for passkey (WebAuthn) sign-in and passkey management, plus a React-free /client subpath carrying the browser half of both ceremonies. Controlled, JSON-serializable, agent-bridgeable — and deliberately not agent-completable: no prop, export or MCP tool finishes a ceremony, because that needs a gesture and a biometric only the human has. Pairs with particle-academy/fancy-passkeys (PHP) or @particle-academy/fancy-passkeys (Node).
Bot protection for Laravel forms behind one Verifier contract: a built-in mode (honeypot, signed render time, optional single-use proof-of-work) with no keys and no network, plus Turnstile, reCAPTCHA and hCaptcha drivers over plain HTTP, no SDKs. Fails closed once configured. Pairs with @particle-academy/fancy-captcha-ui.
One React captcha component for every fancy-captcha driver, built from react-fancy: built-in mode by default, Turnstile, reCAPTCHA v2/v3 and hCaptcha scripts loaded lazily, proof-of-work in a Web Worker, single-use tokens reset on submit. Pairs with particle-academy/fancy-captcha.
Well-known + agent-facing files for Laravel from one declarative registry — robots.txt, security.txt (RFC 9116), humans.txt, llms.txt, sitemap.xml, AGENTS — with a protect() guard that keeps private paths Disallowed for EVERY bot group (no per-bot leak).
Node/TS port of fancy-x-files — the same robots / security.txt / humans / llms / sitemap model, builders, and validators, isomorphic (browser or Node). Headless; no UI.
react-fancy editor suite for the well-known + agent-facing files — controlled, JSON-friendly editors for robots.txt / security.txt / llms.txt / humans.txt / sitemap.xml / AGENTS, each with a live preview, plus a combined XFilesManager. Pairs with particle-academy/fancy-x-files (PHP) / @particle-academy/fancy-x-files (Node).
Service tokens from a Laravel app to its Python or Node sidecar: a short-lived HMAC-SHA256 token (audience, issuer, expiry, the caller's request id, a nonce) on every outgoing request via Http::withServiceToken(), plus a verifier held to the same shared fixtures. Standard library only, no JWT library. Pairs with fancy-service-token (PyPI) and @particle-academy/fancy-service-token.
Verify Fancy service tokens in a Node sidecar: the same fst1 verifier as the Python leg, with a connect-style middleware that refuses before the body is read. node:crypto only, zero runtime dependencies. Pairs with particle-academy/fancy-service-token.
Verify Fancy service tokens in a Python sidecar: a framework-free verifier plus ASGI middleware for Starlette and FastAPI that refuses a request before its body is read and hands the verified request id to handlers and logs. Standard library only. Pairs with particle-academy/fancy-service-token.
Request guards for Starlette and FastAPI, checked before the body is parsed: body size, list length and nesting depth, finite numbers only, every limit configurable per route. Errors render as the one Fancy error envelope with the request id. Pure ASGI, zero runtime dependencies. Pairs with @particle-academy/fancy-http-errors.
Turn any error response into one sentence for the UI: the Fancy error envelope, FastAPI details and 422 lists, Laravel validation, or an HTML proxy page, never echoing 5xx text. Field errors, retry-after and the request id come out in one shape. Zero runtime dependencies, no React.
Add passkey sign-in to your app
Install the backend you run and the UI, then mount the four endpoints. The passkeys UI's pages show every state the sign-in and the manager can be in.

