CURLW vs Disable REST API

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

Health C55

Health D53

Active-install trajectory

Disable REST API moved down one install band, 90K+ to 80K+. That's a single step across the whole window, so there's no trajectory to draw. The download trend below moves daily.

Metric	CURLW	Disable REST API
Active installs Modeled from the public "N+" band and recent downloads.	—	80K–90K ✓
Install trend Change in active installs across the charted window.	—	-11% ✓
Overall health	—	D · 53 ✓
Maintenance How recently the plugin was updated.	36/100 ✓	8/100
Rating quality Volume-adjusted review quality.	—	91/100 ✓
Support Share of forum threads marked resolved.	—	70/100 ✓
Rating (adjusted)	—	4.62★ ✓
Reviews	0	38 ✓
Ranking optimization How well the listing is tuned to rank on wp.org.	72/100 ✓	63/100
Removal risk Maintenance signals that precede a wp.org closure. Not an official status.	Low ✓	Elevated
Last updated	1.6y ago ✓	3.0y ago
Downloads · 30d	25	5.9K ✓
Install conversion Active installs over lifetime downloads. Downloads include every update, so older and more frequently released plugins read lower.	—	10% ✓
Category	Login & Users	Admin & Utilities

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

Release activity

CURLWDisable REST API

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.