← Compare

htaccess protect vs .htaccess Site Access Control

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

.htaccess Site Access Control and htaccess protect are close on health (D · 44 vs D · 43), with nothing separating them on the sub-scores.

Active-install trajectory

htaccess protect.htaccess Site Access Control

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	htaccess protect	.htaccess Site Access Control
Active installs Modeled from the public "N+" band and recent downloads.	700–800	800–900 ✓
Active installs, change over ~6 months Compares the public install bands. One band step shows as the band change, not a percentage.	-22%	Stable ✓
Overall health	D · 43	D · 44 ✓
Maintenance How recently the plugin was updated.	3/100	3/100
Rating quality Volume-adjusted review quality.	70/100	73/100 ✓
Support Share of forum threads marked resolved.	70/100	70/100
Rating (weighted for review count)	3.8★	3.9★ ✓
Reviews	6 ✓	3
Ranking optimization How well the listing is tuned to rank on wp.org.	44/100 ✓	37/100
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	Elevated ✓	High
Last updated	4.8y ago ✓	10.5y ago
Downloads, last 30d	182 ✓	161
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.	+39%	+9%
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	6.1%	7.7% ✓
Category	Security	Security

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

Release activity

htaccess protect.htaccess Site Access Control

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.