[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fxDjUU-mM8BzIpmpDJuA2d8zlBmWJIUY8U4zbrRJFySc":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":36,"analysis":144,"fingerprints":214},"customize-private-protected","Customize Private & Protected – Change or remove title prefix and more","1.3.4","kirkclarke","https:\u002F\u002Fprofiles.wordpress.org\u002Fkirkclarke\u002F","\u003Cp>Use this plugin to hide or edit the prefix on your password protected or private page, add widget areas before and after the password protected form, and modify the label and submit button text. These changes are global and apply to all protected and private content respectively.\u003C\u002Fp>\n\u003Ch3>Donations\u003C\u002Fh3>\n\u003Cp>If you’d like to support future development, \u003Ca href=\"https:\u002F\u002Fwww.paypal.com\u002Fpaypalme\u002FKirkClarke\" rel=\"nofollow ugc\">buy me a tea\u003C\u002Fa>!\u003C\u002Fp>\n","Use WP Customize to modify elements of password protected and private posts and pages.",300,4498,94,3,"2025-10-04T20:41:00.000Z","6.8.5","5.8","7.0",[20,21,22,23,24],"password-protected","prefix","private","remove","widget","https:\u002F\u002Fgithub.com\u002Fkclarkedesign\u002Fcpp","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustomize-private-protected.1.3.4.zip",100,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":11,"avg_security_score":27,"avg_patch_time_days":34,"trust_score":13,"computed_at":35},1,30,"2026-04-04T15:20:31.224Z",[37,63,83,104,123],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":59,"download_link":60,"security_score":61,"vuln_count":33,"unpatched_count":28,"last_vuln_date":62,"fetched_at":30},"classic-editor-addon","Classic Editor +","4.4.1","Pieter Bos","https:\u002F\u002Fprofiles.wordpress.org\u002Fsenlin\u002F","\u003Cblockquote>\n\u003Cp>GDPR-compliant: does not collect any user data\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>The free “Classic Editor +” plugin is targeted at everyone who does not want to use the WP Block Editor (Gutenberg), introduced in WordPress 5.0. Install it now on sites and the UX remains the same as you are used to without redundant styling being added to the frontend of your site!\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What’s New:\u003C\u002Fstrong>\u003Cbr \u002F>\nRemoves WP Patterns\u003C\u002Fp>\n\u003Cp>This plugin simply disables the WP Block Editor, removes any and all styling from both front- and backend and disables the block editor for widgets too.\u003C\u002Fp>\n\u003Cp>And if WooCommerce and\u002For WPML are installed on the site, “Classic Editor +” removes the block styles of those plugins too.\u003C\u002Fp>\n\u003Cp>There are no Settings, it simply does what it says on the label.\u003C\u002Fp>\n\u003Cp>Therefore I highly recommend installing this “Classic Editor +” plugin.\u003C\u002Fp>\n\u003Cp>I support this plugin exclusively through \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fsenlin\u002Fclassic-editor-addon\u002Fissues\" rel=\"nofollow ugc\">Github\u003C\u002Fa>. Therefore, if you have any questions, need help and\u002For want to make a feature request, please open an issue here. You can also browse through open and closed issues to find what you are looking for and perhaps even help others.\u003C\u002Fp>\n\u003Cp>Thanks for your understanding and cooperation.\u003C\u002Fp>\n\u003Cp>If you like the “Classic Editor +” plugin, please consider leaving a \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fview\u002Fplugin-reviews\u002Fclassic-editor-addon?rate=5#postform\" rel=\"ugc\">review\u003C\u002Fa>. Thanks!\u003C\u002Fp>\n\u003Cp>“Classic Editor +” by \u003Ca href=\"https:\u002F\u002Fso-wp.com\u002Fplugin\u002Fclassic-editor-addon\" rel=\"nofollow ugc\">Pieter Bos\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fgschoppe.com\" rel=\"nofollow ugc\">Greg Schoppe\u003C\u002Fa>.\u003C\u002Fp>\n","The \"Classic Editor +\" plugin disables the block editor, removes enqueued scripts\u002Fstyles and brings back classic Widgets.",50000,640327,98,31,"2026-01-12T05:38:00.000Z","6.9.4","4.9","5.6",[54,55,56,57,58],"classic-editor","classic-widgets","remove-frontend-scripts","remove-frontend-styling","remove-patterns","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclassic-editor-addon.4.4.1.zip",99,"2022-01-24 00:00:00",{"slug":64,"name":65,"version":66,"author":67,"author_profile":68,"description":69,"short_description":70,"active_installs":45,"downloaded":71,"rating":72,"num_ratings":73,"last_updated":74,"tested_up_to":50,"requires_at_least":75,"requires_php":59,"tags":76,"homepage":81,"download_link":82,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"remove-category-url","Remove Category URL – Remove 'category' base from category permalinks","1.2.1","Themeisle","https:\u002F\u002Fprofiles.wordpress.org\u002Fthemeisle\u002F","\u003Cp>Remove Category URL strips the \u003Ccode>\u002Fcategory\u002F\u003C\u002Fcode> base from your category URLs, turning something like \u003Ccode>\u002Fcategory\u002Fmy-category\u002F\u003C\u002Fcode> into simply \u003Ccode>\u002Fmy-category\u002F\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Just activate, and you’re done. No configuration needed.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Creates cleaner URLs like \u003Ccode>mydomain.com\u002Fmy-category\u002F\u003C\u002Fcode> and \u003Ccode>mydomain.com\u002Fmy-category\u002Fmy-post\u002F\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Works out of the box with no settings to configure\u003C\u002Fli>\n\u003Cli>Supports multiple sub-categories\u003C\u002Fli>\n\u003Cli>Automatically 301 redirects old category URLs to the new structure (SEO-friendly)\u003C\u002Fli>\n\u003Cli>Sitemaps are automatically updated with the new URLs after activation\u003C\u002Fli>\n\u003Cli>Compatible with WordPress Multisite, WPML, and popular sitemap plugins\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Why remove \u002Fcategory\u002F from URLs?\u003C\u002Fh3>\n\u003Cp>The \u003Ccode>\u002Fcategory\u002F\u003C\u002Fcode> base in WordPress URLs is there by default, but it doesn’t help your visitors or search engines understand your content any better. When you remove \u003Ccode>\u002Fcategory\u002F\u003C\u002Fcode> from URLs, you get cleaner paths like \u003Ccode>mydomain.com\u002Fnews\u002F\u003C\u002Fcode> instead of \u003Ccode>mydomain.com\u002Fcategory\u002Fnews\u002F\u003C\u002Fcode>. They’re shorter, easier to remember and share, and more consistent with how your pages are already structured.\u003C\u002Fp>\n\u003Cp>Shorter URLs also tend to look better in search results and make your site feel more polished overall. Removing the category base is a small change that makes your whole URL structure cleaner.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>We’re here to help. Feel free to open a new thread on the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fremove-category-url\u002F\" rel=\"ugc\">Support Forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Useful Resources\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>If you like this plugin, you’re sure to love \u003Ca href=\"https:\u002F\u002Fthemeisle.com\u002Fwordpress-plugins\u002F\" rel=\"nofollow ugc\">our other plugins\u003C\u002Fa> as well.\u003C\u002Fli>\n\u003Cli>Our blog is a great place to \u003Ca href=\"https:\u002F\u002Fthemeisle.com\u002Fblog\u002F\" rel=\"nofollow ugc\">learn more about WordPress\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Get the most out of your website with our helpful \u003Ca href=\"https:\u002F\u002Fyoutube.com\u002Fplaylist?list=PLmRasCVwuvpSep2MOsIoE0ncO9JE3FcKP\" rel=\"nofollow ugc\">WordPress YouTube Tutorials\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n","Remove Category URL strips the \u002Fcategory\u002F base from your category URLs, turning something like \u002Fcategory\u002Fmy-category\u002F into simply \u002Fmy-category\u002F.",479177,84,58,"2026-01-12T14:02:00.000Z","3.1",[77,78,79,80,64],"custom-permalinks","permalinks","remove-category-base","remove-category-prefix","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fremove-category-url\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-category-url.1.2.1.zip",{"slug":84,"name":85,"version":86,"author":87,"author_profile":88,"description":89,"short_description":90,"active_installs":91,"downloaded":92,"rating":27,"num_ratings":93,"last_updated":94,"tested_up_to":95,"requires_at_least":96,"requires_php":59,"tags":97,"homepage":101,"download_link":102,"security_score":103,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"remove-widget-titles","Remove Widget Titles","1.0","Stephen Cronin","https:\u002F\u002Fprofiles.wordpress.org\u002Fstephencronin\u002F","\u003Cp>The \u003Ca href=\"http:\u002F\u002Fscratch99.com\u002Fproducts\u002Fremove-widget-titles\u002F\" rel=\"nofollow ugc\">Remove Widget Titles\u003C\u002Fa> plugin removes the title from any widget that has a title starting with the “!” character.\u003C\u002Fp>\n\u003Ch4>Why Use It?\u003C\u002Fh4>\n\u003Cp>This allows you to give widgets a title in the backend for convenience – so you can quickly see which widget is which, rather than having to open them to work out what they are for – without having to show the title on the front end.\u003C\u002Fp>\n\u003Ch4>How To Use (once plugin is installed)\u003C\u002Fh4>\n\u003Cp>If you have a widget for which you do not want the title to appear on the front end of your site, simply add the “!” character to the start of the widget title (in Appearance -> Widgets).\u003C\u002Fp>\n\u003Ch4>Compatibility\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>This plugin requires WordPress 2.6 or above.\u003C\u002Fli>\n\u003Cli>I am not currently aware of any compatibility issues with any other WordPress plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Similar Plugins\u003C\u002Fh4>\n\u003Cp>There is another plugin called \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fhide-widget-title\u002F\" rel=\"ugc\">Hide Widget Title\u003C\u002Fa>, but that leaves the widget title in the page source and hides it using CSS (adding another http request which slows load time slightly). Remove Widget Titles actually removes the widget title from the HTML. The plugin is only 7 lines of code, so it is extremely light and has minimal impact on performance.\u003C\u002Fp>\n\u003Ch4>Support\u003C\u002Fh4>\n\u003Cp>This plugin is officially not supported (due to my time constraints), but if you leave a comment on the plugin’s home page or \u003Ca href=\"http:\u002F\u002Fwww.scratch99.com\u002Fcontact\u002F\" rel=\"nofollow ugc\">contact me\u003C\u002Fa>, I’ll try to help if I can.\u003C\u002Fp>\n\u003Ch4>Disclaimer\u003C\u002Fh4>\n\u003Cp>This plugin is released under the \u003Ca href=\"http:\u002F\u002Fwww.gnu.org\u002Fcopyleft\u002Fgpl.html\" rel=\"nofollow ugc\">GPL licence\u003C\u002Fa>. I do not accept any responsibility for any damages or losses, direct or indirect, that may arise from using the plugin or these instructions. This software is provided as is, with absolutely no warranty. Please refer to the full version of the GPL license for more information.\u003C\u002Fp>\n\u003Ch4>Acknowledgements\u003C\u002Fh4>\n\u003Cp>This plugin was originally written for \u003Ca href=\"http:\u002F\u002Ftwitter.com\u002F#!\u002Fqpsmedia\" rel=\"nofollow ugc\">QPS Media\u003C\u002Fa>, who have allowed me to release it to the WordPress community and maintain ownership of the plugin.\u003C\u002Fp>\n","The Remove Widget Titles plugin removes the title from any widget that has a title starting with the \"!\" character.",7000,61646,27,"2017-11-28T11:49:00.000Z","4.8.28","2.6.0",[98,23,99,24,100],"hide","usability","widget-titles","http:\u002F\u002Fscratch99.com\u002Fwordpress\u002Fplugins\u002Fremove-widget-titles\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-widget-titles.1.0.zip",85,{"slug":105,"name":106,"version":75,"author":107,"author_profile":108,"description":109,"short_description":110,"active_installs":111,"downloaded":112,"rating":27,"num_ratings":113,"last_updated":114,"tested_up_to":115,"requires_at_least":116,"requires_php":59,"tags":117,"homepage":121,"download_link":122,"security_score":103,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"remove-protected-in-title","Remove Protected In Title","dblazeski","https:\u002F\u002Fprofiles.wordpress.org\u002Fdblazeski\u002F","\u003Cp>Remove Protected In Title is a plugin that removes the prefix that wordpress adds on private and password protected pages.\u003Cbr \u002F>\nUsage: Install and activate the plugin. Check one of your password protected or private pages to make sure everything works ok.\u003C\u002Fp>\n","This plugin removes the \"Protected\" or \"Private\" prefix that wordpress adds to Password protected \u002F Private pages.",1000,16073,7,"2020-11-23T22:23:00.000Z","5.6.17","2.8",[118,119,120],"page-title","remove-private","remove-protected","http:\u002F\u002Fwww.dejanblazeski.com\u002Fplugin-remove-protected-from-wordpress-page-title\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-protected-in-title.zip",{"slug":124,"name":125,"version":126,"author":127,"author_profile":128,"description":129,"short_description":130,"active_installs":111,"downloaded":131,"rating":27,"num_ratings":132,"last_updated":133,"tested_up_to":134,"requires_at_least":135,"requires_php":59,"tags":136,"homepage":141,"download_link":142,"security_score":143,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"remove-wp-overhead","Remove WordPress Overhead","1.6.0","omnisite","https:\u002F\u002Fprofiles.wordpress.org\u002Fomnisite\u002F","\u003Cp>A standard WP installation contains many links in the head of your HTML (which slow down your site) and has standard widgets you might never use. You can now install this plugin and check the items you want to have removed. The saved options are cached for better performance.\u003C\u002Fp>\n\u003Cp>Header items you can remove:\u003Cbr \u002F>\n* Remove dashicons CSS from frontend\u003Cbr \u002F>\n* Remove RSD \u002F EditURI Link\u003Cbr \u002F>\n* Remove WLW Manifest Link\u003Cbr \u002F>\n* Remove RSS Feed Links\u003Cbr \u002F>\n* Remove Next & Prev Post Links\u003Cbr \u002F>\n* Remove Shortlink URL (also from http headers)\u003Cbr \u002F>\n* Remove WP Generator Meta\u003Cbr \u002F>\n* Remove Version Numbers from Style and Script Links\u003Cbr \u002F>\n* Disable WP Emoji \u002F emoticons\u003Cbr \u002F>\n* Disable JSON API\u003Cbr \u002F>\n* Disable Canonical URL\u003Cbr \u002F>\n* Remove WooCommerce Generator Meta\u003Cbr \u002F>\n* Remove jQuery Migrate script\u003Cbr \u002F>\n* Disable XML-RPC methods that require authentication\u003Cbr \u002F>\n* Remove all scripts and styles added by Gutenberg (in case you still use the classic editor)\u003C\u002Fp>\n\u003Cp>You can disable the following widgets:\u003Cbr \u002F>\n* Archives\u003Cbr \u002F>\n* Calendar\u003Cbr \u002F>\n* Categories\u003Cbr \u002F>\n* Links\u003Cbr \u002F>\n* Meta\u003Cbr \u002F>\n* Nav Menu\u003Cbr \u002F>\n* Pages\u003Cbr \u002F>\n* Recent Comments\u003Cbr \u002F>\n* Recent Posts\u003Cbr \u002F>\n* RSS\u003Cbr \u002F>\n* Search\u003Cbr \u002F>\n* Tag Cloud\u003Cbr \u002F>\n* Text\u003C\u002Fp>\n","Remove overhead from the  HTML, speed up your website and disable widgets you don't use",28758,5,"2024-08-04T11:10:00.000Z","6.6.5","6.0",[137,138,139,23,140],"clean","disable-widgets","header","remove-widgets","https:\u002F\u002Fgithub.com\u002Fomnisite\u002FWP-Plugin-Remove-Wordpress-Overhead","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-wp-overhead.1.6.0.zip",92,{"attackSurface":145,"codeSignals":191,"taintFlows":205,"riskAssessment":206,"analyzedAt":213},{"hooks":146,"ajaxHandlers":187,"restRoutes":188,"shortcodes":189,"cronEvents":190,"entryPointCount":28,"unprotectedCount":28},[147,153,158,162,166,171,175,179,183],{"type":148,"name":149,"callback":150,"file":151,"line":152},"action","customize_register","customize_pp_plugin_register_customizer","customize-private-protected.php",388,{"type":154,"name":155,"callback":156,"file":151,"line":157},"filter","protected_title_format","customize_pp_plugin_set_protected_prefix",440,{"type":154,"name":159,"callback":160,"file":151,"line":161},"private_title_format","customize_pp_plugin_set_private_prefix",451,{"type":148,"name":163,"callback":164,"file":151,"line":165},"widgets_init","customize_pp_plugin_register_widgets",482,{"type":154,"name":167,"callback":168,"priority":169,"file":151,"line":170},"the_password_form","customize_pp_plugin_form",11,532,{"type":148,"name":172,"callback":173,"file":151,"line":174},"admin_notices","customize_pp_plugin_admin_review_notice",552,{"type":148,"name":176,"callback":177,"file":151,"line":178},"wp_enqueue_scripts","customize_pp_plugin_styles",565,{"type":148,"name":180,"callback":181,"file":151,"line":182},"customize_preview_init","customize_pp_plugin_customizer_live_preview",594,{"type":154,"name":184,"callback":185,"file":151,"line":186},"body_class","customize_pp_plugin_body_class",608,[],[],[],[],{"dangerousFunctions":192,"sqlUsage":193,"outputEscaping":195,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":204},[],{"prepared":28,"raw":28,"locations":194},[],{"escaped":196,"rawEcho":197,"locations":198},13,2,[199,202],{"file":151,"line":200,"context":201},54,"raw output",{"file":151,"line":203,"context":201},59,[],[],{"summary":207,"deductions":208},"The 'customize-private-protected' v1.3.4 plugin demonstrates a strong adherence to secure coding practices, as evidenced by its static analysis results. There are no identified AJAX handlers, REST API routes, shortcodes, or cron events, resulting in a minimal attack surface. Crucially, the plugin employs prepared statements for all SQL queries, and a high percentage of its output is properly escaped, mitigating common injection and XSS vulnerabilities. The absence of dangerous functions, file operations, external HTTP requests, and unpatched CVEs further strengthens its security posture. The plugin also shows no history of vulnerabilities, which is a positive indicator of ongoing secure development. However, the complete lack of nonce and capability checks across all entry points (though there are none identified) represents a potential blind spot. If functionality were to be added in the future that involved user interaction or sensitive data, the absence of these fundamental security checks would immediately introduce significant risks.",[209,211],{"reason":210,"points":132},"No nonce checks implemented",{"reason":212,"points":132},"No capability checks implemented","2026-03-16T19:57:38.047Z",{"wat":215,"direct":222},{"assetPaths":216,"generatorPatterns":218,"scriptPaths":219,"versionParams":220},[217],"\u002Fwp-content\u002Fplugins\u002Fcustomize-private-protected\u002Fcss\u002Fcustom-controls.css",[],[],[221],"customize-private-protected\u002Fcss\u002Fcustom-controls.css?ver=",{"cssClasses":223,"htmlComments":227,"htmlAttributes":228,"restEndpoints":230,"jsGlobals":231,"shortcodeOutput":232},[224,225,226],"cpp-customize-control","input-group-append","input-group-text",[],[229],"data-customize-setting-link",[],[],[]]