[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fpufznH41Mdj7mtIf7CzSgjnzek1EjG_pJ664sdICbiI":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":21,"download_link":22,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26,"vulnerabilities":27,"developer":28,"crawl_stats":25,"alternatives":36,"analysis":128,"fingerprints":170},"cf-preview-fix","CF Preview Fix","0.5.1","hide","https:\u002F\u002Fprofiles.wordpress.org\u002Fhideokamoto\u002F","\u003Cp>Add current time to permalink in your preview page.\u003C\u002Fp>\n\u003Cp>You can see Non-Cached Preview posts.\u003C\u002Fp>\n","Fix CloudFront Preview Plugin",10,1409,100,1,"2016-09-20T03:41:00.000Z","4.4.34","4.4.2","",[20],"cloudfront","https:\u002F\u002Fgithub.com\u002Famimoto-ami\u002Fcloudfront-preview-fix","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcf-preview-fix.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":29,"display_name":7,"profile_url":8,"plugin_count":30,"total_installs":31,"avg_security_score":32,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"hideokamoto",6,3820,93,30,89,"2026-04-05T02:03:51.138Z",[37,56,77,93,107],{"slug":38,"name":39,"version":40,"author":7,"author_profile":8,"description":41,"short_description":42,"active_installs":43,"downloaded":44,"rating":45,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":50,"tags":51,"homepage":54,"download_link":55,"security_score":13,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"c3-cloudfront-clear-cache","C3 Cloudfront Cache Controller","7.3.1","\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,3,"2026-02-18T06:51:00.000Z","6.8.5","4.9.0","7.4",[52,53,20],"aws","cdn","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":57,"name":58,"version":59,"author":60,"author_profile":61,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":66,"num_ratings":67,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":50,"tags":71,"homepage":74,"download_link":75,"security_score":13,"vuln_count":14,"unpatched_count":24,"last_vuln_date":76,"fetched_at":26},"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,94,53,"2026-02-12T14:21:00.000Z","6.9.4","5.6",[72,52,53,20,73],"amazon","free","https:\u002F\u002Fwpadmin.ca\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Faws-cdn-by-wpadmin.4.0.1.zip","2023-07-11 00:00:00",{"slug":78,"name":79,"version":80,"author":81,"author_profile":82,"description":83,"short_description":79,"active_installs":84,"downloaded":85,"rating":13,"num_ratings":14,"last_updated":86,"tested_up_to":49,"requires_at_least":87,"requires_php":70,"tags":88,"homepage":91,"download_link":92,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"visual-mode-in-cloudfront","Enable Visual Mode in CloudFront","1.0.3","kawax","https:\u002F\u002Fprofiles.wordpress.org\u002Fkawax\u002F","\u003Cp>When using WordPress in CloudFront, Visual mode can not be used.\u003Cbr \u002F>\nBecause User-Agent is rewritten.\u003C\u002Fp>\n\u003Cp>This plugin checks the CloudFront-Is-Desktop-Viewer header to use Visual mode.\u003C\u002Fp>\n",200,7096,"2017-11-10T13:20:00.000Z","4.7.2",[20,89,90],"editor","post","https:\u002F\u002Fgithub.com\u002Fkawax\u002Fvisual-mode-in-cloudfront","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvisual-mode-in-cloudfront.1.0.3.zip",{"slug":94,"name":95,"version":96,"author":97,"author_profile":98,"description":99,"short_description":95,"active_installs":33,"downloaded":100,"rating":24,"num_ratings":24,"last_updated":101,"tested_up_to":102,"requires_at_least":103,"requires_php":104,"tags":105,"homepage":18,"download_link":106,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"clear-cloudfront-cache","Clear CloudFront Cache","1.0.0","yamaimo","https:\u002F\u002Fprofiles.wordpress.org\u002Fkinocchi\u002F","\u003Cp>It is a plugin that can easily delete the CloudFront cache.\u003Cbr \u002F>\nSetting is easy with only 2 steps.\u003Cbr \u002F>\n* Configure IAM\u003Cbr \u002F>\n* Set a CloudFront distribution ID for this plugin\u003C\u002Fp>\n\u003Ch3>Arbitrary section 1\u003C\u002Fh3>\n",862,"2023-04-01T02:48:00.000Z","6.1.10","6.1.1","7.0",[52,20],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclear-cloudfront-cache.zip",{"slug":108,"name":109,"version":110,"author":111,"author_profile":112,"description":113,"short_description":114,"active_installs":115,"downloaded":116,"rating":117,"num_ratings":118,"last_updated":119,"tested_up_to":120,"requires_at_least":121,"requires_php":18,"tags":122,"homepage":126,"download_link":127,"security_score":23,"vuln_count":24,"unpatched_count":24,"last_vuln_date":25,"fetched_at":26},"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.",20,12350,60,2,"2011-05-25T12:14:00.000Z","3.1.4","2.7",[53,20,123,124,125],"links","media","simplecdn","https:\u002F\u002Fgithub.com\u002Fwmark\u002FCDN-Linker","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fossdl-cdn-off-linker.1.3.1.zip",{"attackSurface":129,"codeSignals":158,"taintFlows":165,"riskAssessment":166,"analyzedAt":169},{"hooks":130,"ajaxHandlers":154,"restRoutes":155,"shortcodes":156,"cronEvents":157,"entryPointCount":24,"unprotectedCount":24},[131,136,138,143,147,150],{"type":132,"name":133,"callback":134,"file":135,"line":11},"action","init","closure","cf-preview-fix.php",{"type":132,"name":137,"callback":137,"file":135,"line":33},"template_redirect",{"type":139,"name":140,"callback":141,"priority":11,"file":135,"line":142},"filter","post_link","post_link_fix",31,{"type":139,"name":144,"callback":145,"priority":11,"file":135,"line":146},"preview_post_link","preview_post_link_fix",32,{"type":139,"name":148,"callback":148,"file":135,"line":149},"the_guid",33,{"type":139,"name":151,"callback":152,"file":135,"line":153},"sanitize_file_name","sanitizeFileName",34,[],[],[],[],{"dangerousFunctions":159,"sqlUsage":160,"outputEscaping":162,"fileOperations":24,"externalRequests":24,"nonceChecks":24,"capabilityChecks":24,"bundledLibraries":164},[],{"prepared":24,"raw":24,"locations":161},[],{"escaped":24,"rawEcho":24,"locations":163},[],[],[],{"summary":167,"deductions":168},"The `cf-preview-fix` plugin version 0.5.1 exhibits an exceptionally strong security posture based on the provided static analysis and vulnerability history. The code analysis reveals no discernible attack surface, as there are no AJAX handlers, REST API routes, shortcodes, or cron events exposed. Furthermore, the code demonstrates excellent security practices by avoiding dangerous functions, utilizing prepared statements exclusively for SQL queries, and ensuring all output is properly escaped.  The absence of file operations, external HTTP requests, nonce checks, and capability checks on entry points, combined with a lack of bundled libraries, further minimizes potential vulnerabilities. The taint analysis also shows no identified flows with unsanitized paths, indicating a clean codebase.\n\nThe plugin's vulnerability history is equally impressive, with no recorded CVEs of any severity. This pattern suggests a consistently secure development approach or a lack of focus from potential attackers.  However, it's important to note that the lack of certain security checks (nonces, capabilities) on entry points, while not currently exploitable due to the absence of entry points, could become a concern if the plugin were to evolve and introduce new functionalities.  In conclusion, `cf-preview-fix` v0.5.1 appears to be a highly secure plugin with no immediate threats identified. Its strengths lie in its minimal attack surface and robust coding practices. The only minor potential weakness is the absence of explicit capability checks, which is more of a proactive recommendation than a current risk.",[],"2026-03-17T01:12:58.712Z",{"wat":171,"direct":176},{"assetPaths":172,"generatorPatterns":173,"scriptPaths":174,"versionParams":175},[],[],[],[],{"cssClasses":177,"htmlComments":178,"htmlAttributes":179,"restEndpoints":180,"jsGlobals":181,"shortcodeOutput":182},[],[],[],[],[],[]]