Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records CertFusion version 1.0.0 as active, updated 3mo ago and tested up to WordPress 7.0.
Overview
About this plugin
com) using a personal API token. It is a pure API client — no CertFusion server changes are required.
Features:
Connection settings with a one-click “Test connection” that shows your account and remaining quota.
Recipient manager in the WordPress admin: browse your certificate lists, add recipients (with custom fields), issue certificates individually or in bulk, and delete recipients.
Native recipient form (no third-party form plugin required): collect a name, email and custom fields, then automatically issue a certificate on submission. Includes nonce protection, a honeypot and per-IP throttling.
Verification widget: visitors look up their issued certificates by email and get direct View / Download links.
Shortcodes and blocks: [certfusion_form id="1"], [certfusion_verify], [certfusion_claim list_id="1"], plus matching Gutenberg blocks.
External services
com, or a self-hosted CertFusion URL you configure in the settings). CertFusion is the certificate platform this plugin is a client for; the connection is required for every feature of the plugin — without it the plugin does nothing.
Data sent to the CertFusion API, and when:
Your CertFusion API token is sent with every request as an Authorization header, to authenticate your account.
When an administrator opens the Recipients or Forms pages, the plugin requests your certificate lists and recipients from the API.
When an administrator adds, issues or deletes a recipient, that recipient’s name, email address and any custom field values are sent to the API.
When a visitor submits the recipient form, the name, email address and custom field values they entered are sent to the API to create the recipient and issue their certificate.
When a visitor uses the verification widget, the email address they entered is sent to the API to look up their issued certificates.
No data is sent to CertFusion on ordinary page loads; requests happen only on the admin actions and visitor submissions listed above.
This service is provided by CertFusion: terms of service, privacy policy.
WordPress.org metadata
Plugin tags
Topics listed for this plugin in the WordPress.org directory.
badges
certificates
credentials
lms
verification
Compatibility & maintenance
Compatibility & maintenance
Tested up to WordPress 7.0
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.
Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 5.8 · PHP 7.4
Update activity20 Jul 20263mo ago
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
Changes recorded by WP PlugIndex
Recent tracked changes
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
Tracking & source
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.
