Functional Weave
Code in Rust

Suites · auth

User accounts and authentication

Sign-up and login forms, password policy and hashing, login lockout, signed access tokens, two-factor codes, email verification and reset tokens, account linking and roles.

42 capabilities (13 core, 29 optional) and 13 gaps, in build order. Put each line in the file that calls it, then fune build.

Core coverage: 50%

13 of 26 needs met by verified capabilities. The needs are this suite's 13 core members and its 13 named gaps; a core member counts when a version of it is verified (by the sandbox, or the registry's seed) and not yanked, and a gap never counts. Optional members are not needs.

Baseline: a hand-written app with no suite meets 0 of the same 26. Method fune-coverage/1, computed 2026-11-22T20:40:19.327Z.

1. Sign-up and login forms

Check what people type into the account forms, the same way in the browser and the API.

auth.validate-registration core
Validates a sign-up form (email, password, name) in one call, with a message per field.
Validate a sign-up form (email, password, name) in one call, with a message per field, in the browser and the API alike.
fune!(auth.validate-registration@^1);  // then call validate_registration(…)
auth.validate-login core
Checks a login form and gives the normalised email to look the account up by.
Check a login form (email, password): the normalised email to look up, or a message for each field to fix.
fune!(auth.validate-login@^1);  // then call validate_login(…)
auth.normalise-email core
Trims an email and lower-cases its domain, so one address is one account.
Trim an email address and lower-case its domain for storage and lookup, or null if it is not a plausible address.
fune!(auth.normalise-email@^1);  // then call normalise_email(…)
auth.validate-password-change optional
Checks a change-password form: current password given and correct, new one meeting the policy and different.
Check a change-password form: current password given and correct, new one meeting the policy and different.
fune!(auth.validate-password-change@^1);  // then call validate_password_change(…)

2. Passwords

Decide what passwords are acceptable and store them safely.

