[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fQjP085h2Vx9C0W8JO71Iqel9wtjPrSI48CLCC9dW88k":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":11,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":37,"analysis":144,"fingerprints":251},"cache-purger-for-bunnycdn","Cache Purger for BunnyCDN","2.0","amanda f","https:\u002F\u002Fprofiles.wordpress.org\u002Fsayatentang\u002F","\u003Cp>Cache Purger for BunnyCDN is a powerful and flexible plugin that automatically purges BunnyCDN cache whenever you publish or update posts\u002Fpages in WordPress. This ensures that your visitors always get the most up-to-date content.\u003C\u002Fp>\n\u003Cp>In version 2.0, the plugin now supports cache purging for additional popular caching plugins including LiteSpeed Cache, WP Fastest Cache, WP-Optimize, Cache Enabler, Breeze, and Hummingbird – alongside the previously supported WP Rocket, WP Super Cache, and W3 Total Cache.\u003C\u002Fp>\n\u003Cp>Developed to address persistent caching issues when using BunnyCDN and Bunny DNS Accelerator, this plugin ensures both your local and CDN caches stay in sync for optimal performance and content freshness.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Features:\u003C\u002Fstrong>\u003Cbr \u002F>\n– Automatically purges BunnyCDN cache for individual URLs whenever content is published or updated.\u003Cbr \u002F>\n– Integrates with major WordPress caching plugins:\u003Cbr \u002F>\n  – WP Rocket\u003Cbr \u002F>\n  – WP Super Cache\u003Cbr \u002F>\n  – W3 Total Cache\u003Cbr \u002F>\n  – LiteSpeed Cache\u003Cbr \u002F>\n  – WP Fastest Cache\u003Cbr \u002F>\n  – WP-Optimize\u003Cbr \u002F>\n  – Cache Enabler\u003Cbr \u002F>\n  – Breeze\u003Cbr \u002F>\n  – Hummingbird Cache\u003Cbr \u002F>\n– Logs all purge requests and responses for easy monitoring.\u003Cbr \u002F>\n– Supports wildcard purging for broad cache invalidation.\u003Cbr \u002F>\n– Asynchronous cache purging via WP-Cron for optimized performance.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why Use Cache Purger for BunnyCDN?\u003C\u002Fstrong>\u003Cbr \u002F>\nThis plugin is ideal for sites using BunnyCDN to accelerate global content delivery. By purging both CDN and local caches when content updates, your users always receive the freshest possible version of your site.\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin connects to an external API to manage cache purging for updated pages, ensuring that users always see the latest content. Each time a page is updated, the plugin sends the page URL to the Bunny.net API at https:\u002F\u002Fapi.bunny.net\u002Fpurge to clear the cache.\u003C\u002Fp>\n\u003Cp>For more information, please refer to Bunny.net’s \u003Ca href=\"https:\u002F\u002Fbunny.net\u002Ftos\u002F\" rel=\"nofollow ugc\">Terms of Use\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fbunny.net\u002Fprivacy\u002F\" rel=\"nofollow ugc\">Privacy Policy\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later. For more information, see https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html.\u003C\u002Fp>\n","Automatically purge BunnyCDN cache on post\u002Fpage updates. Integrates with top WordPress caching plugins for seamless cache clearing.",100,1722,74,3,"2025-05-09T06:11:00.000Z","6.7.5","5.0","7.2",[20,21,22,23,24],"bunnycdn","cache-purging","litespeed","wp-super-cache","wp-rocket","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purger-for-bunnycdn.2.0.zip",0,null,"2026-03-15T15:16:48.613Z",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":11,"avg_security_score":11,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"sayatentang",1,30,94,"2026-04-05T02:49:08.951Z",[38,62,87,105,124],{"slug":23,"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":18,"tags":52,"homepage":57,"download_link":58,"security_score":59,"vuln_count":60,"unpatched_count":27,"last_vuln_date":61,"fetched_at":29},"WP Super Cache","3.0.3","Automattic","https:\u002F\u002Fprofiles.wordpress.org\u002Fautomattic\u002F","\u003Cp>This plugin generates static html files from your dynamic WordPress blog.  After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.\u003C\u002Fp>\n\u003Cp>The static html files will be served to the vast majority of your users:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Users who are not logged in.\u003C\u002Fli>\n\u003Cli>Users who have not left a comment on your blog.\u003C\u002Fli>\n\u003Cli>Or users who have not viewed a password protected post.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.\u003C\u002Fp>\n\u003Cp>The plugin serves cached files in 3 ways (ranked by speed):\u003C\u002Fp>\n\u003Col>\n\u003Cli>Expert. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file which is risky and may take down your site if modified incorrectly.\u003C\u002Fli>\n\u003Cli>Simple. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. It’s easier to configure as the .htaccess file doesn’t need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode.\u003C\u002Fli>\n\u003Cli>WP-Cache caching. This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. Set the constant “DISABLE_SUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If you’re not comfortable with editing PHP files then use simple mode. It’s easy to set up and very fast.\u003C\u002Fp>\n\u003Ch3>Recommended Settings\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Simple caching.\u003C\u002Fli>\n\u003Cli>Compress pages.\u003C\u002Fli>\n\u003Cli>Don’t cache pages for known users.\u003C\u002Fli>\n\u003Cli>Cache rebuild.\u003C\u002Fli>\n\u003Cli>CDN support.\u003C\u002Fli>\n\u003Cli>Extra homepage checks.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds.\u003C\u002Fp>\n\u003Cp>Consider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you.\u003C\u002Fp>\n\u003Cp>Preload as many posts as you can and enable “Preload Mode”. Garbage collection of old cached files will be disabled. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.\u003Cbr \u002F>\nEven with preload mode enabled cached files will still be deleted when posts are modified or comments made.\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Active development of this plugin is handled \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Translation of the plugin into different languages is on the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fwp-super-cache\" rel=\"nofollow ugc\">translation page\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Documentation\u003C\u002Fh3>\n\u003Cp>If you need more information than the following, you can have a look at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\u002Fwiki\" rel=\"nofollow ugc\">the wiki\u003C\u002Fa> or the \u003Ca href=\"https:\u002F\u002Fodd.blog\u002Fwp-super-cache-developers\u002F\" rel=\"nofollow ugc\">Developer documentation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Preloading\u003C\u002Fh4>\n\u003Cp>You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.\u003Cbr \u002F>\nTo make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling “Preload Mode” in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.\u003C\u002Fp>\n\u003Ch4>Garbage Collection\u003C\u002Fh4>\n\u003Cp>Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:\u003Cbr \u002F>\n1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.\u003Cbr \u002F>\n2. Scheduler. Setup how often garbage collection should be done.\u003Cbr \u002F>\n3. Notification emails. You can be informed on garbage collection job progress.\u003Cbr \u002F>\nThere’s no right or wrong settings for garbage collection. It depends on your own site.\u003Cbr \u002F>\nIf your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.\u003Cbr \u002F>\nIf your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.\u003C\u002Fp>\n\u003Cp>The cache directory, usually wp-content\u002Fcache\u002F is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.\u003C\u002Fp>\n\u003Ch4>CDN\u003C\u002Fh4>\n\u003Cp>A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a “poor man’s CDN” by using a sub domain of your domain to serve static files too.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fossdl-cdn-off-linker\u002F\" rel=\"ugc\">OSSDL CDN off-linker\u003C\u002Fa> has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support \u003Ca href=\"https:\u002F\u002Fwww.google.com\u002Fsearch?hl=en&q=%22origin+pull%22\" rel=\"nofollow ugc\">origin pull\u003C\u002Fa>. This means the CDN will download the file automatically from your server when it’s first requested, and will continue to serve it for a configurable length of time before downloading it again from your server.\u003C\u002Fp>\n\u003Cp>Configure this on the “CDN” tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.\u003C\u002Fp>\n\u003Ch4>REST API\u003C\u002Fh4>\n\u003Cp>There are now REST API endpoints for accessing the settings of this plugin. You’ll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the “rest” directory.\u003C\u002Fp>\n\u003Ch4>Custom Caching\u003C\u002Fh4>\n\u003Cp>It is now possible to hook into the caching process using the add_cacheaction() function.\u003C\u002Fp>\n\u003Cp>Three hooks are available:\u003C\u002Fp>\n\u003Col>\n\u003Cli>‘wp_cache_get_cookies_values’ – modify the key used by WP Cache.\u003C\u002Fli>\n\u003Cli>‘add_cacheaction’ – runs in phase2. Allows a plugin to add WordPress hooks.\u003C\u002Fli>\n\u003Cli>‘cache_admin_page’ – runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>There is one regular WordPress filter too. Use the “do_createsupercache” filter\u003Cbr \u002F>\nto customize the checks made before caching. The filter accepts one parameter.\u003Cbr \u002F>\nThe output of WP-Cache’s wp_cache_get_cookies_values() function.\u003C\u002Fp>\n\u003Cp>WP Super Cache has its own plugin system. This code is loaded when WP Super Cache loads and can be used to change how caching is done. This is before most of WordPress loads so some functionality will not be available. Plugins can be located anywhere that PHP can load them. Add your own plugin either:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>by putting your plugin in the wp-content\u002Fplugins\u002Fwp-super-cache-plugins directory, or\u003C\u002Fli>\n\u003Cli>by calling wpsc_add_plugin( $name ) where $name is the full filename and path to the plugin. You only need to call that function once to add it. Use wpsc_delete_plugin( $name ) to remove it from the list of loaded plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The cookies WP Super Cache uses to identify “known users” can be modified now by adding the names of those cookies to a list in the plugin configuration. Use wpsc_add_cookie( $name ) to add a new cookie, and wpsc_delete_cookie( $name ) to remove it. The cookie names also modify the mod_rewrite rules used by the plugin but I recommend using Simple mode caching to avoid complications with updating the .htaccess file.\u003Cbr \u002F>\nThe cookie name and value are used to differenciate users so you can have one cookie, but different values for each type of user on your site for example. They’ll be served different cache files.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\u002Fblob\u002F4cda5c0f2218e40e118232b5bf22d227fb3206b7\u002Fplugins\u002Fsearchengine.php\" rel=\"nofollow ugc\">plugins\u002Fsearchengine.php\u003C\u002Fa> as an example I use for my \u003Ca href=\"https:\u002F\u002Fodd.blog\u002Fno-adverts-for-friends\u002F\" rel=\"nofollow ugc\">No Adverts for Friends\u003C\u002Fa> plugin.\u003C\u002Fp>\n\u003Ch3>Troubleshooting\u003C\u002Fh3>\n\u003Cp>If things don’t work when you installed the plugin here are a few things to check:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Is wp-content writable by the web server?\u003C\u002Fli>\n\u003Cli>Is there a wp-content\u002Fwp-cache-config.php ? If not, copy the file wp-super-cache\u002Fwp-cache-config-sample.php to wp-content\u002Fwp-cache-config.php and make sure WPCACHEHOME points at the right place.\u003C\u002Fli>\n\u003Cli>Is there a wp-content\u002Fadvanced-cache.php ? If not, then you must copy wp-super-cache\u002Fadvanced-cache.php into wp-content\u002F. You must edit the file and change the path so it points at the wp-super-cache folder.\u003C\u002Fli>\n\u003Cli>If pages are not cached at all, remove wp-content\u002Fadvanced-cache.php and recreate it, following the advice above.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Make sure the following line is in wp-config.php and it is ABOVE the “require_once(ABSPATH.’wp-settings.php’);” line:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_CACHE', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>Try the Settings->WP Super Cache page again and enable cache.\u003C\u002Fli>\n\u003Cli>Look in wp-content\u002Fcache\u002Fsupercache\u002F. Are there directories and files there?\u003C\u002Fli>\n\u003Cli>Anything in your php error_log?\u003C\u002Fli>\n\u003Cli>If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression. Go to the Settings->WP Super Cache page and disable it there.\u003C\u002Fli>\n\u003Cli>The plugin does not work very well when PHP’s safe mode is active. This must be disabled by your administrator.\u003C\u002Fli>\n\u003Cli>If pages are randomly super cached and sometimes not, your blog can probably be viewed with and without the “www” prefix on the URL. You should choose one way and install the \u003Ca href=\"http:\u002F\u002Ftxfx.net\u002Fcode\u002Fwordpress\u002Fenforce-www-preference\u002F\" rel=\"nofollow ugc\">Enforce www preference\u003C\u002Fa> plugin if you are using an old WordPress install. The latest versions redirect themselves (you should always be running the latest version of WordPress anyway!)\u003C\u002Fli>\n\u003Cli>Private Server users at Dreamhost should edit wp-content\u002Fwp-cache-config.php and set the cache dir to “\u002Ftmp\u002F” if they are getting errors about increasing CPU usage. See this \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002F145895?replies=42\" rel=\"ugc\">discussion\u003C\u002Fa> for more.\u003C\u002Fli>\n\u003Cli>File locking errors such as “failed to acquire key 0x152b: Permission denied in…” or “Page not cached by WP Super Cache. Could not get mutex lock.” are a sign that you may have to use file locking. Edit wp-content\u002Fwp-cache-config.php and uncomment “$use_flock = true” or set $sem_id to a different value. You can also disable file locking from the Admin screen as a last resort.\u003C\u002Fli>\n\u003Cli>Make sure cache\u002Fwp_cache_mutex.lock is writable by the web server if using coarse file locking.\u003C\u002Fli>\n\u003Cli>The cache folder cannot be put on an NFS or Samba or NAS share. It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. If your hostname resolves to 127.0.0.1 it could be preventing the garbage collection from working. Check your access_logs for wp-cron.php entries. Do they return a 404 (file not found) or 200 code? If it’s 404 or you don’t see wp-cron.php anywhere WordPress may be looking for that script in the wrong place. You should speak to your server administator to correct this or edit \u002Fetc\u002Fhosts on Unix servers and remove the following line. Your hostname must resolve to the external IP address other servers on the network\u002FInternet use. See http:\u002F\u002Fyoast.com\u002Fwp-cron-issues\u002F for more. A line like “127.0.0.1 localhost localhost.localdomain” is ok.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>127.0.0.1 example.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don’t use Apache). 3 modules are required: mod_mime, mod_headers and mod_expires. The last two are especially important for making sure browsers load new versions of existing pages on your site.\u003C\u002Fli>\n\u003Cli>The error message, “WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content\u002Fadvanced-cache.php must be fixed!” appears at the end of every page. Open the file wp-content\u002Fadvanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content\u002Fplugins\u002Fwp-super-cache\u002F. If it is not correct the caching engine will not load.\u003C\u002Fli>\n\u003Cli>Caching doesn’t work. The timestamp on my blog keeps changing when I reload. Check that the path in your .htaccess rules matches where the supercache directory is. You may have to hardcode it. Try disabling supercache mode.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If supercache cache files are generated but not served, check the permissions on all your wp-content\u002Fcache\u002Fsupercache folders (and each of wp-content cache and supercache folders) and wp-content\u002Fcache\u002F.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WP_CACHE define.) Then clear your cache.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>umask( 0022 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server. In Apache you must disable mod_deflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.output_compression setting and make sure it’s “Off” or add this line to your .htaccess:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>php_flag zlib.output_compression off\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If that doesn’t work, add this line to your wp-config.php:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>ini_set('zlib.output_compression', 0);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>The “white screen of death” or a blank page  when you visit your site is almost always caused by a PHP error but \u003Ca href=\"http:\u002F\u002Fwww.johnberns.com\u002F2010\u002F03\u002F19\u002Fwp-super-cache-blank-page-problem-fixed\u002F\" rel=\"nofollow ugc\">it may also be caused by APC\u003C\u002Fa>. Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache.\u003C\u002Fli>\n\u003Cli>After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings->Permalink page and saving that form again.\u003C\u002Fli>\n\u003Cli>If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag?\u003C\u002Fli>\n\u003Cli>Your front  …\u003C\u002Fli>\n\u003C\u002Fol>\n","A very fast caching engine for WordPress that produces static html files.",1000000,62208732,86,1341,"2025-11-11T16:21:00.000Z","6.9.4","6.7",[53,54,55,56,23],"cache","caching","performance","wp-cache","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache.3.0.3.zip",95,12,"2022-10-03 00:00:00",{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":72,"num_ratings":73,"last_updated":74,"tested_up_to":75,"requires_at_least":76,"requires_php":77,"tags":78,"homepage":83,"download_link":84,"security_score":85,"vuln_count":33,"unpatched_count":27,"last_vuln_date":86,"fetched_at":29},"ilab-media-tools","Media Cloud for Bunny CDN, Amazon S3, Cloudflare R2, Google Cloud Storage, DigitalOcean and more","4.6.4","interfacelab","https:\u002F\u002Fprofiles.wordpress.org\u002Finterfacelab\u002F","\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002F3tB3rKkwAJY?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Cp>Media cloud is a revolutionary plug-in for WordPress that will supercharge the performance of your website and radically transform the way that you work with media in WordPress.\u003C\u002Fp>\n\u003Cp>Media Cloud works by moving your images, media and other files from your WordPress server to online cloud storage such as Amazon S3, Google Cloud Storage, DigitalOcean Spaces, DreamHost Object Storage and many others.  You can then serve that media through a CDN like Amazon Cloud front, Cloudflare, Fastly and others.\u003C\u002Fp>\n\u003Cp>Beyond cloud storage, Media Cloud also has deep integration with Imgix, the leading real-time image manipulation and optimization CDN.  Media Cloud is the first plugin for WordPress to bring the full benefit of what Imgix offers – simplifying your development efforts, reducing your site’s page load times and opening up creative options that simply haven’t existed until now.\u003C\u002Fp>\n\u003Cp>Media Cloud also provides advanced image editing tools that provide improved cropping options, effects, filters, watermarking and more.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE\u003C\u002Fstrong>: This plugin requires PHP 7.1 or higher\u003C\u002Fp>\n\u003Ch4>Upload to S3, Cloudflare R2, Minio, Google Cloud Storage, Digital Ocean Spaces, DreamHost Object Storage and others\u003C\u002Fh4>\n\u003Cp>Automatically copy media uploads to the cloud and serve them directly from your cloud storage provider, CloudFront or any other CDN.\u003C\u002Fp>\n\u003Ch4>Video Encoding with Mux\u003C\u002Fh4>\n\u003Cp>Upload videos and encode them nearly instantly to adaptive bitrate HLS that plays back smoothly and beautifully on any device regardless of bandwidth.  Requires an account with \u003Ca href=\"https:\u002F\u002Fmux.com\" rel=\"nofollow ugc\">Mux\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Integrate with Imgix\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fimgix.com\" rel=\"nofollow ugc\">Imgix\u003C\u002Fa> will radically change the way that you build your WordPress sites and themes.  This plugin is the best integration available for WordPress.  Upload your images to S3 with our S3 tool and then host the media with Imgix, providing you with real-time image processing and automatic format delivery.  Forget ImageMagick, Imgix is light years ahead in quality and speed.\u003C\u002Fp>\n\u003Ch4>Native support for Google Cloud Storage\u003C\u002Fh4>\n\u003Cp>Now supports using Google Cloud Storage for uploads without having to use Google’s S3 compatible interop mode.\u003C\u002Fp>\n\u003Ch4>Automatically Tag, Categorize and Caption with Amazon Rekognition\u003C\u002Fh4>\n\u003Cp>Use Amazon’s latest AI tools to tag and categorize your images when uploading to Amazon S3.  With Rekognition, you can automatically detect objects, scenes, and faces in images.\u003C\u002Fp>\n\u003Ch4>Advanced Image Editing\u003C\u002Fh4>\n\u003Cp>When integrating with \u003Ca href=\"https:\u002F\u002Fimgix.com\" rel=\"nofollow ugc\">Imgix\u003C\u002Fa>, Media Cloud by ILAB provides the most advanced WordPress image editor.  Alter contrast, saturation, vibrancy and over 30 other image editing operations – in real time right inside the WordPress admin interface!  Completely non-destructive!\u003C\u002Fp>\n\u003Ch4>Image Cropping\u003C\u002Fh4>\n\u003Cp>Media Cloud by ILAB ships with the most advanced image cropping tool available for WordPress, based on Chen Fengyuan’s amazing Cropper plugin for jQuery.\u003C\u002Fp>\n\u003Ch4>Compatible With Leading Image Optimizers\u003C\u002Fh4>\n\u003Cp>Compatible with Short Pixel, EWWW, Smush and Imagify image optimization plugins!\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Upload to any of a variety of cloud storage providers (Amazon S3, Cloudflare R2, Google Cloud Storage, Minio, Backblaze, DigitalOcean Spaces or any other S3 compatible service)\u003C\u002Fli>\n\u003Cli>Host your media directly from your cloud storage provider or specify a CDN\u003C\u002Fli>\n\u003Cli>Integrate with Imgix media hosting\u003C\u002Fli>\n\u003Cli>Use Amazon Rekognition to automatically tag and categorize images\u003C\u002Fli>\n\u003Cli>Use third party cloud file providers that use S3 compatible APIs\u003C\u002Fli>\n\u003Cli>Advanced image cropping tool\u003C\u002Fli>\n\u003Cli>Advanced image editing with saturation, contrast, auto-correct,\u003Cbr \u002F>\nsharpen, blur and more (only when integrated with Imgix)\u003C\u002Fli>\n\u003Cli>Automatically import your settings from WP Offload Media and WP-Stateless\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Premium Upgrade with Improved Support Options and More Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Built-in image optimization using leading image optimization services like ShortPixel, TinyPNG, Imagify and Kraken.io.  No more third party plugins needed because it’s built into Media Cloud’s process.\u003C\u002Fli>\n\u003Cli>Advanced security for encoded videos and a feature rich video player\u003C\u002Fli>\n\u003Cli>Easily import your existing media library with the push of a button\u003C\u002Fli>\n\u003Cli>WP-CLI support: Import your media library to the cloud, regenerate thumbnails and process your library with Amazon Rekognition using WP-CLI commands.\u003C\u002Fli>\n\u003Cli>Direct uploads integrated directly into WordPress’s media library\u003C\u002Fli>\n\u003Cli>Cloud storage browser that allows you to import media to your media library from the cloud\u003C\u002Fli>\n\u003Cli>WPML, WooCommerce and Easy Digital Downloads integration\u003C\u002Fli>\n\u003Cli>Blubrry Pod Casting, Ultimate Membership integrations\u003C\u002Fli>\n\u003Cli>Push\u002Fpull your CSS and JS assets to the cloud and serve them from a CDN\u003C\u002Fli>\n\u003Cli>Use Google Cloud Vision as a computer vision provider\u003C\u002Fli>\n\u003Cli>Image size manager\u003C\u002Fli>\n\u003Cli>Network level multisite support\u003C\u002Fli>\n\u003Cli>and more!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fmediacloud.press\u002Fcomparison\u002F\" rel=\"nofollow ugc\">Compare the premium plans\u003C\u002Fa>\u003C\u002Fp>\n","Automatically store media on Amazon S3, Cloudflare R2, Google Cloud Storage, DigitalOcean Spaces + others. Serve CSS\u002FJS assets through CDNs.",7000,539664,70,116,"2024-04-09T11:12:00.000Z","6.5.8","4.9","7.4",[79,20,80,81,82],"amazon","cloudflare","offload","s3","https:\u002F\u002Fgithub.com\u002Finterfacelab\u002Filab-media-tools","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Filab-media-tools.4.6.4.zip",92,"2024-03-25 00:00:00",{"slug":88,"name":89,"version":90,"author":91,"author_profile":92,"description":93,"short_description":94,"active_installs":70,"downloaded":95,"rating":96,"num_ratings":97,"last_updated":98,"tested_up_to":50,"requires_at_least":99,"requires_php":25,"tags":100,"homepage":103,"download_link":104,"security_score":11,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"wp-super-cache-clear-cache-menu","Clear All Cache for WP Super Cache","2.4","apasionados","https:\u002F\u002Fprofiles.wordpress.org\u002Fapasionados\u002F","\u003Cp>The plugin clears completely the cache from WP Super Cache, directly from the admin menu.\u003C\u002Fp>\n\u003Cp>We created this plugin, in order to be able to clear the cache completely  from the admin menu and not having to navigate to CONTENTS tab in WP Super Cache Settings.\u003C\u002Fp>\n\u003Cp>In some configuration WP Super Cache shows a menu entry to empty the cache in the menu, but it only empties the cache from the current page. See: \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fplugin-wp-super-cache-menu-delete-cache-doesnt-work-but-on-contents-page-it-does\" rel=\"ugc\">The “Delete Cache” button on the admin menu only deletes the cache for the current page.\u003C\u002Fa>\u003Cbr \u002F>\nNevertheless in the majority of the sites that have WP Super Cache installed it doesn’t display this menu entry.\u003C\u002Fp>\n\u003Cp>Please note that this menu option is only visible for WordPress ADMINISTRATORS.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>This is an add-on to WP SUPER CACHE:\u003C\u002Fstrong>\u003Cbr \u002F>\n  Please keep in mind that this plugin is an add-on to the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F\" rel=\"ugc\">WP SUPER CACHE\u003C\u002Fa> plugin. You need to install and activate WP SUPER CACHE so that this add-on works.\u003C\u002Fp>\n\u003Cp>If you are having trouble with this plugin, feel free to use the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwp-super-cache-clear-cache-menu\" rel=\"ugc\">Clear All Cache for WP Super Cache Support\u003C\u002Fa>. If you are having problems with the WP SUPER CACHE plugin, you should ask for support at \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwp-super-cache\" rel=\"ugc\">WP Super Cache Support\u003C\u002Fa>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>What can I do with this plugin?\u003C\u002Fh4>\n\u003Cp>The plugin clears completely the cache from WP Super Cache, directly from the admin menu.\u003C\u002Fp>\n\u003Ch4>Clear All Cache for WP Super Cache Plugin in your Language!\u003C\u002Fh4>\n\u003Cp>This first release is avaliable in English and Spanish. In the languages folder we have included the necessarry files to translate this plugin.\u003C\u002Fp>\n\u003Cp>If you would like the plugin in your language and you’re good at translating, please drop us a line at \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-wp-super-cache-clear-cache-menu-home\" rel=\"nofollow ugc\">Contact us\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Further Reading\u003C\u002Fh4>\n\u003Cp>You can access the description of the plugin in Spanish at: \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fblog\u002Fvaciar-cache-wp-super-cache-plugin-wordpress-1933\u002F\" rel=\"nofollow ugc\">Clear All Cache for WP Super Cache Plugin en castellano\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Contact\u003C\u002Fh3>\n\u003Cp>For further information please send us an \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-wp-super-cache-clear-cache-menu-contact\" rel=\"nofollow ugc\">email\u003C\u002Fa>.\u003C\u002Fp>\n","Clear all cache for WP Super Cache adds a menu entry to the admin menu to clear the cache completely .",279587,62,11,"2026-02-01T14:44:00.000Z","3.0.1",[53,54,101,102,55],"empty-cache","emtpy-wp-super-cache","https:\u002F\u002Fapasionados.es\u002Fblog\u002Fvaciar-cache-wp-super-cache-plugin-wordpress-1933\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache-clear-cache-menu.2.4.zip",{"slug":106,"name":107,"version":108,"author":109,"author_profile":110,"description":111,"short_description":112,"active_installs":113,"downloaded":114,"rating":47,"num_ratings":115,"last_updated":116,"tested_up_to":117,"requires_at_least":118,"requires_php":119,"tags":120,"homepage":122,"download_link":123,"security_score":11,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"the-cache-purger","The Cache Purger","2.1.63","Kevin Pirnie","https:\u002F\u002Fprofiles.wordpress.org\u002Fkevp75\u002F","\u003Cp>\u003Cstrong>The Cache Purger\u003C\u002Fstrong> takes the headache out of cache management. Instead of juggling a dozen different cache-clearing buttons across your stack, this plugin hooks into WordPress actions and fires them all at once — automatically, on a schedule, or with a single click from the admin bar.\u003C\u002Fp>\n\u003Cp>It covers the full spectrum: popular caching plugins, managed hosting environments, PHP-level caches (OPcache, APC, WinCache), server-level caches (Nginx, Varnish, PageSpeed), in-memory stores (Redis, Memcache, Memcached), and external CDN\u002FWAF APIs (Cloudflare, Sucuri, Fastly).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Every purge is configurable.\u003C\u002Fstrong> Choose which cache types to include, which WordPress events should trigger a purge, and which specific posts, pages, CPTs, or field groups to exclude. You can also run purges on a WP Cron schedule, or kick one off manually via WP-CLI.\u003C\u002Fp>\n\u003Ch4>What Gets Purged\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Caching Plugins\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Flying Press, SiteGround Optimizer, Nginx Helper, LiteSpeed Cache, Cachify, Autoptimize, Fast Velocity Minify, WP Rocket, Swift Performance, Comet Cache, Hummingbird, WP Fastest Cache, WP Super Cache, W3 Total Cache, Hyper Cache, WP-Optimize, Cache Enabler, NitroPack, Divi, Elementor, WP REST Cache, and more.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Hosting Environments\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>WP Engine, Kinsta, GoDaddy Managed WordPress, Pantheon, Bluehost, Cloudways (Breeze), SiteGround, RunCloud, SpinupWP.\u003C\u002Fp>\n\u003Cp>Some of these rely on the host’s companion plugin being installed. Check with your provider if you’re unsure.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Server & PHP Caches\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Zend OPcache, APC\u002FAPCu, WinCache, XCache, Nginx (fastcgi\u002Fproxy cache), PageSpeed Module, Varnish, static file caches.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Memory Stores\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Redis, Memcache, Memcached — with support for remote servers, authentication, per-database flushing, and prefix\u002Fkey-scoped clearing.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>CDN & WAF APIs\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Cloudflare (full cache purge via API token), Sucuri WAF, Fastly CDN.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>WordPress Built-In\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Object cache, options cache, transients, persistent object cache.\u003C\u002Fp>\n\u003Ch4>Purge Triggers\u003C\u002Fh4>\n\u003Cp>Configure purges to fire automatically on any combination of the following WordPress events:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Post save \u002F update \u002F trash\u003C\u002Fli>\n\u003Cli>Page save \u002F update \u002F trash\u003C\u002Fli>\n\u003Cli>Custom Post Type save \u002F update \u002F trash\u003C\u002Fli>\n\u003Cli>Taxonomy \u002F term save \u002F delete\u003C\u002Fli>\n\u003Cli>Category save \u002F delete\u003C\u002Fli>\n\u003Cli>Menu save \u002F delete\u003C\u002Fli>\n\u003Cli>Widget save \u002F delete\u003C\u002Fli>\n\u003Cli>Customizer save\u003C\u002Fli>\n\u003Cli>GravityForms form save \u002F trash \u003Cem>(requires GravityForms)\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Advanced Custom Fields field group save \u002F trash \u003Cem>(requires ACF)\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>WooCommerce settings save \u003Cem>(requires WooCommerce)\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>Plugin activation \u002F deactivation\u003C\u002Fli>\n\u003Cli>Core \u002F plugin \u002F theme updates\u003C\u002Fli>\n\u003Cli>Plugin settings save \u003Cem>(this plugin’s own settings page)\u003C\u002Fem>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Exclusion lists are available for posts, pages, CPTs, GravityForms forms, and ACF field groups — so you can carve out anything that shouldn’t trigger a purge.\u003C\u002Fp>\n\u003Ch4>Additional Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Admin bar button\u003C\u002Fstrong> — Master Cache Purge available on every admin page, one click from anywhere.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purge log\u003C\u002Fstrong> — Optional logging of every purge action to \u003Ccode>wp-content\u002Fpurge.log\u003C\u002Fcode>, viewable directly in the settings UI with a one-click clear.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Scheduled purges\u003C\u002Fstrong> — WP Cron \u002F Action Scheduler integration with any built-in schedule.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Scheduled log clearing\u003C\u002Fstrong> — Keep your log file tidy on its own schedule.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Export \u002F Import settings\u003C\u002Fstrong> — Move your configuration between sites in seconds.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Multisite aware\u003C\u002Fstrong> — Cannot be network-activated by design; activate per-subsite for granular control.\u003C\u002Fli>\n\u003C\u002Ful>\n","Automatically purge every server-side cache on your WordPress site — plugins, hosting environments, PHP, memory stores, and CDNs — all from one place.",1000,16064,4,"2026-03-06T19:10:00.000Z","7.0","6.0","8.2",[53,21,54,55,121],"purge-cache","https:\u002F\u002Fkevinpirnie.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fthe-cache-purger.2.1.63.zip",{"slug":125,"name":126,"version":127,"author":128,"author_profile":129,"description":130,"short_description":131,"active_installs":132,"downloaded":133,"rating":11,"num_ratings":134,"last_updated":135,"tested_up_to":136,"requires_at_least":137,"requires_php":77,"tags":138,"homepage":141,"download_link":142,"security_score":143,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"cache-purge-helper","Cache Purge Helper","0.1.3","jordantrizz","https:\u002F\u002Fprofiles.wordpress.org\u002Fjordantrizz\u002F","\u003Cp>This plugin will trigger a cache purge using the LSCache or Nginx Helper plugin when hooks are fired by popular plugins or themes.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>If using the LSCache plugin, Litespeed Enterprise or Openlightspeed is required to purge server cache.\u003C\u002Fli>\n\u003Cli>If using the Nginx Helper plugin, Nginx cache method FastCGI or Nginx Redi Cache is required to purge server cache.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The following themes and plugins hooks are used.\u003C\u002Fp>\n\u003Ch3>WordPress Core Hooks\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>upgrader_process_complete\u003C\u002Fli>\n\u003Cli>activated_plugin\u003C\u002Fli>\n\u003Cli>deactivated_plugin\u003C\u002Fli>\n\u003Cli>switch_theme\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Beaver Builder Plugin\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>fl_builder_cache_cleared\u003C\u002Fli>\n\u003Cli>fl_builder_after_save_layout\u003C\u002Fli>\n\u003Cli>fl_builder_after_save_user_template\u003C\u002Fli>\n\u003Cli>upgrader_process_complete\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Elementor Plugin\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>elementor\u002Fcore\u002Ffiles\u002Fclear_cache\u003C\u002Fli>\n\u003Cli>update_option__elementor_global_css\u003C\u002Fli>\n\u003Cli>delete_option__elementor_global_css\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Autoptimizer Plugin\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>delete_option__elementor_global_css\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Oxygen Theme\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>wp_ajax_oxygen_vsb_cache_generated\u003C\u002Fli>\n\u003Cli>update_option__oxygen_vsb_universal_css_url\u003C\u002Fli>\n\u003Cli>update_option__oxygen_vsb_css_files_state\u003C\u002Fli>\n\u003C\u002Ful>\n","A helper plugin to purge cache via the LSCache and Nginx Helper plugins for popular WordPress plugins and themes.",300,8997,2,"2021-12-21T21:00:00.000Z","5.8.13","3.0",[53,22,139,140],"nginx","purge","https:\u002F\u002Fwpinfo.net","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purge-helper.0.1.4.zip",85,{"attackSurface":145,"codeSignals":185,"taintFlows":213,"riskAssessment":240,"analyzedAt":250},{"hooks":146,"ajaxHandlers":169,"restRoutes":180,"shortcodes":181,"cronEvents":182,"entryPointCount":134,"unprotectedCount":27},[147,153,157,161,165],{"type":148,"name":149,"callback":150,"file":151,"line":152},"action","admin_menu","bunnycdn_cache_purger_menu","cache-purger-for-bunnycdn.php",18,{"type":148,"name":154,"callback":155,"file":151,"line":156},"admin_init","bunnycdn_cache_purger_settings",82,{"type":148,"name":158,"callback":159,"file":151,"line":160},"bunnycdn_purge_event","bunnycdn_bulk_purge_cache",250,{"type":148,"name":162,"callback":163,"file":151,"line":164},"save_post","bunnycdn_purge_on_update",253,{"type":148,"name":166,"callback":167,"file":151,"line":168},"admin_enqueue_scripts","enqueue_bunny_admin_scripts",501,[170,176],{"action":171,"nopriv":172,"callback":173,"hasNonce":174,"hasCapCheck":172,"file":151,"line":175},"fetch_bunny_zones",false,"fetch_bunny_zones_callback",true,448,{"action":177,"nopriv":172,"callback":178,"hasNonce":174,"hasCapCheck":172,"file":151,"line":179},"save_bunny_zone","save_bunny_zones_callback",478,[],[],[183],{"hook":158,"callback":158,"file":151,"line":184},247,{"dangerousFunctions":186,"sqlUsage":187,"outputEscaping":200,"fileOperations":27,"externalRequests":134,"nonceChecks":134,"capabilityChecks":27,"bundledLibraries":212},[],{"prepared":33,"raw":115,"locations":188},[189,192,195,197],{"file":151,"line":190,"context":191},58,"$wpdb->get_results() with variable interpolation",{"file":151,"line":193,"context":194},152,"$wpdb->get_var() with variable interpolation",{"file":151,"line":196,"context":191},154,{"file":151,"line":198,"context":199},158,"$wpdb->query() with variable interpolation",{"escaped":201,"rawEcho":115,"locations":202},14,[203,206,208,210],{"file":151,"line":204,"context":205},111,"raw output",{"file":151,"line":207,"context":205},117,{"file":151,"line":209,"context":205},123,{"file":151,"line":211,"context":205},127,[],[214,232],{"entryPoint":215,"graph":216,"unsanitizedCount":27,"severity":231},"save_bunny_zones_callback (cache-purger-for-bunnycdn.php:479)",{"nodes":217,"edges":229},[218,223],{"id":219,"type":220,"label":221,"file":151,"line":222},"n0","source","$_POST (x3)",491,{"id":224,"type":225,"label":226,"file":151,"line":227,"wp_function":228},"n1","sink","update_option() [Settings Manipulation]",494,"update_option",[230],{"from":219,"to":224,"sanitized":174},"low",{"entryPoint":233,"graph":234,"unsanitizedCount":27,"severity":231},"\u003Ccache-purger-for-bunnycdn> (cache-purger-for-bunnycdn.php:0)",{"nodes":235,"edges":238},[236,237],{"id":219,"type":220,"label":221,"file":151,"line":222},{"id":224,"type":225,"label":226,"file":151,"line":227,"wp_function":228},[239],{"from":219,"to":224,"sanitized":174},{"summary":241,"deductions":242},"The \"cache-purger-for-bunnycdn\" plugin v2.0 exhibits a generally good security posture based on the provided static analysis. The plugin has a small attack surface with no unprotected entry points, and it utilizes nonce checks for its AJAX handlers. The absence of dangerous functions, file operations, and critical or high severity taint flows is a significant strength. Furthermore, the plugin has no recorded vulnerability history, which suggests a commitment to security by the developers or a lack of past discovered issues.\n\nHowever, there are areas for improvement. While most output is properly escaped, a small percentage is not, which could potentially lead to cross-site scripting (XSS) vulnerabilities if certain conditions are met. The plugin also makes external HTTP requests, which, although not inherently a vulnerability, can be a vector for certain attacks if the target endpoint is compromised or the request is not properly validated. The low percentage of SQL queries using prepared statements, coupled with the total number of queries, indicates a potential risk for SQL injection vulnerabilities, especially if any unsanitized user input is directly incorporated into these queries.\n\nIn conclusion, this plugin appears to be relatively secure with a strong foundation. The absence of known vulnerabilities and a protected attack surface are positive indicators. The primary concerns revolve around the unescaped outputs, external HTTP requests, and the prevalent use of raw SQL queries. Addressing these areas would further enhance the plugin's security.",[243,246,248],{"reason":244,"points":245},"SQL queries not using prepared statements",8,{"reason":247,"points":14},"Unescaped output found",{"reason":249,"points":134},"External HTTP requests made","2026-03-16T21:02:29.833Z",{"wat":252,"direct":261},{"assetPaths":253,"generatorPatterns":256,"scriptPaths":257,"versionParams":258},[254,255],"\u002Fwp-content\u002Fplugins\u002Fcache-purger-for-bunnycdn\u002Fcss\u002Fadmin-style.css","\u002Fwp-content\u002Fplugins\u002Fcache-purger-for-bunnycdn\u002Fjs\u002Fadmin-script.js",[],[255],[259,260],"cache-purger-for-bunnycdn\u002Fcss\u002Fadmin-style.css?ver=","cache-purger-for-bunnycdn\u002Fjs\u002Fadmin-script.js?ver=",{"cssClasses":262,"htmlComments":263,"htmlAttributes":267,"restEndpoints":271,"jsGlobals":272,"shortcodeOutput":273},[],[264,265,266],"\u003C!-- Display the purge logs directly below the settings -->","\u003C!-- If the column doesn't exist, add it -->","\u003C!-- If the table doesn't exist, create it -->",[268,269,270],"id=\"fetchZonesButton\"","id=\"bunny_zone_name\"","id=\"bunny_zone\"",[],[],[]]