Skip to content
PluginCanary

Razorpay Subscriptions for WooCommerce

by Razorpay · 700+ active installs · Checked 3 Nov 2026
Healthy1 Warning

Healthy: maintained, last release 1 Jun 2026, 1 release in 24 months, no unpatched vulnerabilities.

Tested up to WordPress 6.9.11, 2 major versions behind 7.1.4.

89/ 100 Canary Score
Sub-scores for Razorpay Subscriptions for WooCommerce
Ownership100
Maintenance70
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Razorpay Subscriptions for WooCommerce still maintained?
Yes. Last release 1 Jun 2026, 1 release in the last 24 months. 1 Jun 2026 · wordpress.org
Who owns Razorpay Subscriptions for WooCommerce, and has it changed hands?
No change recorded. Main committer razorpay since Sep 2019. 3 Nov 2026 · SVN log
Was Razorpay Subscriptions for WooCommerce removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Razorpay Subscriptions for WooCommerce safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Razorpay Subscriptions for WooCommerce update safe to install?
No ownership change before 2.4.2. No one-star spike after it. 1 Jun 2026 · Release history

Active signals

Facts we detected, with links to the source.

  • WarningMNT-2Tested up to WordPress 6.9.11, 2 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence

Ownership timeline

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

Committers and their active periods
premtechchefs30 Jul 2019 to 30 Jul 2019, 6 commits
razorpay16 Sep 2019 to 1 Jun 2026, 37 commits

2 committers recorded. No ownership change since 2017.

Maintenance

Last release
5 months ago
Releases, 24 months
1
Tested up to
6.9 vs 7.1
Requires PHP
7.4 supported 8.2+
Releases per quarter
Releases per quarter for Razorpay Subscriptions for WooCommerce
Q1 20241
Q2 20241
Q3 20241
Q4 20240
Q1 20250
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20261
Q3 20260
Q4 20260

Last release 1 Jun 2026. Tested up to 6.9, 2 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 3.3.

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

Security record

No published vulnerabilities on record for this plugin.

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

Support

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

Momentum

700+ 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

Version2.4.2
AuthorRazorpay
Added15 Nov 2017
Last updated1 Jun 2026
Active installs700+
Requires WordPress3.9.2
Tested up to6.9.11
Requires PHP7.4
Categorynot stated
Tagsindia, payments, razorpay, ecommerce, woocommerce

Other plugins by this author: Razorpay for WooCommerce, Razorpay Quick Payments, Razorpay Payment Button Plugin, Razorpay for Gravity Forms, Razorpay Subscription Button Elementor Plugin, Razorpay Subscription Button Plugin, Razorpay Payment Button for Visual Composer, Razorpay Payment Button SiteOrigin Plugin

Questions

Is Razorpay Subscriptions for WooCommerce still maintained?

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

Who owns Razorpay Subscriptions for WooCommerce, and has it changed hands?

No change recorded. Main committer razorpay since Sep 2019.

Was Razorpay Subscriptions for WooCommerce removed from wordpress.org?

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

Is Razorpay Subscriptions for WooCommerce safe?

No known vulnerabilities on record.

Is the latest Razorpay Subscriptions for WooCommerce update safe to install?

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