[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f8QwNfAUKlQ_EIMkNr-8BdUTN15_-8OI7ZZSSPIVAWuc":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":36,"analysis":134,"fingerprints":179},"rocketfront-connect","RocketFront Connect","1.0.1","kodeala","https:\u002F\u002Fprofiles.wordpress.org\u002Fkodeala\u002F","\u003Cp>RocketFront Connect simplifies cache management and ensures optimal content delivery by connecting WP Rocket Cache with AWS CloudFront through C3 Cloudfront Cache Controller. This plugin requires both WP Rocket and C3 Cloudfront Cache Controller to be installed and activated. With this integration, CloudFront cache is automatically cleared whenever WP Rocket cache is cleared, guaranteeing that your website’s content remains up-to-date and is delivered swiftly to your users.\u003C\u002Fp>\n","Automate AWS CloudFront CDN clearing and cache management by seamlessly integrating the WP Rocket plugin with C3 Cloudfront Cache Controller.",20,1037,0,"2025-08-27T15:45:00.000Z","6.8.5","5.0","7.0",[19,20,21,22,23],"c3-cloudfront-cache-controller","cdn","cloudfront","rocketfront","wp-rocket","https:\u002F\u002Fwww.kodeala.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frocketfront-connect.1.0.1.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":26,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},3,60,30,94,"2026-04-04T21:12:07.499Z",[37,55,76,96,116],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":31,"last_updated":48,"tested_up_to":15,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":53,"download_link":54,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"c3-cloudfront-clear-cache","C3 Cloudfront Cache Controller","7.3.1","hide","https:\u002F\u002Fprofiles.wordpress.org\u002Fhideokamoto\u002F","\u003Cp>This is simple plugin that clear all cloudfront cache if you publish posts.\u003Cbr \u002F>\nYou can easy use CloudFront in front of WordPress.\u003C\u002Fp>\n\u003Ch3>Fixtures\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>wp_is_mobile()\u003Cbr \u002F>\nCheck device viewer type by CloudFront header.\u003Cbr \u002F>\nNow supports \u003Ccode>HTTP_CLOUDFRONT_IS_MOBILE_VIEWER\u003C\u002Fcode> and \u003Ccode>HTTP_CLOUDFRONT_IS_TABLET_VIEWER\u003C\u002Fcode>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>preview url\u003Cbr \u002F>\nIn preview page, plugin add \u003Ccode>post_date\u003C\u002Fcode> query to avoid CloudFront cache.\u003Cbr \u002F>\nAnd set \u003Ccode>wordpress_loginuser_last_visit\u003C\u002Fcode> cookie for avoid CloudFront cache too.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The \u003Ccode>wordpress_loginuser_last_visit\u003C\u002Fcode> cookie will be removed if user sign out.\u003C\u002Fp>\n\u003Ch4>Invalidation(Clear Cache) Page URL\u003C\u002Fh4>\n\u003Cp>This plugin send following page url to CloudFront Invalidation API.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>TOP page URL\u003C\u002Fli>\n\u003Cli>Published Post Page URL\u003C\u002Fli>\n\u003Cli>Category Archive Page URL\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>AWS IAM Policy Example\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>{\n    \"Version\": \"2012-10-17\",\n    \"Statement\": [\n        {\n            \"Action\": [\n                \"cloudfront:GetDistribution\",\n                \"cloudfront:ListInvalidations\",\n                \"cloudfront:GetStreamingDistribution\",\n                \"cloudfront:GetDistributionConfig\",\n                \"cloudfront:GetInvalidation\",\n                \"cloudfront:CreateInvalidation\"\n            ],\n            \"Effect\": \"Allow\",\n            \"Resource\": \"*\"\n        }\n    ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> The \u003Ccode>cloudfront:GetInvalidation\u003C\u002Fcode> permission is required for viewing detailed invalidation information. If this permission is not granted, the detail view feature will be disabled gracefully without affecting other plugin functionality.\u003C\u002Fp>\n\u003Ch3>Adding your configuration through env vars\u003C\u002Fh3>\n\u003Cp>The plugin can be configured by defining the following variables:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>AWS_ACCESS_KEY_ID\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>AWS_SECRET_ACCESS_KEY\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>C3_DISTRIBUTION_ID\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You can put these variables like the code into the wp-config.php\u003C\u002Fp>\n\u003Cpre>\u003Ccode>php\ndefine( 'AWS_ACCESS_KEY_ID', '' );\ndefine( 'AWS_SECRET_ACCESS_KEY', '' );\ndefine( 'C3_DISTRIBUTION_ID', '' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Cookie\u003C\u002Fh3>\n\u003Cp>This plugin set a Cookie named \u003Ccode>wordpress_loginuser_last_visit\u003C\u002Fcode> to the user.\u003Cbr \u002F>\nIt prevents CDN caching when the user is previewing his posts or contents.\u003Cbr \u002F>\nOnce logging out from Dashboard, plugin removes this cookie from user.\u003C\u002Fp>\n\u003Ch3>7.1.0\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Feature] Add invalidation detail view with modal popup showing invalidation paths, caller reference, and status\u003C\u002Fli>\n\u003Cli>[Fix] Fix invalid path returned for post type without archive page\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>7.0.1\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Update] Improved AWS API call processing for better security and PHP 8.x compatibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>7.0.0\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Breaking Change] Remove AWS SDK dependency and implement custom HTTP CloudFront API client\u003C\u002Fli>\n\u003Cli>[Update] Add comprehensive invalidation logging with c3_log_invalidation_list filter\u003C\u002Fli>\n\u003Cli>[Update] Add configurable CloudFront region and HTTP timeout settings\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.1.6\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Fix] Fixed PHP 8 syntax errors by adding nullable type hints\u003C\u002Fli>\n\u003Cli>[Fix] Fixed deprecation warnings about creation of dynamic properties in Invalidation_Service.php\u003C\u002Fli>\n\u003Cli>[Fix] Fixed deprecation warnings about creation of dynamic properties in Cron_Service.php\u003C\u002Fli>\n\u003Cli>[Fix] Fixed PHP 7.4 syntax errors in test files\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.1.5\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Fix] Changed to install the AWS SDK using composer instead of aws.phar.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.1.4\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Update] Support post_type_archive_link\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.1.3\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Fix] Lost filter c3_invalidation_items From v6.0.0\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.1.2\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Fix] php version compare issue\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.1.1\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Fix] Plugin deactivation issue\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.1.0\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Update] Flush cache by post_ids\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.0.0\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Breaking Change] Re-write entire code\u003C\u002Fli>\n\u003Cli>[Update] Add \u003Ccode>c3_log_cron_invalidation_task\u003C\u002Fcode> filter to show cron job Logs\u003C\u002Fli>\n\u003Cli>[Update] Add \u003Ccode>c3_aws_sdk_path\u003C\u002Fcode> filter to change or remove bundled AWS SDK path\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>5.5.1\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Update] Replace the top level menu with a Settings submenu\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.5.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Update] Can use defined variables for AWS Credentials\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.4.2\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Bug fix] Set cookie path in preview page\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.4.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Bug fix] Undefined Paths index in invalidation query cron event\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.4.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Update] Update preview fix plugin\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.3.4\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Bug fix] Small bug fix\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.3.3\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Change SDK] replace sdk\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.3.2\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Bug fix] Use EC2 role if using as AMIMOTO Managed hosting\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.3.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Add filter] Can select AWS SDK version by filter\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.3.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Update SDK] Use AWS SDK v3 when you using php 5.6 or later\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.2.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[For AMIMOTO Managed] bug fix to run by WP-CLI\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.2.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Add filter] We can disable to register wp-cron that retry request invalidation.\u003C\u002Fli>\n\u003Cli>[Readme] Update readme to see IAM Policy example.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.1.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>[Update preview fixture] Set cookie to avoid CloudFront cache if user sign in\u003C\u002Fli>\n\u003Cli>[Update preview fixture] Unset cookie for avoide CloudFront cache if user sign out\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>5.0.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Support CloudFront viewer params on \u003Ccode>wp_is_mobile()\u003C\u002Fcode>.(4.9.0 or later)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.4.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix small bug\u003C\u002Fli>\n\u003Cli>Add some feature for AMIMOTO Managed hosting user\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.3.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix cron interval\u003C\u002Fli>\n\u003Cli>add filters \u003Ccode>'c3_invalidation_interval\u003C\u002Fcode>, \u003Ccode>c3_invalidation_cron_interval\u003C\u002Fcode>, \u003Ccode>c3_invalidation_item_limits\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>update default invalidation interval & items.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.3.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Schedule cron event if you published many post at the same time\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.2.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix ‘c3_credential’ filter position\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.2.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Support AMIMOT Dashboard\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.1.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Show Invalidation Logs\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.0.3\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Auto Deploy by Travis\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.0.2\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Add WP-CLI param check ( wp c3 flush)\u003C\u002Fli>\n\u003Cli>change transient_key\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.0.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Bug fix ( conflict Nephila Clavata )\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>4.0.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Support AWS SDK Version3\u003C\u002Fli>\n\u003Cli>Remove action hook -> ‘c3_add_setting_before’\u003Cbr \u002F>\nuse ‘c3_after_title’ filter hook instead.\u003C\u002Fli>\n\u003Cli>Remove action hook -> ‘c3_add_setting_after’\u003Cbr \u002F>\nuse ‘c3_after_auth_form’ filter hook instead.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>3.0.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Include CF Preview Fix plugin\u003C\u002Fli>\n\u003Cli>Rename\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.4.3\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix Catch Exception BUG\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.4.2\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix CLI BUG\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.4.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix CLI BUG\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.4.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Add WP-CLI Command ( Update Settings )\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.3.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Add WP-CLI Command\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.2.2\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Force Invalidation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.2.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix Typo\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.2.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Add Filter for using EC2 Instance Role.\u003C\u002Fli>\n\u003Cli>Translationable in t.w.org\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.1.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fix too many invalidation url error.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.1.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Add hook to customize invalidation URL\u003C\u002Fli>\n\u003Cli>support new invalidation url, terms.\u003C\u002Fli>\n\u003Cli>Manualy invalidation button added\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.0.2\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Change AWS SDK\u003C\u002Fli>\n\u003Cli>code refactoring by wokamoto\u003C\u002Fli>\n\u003Cli>Invalidation URL\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>2.0.1\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Change AWS SDK\u003C\u002Fli>\n\u003Cli>code refactoring by wokamoto\u003C\u002Fli>\n\u003Cli>Invalidation URL\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>1.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Initial released.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>6.1.0\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[Fix] Plugin deactivation issue\u003C\u002Fli>\n\u003C\u002Ful>\n","This is simple plugin that clear all cloudfront cache if you publish posts.",3000,272378,86,"2026-02-18T06:51:00.000Z","4.9.0","7.4",[52,20,21],"aws","https:\u002F\u002Fgithub.com\u002Famimoto-ami\u002Fc3-cloudfront-clear-cache","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fc3-cloudfront-clear-cache.7.3.1.zip",{"slug":56,"name":57,"version":58,"author":59,"author_profile":60,"description":61,"short_description":62,"active_installs":63,"downloaded":64,"rating":34,"num_ratings":65,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":50,"tags":69,"homepage":72,"download_link":73,"security_score":26,"vuln_count":74,"unpatched_count":13,"last_vuln_date":75,"fetched_at":28},"aws-cdn-by-wpadmin","WPAdmin AWS CDN","4.0.1","luckychingi","https:\u002F\u002Fprofiles.wordpress.org\u002Fluckychingi\u002F","\u003Cp>The new & improved Amazon Cloudfront Distribution Plugin by WPAdmin. Setup Amazon Cloudfront CDN for your website. Now with intuitive layout and more flexibility. The new & improved Amazon Cloudfront Distribution Plugin by WPAdmin. Setup Amazon Cloudfront CDN for your website. Now with intuitive layout and more flexibility. Also supports WordPress Multisite installation (not tested though).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>One-click distribution creation\u003C\u002Fstrong> – Create CloudFront distributions directly from WordPress\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Full CDN settings control\u003C\u002Fstrong> – Configure cache policy, TLS version, price class, and compression\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Custom domain support\u003C\u002Fstrong> – Use your own CDN domain (e.g., cdn.yoursite.com)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SSL certificate management\u003C\u002Fstrong> – Request free SSL certificates from AWS Certificate Manager\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Smart URL rewriting\u003C\u002Fstrong> – Automatically rewrites media, CSS, and JS URLs to use CloudFront\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Granular exclusions\u003C\u002Fstrong> – Exclude specific pages and assets containing certain keywords\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sub-folder & sub-domain support\u003C\u002Fstrong> – Works with all WordPress installation types\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cache invalidation\u003C\u002Fstrong> – Purge CloudFront cache directly from WordPress\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Enable\u002Fdisable toggle\u003C\u002Fstrong> – Instantly switch CDN on or off without losing settings\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Built-in documentation\u003C\u002Fstrong> – Comprehensive how-it-works guide and FAQ\u003C\u002Fli>\n\u003C\u002Ful>\n","Setup Amazon Cloudfront CDN for your website. Now with intuitive layout and more flexibility.",500,90059,53,"2026-02-12T14:21:00.000Z","6.9.4","5.6",[70,52,20,21,71],"amazon","free","https:\u002F\u002Fwpadmin.ca\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Faws-cdn-by-wpadmin.4.0.1.zip",1,"2023-07-11 00:00:00",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":26,"downloaded":84,"rating":85,"num_ratings":31,"last_updated":86,"tested_up_to":87,"requires_at_least":16,"requires_php":88,"tags":89,"homepage":94,"download_link":95,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"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.",1722,74,"2025-05-09T06:11:00.000Z","6.7.5","7.2",[90,91,92,93,23],"bunnycdn","cache-purging","litespeed","wp-super-cache","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-purger-for-bunnycdn.2.0.zip",{"slug":97,"name":98,"version":99,"author":100,"author_profile":101,"description":102,"short_description":103,"active_installs":11,"downloaded":104,"rating":32,"num_ratings":105,"last_updated":106,"tested_up_to":107,"requires_at_least":108,"requires_php":94,"tags":109,"homepage":113,"download_link":114,"security_score":115,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"ossdl-cdn-off-linker","CDN Linker lite","1.3.1","wmark","https:\u002F\u002Fprofiles.wordpress.org\u002Fwmark\u002F","\u003Cp>Replaces the blog URL by another for all files under \u003Ccode>wp-content\u003C\u002Fcode> and \u003Ccode>wp-includes\u003C\u002Fcode>.\u003Cbr \u002F>\nThat way static content can be handled by a CDN by origin pull. (The origin is your blog address.)\u003C\u002Fp>\n\u003Cp>You could upload your static files to S3, CloudFront or just any site, too.\u003Cbr \u002F>\nFor S3\u002FCloudfront, see \u003Ca href=\"http:\u002F\u002Fmark.ossdl.de\u002F2009\u002F09\u002Fhow-to-copy-your-wordpress-files-to-cloudfront-efficiently\u002F\" title=\"how to copy your WordPress files to CloudFront efficiently\" rel=\"nofollow ugc\">this script\u003C\u002Fa>\u003Cbr \u002F>\nto help you with uploading\u002Fsynchronizing your blog files.\u003C\u002Fp>\n\u003Cp>This \u003Ccode>lite\u003C\u002Fcode> version of the plugin works like the regular version but is not supported.\u003Cbr \u002F>\nYou can get the regular version at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwmark\u002FCDN-Linker\" title=\"CDN Linker at Github\" rel=\"nofollow ugc\">Github\u003C\u002Fa>, which:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Is free of charge, open source and without any ads.\u003C\u002Fli>\n\u003Cli>Supported. Here is \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwmark\u002FCDN-Linker\u002Fissues\" title=\"bug tracker\" rel=\"nofollow ugc\">the bug tracker\u003C\u002Fa> if you encounter any issues.\u003C\u002Fli>\n\u003Cli>Has more and advanced features.\u003C\u002Fli>\n\u003Cli>Is updated more frequently. See \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwmark\u002FCDN-Linker\u002Fdownloads\" title=\"Downloads page\" rel=\"nofollow ugc\">Downloads\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Quality assurance.\u003C\u002Fli>\n\u003C\u002Ful>\n","Rewrites links to static files to your own CDN network.",12350,2,"2011-05-25T12:14:00.000Z","3.1.4","2.7",[20,21,110,111,112],"links","media","simplecdn","https:\u002F\u002Fgithub.com\u002Fwmark\u002FCDN-Linker","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fossdl-cdn-off-linker.1.3.1.zip",85,{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":124,"downloaded":125,"rating":13,"num_ratings":13,"last_updated":94,"tested_up_to":126,"requires_at_least":127,"requires_php":94,"tags":128,"homepage":94,"download_link":132,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":133},"pxp-press","PXP-Press","1.5.3","pxpadmin","https:\u002F\u002Fprofiles.wordpress.org\u002Fpxpadmin\u002F","\u003Cp>A plugin that will invalidate Cloudfront automatically on a post\u002Fpage save.\u003C\u002Fp>\n\u003Ch3>PHP Dependencies\u003C\u002Fh3>\n\u003Cp>PHP XML is required before using.  On a linux environment, it can be installed with the following command:\u003Cbr \u002F>\n    sudo apt-get install php-xml\u003C\u002Fp>\n","A plugin that will invalidate Cloudfront automatically on a post\u002Fpage save.",10,1553,"5.0.25","4.7",[20,21,129,130,131],"enterprise","invalidation","pxp","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpxp-press.1.5.3.zip","2026-03-15T10:48:56.248Z",{"attackSurface":135,"codeSignals":160,"taintFlows":167,"riskAssessment":168,"analyzedAt":178},{"hooks":136,"ajaxHandlers":156,"restRoutes":157,"shortcodes":158,"cronEvents":159,"entryPointCount":13,"unprotectedCount":13},[137,143,146,149,152],{"type":138,"name":139,"callback":140,"file":141,"line":142},"action","after_rocket_clean_domain","anonymous","functions.php",215,{"type":138,"name":144,"callback":140,"file":141,"line":145},"after_rocket_clean_minify",216,{"type":138,"name":147,"callback":140,"file":141,"line":148},"after_rocket_clean_cache",217,{"type":138,"name":150,"callback":140,"file":141,"line":151},"after_rocket_clean_files",219,{"type":138,"name":153,"callback":154,"file":141,"line":155},"plugins_loaded","kodealarocketfront_boot",221,[],[],[],[],{"dangerousFunctions":161,"sqlUsage":162,"outputEscaping":164,"fileOperations":13,"externalRequests":74,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":166},[],{"prepared":13,"raw":13,"locations":163},[],{"escaped":74,"rawEcho":13,"locations":165},[],[],[],{"summary":169,"deductions":170},"The rocketfront-connect plugin v1.0.1 exhibits a strong security posture based on the provided static analysis. There are no identified attack vectors through AJAX, REST API, shortcodes, or cron events. The code also demonstrates good practices by utilizing prepared statements for all SQL queries and properly escaping all outputs. The absence of file operations and external HTTP requests further minimizes potential risks. Taint analysis revealing zero unsanitized paths indicates no immediate risks of injection vulnerabilities within the analyzed code flows.\n\nHowever, the plugin has some areas for improvement. The complete lack of nonce checks and capability checks across all entry points, even though the attack surface is currently reported as zero, represents a significant oversight. If new entry points are introduced in future versions, they would be inherently vulnerable without these fundamental security measures. The single external HTTP request, while not inherently risky in isolation, warrants closer scrutiny in a production environment to ensure it's handled securely and doesn't expose any sensitive data or introduce supply chain risks.\n\nThe plugin's vulnerability history is clean, with no recorded CVEs. This, combined with the robust code signals, suggests a developer who is either diligent in their security practices or has not yet encountered vulnerabilities. Nevertheless, the absence of checks for nonces and capabilities is a notable weakness that could become a problem as the plugin evolves.",[171,174,176],{"reason":172,"points":173},"Missing nonce checks on all entry points",8,{"reason":175,"points":173},"Missing capability checks on all entry points",{"reason":177,"points":105},"Single external HTTP request (potential risk)","2026-03-16T23:04:28.672Z",{"wat":180,"direct":185},{"assetPaths":181,"generatorPatterns":182,"scriptPaths":183,"versionParams":184},[],[],[],[],{"cssClasses":186,"htmlComments":187,"htmlAttributes":188,"restEndpoints":189,"jsGlobals":190,"shortcodeOutput":191},[],[],[],[],[],[]]