Skip to content

Requirements

Requirements

These are taken from this app's composer.json (and, where noted, the framework dependency it pulls in). The Composer resolver enforces the versions below, so this page just explains them. Storage engines are listed separately as operations guidance, not hard requirements.

Runtime

Requirement Version Enforced by Why
PHP ^8.4 composer.json Uses PHP 8.4 language features throughout.
ext-openssl * cboxdk/laravel-id + cbox-id:doctor RSA/EC key generation and JWT/SAML signing.
ext-sodium * cboxdk/laravel-id + cbox-id:doctor Ed25519 signing and AEAD sealing of secrets at rest.

ext-sodium and ext-openssl are not listed in this app's own require block, but the crypto layer in cboxdk/laravel-id needs both and php artisan cbox-id:doctor fails loudly if either is missing.

Framework

Requirement Version
laravel/framework ^13.0
livewire/livewire ^4.3
livewire/volt ^1.10

Cbox / cboxdk dependencies

Pulled in automatically by composer install:

Package Version Used for
cboxdk/laravel-id ^0.4 The identity engine (crypto, tenancy, OAuth/OIDC, SCIM, SAML, audit).
cboxdk/laravel-health ^2.0 Health/readiness reporting.
cboxdk/laravel-risk ^1.0 Bot/abuse risk scoring on signup/login (monitor mode by default).
cboxdk/laravel-telemetry ^0.3.3 Tracing / telemetry (trace IDs on error screens).
cboxdk/laravel-queue-metrics ^3.2 Queue depth/throughput metrics.
cboxdk/laravel-queue-autoscale ^3.0 Worker autoscaling.

Other Composer dependencies

Package Version Used for
laravel/socialite ^5.28 Social/enterprise OAuth sign-in.
socialiteproviders/microsoft ^4.9 Microsoft/Entra provider for Socialite.
laravel/tinker ^3.0 REPL for operations/debugging.

cboxdk/laravel-id is pinned to a pre-1.0 series (^0.4). Minor bumps in that range may carry breaking changes — read its changelog before upgrading.

Building assets

The UI is built with Vite + Tailwind. Producing production assets requires Node.js (CI uses Node 22) and runs npm ci && npm run build. Node is a build-time requirement only; it is not needed to serve the built app.

Storage (operations guidance, not a hard requirement)

The default .env.example ships DB_CONNECTION=sqlite and the test suite runs on SQLite, so nothing in composer.json mandates a particular database. For a production identity provider, however, run a server database:

  • Recommended in production: PostgreSQL or MySQL/MariaDB (not SQLite).
  • Recommended cache/queue/session backend: Redis.

These are recommendations for a live deployment — see Deployment — not constraints the resolver enforces.