ramon / verified
Verified user badges with admin reviewed requests for Flarum 2
Requires
- php: ^8.3
- flarum/core: ^2.0.0
Requires (Dev)
- flarum/gdpr: ^2.0
- phpstan/phpstan: ^2.0
- roave/security-advisories: dev-latest
- vimeo/psalm: ^6.0
Suggests
- flarum/gdpr: Required for data-export, anonymization and erasure integration (^2.0).
Provides
None
Conflicts
None
Replaces
None
- dev-main
- v2.1.24
- v2.1.23
- v2.1.22
- v2.1.21
- v2.1.20
- v2.1.19
- v2.1.18
- v2.1.17
- v2.1.16
- v2.1.15
- v2.1.14
- v2.1.13
- v2.1.12
- v2.1.11
- v2.1.10
- v2.1.9
- v2.1.8
- v2.1.7
- v2.1.6
- v2.1.5
- v2.1.4
- v2.1.3
- v2.1.2
- v2.1.1
- v2.1.0
- v2.0.22
- v2.0.21
- v2.0.20
- v2.0.19
- 2.0.18
- 2.0.17
- 2.0.16
- 2.0.15
- 2.0.14
- 2.0.13
- 2.0.11
- 2.0.10
- 2.0.9
- 2.0.8
- 2.0.7
- 2.0.6
- 2.0.5
- 2.0.4
- 2.0.3
- 2.0.2
- 2.0.1
- 2.0.0
- dev-feat/audit-sqlite
- dev-BC
- dev-claude/awesome-noether-ioyka0
This package is auto-updated.
Last update: 2026-09-14 10:18:55 UTC
README
Verified
A verified badge for Flarum users, the way X does it.
Verified adds a blue check next to usernames everywhere they show up: posts, profiles, user cards and mentions. Users apply from their own settings page, admins approve or reject from a dedicated panel, and the badge follows the user around the forum from then on.
It can be as light or as strict as your community needs. Run it as a simple request and approve flow, or require an identity document with each request, encrypt the uploads with a public key and let a retention policy purge the files later.
What it does
- Blue verified badge wherever the username is rendered, with an optional hover tooltip showing who verified and when
- Verification requests from the user's settings page, reviewed in an admin panel
- Optional identity document upload, with public key encryption and configurable retention
- Avatar lock for verified users, so the face people trust does not change silently
- Custom badge SVG, size and color if the default does not match your theme
- Notifications by alert and email when a request is handled
- Plays nice with
flarum/gdprfor export, anonymization and erasure
Installation
composer require ramon/verified php flarum migrate php flarum cache:clear
Then enable Verified on the Extensions page. Settings, permissions and the request queue all live in the admin panel, each option explained in place.
Good to know
- Documents are wiped on the schedule you choose. The nightly
verified:purge-documentscommand takes care of it, no cron of your own needed. - Encryption is opt in: set a public key in the settings and uploads are sealed before they touch the disk. The private key never goes in the database.
- Everything the frontend does goes through the
/api/verified/*endpoints, so verification can also be automated from outside.
License
MIT. Questions and ideas are welcome on the issue tracker.