← Compare

Login with Vipps and MobilePay vs Pay with Vipps and MobilePay for WooCommerce

Head-to-head on the signals that matter, from the public WordPress.org data.

Login with Vipps and MobilePay and Pay with Vipps and MobilePay for WooCommerce are close on health (A · 86 vs A · 86). Login with Vipps and MobilePay has the stronger support.

Active-install trajectory

No change to chart. WordPress.org reports active installs in coarse bands, so neither plugin crossed a band during this window. The download trend below moves daily and is the better read over a period this short.

Metric	Login with Vipps and MobilePay	Pay with Vipps and MobilePay for WooCommerce
Active installs Modeled from the public "N+" band and recent downloads.	900–1K	5K–6K ✓
Active installs, change over ~6 months Compares the public install bands. One band step shows as the band change, not a percentage.	Stable	Stable
Overall health	A · 86	A · 86
Maintenance How recently the plugin was updated.	100/100	100/100
Rating quality Volume-adjusted review quality.	80/100	86/100 ✓
Support Share of forum threads marked resolved.	70/100 ✓	64/100
Rating (weighted for review count)	4.2★	4.4★ ✓
Reviews	4	13 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	88/100 ✓	87/100
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	Low	Low
Last updated	2mo ago	yesterday ✓
Downloads, last 30d	787	22.2K ✓
Download momentum, last 30d vs prior 30d Dips that follow a release spike are normal: wp.org counts every update as a download, so the weeks after a release run lower.	+20%	-34%
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	2.2% ✓	0.9%
Category	Login & Users	eCommerce

✓ marks the stronger plugin on each row. Rows where they're level show no marker.

Release activity

Login with Vipps and MobilePayPay with Vipps and MobilePay for WooCommerce

7-day average daily downloads. Downloads spike for about a week after each release as the install base re-downloads, so read this as release cadence, not growth.