[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fOAWBroHmygaBvfSAAev754IaCySGQd6oPMqZLRkJPvY":3,"$f9VOckCQFifDoj0val2HBTHJKzqUK1ZGNIh6jMI2PR38":271,"$fDFoMLGFsO7p830TdXJZUn41un-9ZFdCOFsaC7vMjhSA":275},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":35,"analysis":137,"fingerprints":239},"cache-purge-for-azure-front-door","Cache Purge for Azure Front Door","1.3","hiberus","https:\u002F\u002Fprofiles.wordpress.org\u002Fhiberus\u002F","\u003Cul>\n\u003Cli>\u003Cstrong>Manual Purge Control:\u003C\u002Fstrong> Execute a global cache purge (\u002F*) at the click of a button from the admin interface.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Connection Validator:\u003C\u002Fstrong> Quickly verify if your Azure credentials (Tenant ID, Client ID, etc.) are correctly configured.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Detailed Activity Logs:\u003C\u002Fstrong> A comprehensive history of all purge actions, showing who triggered the purge, the result, and the API response time.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Security Focused:\u003C\u002Fstrong> Built using WordPress best practices, including Settings API and secure AJAX handlers.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This plugin uses Azure’s REST API to send cache invalidation requests. It is lightweight and non-intrusive.\u003Cbr \u002F>\nThis plugin is not affiliated with Microsoft. “Azure” and “Azure Front Door” are trademarks of Microsoft Corporation.\u003Cbr \u002F>\nFor more details, see the official \u003Ca href=\"https:\u002F\u002Flearn.microsoft.com\u002Fen-us\u002Frest\u002Fapi\u002Ffrontdoor\u002Fazurefrontdoorstandardpremium\u002Fafd-endpoints\u002Fpurge-content\" rel=\"nofollow ugc\">Azure Front Door Purge Content API documentation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin relies on the \u003Cstrong>Azure Management API\u003C\u002Fstrong> to perform cache purges.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Service:\u003C\u002Fstrong> Azure Management API (https:\u002F\u002Fmanagement.azure.com)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purpose:\u003C\u002Fstrong> This service is used to send purge commands to your Azure Front Door profile.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Sent:\u003C\u002Fstrong> No user data is sent. The plugin only sends the content paths (URLs) to be purged and the authentication token provided by your Azure Tenant.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Terms of Service:\u003C\u002Fstrong> \u003Ca href=\"https:\u002F\u002Fazure.microsoft.com\u002Fen-us\u002Fsupport\u002Flegal\u002F\" rel=\"nofollow ugc\">Azure Legal Information\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>This plugin sends requests to the Azure API to purge cache. It does not transmit or store any personal user data. It is fully GDPR-compliant.\u003C\u002Fp>\n","Manage and execute Azure Front Door cache purges from your WordPress dashboard.",0,222,"2026-02-09T12:02:00.000Z","6.9.4","5.8","7.4",[18,19,20,21,22],"azure","cache","cdn","front-door","purge","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purge-for-azure-front-door.1.3.zip",100,null,"2026-04-06T09:54:40.288Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,94,"2026-05-19T18:33:19.979Z",[36,55,74,91,115],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":25,"downloaded":44,"rating":45,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":23,"tags":50,"homepage":51,"download_link":52,"security_score":53,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":54},"akamai","Akamai for WordPress","0.6.0","akamaidevrel","https:\u002F\u002Fprofiles.wordpress.org\u002Fakamaidevrel\u002F","\u003Cp>The Akamai for WordPress plugin will automatically purge the cache using the new Fast Purge feature whenever you create or update a post.\u003C\u002Fp>\n\u003Cp>With the Fast Purge API, you can automate your publishing flow to maximize performance and offload without compromising on freshness. Switching to a Hold ‘Til Told methodology, you can cache semi-dynamic content with long TTLs, and then refresh it in approximately 5 seconds with Fast Purge.\u003C\u002Fp>\n\u003Ch4>Development & Support\u003C\u002Fh4>\n\u003Cp>This plugin is developed on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fakamai\u002Fwp-akamai\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>. Issues should be filed \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fakamai\u002Fwp-akamai\u002Fissues\" rel=\"nofollow ugc\">here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>References\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdeveloper.akamai.com\" rel=\"nofollow ugc\">Akamai OPEN APIs\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdeveloper.akamai.com\u002Fintroduction\u002FIdentity_Model.html\" rel=\"nofollow ugc\">Akamai Credentials\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdeveloper.akamai.com\u002Fapi\u002Fpurge\u002Fccu\u002Foverview.html\" rel=\"nofollow ugc\">Content Control Utility API v3 (CCUv3) Documentation\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","The Akamai for WordPress plugin integrates automatically with Akamai to purge the cache when you create or update a post\u002Fpage.",12206,40,2,"2018-03-30T19:27:00.000Z","4.9.29","4.3",[37,19,20,22],"http:\u002F\u002Fgithub.com\u002Fakamai\u002Fwp-akamai","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fakamai.zip",85,"2026-04-16T10:56:18.058Z",{"slug":56,"name":57,"version":58,"author":59,"author_profile":60,"description":61,"short_description":62,"active_installs":63,"downloaded":64,"rating":25,"num_ratings":31,"last_updated":65,"tested_up_to":66,"requires_at_least":67,"requires_php":23,"tags":68,"homepage":71,"download_link":72,"security_score":73,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":54},"purgebox","PURGE BOX","1.9","katsuhisa ogawa","https:\u002F\u002Fprofiles.wordpress.org\u002Fredboxcdn\u002F","\u003Cp>合同会社レッドボックスが国内向けに提供している「エッジキャッシュCDN」全サービスでご利用できるWordpress用キャッシュ削除プラグインです。\u003C\u002Fp>\n\u003Cp>プラグインを導入後、APIキーとグループ名を設定するだけで、\u003Cbr \u002F>\n固定ページ・投稿の修正やアップデートが即時反映されます。\u003C\u002Fp>\n","合同会社レッドボックスが提供している「定額CDN エッジキャッシュCDN」全サービスでご利用できるWordpress用キャッシュ削除プラグインです。",10,1886,"2024-12-22T10:43:00.000Z","6.7.5","4.6",[69,20,22,70],"cache-delete","redbox","https:\u002F\u002Fja.wordpress.org\u002Fplugins\u002Fpurgebox\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpurgebox.zip",92,{"slug":75,"name":76,"version":77,"author":78,"author_profile":79,"description":80,"short_description":81,"active_installs":11,"downloaded":82,"rating":11,"num_ratings":11,"last_updated":83,"tested_up_to":14,"requires_at_least":84,"requires_php":85,"tags":86,"homepage":89,"download_link":90,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":54},"naibabiji-cache-purger-for-edgeone","Naibabiji Cache Purger for EdgeOne","2.3.0","奶爸建站笔记","https:\u002F\u002Fprofiles.wordpress.org\u002Fnaibabiji\u002F","\u003Cp>A powerful WordPress plugin that automatically purges Tencent Cloud EdgeOne cache when your posts, pages, or custom post types are published, updated, or deleted.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin connects to the Tencent Cloud EdgeOne API (https:\u002F\u002Fteo.tencentcloudapi.com) to provide cache purging and prefetching functionality.\u003C\u002Fp>\n\u003Cp>It sends the Following information to Tencent Cloud when a purge or prefetch operation is triggered (e.g., when a post is updated, or when manual purge is used):\u003Cbr \u002F>\n*   Tencent Cloud API Credentials (SecretId): Used for request authentication and signing.\u003Cbr \u002F>\n*   EdgeOne Zone ID: Used to identify the specific site\u002Fzone in EdgeOne.\u003Cbr \u002F>\n*   Target URLs or Paths: The specific resources that need to be cleared or prefetched from the CDN nodes.\u003C\u002Fp>\n\u003Cp>This service is provided by “Tencent Cloud”: \u003Ca href=\"https:\u002F\u002Fcloud.tencent.com\u002Fdocument\u002Fproduct\u002F301\u002F127483\" rel=\"nofollow ugc\">Terms of Service\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fcloud.tencent.com\u002Fdocument\u002Fproduct\u002F301\u002F11470\" rel=\"nofollow ugc\">Privacy Policy\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Ch4>Automatic Cache Purge\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Automatically purges cache when posts are published, updated, or deleted\u003C\u002Fli>\n\u003Cli>Supports all public post types (posts, pages, and custom post types)\u003C\u002Fli>\n\u003Cli>Smart purge: automatically refreshes post pages, homepage, category archives, tag archives, author archives, and date archives\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Comment Integration\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Automatically purges related post cache when new comments are approved\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Manual Purge\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Support for manual purge of specific posts or entire site\u003C\u002Fli>\n\u003Cli>Quick purge buttons in admin panel for recent posts\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Flexible Configuration\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Choose purge method: delete cache (delete) or mark as expired (invalidate)\u003C\u002Fli>\n\u003Cli>Optional logging of purge operations\u003C\u002Fli>\n\u003Cli>Secure key configuration via wp-config.php constants\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Cache Plugin Integration\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Automatically purges EdgeOne cache when popular WordPress cache plugins clear their cache\u003C\u002Fli>\n\u003Cli>Supports WP Super Cache, W3 Total Cache, WP Rocket, and LiteSpeed Cache\u003C\u002Fli>\n\u003Cli>Force mode ensures cache plugin integrations work even when auto purge is disabled\u003C\u002Fli>\n\u003Cli>Proper timing control ensures compatibility with all cache plugin loading sequences\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Cache Prefetching\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Optional cache prefetching after purging (disabled by default)\u003C\u002Fli>\n\u003Cli>Only prefetches post URLs, not archive pages to conserve EdgeOne prefetch quota\u003C\u002Fli>\n\u003Cli>Ensures first visitor gets cached content immediately\u003C\u002Fli>\n\u003Cli>Prefetch results are displayed in the purge logs for easy monitoring\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Enhanced Logging\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Detailed logging of all purge operations with success\u002Ffailure status\u003C\u002Fli>\n\u003Cli>Manual log clearing functionality for easier debugging\u003C\u002Fli>\n\u003Cli>Prefetch operation results displayed alongside purge results\u003C\u002Fli>\n\u003Cli>Job IDs and error messages for easy troubleshooting\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Advanced Manual Purge\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Optimized host-specific “Purge All” using the purge_host method\u003C\u002Fli>\n\u003Cli>Manual purge operations are not affected by auto purge settings\u003C\u002Fli>\n\u003Cli>Force mode support for cache plugin integrations\u003C\u002Fli>\n\u003Cli>Comprehensive URL coverage for post-related purges\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Custom URL Purge\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Purge cache for specific URLs (CSS, JS, images, etc.)\u003C\u002Fli>\n\u003Cli>Support for directory prefix purge using trailing slash (\u002F)\u003C\u002Fli>\n\u003Cli>Batch processing: enter multiple URLs, one per line\u003C\u002Fli>\n\u003Cli>Automatic URL validation and filtering\u003C\u002Fli>\n\u003Cli>Smart type detection: files use purge_url, directories use purge_prefix\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Nginx Cache Integration\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Optionally clear Nginx server-side page cache (FastCGI cache or Proxy cache) alongside EdgeOne CDN cache\u003C\u002Fli>\n\u003Cli>Configured separately — most sites using only WordPress cache plugins do not need this\u003C\u002Fli>\n\u003Cli>Nginx cache and EdgeOne cache are cleared independently; either can succeed even if the other fails\u003C\u002Fli>\n\u003Cli>Includes path validation with real-time feedback in the settings page\u003C\u002Fli>\n\u003Cli>Uses ngx_cache_purge module for precise URL-based cache clearing (faster and more efficient)\u003C\u002Fli>\n\u003Cli>Added “Purge Endpoint Path” option for customizable Nginx purge URL path (e.g., use a random string like \u002FxK9mPurge_q7z for better security)\u003C\u002Fli>\n\u003Cli>Uses HTTPS requests to your site’s own domain for purge, avoiding HTTP-to-HTTPS redirect issues\u003C\u002Fli>\n\u003Cli>Friendly error messages in purge logs: clearly explains why a URL wasn’t cached (e.g., “Not cached — the page was returned instead of a purge response”) instead of showing raw HTML\u003C\u002Fli>\n\u003Cli>Fallback to file deletion for full-site purge operations\u003C\u002Fli>\n\u003Cli>Detailed per-URL purge logging for Nginx cache operations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>No SDK Required\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Direct API calls, no need to install Tencent Cloud SDK\u003C\u002Fli>\n\u003Cli>Compatible with all WordPress versions 5.5+\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Configuration\u003C\u002Fh3>\n\u003Ch4>Get Tencent Cloud API Keys\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Visit \u003Ca href=\"https:\u002F\u002Fconsole.cloud.tencent.com\u002Fcam\u002Fcapi\" rel=\"nofollow ugc\">Tencent Cloud Console\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Create or get your \u003Ccode>SecretId\u003C\u002Fcode> and \u003Ccode>SecretKey\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Get EdgeOne Zone ID\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Visit \u003Ca href=\"https:\u002F\u002Fconsole.cloud.tencent.com\u002Fteo\" rel=\"nofollow ugc\">EdgeOne Console\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Select your site and find the Zone ID (format: zone-xxxxxx)\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Configure Plugin\u003C\u002Fh4>\n\u003Cp>There are two configuration methods:\u003C\u002Fp>\n\u003Ch3>Method 1: Using wp-config.php (Recommended)\u003C\u002Fh3>\n\u003Cp>Add these constants to your WordPress \u003Ccode>wp-config.php\u003C\u002Fcode> file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'NB_CACHE_PURGER_SECRET_ID', 'your-secret-id' );\ndefine( 'NB_CACHE_PURGER_SECRET_KEY', 'your-secret-key' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Then in WordPress admin:\u003Cbr \u002F>\n1. Go to “Settings” \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> “Naibabiji Cache Purger”\u003Cbr \u002F>\n2. Fill in the \u003Cstrong>Zone ID\u003C\u002Fstrong> (Secret ID and Secret Key will be automatically loaded from constants)\u003Cbr \u002F>\n3. Choose other options and save\u003C\u002Fp>\n\u003Ch3>Method 2: Direct Configuration in Admin\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Log in to WordPress admin\u003C\u002Fli>\n\u003Cli>Go to “Settings” \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> “Naibabiji Cache Purger”\u003C\u002Fli>\n\u003Cli>Fill in the following information:\n\u003Cul>\n\u003Cli>\u003Cstrong>Secret ID\u003C\u002Fstrong>: Tencent Cloud API Secret ID\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Secret Key\u003C\u002Fstrong>: Tencent Cloud API Secret Key\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Zone ID\u003C\u002Fstrong>: EdgeOne Zone ID\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Choose other options:\n\u003Cul>\n\u003Cli>\u003Cstrong>Enable Auto Purge\u003C\u002Fstrong>: Whether to automatically purge cache when posts are updated\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purge Method\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>\u003Ccode>delete\u003C\u002Fcode>: Directly delete node cache\u003C\u002Fli>\n\u003Cli>\u003Ccode>invalidate\u003C\u002Fcode>: Mark as expired, revalidate from origin\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enable Logging\u003C\u002Fstrong>: Whether to log purge operations\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Nginx Cache Integration (Optional)\u003C\u002Fh4>\n\u003Cp>Only needed if your server uses Nginx FastCGI cache or Proxy cache (configured via \u003Ccode>fastcgi_cache_path\u003C\u002Fcode> or \u003Ccode>proxy_cache_path\u003C\u002Fcode> in nginx.conf). Most sites using WordPress cache plugins do not need this.\u003C\u002Fp>\n\u003Col>\n\u003Cli>In “Settings” \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> “Naibabiji Cache Purger” \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> scroll to the \u003Cstrong>Nginx Cache Integration\u003C\u002Fstrong> section at the bottom\u003C\u002Fli>\n\u003Cli>Check \u003Cstrong>Enable Nginx Cache Purge\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>Set a \u003Cstrong>Purge Endpoint Path\u003C\u002Fstrong> — we recommend using a random string (e.g., \u003Ccode>\u002FxK9mPurge_q7z\u003C\u002Fcode>) for security, so you can use \u003Ccode>allow all;\u003C\u002Fcode> in Nginx without exposing the endpoint to attackers\u003C\u002Fli>\n\u003Cli>Enter the absolute filesystem path to your Nginx cache zone directory (e.g. \u003Ccode>\u002Fvar\u002Frun\u002Fnginx-cache\u003C\u002Fcode>) — this is only used as fallback when purging the entire site\n\u003Cul>\n\u003Cli>The web server process (e.g. \u003Ccode>www-data\u003C\u002Fcode>) must have write permission to this directory\u003C\u002Fli>\n\u003Cli>The settings page will validate the path and show whether it is writable\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Save settings — Nginx cache will now be cleared automatically every time EdgeOne cache is purged\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Nginx Purge Configuration\u003C\u002Fh4>\n\u003Cp>To use the ngx_cache_purge module integration, you need to configure your Nginx server block with the appropriate purge rules. Replace \u003Ccode>\u002FxK9mPurge_q7z\u003C\u002Fcode> with your custom purge path:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>nginx\nlocation ~ \u002FxK9mPurge_q7z(\u002F.*) {\n    allow all;\n    deny none;\n    fastcgi_cache_purge YOUR_CACHE_ZONE \"https$request_method$host$1\";\n    # Or for proxy cache:\n    # proxy_cache_purge YOUR_CACHE_ZONE \"https$request_method$host$1\";\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Replace \u003Ccode>YOUR_CACHE_ZONE\u003C\u002Fcode> with the name of your Nginx cache zone (e.g., \u003Ccode>wordpress\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important notes:\u003C\u002Fstrong>\u003Cbr \u002F>\n* The \u003Ccode>fastcgi_cache_purge\u003C\u002Fcode> key (\u003Ccode>\"https$request_method$host$1\"\u003C\u002Fcode>) must match your \u003Ccode>fastcgi_cache_key\u003C\u002Fcode> directive exactly, including the \u003Ccode>https\u003C\u002Fcode> prefix\u003Cbr \u002F>\n* If you are using BT Panel (宝塔) with an HTTP-to-HTTPS redirect rule, the plugin sends HTTPS requests to your own domain, so no additional exclusion rules are needed\u003Cbr \u002F>\n* For detailed configuration instructions, see the \u003Ca href=\"https:\u002F\u002Fwww.quhenet.com\u002Fbt-panel-nginx-fastcgi\u002F\" rel=\"nofollow ugc\">configuration tutorial\u003C\u002Fa>\u003C\u002Fp>\n","Automatically purge Tencent Cloud EdgeOne cache when WordPress posts are published, updated, or deleted.",166,"2026-04-15T01:28:00.000Z","5.0","7.2",[19,20,87,22,88],"edgeone","tencent-cloud","https:\u002F\u002Fblog.naibabiji.com\u002Ffiles\u002Fwordpress-plugins\u002Fedgeone-purge.html","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnaibabiji-cache-purger-for-edgeone.2.3.0.zip",{"slug":92,"name":93,"version":94,"author":95,"author_profile":96,"description":97,"short_description":98,"active_installs":99,"downloaded":100,"rating":101,"num_ratings":102,"last_updated":103,"tested_up_to":104,"requires_at_least":105,"requires_php":104,"tags":106,"homepage":110,"download_link":111,"security_score":112,"vuln_count":113,"unpatched_count":11,"last_vuln_date":114,"fetched_at":54},"speedycache","SpeedyCache – Cache, Optimization, Performance","1.3.9","Softaculous","https:\u002F\u002Fprofiles.wordpress.org\u002Fsoftaculous\u002F","\u003Cp>SpeedyCache is a WordPress cache plugin that helps you improve performance of your WordPress site by caching, minifying, and compressing your website.\u003C\u002Fp>\n\u003Cp>You can find our official documentation at \u003Ca href=\"https:\u002F\u002Fspeedycache.com\u002Fdocs\" rel=\"nofollow ugc\">https:\u002F\u002Fspeedycache.com\u002Fdocs\u003C\u002Fa>. We are also active in our community support forums on wordpress.org if you are one of our free users. Our Premium Support Ticket System is at \u003Ca href=\"https:\u002F\u002Fsoftaculous.deskuss.com\" rel=\"nofollow ugc\">https:\u002F\u002Fsoftaculous.deskuss.com\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fspeedycache.com\" title=\"SpeedyCache Homepage\" rel=\"nofollow ugc\">Home Page\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fsoftaculous.deskuss.com\" title=\"SpeedyCache Support\" rel=\"nofollow ugc\">Support\u003C\u002Fa> | \u003Ca href=\"http:\u002F\u002Fspeedycache.com\u002Fdocs\" title=\"Documents\" rel=\"nofollow ugc\">Documents\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Other than caching SpeedyCache can also do the following:-\u003Cbr \u002F>\n1. It can minify and combine CSS\u002FJS giving even better optimization as it reduces the file sizes and reduces the HTTP requests to the server.\u003Cbr \u002F>\n2. Eliminate render-blocking JavaScript resources helping your website to load faster.\u003Cbr \u002F>\n3. Lazy load images so that the images can be requested only if they come into the viewport.\u003Cbr \u002F>\n4. GZIP files to reduce the size of the file sent from the server.\u003C\u002Fp>\n\u003Ch3>Free Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Caching:\u003C\u002Fstrong> Storing copies of the web pages of the desktop version. Caching happens when a user visits a webpage on your website\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Preload:\u003C\u002Fstrong> Preload makes sure the user always sees the cached version of your website as it periodically creates cache.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Combine CSS:\u003C\u002Fstrong> Combines CSS files present in the header of the page reducing HTTP requests.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Minify CSS:\u003C\u002Fstrong> Reduces the size of the CSS files.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Automatic Cache:\u003C\u002Fstrong> Creates cache of post when it gets deleted if preload is enabled.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Combine JS:\u003C\u002Fstrong> Combines JS files present in the header of the page reducing HTTP requests.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>GZIP:\u003C\u002Fstrong> It applies GZIP compression on the files hence reducing the file size sent from the server.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Browser Caching:\u003C\u002Fstrong> Caches the website on the browser of the client for repeating visitors.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>DNS-Prefetch:\u003C\u002Fstrong> DNS prefetch is a technique that improves website performance by resolving domain names in advance, before they are needed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Disable Emojis:\u003C\u002Fstrong> You can remove the emoji inline CSS and wp-emoji-release.min.js.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Exclude:\u003C\u002Fstrong> You can exclude certain Pages, User-Agent, Cookies, CSS, or JS from being cached.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>CDN:\u003C\u002Fstrong> CDN helps improve website speed by placing the static files of your cached on their network of servers hence helping deliver content faster at any point in the world.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Display Swap:\u003C\u002Fstrong> Adds display swap to Google font URL, so when Google font loads the font will stay visible this is enabled by default.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purge Varnish:\u003C\u002Fstrong> If enabled it will purge Varnish cache, whenever cache from SpeedyCache is purged.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gravatar Cache:\u003C\u002Fstrong> Host Gravatars on your server.\u003C\u002Fli>\n\u003Cli>*Improve Font Rendering:** Adding CSS property of text-rendering to prioritize speed of render of Fonts.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>GET SUPPORT AND PRO FEATURES\u003C\u002Fh3>\n\u003Cp>Get professional support and more features to make your website load faster with \u003Ca href=\"https:\u002F\u002Fspeedycache.com\u002Fpricing\" rel=\"nofollow ugc\">SpeedyCache\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Pro Features:-\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Image Optimization:\u003C\u002Fstrong> Image optimization is a way to convert an image to next-gen image formats like webp which load images faster on the web.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Instant Page:\u003C\u002Fstrong> It loads the page just before user clicks the link, reducing the page load time.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Google Fonts:\u003C\u002Fstrong> Google fonts are also seen as render-blocking so this feature helps load Google fonts asynchronously.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Local Google Fonts:\u003C\u002Fstrong> Cache the Google fonts to be compliant with the GDPR rules.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lazy Load:\u003C\u002Fstrong> Loading all assets at once can make the page load slower hence lazy load helps by only loading certain resources when they come into the viewport.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Minify HTML:\u003C\u002Fstrong> It removes empty lines, line breaks, minifies inline Js And Css, removes comments and space in Tags\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Minify JS:\u003C\u002Fstrong> Reduces JS file size.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Delay JS:\u003C\u002Fstrong> Delays the JS to load on user interaction to reduce or remove the issue of Unused JS.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Advanced Combine JS:\u003C\u002Fstrong> Combines JS files placed in the footer section helping reduce HTTP calls.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Render blocking JS:\u003C\u002Fstrong> Before rendering a page the browser parses the HTML to create a DOM tree and if an external script comes it has to stop and wait for the script to execute hence the rendering of the page ends up taking time, hence Render blocking JS feature helps in deferring the load of JS after the render has happened hence the first load get faster.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Delete Cache Stats:\u003C\u002Fstrong> Provides statistics about the cached files of Desktop or Mobile version and combined\u002F minified version of CSS and JS.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mobile Cache:\u003C\u002Fstrong> Caches the mobile version of your website and shows that version on mobile devices.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Database Cleanup:\u003C\u002Fstrong> Database cleanup helps you free up your database storage from temporary data, trashed contents, and post revisions which may take a lot of your database storage.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>PreConnect:\u003C\u002Fstrong> Preconnect improves website loading times by establishing early connections to third-party domains.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Preload:\u003C\u002Fstrong> Preload improves website performance by downloading resources in advance, before they are needed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Critical CSS:\u003C\u002Fstrong> Extracts the CSS used by the page in the visible viewport at the time of load.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Unused CSS:\u003C\u002Fstrong> Removes the unused CSS, keeping the CSS that is being used by the paged, which reduces the size of CSS used on the page.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Object Cache:\u003C\u002Fstrong> It makes the object to persist by using Redis, to improve availability of the cache.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bloat Remover:\u003C\u002Fstrong> Options to remove unnecessary features of WordPress or WooCommerce.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Image Dimension:\u003C\u002Fstrong> Adds dimensions to the image tag which does not have width or height, to reduce (CLS)Cumulative Layout Shift.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lazy Render HTML:\u003C\u002Fstrong> User can lazy render HTML elements which are not in view-port.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Preload Critical Images:\u003C\u002Fstrong> Preload above-the-fold images to improve LCP(Largest Contentful paint).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Caching\u003C\u002Fh3>\n\u003Cp>SpeedyCache caches the website by creating static files on the server and delivers those static files to most of the users who visit the website, The static files eliminate the heavy load of Querying the database for data hence the load of your website is faster.\u003C\u002Fp>\n\u003Cp>You can preload as many pages as you want, and preloading caches the website in regular intervals of time to reduce the load on the server.\u003C\u002Fp>\n\u003Cp>Deleting Cache on New\u002Fupdating Post.\u003Cbr \u002F>\nYou can decide to delete the cache on the creation or updating of a post so that the cache can always stay updated.\u003C\u002Fp>\n\u003Ch3>Minifying\u002FCombining CSS and JS\u003C\u002Fh3>\n\u003Cp>SpeedyCache helps minify the JS and CSS hence it reduces the file sizes.\u003Cbr \u002F>\nCombining JS combines the CSS and JS fines reducing the file count and making the server handle lesser requests.\u003C\u002Fp>\n\u003Ch3>Cache Lifespan\u003C\u002Fh3>\n\u003Cp>Cache Lifespan is a way to schedule the deletion of cache.\u003C\u002Fp>\n\u003Ch3>Exclude\u003C\u002Fh3>\n\u003Cp>Exclude is a way to prevent SpeedyCache from caching certain files\u002F user-agents\u002F cookies.\u003C\u002Fp>\n\u003Ch3>CDN (Content Delivery Network)\u003C\u002Fh3>\n\u003Cp>CDN helps you host your static content on a distributed network optimized to deliver internet content faster it’s not a replacement to a web host. It caches your files on the network edge and delivers the content to the user through the closest and fastest server.\u003Cbr \u002F>\nSpeedyCache helps you integrate a CDN by rewriting the URLs of the static files you want to host on the CDN or in the Case of Cloudflare it helps with the purging of the cache on the Cloudflare servers.\u003C\u002Fp>\n\u003Ch3>[Pro] Image Optimization\u003C\u002Fh3>\n\u003Cp>Image optimization is a way to convert your images from old formats like JPG and PNG to the new next-gen formats like webp which is designed with the web as the target platform to load images faster. webp images result in smaller and richer images that make the web faster.\u003Cbr \u002F>\nWe provide 3 ways to convert your images to webp.\u003Cbr \u002F>\nGD(a PHP extension), Imagick(a PHP extension), and cwebp(a webp conversion utility from Google).\u003C\u002Fp>\n\u003Ch3>[Pro] Bloat Remover\u003C\u002Fh3>\n\u003Cp>SpeedyCache has 12 bloat removal options which are listed below.\u003Cbr \u002F>\n1. Disable Dashicons\u003Cbr \u002F>\n2. Update Heartbeat\u003Cbr \u002F>\n3. Limit Post Revisions\u003Cbr \u002F>\n4. Disable XML-RPC\u003Cbr \u002F>\n5. Disable Google Fonts\u003Cbr \u002F>\n6. Disable jQuery Migrate\u003Cbr \u002F>\n7. Disable RSS feeds\u003Cbr \u002F>\n8. Disable Gutenberg\u003Cbr \u002F>\n9. Disable OEmbeds\u003Cbr \u002F>\n10. Disable Block Editor CSS\u003Cbr \u002F>\n11. Disable Cart Fragments\u003Cbr \u002F>\n12. Disable WooCommerce Assets\u003C\u002Fp>\n\u003Ch3>[Pro] Database Cleanup\u003C\u002Fh3>\n\u003Cp>Data cleanup cleans the database by removing the following data:-\u003Cbr \u002F>\n1. Post Revisions\u003Cbr \u002F>\n2. Trashed Content\u003Cbr \u002F>\n3. Trashed and Spam comments\u003Cbr \u002F>\n4. Trackbacks and pingbacks\u003Cbr \u002F>\n5. All Transient options\u003Cbr \u002F>\n6. Expired Transient Options\u003C\u002Fp>\n","SpeedyCache is a WordPress cache plugin that helps you improve performance of your WordPress site by caching, minifying, and compressing your website.",600000,4158248,90,28,"2026-03-31T12:58:00.000Z","7.0","4.7",[19,20,107,108,109],"minify","pagespeed","seo","https:\u002F\u002Fspeedycache.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fspeedycache.1.3.9.zip",97,4,"2024-08-16 00:00:00",{"slug":116,"name":117,"version":118,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":123,"downloaded":124,"rating":125,"num_ratings":126,"last_updated":127,"tested_up_to":14,"requires_at_least":128,"requires_php":16,"tags":129,"homepage":23,"download_link":133,"security_score":134,"vuln_count":135,"unpatched_count":11,"last_vuln_date":136,"fetched_at":54},"breeze","Breeze Cache","2.4.4","Cloudways","https:\u002F\u002Fprofiles.wordpress.org\u002Fcloudways\u002F","\u003Cp>Breeze is a free, simple (yet powerful) and user-friendly caching plugin developed by the Cloudways team. It offers various options to optimize WordPress site performance at various levels. It works equally great with WordPress, WordPress with WooCommerce and WordPress Multisite.\u003C\u002Fp>\n\u003Cp>Breeze excels in the following areas:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Performance:\u003C\u002Fstrong> Breeze improves website speed and resource optimization. Other features include file level cache system, database cleanup, minification, support for Varnish cache and simplified CDN integration options.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Convenience:\u003C\u002Fstrong> Breeze is easy to install and configure directly from WordPress. Configuring Breeze is easy and most of the default options work well right out of the box. The recommended settings should work on all your WordPress websites seamlessly.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Simplicity:\u003C\u002Fstrong> Breeze is designed to be simple for all users. Just install and activate the plugin and you’ll see the results instantaneously.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>What makes Breeze Cache Plugin awesome is that it comes with builtin support for Varnish. If Varnish is not installed on your servers, Breeze will utilize its internal cache mechanism to boost up your WordPress site performance.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>FEATURES\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Seamless integration with Varnish Cache for efficient content delivery. No manual adjustments needed – all settings come pre-configured for your convenience.\u003C\u002Fli>\n\u003Cli>Optimize performance using Cloudflare’s caching capabilities. No specific Breeze configurations are needed – it works out of the box.\u003C\u002Fli>\n\u003Cli>Effortlessly integrate your preferred Content Delivery Network (CDN) for global content distribution with Breeze instead of using the the CDN providers’ plugins.\u003C\u002Fli>\n\u003Cli>Trim WordPress database bloat effortlessly. Breeze’s Database Options optimize and declutter your database, boosting performance by removing unneeded data like post revisions and trashed content.\u003C\u002Fli>\n\u003Cli>Take command over caching exclusions. With Breeze, you have the power to prevent specific URLs, JS files, and CSS files from being cached.\u003C\u002Fli>\n\u003Cli>Achieve smaller page sizes and faster load times through HTML, CSS, and JavaScript minification, including inline CSS and JavaScript minification.\u003C\u002Fli>\n\u003Cli>Load images when they’re visible, not all at once, for faster webpage performance by implementing lazy loading for images.\u003C\u002Fli>\n\u003Cli>Load JS files with deferred loading, enhancing overall performance.\u003C\u002Fli>\n\u003Cli>Supercharge your site’s speed with Breeze’s advanced preloading features: load fonts early, quicken link clicks, and enhance DNS requests for a seamless user experience.\u003C\u002Fli>\n\u003Cli>Master real-time interactions with Breeze’s Heartbeat API management. Fine-tune notifications, sales data, autosaves, and more to optimize WordPress website performance by adjusting API call frequencies.\u003C\u002Fli>\n\u003Cli>Effortlessly manage Breeze settings using Import\u002FExport. Download your configurations as a .json file for backup, or effortlessly import existing settings to quickly fine-tune your optimization.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Support:\u003C\u002Fstrong> We love to provide support! Post your questions on the WordPress.org support forums, or if you are a Cloudways Customer you may ask questions on the \u003Ca href=\"https:\u002F\u002Fcommunity.cloudways.com\u002F\" rel=\"nofollow ugc\">Cloudways Community Forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cp>PHP 7.4, PHP 8 recommended for better performance, WordPress 6.0+\u003C\u002Fp>\n","Breeze is a caching plugin developed by Cloudways. Breeze uses advance caching systems to improve site loading times exponentially.",400000,14131951,70,124,"2026-04-08T09:32:00.000Z","6.0",[19,130,20,131,132],"caching","performance","wp-cache","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbreeze.2.4.4.zip",89,9,"2026-04-22 13:59:41",{"attackSurface":138,"codeSignals":169,"taintFlows":229,"riskAssessment":230,"analyzedAt":238},{"hooks":139,"ajaxHandlers":154,"restRoutes":166,"shortcodes":167,"cronEvents":168,"entryPointCount":46,"unprotectedCount":11},[140,146,150],{"type":141,"name":142,"callback":143,"file":144,"line":145},"action","admin_init","azure_cache_purge_register_settings","cache-purge-for-azure-front-door.php",69,{"type":141,"name":147,"callback":148,"file":144,"line":149},"admin_menu","azure_cache_purge_add_admin_menu",169,{"type":141,"name":151,"callback":152,"file":153,"line":53},"admin_enqueue_scripts","azure_cache_purge_admin_enqueue_scripts","includes\\admin\\admin-enqueue.php",[155,162],{"action":156,"nopriv":157,"callback":158,"hasNonce":159,"hasCapCheck":159,"file":160,"line":161},"azure_check_connection",false,"azure_cache_purge_ajax_check_connection",true,"includes\\admin\\admin-ajax.php",41,{"action":163,"nopriv":157,"callback":164,"hasNonce":159,"hasCapCheck":159,"file":160,"line":165},"azure_manual_purge","azure_cache_purge_ajax_manual_purge",67,[],[],[],{"dangerousFunctions":170,"sqlUsage":171,"outputEscaping":177,"fileOperations":11,"externalRequests":46,"nonceChecks":227,"capabilityChecks":227,"bundledLibraries":228},[],{"prepared":172,"raw":31,"locations":173},8,[174],{"file":144,"line":175,"context":176},188,"$wpdb->query() with variable interpolation",{"escaped":178,"rawEcho":179,"locations":180},63,23,[181,185,187,189,192,194,196,197,199,201,203,205,207,209,211,213,215,217,219,221,223,224,225],{"file":182,"line":183,"context":184},"templates\\admin\\main-page.php",13,"raw output",{"file":182,"line":186,"context":184},18,{"file":182,"line":188,"context":184},22,{"file":190,"line":191,"context":184},"templates\\filters\\activity-filters.php",27,{"file":190,"line":193,"context":184},31,{"file":190,"line":195,"context":184},34,{"file":190,"line":161,"context":184},{"file":190,"line":198,"context":184},43,{"file":190,"line":200,"context":184},53,{"file":190,"line":202,"context":184},55,{"file":190,"line":204,"context":184},59,{"file":190,"line":206,"context":184},61,{"file":190,"line":208,"context":184},71,{"file":190,"line":210,"context":184},83,{"file":190,"line":212,"context":184},84,{"file":190,"line":214,"context":184},88,{"file":216,"line":179,"context":184},"templates\\filters\\activity-table.php",{"file":216,"line":218,"context":184},24,{"file":216,"line":220,"context":184},25,{"file":216,"line":222,"context":184},26,{"file":216,"line":191,"context":184},{"file":216,"line":102,"context":184},{"file":216,"line":226,"context":184},47,3,[],[],{"summary":231,"deductions":232},"The 'cache-purge-for-azure-front-door' plugin version 1.3 exhibits a generally strong security posture based on the provided static analysis.  The plugin has a limited attack surface with only two AJAX entry points, and importantly, both are protected by authentication checks.  The code demonstrates good practices with a high percentage of SQL queries using prepared statements and a substantial amount of output escaping.  Furthermore, the absence of dangerous functions, file operations, and critical\u002Fhigh severity taint flows is highly positive.  The plugin also benefits from a clean vulnerability history with no recorded CVEs, indicating consistent security maintenance and awareness by the developers.\n\nDespite the positive indicators, there are minor areas for improvement.  While the overall output escaping is good, a portion remains unescaped, which could be a potential vector for cross-site scripting (XSS) vulnerabilities if user-controlled data is involved.  Similarly, the presence of external HTTP requests, though only two, warrants careful monitoring as these can sometimes be exploited if not handled securely.  The absence of known vulnerabilities is a significant strength, but it's crucial to remember that no software is entirely immune, and ongoing vigilance is always recommended.\n\nIn conclusion, this plugin appears to be developed with security in mind, adhering to many best practices. The protected entry points, use of prepared statements, and lack of historical vulnerabilities are commendable. The minor concerns revolve around the unescaped outputs and external HTTP requests, which, given the context and limited nature, are likely low-risk but should be considered for further hardening.",[233,236],{"reason":234,"points":235},"Unescaped output found",5,{"reason":237,"points":46},"External HTTP requests present","2026-03-17T07:34:15.817Z",{"wat":240,"direct":255},{"assetPaths":241,"generatorPatterns":247,"scriptPaths":248,"versionParams":249},[242,243,244,245,246],"\u002Fwp-content\u002Fplugins\u002Fcache-purge-for-azure-front-door\u002Fassets\u002Fjs\u002Fazure-tools.js","\u002Fwp-content\u002Fplugins\u002Fcache-purge-for-azure-front-door\u002Fassets\u002Fjs\u002Fdate-range-picker.js","\u002Fwp-content\u002Fplugins\u002Fcache-purge-for-azure-front-door\u002Fassets\u002Flibraries\u002Fflatpickr.min.css","\u002Fwp-content\u002Fplugins\u002Fcache-purge-for-azure-front-door\u002Fassets\u002Flibraries\u002Fflatpickr.min.js","\u002Fwp-content\u002Fplugins\u002Fcache-purge-for-azure-front-door\u002Fassets\u002Flibraries\u002Fes.js",[],[242,243,245,246],[250,251,252,253,254],"cache-purge-for-azure-front-door\u002Fassets\u002Fjs\u002Fazure-tools.js?ver=","cache-purge-for-azure-front-door\u002Fassets\u002Fjs\u002Fdate-range-picker.js?ver=","cache-purge-for-azure-front-door\u002Fassets\u002Flibraries\u002Fflatpickr.min.css?ver=","cache-purge-for-azure-front-door\u002Fassets\u002Flibraries\u002Fflatpickr.min.js?ver=","cache-purge-for-azure-front-door\u002Fassets\u002Flibraries\u002Fes.js?ver=",{"cssClasses":256,"htmlComments":257,"htmlAttributes":258,"restEndpoints":267,"jsGlobals":268,"shortcodeOutput":270},[],[],[259,260,261,262,263,264,265,266],"data-i18n-checkButton","data-i18n-purgeButton","data-i18n-checking","data-i18n-purging","data-i18n-confirmCheck","data-i18n-confirmPurge","data-i18n-networkError","data-i18n-unexpectedError",[],[269],"AzurePurge",[],{"error":159,"url":272,"statusCode":273,"statusMessage":274,"message":274},"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fcache-purge-for-azure-front-door\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":227,"versions":276},[277,282,289],{"version":6,"download_url":24,"svn_tag_url":278,"released_at":26,"has_diff":157,"diff_files_changed":279,"diff_lines":26,"trac_diff_url":280,"vulnerabilities":281,"is_current":159},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcache-purge-for-azure-front-door\u002Ftags\u002F1.3\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fcache-purge-for-azure-front-door%2Ftags%2F1.2&new_path=%2Fcache-purge-for-azure-front-door%2Ftags%2F1.3",[],{"version":283,"download_url":284,"svn_tag_url":285,"released_at":26,"has_diff":157,"diff_files_changed":286,"diff_lines":26,"trac_diff_url":287,"vulnerabilities":288,"is_current":157},"1.2","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purge-for-azure-front-door.1.2.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcache-purge-for-azure-front-door\u002Ftags\u002F1.2\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fcache-purge-for-azure-front-door%2Ftags%2F1.1&new_path=%2Fcache-purge-for-azure-front-door%2Ftags%2F1.2",[],{"version":290,"download_url":291,"svn_tag_url":292,"released_at":26,"has_diff":157,"diff_files_changed":293,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":294,"is_current":157},"1.1","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purge-for-azure-front-door.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcache-purge-for-azure-front-door\u002Ftags\u002F1.1\u002F",[],[]]