Restricted content based on purchase vs Access Governance for WordPress (aka AAM)

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

Restricted content based on purchase

by Maciej Molenda

Health B79

Access Governance for WordPress (aka AAM)

by AAM Plugin

Health A86

Active-install trajectory

Restricted content based on purchaseAccess Governance for WordPress (aka AAM)

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	Restricted content based on purchase	Access Governance for WordPress (aka AAM)
Active installs Modeled from the public "N+" band and recent downloads.	30–40	100K–200K ✓
Install trend Change in active installs across the charted window.	+200% ✓	0%
Overall health	B · 79	A · 86 ✓
Maintenance How recently the plugin was updated.	86/100	100/100 ✓
Rating quality Volume-adjusted review quality.	76/100	80/100 ✓
Support Share of forum threads marked resolved.	70/100	70/100
Rating (weighted for review count)	4.1★	4.2★ ✓
Reviews	2	420 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	77/100	82/100 ✓
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	Low	Low
Last updated	7mo ago	17d ago ✓
Downloads · 30d	101	102K ✓
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	1.7% ✓	1.3%
Category	Uncategorized	Security

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

Release activity

Restricted content based on purchaseAccess Governance for WordPress (aka AAM)

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.