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.

SQL To CPT

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

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

95/ 100Limited data
Canary Score

Based on 3 of 5 areas

Capped at 95: not enough support or review data for a full score.

Sub-scores for SQL To CPT
Ownership100
Maintenance85
Security100
SupportNo data
ReputationNo data

How the score works

Active signals

Open issues right now, with links to the source.

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

Quick answers

Is SQL To CPT still maintained?
Yes. Last release 8 Jul 2026, 1 release in the last 24 months. 8 Jul 2026 · wordpress.org
Who owns SQL To CPT, and has it changed hands?
Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist. 3 Nov 2026 · SVN log
Was SQL To CPT removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is SQL To CPT safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest SQL To CPT update safe to install?
No ownership change before 1.5.0. No one-star spike after it. 8 Jul 2026 · Release history

Ownership timeline

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

Commit history is collected for plugins with 1,000+ installs or on a watchlist.

Maintenance

Last release
4 months ago
Releases, 24 months
1
Tested up to
7.0 vs 7.1
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for SQL To CPT
Q1 20240
Q2 20240
Q3 20240
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20261
Q4 20260

Last release 8 Jul 2026. Tested up to 7.0, 1 major version behind WordPress 7.1.

Support

Resolved, last 2 months
n/a
Threads, last 2 months
0

Trend appears after 8 weekly snapshots.

Security record

No published vulnerabilities on record for this plugin.

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

Reputation

Last 90 days: no reviews.

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

Momentum

Active installs
Fewer than 10

Trend appears after 8 weekly snapshots.

Facts

Version
1.5.0
Author
badasswp
Added
12 Oct 2024
Last updated
8 Jul 2026
Active installs
Fewer than 10
Requires WordPress
6.0
Tested up to
7.0.8
Requires PHP
7.4
Category
not stated
Tags
cpt, sql, post, import, convert

Other plugins by this author: Image Converter for WebP, Search and Replace for Block Editor, AI + Block Editor, Convert Blocks to JSON, Create Product On Image Upload, Redirect Duplicate Posts, Pending Order Bot, Trash Post in Block Editor, Censor Order Details, Watermark My Images, Addon for Post Meta Translation using, Display Site Notification Bar

Questions about SQL To CPT

Is SQL To CPT still maintained?

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

Who owns SQL To CPT, and has it changed hands?

Not enough data. Commit history is collected for plugins with 1,000+ installs or on a watchlist.

Was SQL To CPT removed from wordpress.org?

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

Is SQL To CPT safe?

No known vulnerabilities on record.

Is the latest SQL To CPT update safe to install?

No ownership change before 1.5.0. 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