auth.password-policy core
Checks a new password against NIST SP 800-63B-4 by default: length, common passwords, name and email.
Check a new password against a named policy (NIST SP 800-63B-4 by default): length, common passwords, name and email.
fune!(auth.password-policy@^1);  // then call password_policy, check_password
auth.password-hash core
Hashes passwords as PBKDF2-SHA256 for storage, verifies in constant time, and flags hashes to upgrade.
Hash a password for storage as pbkdf2_sha256$iterations$salt$hash, verify one in constant time, and spot weak hashes.
fune!(auth.password-hash@^1);  // then call hash_password, verify_password, password_needs_rehash
crypto.pbkdf2-sha256 optional
The PBKDF2 key derivation underneath, if you need it directly.
PBKDF2 with HMAC-SHA256 (RFC 8018): derive a key from a password and salt, slowly, fast enough for a login request.
fune!(crypto.pbkdf2-sha256@^1);  // then call pbkdf2_sha256(…)
crypto.constant-time-equal optional
Compares MACs and hashes in constant time, for your own token or signature checks.
Compare two byte strings in time that does not depend on where they differ, for checking MACs and hashes.
fune!(crypto.constant-time-equal@^1);  // then call constant_time_equal(…)
  • breached-passwords Checking passwords against a breach corpus (Have I Been Pwned's range API) is network work; the policy's common-password list is built in.

3. Login protection

Slow down password guessing.

auth.login-throttle core
Allows a login attempt or locks the account out from its recent failures, with the seconds until retry.
Allow a login attempt or lock the account out, from its recent failed attempts, with the seconds until it may retry.
fune!(auth.login-throttle@^1);  // then call login_throttle(…)
http.retry-after optional
Reads a Retry-After header, for a client that backs off when locked out or rate limited.
Seconds to wait from an HTTP Retry-After header (delay-seconds or an HTTP date), or null if missing or malformed.
fune!(http.retry-after@^1);  // then call retry_after_seconds(…)
  • ip-rate-limiting Rate limiting by IP address across accounts, with its shared counter store (Redis, a database).

4. Tokens

Issue and check signed tokens for an API or a single-page app.

auth.access-token core
Issues HS256 access tokens, reads them from the Authorization header, and refuses revoked or superseded ones.
Issue an API's HS256 access token, read one from an Authorization header, and refuse revoked or superseded ones.
fune!(auth.access-token@^1);  // then call issue_access_token, read_access_token, confirm_access_token
auth.bearer-token core
Takes the token out of an "Authorization: Bearer ..." header, or null.
The token from an HTTP Authorization header of the form "Bearer <token>" (RFC 6750), or null if it has none.
fune!(auth.bearer-token@^1);  // then call parse_bearer_token(…)
auth.jwt optional
Signs, verifies and decodes HS256 JWTs with exp/nbf/iat checks, for tokens of your own shape.
Sign, verify and decode HS256 JSON Web Tokens (RFC 7519): signature, algorithm and exp/nbf/iat checked with leeway.
fune!(auth.jwt@^1);  // then call sign_jwt, verify_jwt, decode_jwt
crypto.hmac-sha256 optional
HMAC-SHA256, for signing webhooks, links or cookies.
HMAC-SHA256 of a message under a secret key (RFC 2104, RFC 4231), in pure code that also runs in the browser.
fune!(crypto.hmac-sha256@^1);  // then call hmac_sha256(…)
crypto.sha256 optional
SHA-256 digests, for storing API keys or reset tokens hashed.
The SHA-256 digest of a byte string (FIPS 180-4), in pure code that also runs in the browser.
fune!(crypto.sha256@^1);  // then call sha256(…)
encoding.base64 optional
Base64 and base64url, for encoding tokens and keys.
Bytes to base64 and base64url text and back (RFC 4648), with strict decoding, identically in every language.
fune!(encoding.base64@^1);  // then call base64_encode, base64_decode, base64_url_encode, base64_url_decode
time.countdown optional
Seconds left until a token expires and a timer text, for "session expires in 4:05".
Seconds left until a Unix time, whether it has passed, and a timer text like 4:05, for tokens or retry waits.
fune!(time.countdown@^1);  // then call countdown(…)
  • sessions Server-side session stores and CSRF tokens are yours; auth.oauth-sign-in signs a stateless session cookie with Secure/HttpOnly/SameSite set.
  • asymmetric-jwt RS256/ES256 tokens and JWKS key sets (for third-party identity providers): auth.jwt is HS256 only.

5. Sign-in with an identity provider

Let people sign in with Google, Microsoft, GitHub or any OpenID Connect provider, and keep them signed in.

auth.oauth-sign-in optional
OAuth 2.0 / OpenID Connect sign-in with PKCE, and signed session cookies (an integration: does I/O, needs SESSION_SECRET and the provider's client id).
Sign users in with OpenID Connect or GitHub (authorisation code + PKCE), and keep them in a signed session cookie.
Not available in Rust: typescript only
auth.account-link optional
Decides whether a provider sign-in signs in, links to an account by verified email, creates one, or is refused.
Decide whether an OAuth sign-in signs in, links to an existing account by verified email, creates one, or is refused.
fune!(auth.account-link@^1);  // then call decide_account_link(…)
  • identity-links The table of provider identities linked to accounts, and the unlink page, are yours; auth.account-link decides.

6. Email verification, password reset and magic links

Prove someone owns an address with a single-use link that expires.

auth.email-token core
Hashed single-use tokens for verify-email, reset-password and magic-link, with expiry and consume-once.
Hashed single-use tokens for email verification, password reset and magic links, with expiry, as pure steps.
fune!(auth.email-token@^1);  // then call generate_email_token, hash_email_token, check_email_token, consume_email_token
email.send optional
Sends the verification, reset or magic-link email through Resend, SMTP or the log (an integration: does I/O).
Send a transactional email through Resend, any SMTP server or the log, behind one call.
Not available in Rust: typescript only
  • email-token-table The table the hashed tokens live in (token_hash, purpose, subject, expires_at, used_at) is yours.

7. Two-factor sign-in

Ask for a second factor after the password: an authenticator app code, or a recovery code.

auth.totp optional
TOTP (RFC 6238) secrets, the otpauth:// QR-code URI, codes, and verification with a window, drift and replay refusal.
Authenticator-app two-factor codes (TOTP RFC 6238, HOTP RFC 4226): secret, QR URI, codes, verify with window and drift.
fune!(auth.totp@^1);  // then call totp_secret, totp_uri, hotp_code, totp_code, verify_totp
auth.recovery-codes optional
One-time recovery codes: generate, store hashed, verify and consume.
Two-factor recovery codes: generate from caller entropy, hash for storage, and verify-and-consume as a pure step.
fune!(auth.recovery-codes@^1);  // then call generate_recovery_codes, normalise_recovery_code, hash_recovery_code, consume_recovery_code
  • passkeys-sms Passkeys/WebAuthn and SMS codes are not in Functional Weave.

8. Roles and permissions

Decide who may do what, and test it.

auth.rbac optional
Role inheritance, wildcard permissions, resource ownership, and a generated per-role access test matrix.
Roles with inheritance, permission checks with wildcards and ownership, and a generated per-role access-test matrix.
fune!(auth.rbac@^1);  // then call resolve_roles, has_permission, check_access, access_matrix
  • org-membership Organisations, invitations and membership tables are yours to model.

9. Forms in React

Accessible account pages in a React front end (TypeScript only).

react.form.password-field optional
A password input with Show/Hide and a live checklist of the password policy.
A password input with a Show/Hide button and an optional live checklist of a password policy (GOV.UK password input).
Not available in Rust: typescript only
react.form.text-field optional
Labelled email and name inputs with hints and errors.
A labelled single-line text input with hint, error message, autocomplete, prefix and suffix (GOV.UK text input).
Not available in Rust: typescript only
react.form.validated-input optional
Sign-up inputs that check required, length and pattern rules, with the same check on the server.
A text, email or number input that checks itself with form.validate-input and shows the error accessibly.
Not available in Rust: typescript only
react.form.error-summary optional
The "There is a problem" box linking to each field in error.
A "There is a problem" box linking to each field in error, focused on arrival, built from a validator's fields (GOV.UK).
Not available in Rust: typescript only
form.state optional
Form values, touched fields and validator errors as a reducer for useReducer.
A form's state as a pure reducer: values, touched fields, validator errors and the submit, for useReducer.
Not available in Rust: typescript only

10. Contact details from validation-basics

Check and normalise a person's contact details before storing them.

validation.email core
Is an email address plausible, by a documented subset of RFC 5322.
Is this a plausible email address? A documented, pragmatic subset of RFC 5322, not the full grammar.
fune!(validation.email@^1);  // then call is_email(…)
validation.phone-e164 core
Normalises a phone number to +44… E.164 for a default country.
Normalise a phone number to E.164 (+447700900123) using a default country's trunk and dialling prefixes.
fune!(validation.phone-e164@^2);  // then call validate_phone_e164(…)
validation.uk-postcode core
Validates a UK postcode and puts it in canonical form.
Validate a UK postcode and normalise it to canonical upper case with one space before the inward code.
fune!(validation.uk-postcode@^2);  // then call validate_uk_postcode(…)
text.normalise-name optional
Tidies a typed name: spacing and title case with Mc, O' and hyphen rules.
Tidy a personal name: trim, collapse whitespace and title-case, with Mc, Mac, O', hyphen and van/de rules.
fune!(text.normalise-name@^1);  // then call normalise_name(…)

11. Bank details from validation-basics

Check payee and customer bank details before money moves.

validation.iban core
Checks an IBAN's mod-97 checksum and its country's length.
Check an IBAN against the ISO 13616 mod-97-10 checksum and the registered length for its country.
fune!(validation.iban@^1);  // then call is_iban(…)
validation.bic optional
Checks a SWIFT/BIC code's format and splits it.
Check the format of a SWIFT/BIC code (8 or 11 characters) and split it into its parts.
fune!(validation.bic@^1);  // then call validate_bic(…)
validation.uk-sort-code-account optional
Checks a UK sort code and account number by the Vocalink modulus rules, against a table you supply.
Check a UK sort code and account number with the Vocalink/Pay.UK modulus rules, against a table you supply.
fune!(validation.uk-sort-code-account@^3);  // then call validate_uk_sort_code_account(…)
validation.uk-modulus-table optional
Parses Vocalink's VALACDOS and SCSUBTAB files into that table.
Parse Vocalink's VALACDOS.txt and SCSUBTAB.txt into the table UK sort code modulus checking needs.
fune!(validation.uk-modulus-table@^1);  // then call parse_uk_modulus_table(…)

12. Identifiers and check digits from validation-basics

Catch mistyped reference numbers by their check digits.

validation.luhn optional
Luhn mod-10 check, for card numbers and many reference numbers.
Check a digit string against the Luhn mod-10 checksum used by payment cards and many identifiers.
fune!(validation.luhn@^1);  // then call is_luhn(…)
validation.uk-company-number optional
Checks a Companies House number's format and prefix.
Check a Companies House company number's format and prefix (SC, NI, OC, LP...) and zero-pad it to eight characters.
fune!(validation.uk-company-number@^2);  // then call validate_uk_company_number(…)
validation.lei optional
Checks a Legal Entity Identifier's check digits.
Check a 20-character Legal Entity Identifier against its ISO 17442 / ISO 7064 MOD 97-10 check digits.
fune!(validation.lei@^1);  // then call validate_lei(…)
validation.gtin optional
Checks an EAN/UPC/GTIN barcode number.
Check an EAN-8, UPC-A, EAN-13 or GTIN-14 barcode number against the GS1 mod-10 check digit.
fune!(validation.gtin@^1);  // then call validate_gtin(…)

13. Displaying sensitive values from validation-basics

Show stored identifiers without exposing them.

text.mask optional
Masks all but the last digits of a card, account or phone number.
Mask all but the last n characters of a card, account or phone number, optionally keeping separators.
fune!(text.mask@^1);  // then call mask(…)

Gaps

What this kind of app usually needs that Functional Weave does not have yet: write these yourself, or use a service.

  • email-wording The wording of the verification, reset and magic-link emails; email.send sends them.
  • user-storage The users table, unique email index, migrations and account deletion.
  • address-lookup Turning a postcode into a list of addresses (Royal Mail PAF or a lookup API) is network work and not in caps.
  • email-deliverability Whether a mailbox exists (MX lookups, a confirmation email): validation.email checks the syntax only.
  • vocalink-data The Vocalink modulus tables themselves: download them from Pay.UK under its terms; caps parses them but does not ship them.