misaf / vendra-verification
Provider-neutral user profile verification records for Vendra
Package info
github.com/misaf/vendra-verification
Type:vendra-module
pkg:composer/misaf/vendra-verification
Requires
- php: ^8.3
- misaf/vendra-support: v1.6.0
- misaf/vendra-user-profile: v1.6.0
- spatie/laravel-package-tools: ^1.93.1
Requires (Dev)
- fakerphp/faker: ^1.24.1
- larastan/larastan: ^3.10.0
- laravel/boost: ^2.4.12
- laravel/pint: ^1.29.3
- misaf/vendra-testing: v1.6.0
- orchestra/testbench: ^11.1
- pestphp/pest: ^4.7.5
- pestphp/pest-plugin-arch: ^4.0.2
- pestphp/pest-plugin-laravel: ^4.1
- pestphp/pest-plugin-profanity: ^4.2.1
- pestphp/pest-plugin-type-coverage: ^4.0.4
- phpstan/extension-installer: ^1.4.3
README
Provider-neutral user profile verification records for Vendra applications.
Features
- Dynamic
verificationsrelation on Vendra user profiles - Filament relation manager contributed through the User Profile extension registry
- Open verification types, statuses, and providers — no vendor lock-in
- ISO country code and structured JSON metadata for jurisdiction- or provider-specific fields
- Tenant-aware storage and permission-seeded authorization
Requirements
- PHP 8.3+
- Laravel 13
- Filament 5
misaf/vendra-user-profilemisaf/vendra-support
Installation
composer require misaf/vendra-verification php artisan vendor:publish --tag=vendra-verification-migrations php artisan migrate
Tenant columns are determined when the migration runs. If verifications must be tenant-scoped, install a tenant provider such as misaf/vendra-tenant before running the migration. Enabling tenancy later does not add a tenant column to an existing table.
The service provider and the user-profile relation manager are auto-registered.
Seeding
Verification permissions seed automatically when a tenant is provisioned. To seed them manually:
php artisan vendra-verification:seed {tenant}
Testing
composer test
License
MIT. See LICENSE.