Skip to content
PluginCanary
Limited data: this plugin has under 1,000 active installs and less than 12 weeks of history with us, so we show signals but no status band yet.

Cnvrse

by cnvrse · Fewer than 10 active installs · Checked 3 Nov 2026
Limited data

Limited data: Cnvrse has under 1,000 active installs and less than 12 weeks of history, so we do not rate it yet.

98/ 100 Canary Score
Sub-scores for Cnvrse
Ownership100
Maintenance100
Security95
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Cnvrse still maintained?
Yes. Last release 1 Nov 2026, 1 release in the last 24 months. 1 Nov 2026 · wordpress.org
Who owns Cnvrse, and has it changed hands?
Changed. New committer cnvrse made a first commit on 1 Nov 2026. 1 Nov 2026 · SVN log
Was Cnvrse removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Cnvrse safe?
1 known vulnerability, fixed (latest in 026.02.10.20). Not on the exploited list. 11 Feb 2026 · Wordfence Intelligence
Is the latest Cnvrse update safe to install?
No ownership change before 26.11.01.1. No one-star spike after it. 1 Nov 2026 · Release history

Active signals

Facts we detected, with links to the source.

No open risk signals. Signals appear here when we detect an ownership change, closure, vulnerability or decline.

Ownership timeline

Who commits to the plugin's code on wordpress.org, over time.

Committers and their active periods
cnvrse1 Nov 2026 to 1 Nov 2026, 1 commits

New committer cnvrse made a first commit on 1 Nov 2026.

Maintenance

Last release
3 days ago
Releases, 24 months
1
Tested up to
7.1 current
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for Cnvrse
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20260
Q4 20261

Last release 1 Nov 2026. Tested with WordPress 7.1 (current).

Reputation

Last 90 days: no reviews. Lifetime: 5.0.

Rating distribution
5 star1
4 star0
3 star0
2 star0
1 star0

Security record

1 vulnerability in 24 months, patched (latest fixed in 026.02.10.20).

Show 1 patched vulnerability
PublishedIssueCVSSAffectedFixed inDays to patch
11 Feb 2026Cnvrse < 026.02.10.20 - Unauthenticated Insecure Direct Object Reference5.3< 026.02.10.20026.02.10.20n/a

Sources: Wordfence Intelligence, CISA Known Exploited Vulnerabilities, readme changelogs.

Support

Support history appears after our first snapshots of the forum counts.

Momentum

Fewer than 10 active installs. History builds with each weekly snapshot.

Momentum history builds with each snapshot.

Healthier alternatives

Same job, rated Healthy, higher Canary Score and at least 10,000 installs. Never sponsored.

No healthier plugin in the same category yet.

Facts

Version26.11.01.1
Authorcnvrse
Added28 Nov 2025
Last updated1 Nov 2026
Active installsFewer than 10
Requires WordPress6.1
Tested up to7.1.4
Requires PHP7.4
Categorynot stated
Tagsdiscord, support, telegram, live chat, chat widget

Questions

Is Cnvrse still maintained?

Yes. Last release 1 Nov 2026, 1 release in the last 24 months.

Who owns Cnvrse, and has it changed hands?

Changed. New committer cnvrse made a first commit on 1 Nov 2026.

Was Cnvrse removed from wordpress.org?

No. Listed on wordpress.org as of 3 Nov 2026.

Is Cnvrse safe?

1 known vulnerability, fixed (latest in 026.02.10.20). Not on the exploited list.

Is the latest Cnvrse update safe to install?

No ownership change before 26.11.01.1. No one-star spike after it.

Data: wordpress.org Plugins API, plugins SVN and Trac, wordpress.org reviews and support forum, Wordfence Intelligence, CISA KEV, NVD.Plugin data refreshed 3 Nov 2026.Report a data issue