Force login to make the site private vs Force Login

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

Force login to make the site private

by Fernando Tellado

Health B83

Force Login

by Kevin Vess

Health A88

Active-install trajectory

Force login to make the site privateForce Login

Active installs, each indexed to 100 at the start of the window. A line above 100 is growing its install base, below 100 is shrinking.

Metric	Force login to make the site private	Force Login
Active installs Modeled from the public "N+" band and recent downloads.	50–60	30K–40K ✓
Install trend Change in active installs across the charted window.	+400% ✓	0%
Overall health	B · 83	A · 88 ✓
Maintenance How recently the plugin was updated.	100/100 ✓	94/100
Rating quality Volume-adjusted review quality.	74/100	93/100 ✓
Support Share of forum threads marked resolved.	70/100	70/100
Rating (weighted for review count)	4.0★	4.7★ ✓
Reviews	1	101 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	88/100	91/100 ✓
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	Low	Low
Last updated	2mo ago ✓	5mo ago
Downloads · 30d	200	175.7K ✓
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	3.0% ✓	0.3%
Category	Login & Users	Privacy & Consent

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

Release activity

Force login to make the site privateForce Login

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.