[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f-Zsxh_H2Y-TyINHHPv-Jl0ZmjX9HdgnZ4D8_m6eFR8w":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":18,"download_link":25,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":38,"analysis":136,"fingerprints":218},"prevent-browser-caching","Prevent Browser Caching","2.3.5","kostyatereshchuk","https:\u002F\u002Fprofiles.wordpress.org\u002Fkostyatereshchuk\u002F","\u003Cp>Are you a frontend developer? Do you want to clear browser cache for all users? Just activate this plugin and show your work!\u003C\u002Fp>\n\u003Cp>Prevent Browser Caching allows you to update the assets version of all CSS and JS files automatically or manually in one click.\u003C\u002Fp>\n\u003Cp>Now you can show the latest changes on the site without asking the client to clear the cache.\u003C\u002Fp>\n\u003Ch4>How it works?\u003C\u002Fh4>\n\u003Cp>Usually, WordPress loads assets using query param “ver” in the URL (e.g., style.css?ver=4.9.6). It allows browsers to cache these files until the parameter will not be updated.\u003C\u002Fp>\n\u003Cp>To prevent caching of CSS and JS files, this plugin adds a unique number (e.g., 1526905286) to the “ver” parameter (e.g., style.css?ver=4.9.6.1526905286) for all links, loaded using wp_enqueue_style and wp_enqueue_script functions.\u003C\u002Fp>\n\u003Ch4>For developers\u003C\u002Fh4>\n\u003Cp>By default, this plugin updates all assets files every time a user loads a page and adds options in the admin panel (Settings -> Prevent Browser Caching) which allows you to configure updating of these files.\u003C\u002Fp>\n\u003Cp>But you can also set the version of CSS and JS files programmatically.\u003C\u002Fp>\n\u003Cp>Just insert this code in functions.php file of your theme and change the value of assets_version when you need to update assets:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>prevent_browser_caching( array( \n    'assets_version' => '123' \n) );\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Updates the assets version of all CSS and JS files. Shows the latest changes on the site without asking the client to clear browser cache.",10000,109482,98,28,"2024-04-09T17:18:00.000Z","6.5.8","4.0","",[20,21,22,23,24],"assets","browser-cache","clear","development","frontend","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fprevent-browser-caching.2.3.5.zip",92,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},3,10050,87,30,85,"2026-04-04T00:37:38.109Z",[39,53,73,93,112],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":10,"active_installs":46,"downloaded":47,"rating":48,"num_ratings":32,"last_updated":49,"tested_up_to":50,"requires_at_least":17,"requires_php":18,"tags":51,"homepage":18,"download_link":52,"security_score":36,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"disable-version-caching","Disable Version Caching – Khanakia","1.0.1","mrkhanakia","https:\u002F\u002Fprofiles.wordpress.org\u002Fmrkhanakia\u002F","\u003Cp>Are you a frontend developer? Do you want to clear browser cache for all users? Just activate this plugin and show your work!\u003C\u002Fp>\n\u003Cp>Disable Version Caching allows you to update the assets version of all CSS and JS files automatically or manually in one click.\u003C\u002Fp>\n\u003Cp>Now you can show the latest changes on the site without asking the client to clear the cache.\u003C\u002Fp>\n\u003Ch4>How it works?\u003C\u002Fh4>\n\u003Cp>Usually, WordPress loads assets using query param “ver” in the URL (e.g., style.css?ver=4.9.6). It allows browsers to cache these files until the parameter will not be updated.\u003C\u002Fp>\n\u003Cp>To prevent caching of CSS and JS files, this plugin adds a unique number (e.g., 1526903434) to the “ver” parameter (e.g., style.css?ver=4.9.6.1526903434) for all links, loaded using wp_enqueue_style and wp_enqueue_script functions.\u003C\u002Fp>\n\u003Ch4>For developers\u003C\u002Fh4>\n\u003Cp>By default, this plugin updates all assets files every time a user loads a page and adds options in the admin panel (Settings -> Disable Version Caching) which allows you to configure updating of these files.\u003C\u002Fp>\n\u003Cp>But you can also set the version of CSS and JS files programmatically.\u003C\u002Fp>\n\u003Cp>Just insert this code in functions.php file of your theme and change the value of assets_version when you need to update assets:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>disable_version_caching( array( \n    'assets_version' => '123' \n) );\n\u003C\u002Fcode>\u003C\u002Fpre>\n",200,3560,100,"2020-11-30T06:45:00.000Z","5.5.18",[20,21,22,23,24],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-version-caching.zip",{"slug":54,"name":55,"version":56,"author":57,"author_profile":58,"description":59,"short_description":60,"active_installs":61,"downloaded":62,"rating":48,"num_ratings":63,"last_updated":64,"tested_up_to":65,"requires_at_least":66,"requires_php":18,"tags":67,"homepage":71,"download_link":72,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"rebusted","reBusted!","1.2","Simon Prosser","https:\u002F\u002Fprofiles.wordpress.org\u002Fpross\u002F","\u003Cp>Saves you from asking “have you emptied your cache?”.\u003C\u002Fp>\n\u003Cp>Forked and updated for todays WordPress and PHP from the original plugin by Paul Clark.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Safe to leave running on live sites.\u003C\u002Fli>\n\u003Cli>Only refreshes browser cache for a file if it has been modified.\u003C\u002Fli>\n\u003Cli>Resolves Content Delivery Network (CDN) issues. No need to purge CDN cache.\u003C\u002Fli>\n\u003Cli>Multisite compatible.\u003C\u002Fli>\n\u003Cli>“Just works” – no configuration necessary.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Requirements\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Requires scripts use any of the below functions to load. Almost all files meet these requirements. The only case it doesn’t account for is when URLs are hard-coded. This shouldn’t ever be done, since it can break sites for other reasons.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_enqueue_style\" rel=\"nofollow ugc\">wp_enqueue_style\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_enqueue_script\" rel=\"nofollow ugc\">wp_enqueue_script\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fget_stylesheet_uri\" rel=\"nofollow ugc\">get_stylesheet_uri\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Force browsers to load the most recent file if modified.",6000,34186,11,"2024-10-10T14:16:00.000Z","6.7.5","3.4",[21,22,68,69,70],"client","debug","develop","https:\u002F\u002Fgithub.com\u002FPross\u002FreBusted","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frebusted.1.2.zip",{"slug":74,"name":75,"version":76,"author":77,"author_profile":78,"description":79,"short_description":80,"active_installs":81,"downloaded":82,"rating":13,"num_ratings":83,"last_updated":84,"tested_up_to":85,"requires_at_least":86,"requires_php":87,"tags":88,"homepage":91,"download_link":92,"security_score":48,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"query-monitor","Query Monitor – The developer tools panel for WordPress","3.20.2","John Blackbourn","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnbillion\u002F","\u003Cp>Query Monitor is the developer tools panel for WordPress and WooCommerce. It enables debugging of database queries, PHP errors, hooks and actions, block editor blocks, enqueued scripts and stylesheets, HTTP API calls, and more.\u003C\u002Fp>\n\u003Cp>It includes some advanced features such as debugging of Ajax calls, REST API calls, user capability checks, and full support for block themes and full site editing. It includes the ability to narrow down much of its output by plugin or theme, allowing you to quickly determine poorly performing plugins, themes, or functions.\u003C\u002Fp>\n\u003Cp>Query Monitor focuses heavily on presenting its information in a useful manner, for example by showing aggregate database queries grouped by the plugins, themes, or functions that are responsible for them. It adds an admin toolbar menu showing an overview of the current page, with complete debugging information shown in panels once you select a menu item.\u003C\u002Fp>\n\u003Cp>Query Monitor supports versions of WordPress up to three years old, and PHP version 7.4 or higher.\u003C\u002Fp>\n\u003Cp>For complete information, please see \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002F\" rel=\"nofollow ugc\">the Query Monitor website\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Here’s an overview of what’s shown for each page load:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Database queries, including notifications for slow, duplicate, or erroneous queries. Allows filtering by query type (\u003Ccode>SELECT\u003C\u002Fcode>, \u003Ccode>UPDATE\u003C\u002Fcode>, \u003Ccode>DELETE\u003C\u002Fcode>, etc), responsible component (plugin, theme, WordPress core), and calling function, and provides separate aggregate views for each.\u003C\u002Fli>\n\u003Cli>The template filename, the complete template hierarchy, and names of all template parts that were loaded or not loaded (for block themes and classic themes).\u003C\u002Fli>\n\u003Cli>PHP errors presented nicely along with their responsible component and call stack, and a visible warning in the admin toolbar.\u003C\u002Fli>\n\u003Cli>Usage of “Doing it Wrong” or “Deprecated” functionality in the code on your site.\u003C\u002Fli>\n\u003Cli>Blocks and associated properties within post content and within full site editing (FSE).\u003C\u002Fli>\n\u003Cli>Matched rewrite rules, associated query strings, and query vars.\u003C\u002Fli>\n\u003Cli>Enqueued scripts and stylesheets, along with their dependencies, dependents, and alerts for broken dependencies.\u003C\u002Fli>\n\u003Cli>Language settings and loaded translation files (MO files and JSON files) for each text domain.\u003C\u002Fli>\n\u003Cli>HTTP API requests, with response code, responsible component, and time taken, with alerts for failed or erroneous requests.\u003C\u002Fli>\n\u003Cli>User capability checks, along with the result and any parameters passed to the capability check.\u003C\u002Fli>\n\u003Cli>Environment information, including detailed information about PHP, the database, WordPress, and the web server.\u003C\u002Fli>\n\u003Cli>The values of all WordPress conditional functions such as \u003Ccode>is_single()\u003C\u002Fcode>, \u003Ccode>is_home()\u003C\u002Fcode>, etc.\u003C\u002Fli>\n\u003Cli>Transients that were updated.\u003C\u002Fli>\n\u003Cli>Usage of \u003Ccode>switch_to_blog()\u003C\u002Fcode> and \u003Ccode>restore_current_blog()\u003C\u002Fcode> on Multisite installations.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Whenever a redirect occurs, Query Monitor adds an HTTP header containing the call stack, so you can use your favourite HTTP inspector or browser developer tools to trace what triggered the redirect.\u003C\u002Fli>\n\u003Cli>The response from any jQuery-initiated Ajax request on the page will contain various debugging information in its headers. PHP errors also get output to the browser’s developer console.\u003C\u002Fli>\n\u003Cli>The response from an authenticated WordPress REST API request will contain an overview of performance information and PHP errors in its headers, as long as the authenticated user has permission to view Query Monitor’s output. An \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Frest-api\u002Fusing-the-rest-api\u002Fglobal-parameters\u002F#_envelope\" rel=\"nofollow ugc\">an enveloped REST API request\u003C\u002Fa> will include even more debugging information in the \u003Ccode>qm\u003C\u002Fcode> property of the response.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>By default, Query Monitor’s output is only shown to Administrators on single-site installations, and Super Admins on Multisite installations.\u003C\u002Fp>\n\u003Cp>In addition to this, you can set an authentication cookie which allows you to view Query Monitor output when you’re not logged in (or if you’re logged in as a non-Administrator). See the Settings panel for details.\u003C\u002Fp>\n\u003Ch3>Other Plugins\u003C\u002Fh3>\n\u003Cp>I maintain several other plugins for developers. Check them out:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002F\" rel=\"ugc\">User Switching\u003C\u002Fa> provides instant switching between user accounts in WordPress.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-crontrol\u002F\" rel=\"ugc\">WP Crontrol\u003C\u002Fa> lets you view and control what’s happening in the WP-Cron system\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Statement\u003C\u002Fh3>\n\u003Cp>Query Monitor is private by default and always will be. It does not persistently store any of the data that it collects. It does not send data to any third party, nor does it include any third party resources. \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002Fprivacy\u002F\" rel=\"nofollow ugc\">Query Monitor’s full privacy statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Accessibility Statement\u003C\u002Fh3>\n\u003Cp>Query Monitor aims to be fully accessible to all of its users. \u003Ca href=\"https:\u002F\u002Fquerymonitor.com\u002Faccessibility\u002F\" rel=\"nofollow ugc\">Query Monitor’s full accessibility statement can be found here\u003C\u002Fa>.\u003C\u002Fp>\n","Query Monitor is the developer tools panel for WordPress and WooCommerce.",200000,19156533,463,"2025-12-11T22:16:00.000Z","6.9.4","6.1","7.4",[69,89,23,90,74],"debug-bar","performance","https:\u002F\u002Fquerymonitor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquery-monitor.3.20.2.zip",{"slug":94,"name":95,"version":96,"author":97,"author_profile":98,"description":99,"short_description":100,"active_installs":101,"downloaded":102,"rating":13,"num_ratings":103,"last_updated":104,"tested_up_to":85,"requires_at_least":105,"requires_php":106,"tags":107,"homepage":110,"download_link":111,"security_score":48,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"yoast-test-helper","Yoast Test Helper","1.18","Yoast","https:\u002F\u002Fprofiles.wordpress.org\u002Fyoast\u002F","\u003Cp>This plugin makes testing Yoast SEO, Yoast SEO add-ons and integrations and resetting the different features a lot easier. It also makes testing database migrations a lot easier as it allows you to set the database version and see if the upgrade process runs smoothly.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cp>This test helper plugin has several features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Easily enable Yoast SEO development mode.\u003C\u002Fli>\n\u003Cli>Saving and restoring Yoast SEO and Yoast SEO extension options, to test upgrade paths.\u003C\u002Fli>\n\u003Cli>Add options debug info to Yoast SEO admin pages.\u003C\u002Fli>\n\u003Cli>Reset the internal link counter, prominent words calculation and other features.\u003C\u002Fli>\n\u003Cli>Add two post types (Books and Movies) with two taxonomies (Category and Genre) each and optionally disable the block editor for them.\u003C\u002Fli>\n\u003Cli>Easily add an inline script after a selected script.\u003C\u002Fli>\n\u003Cli>Replace your \u003Ccode>.test\u003C\u002Fcode> TLD with \u003Ccode>example.com\u003C\u002Fcode> in your Schema output, so you can easily copy paste to Google’s Structured Data Testing Tool.\u003C\u002Fli>\n\u003Cli>Change the number of URLs shown in an XML Sitemap.\u003C\u002Fli>\n\u003Cli>Easily change your MyYoast URL.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you find bugs or would like to contribute, see our \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FYoast\u002Fyoast-test-helper\" rel=\"nofollow ugc\">GitHub repo\u003C\u002Fa>.\u003C\u002Fp>\n","This plugin makes testing Yoast SEO, Yoast SEO add-ons and integrations and resetting the different features a lot easier.",60000,762113,12,"2025-12-01T18:28:00.000Z","6.4","7.2.5",[23,108,109],"yoast","yoast-seo","https:\u002F\u002Fgithub.com\u002Fyoast\u002Fyoast-test-helper","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fyoast-test-helper.1.18.zip",{"slug":113,"name":114,"version":115,"author":116,"author_profile":117,"description":118,"short_description":119,"active_installs":120,"downloaded":121,"rating":13,"num_ratings":122,"last_updated":123,"tested_up_to":85,"requires_at_least":124,"requires_php":125,"tags":126,"homepage":18,"download_link":132,"security_score":133,"vuln_count":134,"unpatched_count":27,"last_vuln_date":135,"fetched_at":29},"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,31,"2026-01-12T05:38:00.000Z","4.9","5.6",[127,128,129,130,131],"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,1,"2022-01-24 00:00:00",{"attackSurface":137,"codeSignals":188,"taintFlows":211,"riskAssessment":212,"analyzedAt":217},{"hooks":138,"ajaxHandlers":178,"restRoutes":185,"shortcodes":186,"cronEvents":187,"entryPointCount":134,"unprotectedCount":27},[139,144,147,153,156,160,163,166,168,170,175],{"type":140,"name":141,"callback":142,"file":143,"line":63},"action","admin_menu","add_plugin_page","includes\\admin\\class-prevent-browser-caching-admin-settings.php",{"type":140,"name":145,"callback":146,"file":143,"line":103},"admin_init","page_init",{"type":148,"name":149,"callback":150,"priority":11,"file":151,"line":152},"filter","style_loader_src","add_query_arg","includes\\class-prevent-browser-caching-function.php",51,{"type":148,"name":154,"callback":150,"priority":11,"file":151,"line":155},"script_loader_src",52,{"type":140,"name":157,"callback":157,"priority":11,"file":158,"line":159},"admin_bar_menu","includes\\class-prevent-browser-caching.php",66,{"type":140,"name":145,"callback":161,"priority":11,"file":158,"line":162},"update_css_js",69,{"type":140,"name":164,"callback":161,"priority":11,"file":158,"line":165},"template_redirect",71,{"type":148,"name":149,"callback":150,"priority":11,"file":158,"line":167},76,{"type":148,"name":154,"callback":150,"priority":11,"file":158,"line":169},77,{"type":140,"name":171,"callback":172,"file":173,"line":174},"plugins_loaded","prevent_browser_caching_load_textdomain","prevent-browser-caching.php",41,{"type":140,"name":176,"callback":177,"file":173,"line":165},"after_setup_theme","maybe_load_class_prevent_browser_caching",[179],{"action":180,"nopriv":181,"callback":182,"hasNonce":183,"hasCapCheck":181,"file":143,"line":184},"pbc_update_clear_cache_time",false,"update_clear_cache_time",true,13,[],[],[],{"dangerousFunctions":189,"sqlUsage":190,"outputEscaping":192,"fileOperations":27,"externalRequests":27,"nonceChecks":209,"capabilityChecks":134,"bundledLibraries":210},[],{"prepared":27,"raw":27,"locations":191},[],{"escaped":193,"rawEcho":194,"locations":195},5,6,[196,199,201,203,205,207],{"file":143,"line":197,"context":198},46,"raw output",{"file":143,"line":200,"context":198},62,{"file":143,"line":202,"context":198},65,{"file":143,"line":204,"context":198},134,{"file":143,"line":206,"context":198},168,{"file":143,"line":208,"context":198},172,2,[],[],{"summary":213,"deductions":214},"The \"prevent-browser-caching\" v2.3.5 plugin exhibits a generally good security posture, with no known vulnerabilities or critical code signals. The plugin has a very small attack surface, consisting of a single AJAX handler which, importantly, has authentication checks. The absence of dangerous functions, raw SQL queries, file operations, and external HTTP requests are all positive indicators. Furthermore, the presence of nonce and capability checks on its entry points suggests a deliberate effort to secure its functionalities.\n\nHowever, there is a notable concern regarding output escaping. With 11 total outputs, only 45% are properly escaped. This means that a significant portion of the plugin's output could be vulnerable to Cross-Site Scripting (XSS) attacks if user-supplied data is incorporated into these unescaped outputs without proper sanitization. While taint analysis showed no flows, this is likely due to the limited nature of the analysis or the absence of complex data flows within this specific plugin, and does not negate the risk posed by unescaped output.\n\nOverall, the plugin demonstrates a commitment to secure coding practices in many areas, especially concerning its limited attack surface and use of prepared statements. The primary weakness lies in the insufficient output escaping, which presents a moderate risk that should be addressed to achieve a more robust security profile.",[215],{"reason":216,"points":194},"Insufficient output escaping (45% properly escaped)","2026-03-16T17:42:00.378Z",{"wat":219,"direct":226},{"assetPaths":220,"generatorPatterns":221,"scriptPaths":222,"versionParams":223},[],[],[],[224,225],"prevent-browser-caching\u002Fstyle.css?ver=","prevent-browser-caching\u002Fscript.js?ver=",{"cssClasses":227,"htmlComments":228,"htmlAttributes":229,"restEndpoints":230,"jsGlobals":231,"shortcodeOutput":232},[],[],[],[],[],[]]