Skip to content
PluginCanary

Razorpay for Gravity Forms

by Razorpay · 500+ active installs · Checked 3 Nov 2026
Watch2 Warnings

Watch: tested up to WordPress 6.1.16, 10 major versions behind 7.1.4.

71/ 100 Canary Score
Sub-scores for Razorpay for Gravity Forms
Ownership100
Maintenance20
Security100
SupportNo data
ReputationNo data

How the score works

Quick answers

Is Razorpay for Gravity Forms still maintained?
No. Last release 23 Jan 2025, over 1 year ago. 23 Jan 2025 · wordpress.org
Who owns Razorpay for Gravity Forms, and has it changed hands?
No change recorded. Main committer razorpay since Sep 2019. 3 Nov 2026 · SVN log
Was Razorpay for Gravity Forms removed from wordpress.org?
No. Listed on wordpress.org as of 3 Nov 2026. 3 Nov 2026 · wordpress.org
Is Razorpay for Gravity Forms safe?
No known vulnerabilities on record. 3 Nov 2026 · Wordfence Intelligence
Is the latest Razorpay for Gravity Forms update safe to install?
No ownership change before 1.3.7. No one-star spike after it. 23 Jan 2025 · Release history

Active signals

Facts we detected, with links to the source.

  • WarningMNT-2Tested up to WordPress 6.1.16, 10 major versions behind 7.1.4. Plan a replacement if the plugin is important to your site.3 Nov 2026Evidence
  • WarningMNT-1No release in 21 months (last release 23 Jan 2025). Plan a replacement if the plugin is important to your site.23 Jan 2026Evidence

Ownership timeline

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

Committers and their active periods
plugin-master12 Sep 2019 to 12 Sep 2019, 1 commits
razorpay14 Sep 2019 to 23 Jan 2025, 18 commits
ramprak20 Feb 2020 to 7 Apr 2020, 6 commits
chetangn8 Sep 2020 to 8 Sep 2020, 2 commits

4 committers recorded. No ownership change since 2019.

Maintenance

Last release
22 months ago
Releases, 24 months
2
Tested up to
6.1 vs 7.1
Requires PHP
not stated supported 8.2+
Releases per quarter
Releases per quarter for Razorpay for Gravity Forms
Q1 20241
Q2 20240
Q3 20240
Q4 20241
Q1 20251
Q2 20250
Q3 20250
Q4 20250
Q1 20260
Q2 20260
Q3 20260
Q4 20260

Last release 23 Jan 2025. Tested up to 6.1, 10 major versions behind WordPress 7.1.

Reputation

Last 90 days: no reviews. Lifetime: 1.0.

Rating distribution
5 star0
4 star0
3 star0
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

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

Version1.3.7
AuthorRazorpay
Added14 Sep 2019
Last updated23 Jan 2025
Active installs500+
Requires WordPress3.9.2
Tested up to6.1.16
Requires PHPnot stated
CategoryE-commerce & Shopping
Tagsindia, payments, razorpay, ecommerce, GravityForms

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

Questions

Is Razorpay for Gravity Forms still maintained?

No. Last release 23 Jan 2025, over 1 year ago.

Who owns Razorpay for Gravity Forms, and has it changed hands?

No change recorded. Main committer razorpay since Sep 2019.

Was Razorpay for Gravity Forms removed from wordpress.org?

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

Is Razorpay for Gravity Forms safe?

No known vulnerabilities on record.

Is the latest Razorpay for Gravity Forms update safe to install?

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