Provides a UI to control which REST API endpoints are enabled and which require authentication.
Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →
WP PlugIndex currently records WP REST API Security version 1.1.2 as active, updated 7y ago and tested up to WordPress 5.1.
The REST API is essential for any modern web framework, but with it comes a huge attack surface. WP REST API Security reduces the attack surface by disabling all the REST API endpoints by default, allowing you to enable only those actually needed. Those that are enabled require authentication by default, allowing you to choose which to make public.
>
B. If you are using the new Block Editor you must keep nearly all the endpoints enabled for it to work, but none need be public.
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 5.1.
“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.
No tracked version or compatibility changes have been recorded by WP PlugIndex yet.
WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.
