Timeline and roadmap
Build timeline
235 commits between 2025-12-27 and 2026-10-28, in distinct bursts.
• Aug to Oct 2025: precursors, a NestJS auth starter and an identity backend. Nov to Dec 2025: auth-0-vc and the @rsxt/auth package. 2025-12-27: first commit of my-auth (28 commits that month).
• March 2026 (86 commits): dashboard overview and tenant settings endpoints, social connections and account linking, a hardened security-event audit, and the first admin portal build.
• June 2026 (77 commits): the MFA flow, portal upgrades, backup-code auth in the SDK, and replacing a mock applications table with a real OAuth client lifecycle. A feature audit against Auth0 was written on 2026-06-20.
• October 2026 (38 commits): foundation hardening and ADRs 0001 to 0007, signed SAML SSO, per-tenant signing keys, the ASVS pass and frontend audit on 2026-10-20, link-first auth contracts, step-up and pre-session enrolment, per-tenant CORS and the Guest role, and the Playwright journeys.
Next: reliability and compliance
• Scope the database connection to the unit of work instead of the whole request, with pool metrics and a 200-concurrent-request load test as the acceptance bar.
• Fix the Redis cache store compatibility, remove or back the in-memory handshake session store, and route every raw schema-name SQL through the single quoting helper.
• Append-only audit with retention, subject export and erasure endpoints, IP pseudonymisation and a control-to-evidence matrix.
• Require a verified database TLS configuration in production and namespace rate-limit keys by tenant with per-account throttling.
• Code hygiene: remove remaining any types, raw fetches and stray console calls, and move app dependencies out of the root manifest.
Next: product completeness
• Observability: request ids already flow end to end; add OpenTelemetry traces and Prometheus metrics.
• Release engineering: non-root Dockerfiles with health checks, a Helm chart, SDK publishing through changesets, and dependency automation.
• SDK and API gaps: passwordless sign-up, passkey sign-in without typing an email, sign-in on invite acceptance with a wrong-account check, a consistent response envelope across the remaining raw responses, a typed profile response with email change and avatar upload, and multipart branding upload.
• Console areas that render Planned shells until their contracts exist: billing and usage, platform people and support, provisioning history, notification preferences, connected applications, domain and email setup, organisation ownership, service credentials and privacy governance.
Deliberately out of scope
The implicit OAuth flow, opaque access tokens, and a body copy of the access token for browsers are excluded on purpose. SOC 2 certification, HIPAA and PCI are out of scope for the repository itself.