Download the PHP package ramon/verified without Composer
On this page you can find all versions of the php package ramon/verified. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download ramon/verified
More information about ramon/verified
Files in ramon/verified
Package verified
Short Description Verified user badges with admin reviewed requests for Flarum 2
License MIT
Informations about the package verified
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
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
issue tracker.