[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fTD1UT8v1RY-_n2fH6F4t1vCG8IXjHGEVnI8DIcGMhKc":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":39,"analysis":139,"fingerprints":168},"post-script-responsive-images","Post Script Responsive Images","2.1.0","PStevenson","https:\u002F\u002Fprofiles.wordpress.org\u002Fsilverokami42\u002F","\u003Cp>In short, this plugin modifies “the_content()” and the post thumbnail function by re-rendering the images with use of the SRCSET attribute. Other plugins do this for templated images, but not in the content region itself. This plugin will automatically work with any previously uploaded images as well.\u003C\u002Fp>\n","SRCSET responsive images on wordpress for content images.",40,5443,74,3,"2017-01-06T18:54:00.000Z","4.7.32","4.0","",[20,21,22,23,24],"images","post-script","responsive","responsive-images","srcset","https:\u002F\u002Fwww.p-stevenson.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpost-script-responsive-images.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":27,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},"silverokami42",2,50,30,84,"2026-04-04T01:04:49.821Z",[40,61,78,101,117],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":48,"downloaded":49,"rating":50,"num_ratings":51,"last_updated":52,"tested_up_to":53,"requires_at_least":54,"requires_php":55,"tags":56,"homepage":58,"download_link":59,"security_score":60,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"disable-responsive-images-complete","Disable Responsive Images Complete","2.6.7","Jeff Starr","https:\u002F\u002Fprofiles.wordpress.org\u002Fspecialk\u002F","\u003Cp>This plugin completely disables WP responsive-image feature that was introduced in version 4.4. It is meant for people who know what they are doing and want to use their own responsive-image techniques.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Features\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disables responsive images on the front-end\u003C\u002Fli>\n\u003Cli>Disables generation of \u003Ccode>medium_large\u003C\u002Fcode> 768px image size\u003C\u002Fli>\n\u003Cli>Completely plug-and-play, no configuration required\u003C\u002Fli>\n\u003Cli>Works perfectly with or without Gutenberg block editor\u003C\u002Fli>\n\u003Cli>Uses the WP API to disable responsive images\u003C\u002Fli>\n\u003Cli>Clean, lightweight code, a real pleasure\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Why would anyone want to do this? Check out the FAQs below for all sorts of good reasons.\u003C\u002Fp>\n\u003Cp>Check out \u003Ca href=\"https:\u002F\u002Fperishablepress.com\u002Fdisable-wordpress-responsive-images\u002F\" rel=\"nofollow ugc\">Disable WordPress Responsive Images\u003C\u002Fa> at Perishable Press for more information about how this plugin works, etc.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>👉 \u003Cstrong>Related:\u003C\u002Fstrong> Free plugin to control which image sizes are generated by WordPress, check out \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdisable-media-sizes\u002F\" rel=\"ugc\">Disable Media Sizes\u003C\u002Fa>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cstrong>Privacy\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This plugin does not collect or store any user data. It does not set any cookies, and it does not connect to any third-party locations. Thus, this plugin does not affect user privacy in any way.\u003C\u002Fp>\n\u003Cp>Disable Responsive Images Complete is developed and maintained by \u003Ca href=\"https:\u002F\u002Fx.com\u002Fperishable\" rel=\"nofollow ugc\">Jeff Starr\u003C\u002Fa>, 15-year \u003Ca href=\"https:\u002F\u002Fplugin-planet.com\u002F\" rel=\"nofollow ugc\">WordPress developer\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fbooks.perishablepress.com\u002F\" rel=\"nofollow ugc\">book author\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Support development\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>I develop and maintain this free plugin with love for the WordPress community. To show support, you can \u003Ca href=\"https:\u002F\u002Fmonzillamedia.com\u002Fdonate.html\" rel=\"nofollow ugc\">make a donation\u003C\u002Fa> or purchase one of my books:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwp-tao.com\u002F\" rel=\"nofollow ugc\">The Tao of WordPress\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdigwp.com\u002F\" rel=\"nofollow ugc\">Digging into WordPress\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fhtaccessbook.com\u002F\" rel=\"nofollow ugc\">.htaccess made easy\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwp-tao.com\u002Fwordpress-themes-book\u002F\" rel=\"nofollow ugc\">WordPress Themes In Depth\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fbooks.perishablepress.com\u002Fdownloads\u002Fwizards-collection-sql-recipes-wordpress\u002F\" rel=\"nofollow ugc\">Wizard’s SQL Recipes for WordPress\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>And\u002For purchase one of my premium WordPress plugins:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugin-planet.com\u002Fbbq-pro\u002F\" rel=\"nofollow ugc\">BBQ Pro\u003C\u002Fa> – Blazing fast WordPress firewall\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugin-planet.com\u002Fblackhole-pro\u002F\" rel=\"nofollow ugc\">Blackhole Pro\u003C\u002Fa> – Automatically block bad bots\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugin-planet.com\u002Fbanhammer-pro\u002F\" rel=\"nofollow ugc\">Banhammer Pro\u003C\u002Fa> – Monitor traffic and ban the bad guys\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugin-planet.com\u002Fga-google-analytics-pro\u002F\" rel=\"nofollow ugc\">GA Google Analytics Pro\u003C\u002Fa> – Connect WordPress to Google Analytics\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugin-planet.com\u002Fhead-meta-pro\u002F\" rel=\"nofollow ugc\">Head Meta Pro\u003C\u002Fa> – Ultimate Meta Tags for WordPress\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugin-planet.com\u002Fsimple-ajax-chat-pro\u002F\" rel=\"nofollow ugc\">Simple Ajax Chat Pro\u003C\u002Fa> – Unlimited chat rooms\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fplugin-planet.com\u002Fusp-pro\u002F\" rel=\"nofollow ugc\">USP Pro\u003C\u002Fa> – Unlimited front-end forms\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Links, tweets and likes also appreciated. Thank you! 🙂\u003C\u002Fp>\n","Completely disables WP responsive images.",2000,47461,86,11,"2026-01-29T00:01:00.000Z","6.9.4","4.7","5.6.20",[57,20,22,23,24],"disable","https:\u002F\u002Fperishablepress.com\u002Fdisable-wordpress-responsive-images\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-responsive-images-complete.2.6.7.zip",100,{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":48,"downloaded":69,"rating":70,"num_ratings":71,"last_updated":72,"tested_up_to":73,"requires_at_least":17,"requires_php":18,"tags":74,"homepage":76,"download_link":77,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"ricg-responsive-images","RICG Responsive Images","3.1.1","tevko","https:\u002F\u002Fprofiles.wordpress.org\u002Ftevko\u002F","\u003Cp>Bringing automatic default responsive images to WordPress.\u003C\u002Fp>\n\u003Cp>This plugin works by including all available image sizes for each image upload. Whenever WordPress outputs the image through the media uploader, or whenever a featured image is generated, those sizes will be included in the image tag via the srcset attribute.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important notes\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>As of WordPress 4.4, images are responsive by default. If you are on WordPress 4.4 or plan to update, you will not need to install this plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you have had this plugin installed since before version 2.5 but are running version 4.4 of WordPress, it is important that you leave the plugin installed. This is because all versions of the plugin before version 2.5 relied on a \u003Ccode>data-sizes\u003C\u002Fcode> attribute being present on an image in order to provide the responsive markup needed. If the plugin in this case is removed, then images in posts will be left with invalid markup. We are working to address this issue, and you can keep track of our progress here at https:\u002F\u002Fgithub.com\u002FResponsiveImagesCG\u002Fwp-tevko-responsive-images\u002Fissues\u002F178.\u003C\u002Fp>\n\u003Cp>You can still use the plugin for advanced image compression support or as a simple way to include the picturefill script. The plugin will fall back to WordPress default functions if responsive image support is detected in your installation.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>Version 3.1.0 includes important changes that make this plugin compatible with WordPress version 4.4. Upgrading is highly recommended.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>As of version 2.5.0, the plugin adds \u003Ccode>srcset\u003C\u002Fcode> and \u003Ccode>sizes\u003C\u002Fcode> attributes to images on the front end instead of adding them to the image markup saved in posts.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Full documentation and contributor guidelines can be found on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FResponsiveImagesCG\u002Fwp-tevko-responsive-images\" rel=\"nofollow ugc\">Github\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n","Bringing automatic default responsive images to WordPress.",155045,94,20,"2017-11-28T13:19:00.000Z","4.4.34",[20,75,22,23,24],"picturefill","https:\u002F\u002Fgithub.com\u002FResponsiveImagesCG\u002Fwp-tevko-responsive-images","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fricg-responsive-images.3.1.1.zip",{"slug":79,"name":80,"version":81,"author":82,"author_profile":83,"description":84,"short_description":85,"active_installs":86,"downloaded":87,"rating":60,"num_ratings":88,"last_updated":89,"tested_up_to":90,"requires_at_least":91,"requires_php":18,"tags":92,"homepage":96,"download_link":97,"security_score":98,"vuln_count":99,"unpatched_count":99,"last_vuln_date":100,"fetched_at":30},"responsify-wp","Responsify WP","1.9.11","stefanledin","https:\u002F\u002Fprofiles.wordpress.org\u002Fstefanledin\u002F","\u003Cp>Responsify WP is the WordPress plugin that cares about responsive images.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Use \u003Ccode>img\u003C\u002Fcode> with srcset\u002Fsizes attributes.\u003C\u002Fli>\n\u003Cli>…or the \u003Ccode>picture\u003C\u002Fcode> element.\u003C\u002Fli>\n\u003Cli>Works with or without \u003Ca href=\"http:\u002F\u002Fscottjehl.github.io\u002Fpicturefill\u002F\" rel=\"nofollow ugc\">Picturefill\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Supports high resolution images (retina).\u003C\u002Fli>\n\u003Cli>Custom media queries.\u003C\u002Fli>\n\u003Cli>Handpick which image sizes to use.\u003C\u002Fli>\n\u003Cli>Responsive background images.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>\u003Ca href=\"https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=3ThYWO6vHKI&spfreload=10\" rel=\"nofollow ugc\">Demo\u003C\u002Fa>\u003C\u002Fh3>\n\u003Cp>Responsify WP finds featured images and all images inside the content and makes them responsive.\u003Cbr \u002F>\nFor example, you might have a template that looks like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Carticle>\n    \u003Ch1>\u003C?php the_title();?>\u003C\u002Fh1>\n    \u003C?php the_content();?>\n\u003C\u002Farticle>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>That will output something like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Carticle>\n    \u003Ch1>Hello world\u003C\u002Fh1>\n    \u003Cp>Lorem ipsum dolor sit amet...\u003C\u002Fp>\n    \u003Cimg src=\"large.jpg\" alt=\"Image description\">\n\u003C\u002Farticle>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>But once you have activated the plugin, it will look like this instead:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Carticle>\n    \u003Ch1>Hello world\u003C\u002Fh1>\n    \u003Cp>Lorem ipsum dolor sit amet...\u003C\u002Fp>\n    \u003Cimg sizes=\"(min-width: 300px) 1024px, (min-width: 150x) 300px, 150px\"\n        srcset=\"thumbnail.jpg 150w,\n        medium.jpg 300w,\n        large.jpg 1024w\"\n        alt=\"Image description\">\n\u003C\u002Farticle>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can also choose to use the \u003Ccode>picture\u003C\u002Fcode> element instead:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Carticle>\n    \u003Ch1>Hello world\u003C\u002Fh1>\n    \u003Cp>Lorem ipsum dolor sit amet...\u003C\u002Fp>\n    \u003Cpicture>\n        \u003Csource srcset=\"full-size.jpg\" media=\"(min-width: 1024px)\">\n        \u003Csource srcset=\"large.jpg\" media=\"(min-width: 300px)\">\n        \u003Csource srcset=\"medium.jpg\" media=\"(min-width: 150px)\">\n        \u003Cimg srcset=\"thumbnail.jpg\" alt=\"Image description\">\n    \u003C\u002Fpicture>\n\u003C\u002Farticle>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>It also works with high resolution (retina) images:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Carticle>\n    \u003Ch1>Hello world\u003C\u002Fh1>\n    \u003Cp>Lorem ipsum dolor sit amet...\u003C\u002Fp>\n    \u003Cpicture>\n        \u003Csource srcset=\"full-size.jpg\" media=\"(min-width: 1024px)\">\n        \u003Csource srcset=\"large.jpg, large_retina.jpg 2x\" media=\"(min-width: 300px)\">\n        \u003Csource srcset=\"medium.jpg, medium_retina.jpg 2x\" media=\"(min-width: 150px)\">\n        \u003Cimg srcset=\"thumbnail.jpg, thumbnail_retina.jpg 2x\" alt=\"Image description\">\n    \u003C\u002Fpicture>\n\u003C\u002Farticle>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The different versions of the image in the examples above is in the standard \u003Ccode>thumbnail\u003C\u002Fcode>, \u003Ccode>medium\u003C\u002Fcode>, \u003Ccode>large\u003C\u002Fcode> and \u003Ccode>full\u003C\u002Fcode> sizes.\u003Cbr \u002F>\nThe \u003Cstrong>media queries\u003C\u002Fstrong> are based on the width of the “previous” image.\u003Cbr \u002F>\nAny \u003Cstrong>custom sizes\u003C\u002Fstrong> of the image will also be found and used.\u003C\u002Fp>\n\u003Ch3>Settings\u003C\u002Fh3>\n\u003Cp>You can \u003Cstrong>select which image sizes\u003C\u002Fstrong> that the plugin should use from the RWP settings page.\u003Cbr \u002F>\nThese settings can be overwritten from your templates.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php\n\n\u002F\u002F Using get_posts()\n$posts = get_posts( array(\n    'post_type' => 'portfolio',\n    'rwp_settings' => array(\n        'sizes' => array('large', 'full')\n    )\n) );\nforeach( $posts as $post ) {\n    \u002F\u002F ...\n}\n\n\u002F\u002F Using WP_Query()\n$query = new WP_Query( array(\n    'category_name' => 'wordpress',\n    'rwp_settings' => array(\n        'sizes' => array('large', 'full')\n    )\n) );\nif ( $query->have_posts() ) {\n    \u002F\u002F ...\n}\n?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Available settings:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Select which image sizes to use.\u003C\u002Fli>\n\u003Cli>Set\u002Foverride attributes.\u003C\u002Fli>\n\u003Cli>Set custom media queries.\u003C\u002Fli>\n\u003Cli>Turn on\u002Foff retina.\u003C\u002Fli>\n\u003Cli>Ignore image formats.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Functions\u003C\u002Fh3>\n\u003Cp>RWP provides a number of functions that can generate responsive images in your templates.\u003Cbr \u002F>\nLet’s say that you have the following markup for a very large header image:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cheader>\n    \u003C?php the_post_thumbnail( 'full' ); ?>\n\u003C\u002Fheader>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>As you probably know, \u003Ccode>the_post_thumbnail()\u003C\u002Fcode> will create a regular \u003Ccode>\u003Cimg>\u003C\u002Fcode> tag with the full-size image in this case.\u003Cbr \u002F>\nBut you don’t want to send a big 1440px image to a mobile device. This can easily be solved like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cheader>\n    \u003C?php\n    $thumbnail_id = get_post_thumbnail_id( $post->ID );\n\n    \u002F\u002F Generate an \u003Cimg> tag with srcset\u002Fsizes attributes.\n    echo rwp_img( $thumbnail_id );\n\n    \u002F\u002F Generate a \u003Cpicture> element\n    echo rwp_picture( $thumbnail_id );\n    ?>\n\u003C\u002Fheader>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch3>Website\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fresponsifywp.com\" rel=\"nofollow ugc\">http:\u002F\u002Fresponsifywp.com\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Demo\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fresponsifywp.com\u002Fdemo\" rel=\"nofollow ugc\">http:\u002F\u002Fresponsifywp.com\u002Fdemo\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Documentation and examples\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fstefanledin\u002Fresponsify-wp\" rel=\"nofollow ugc\">https:\u002F\u002Fgithub.com\u002Fstefanledin\u002Fresponsify-wp\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>PHP 5.3\u003C\u002Fli>\n\u003C\u002Ful>\n","Responsive images. Plug and play.",600,45088,18,"2018-06-07T06:21:00.000Z","4.9.29","3.8.1",[93,94,23,95,24],"picture","picture-element","sizes","https:\u002F\u002Fgithub.com\u002Fstefanledin\u002Fresponsify-wp","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fresponsify-wp.1.9.11.zip",63,1,"2025-06-05 00:00:00",{"slug":102,"name":103,"version":104,"author":105,"author_profile":106,"description":107,"short_description":108,"active_installs":60,"downloaded":109,"rating":50,"num_ratings":110,"last_updated":111,"tested_up_to":73,"requires_at_least":112,"requires_php":18,"tags":113,"homepage":115,"download_link":116,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"force-https-srcset","Force HTTPS srcset","1.0","Hinaloe","https:\u002F\u002Fprofiles.wordpress.org\u002Fhnle\u002F","\u003Cp>Responsive Image is introduced from WP 4.4, but thats url sometime \u003Ccode>http\u003C\u002Fcode> not \u003Ccode>https\u003C\u002Fcode> when you access from \u003Ccode>https\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>This plugin make force https srcset when access from https, or everytime.(You can chose in setting).\u003C\u002Fp>\n","Replace Responsive images srcset since wp 4.4 to https!",4513,6,"2015-12-19T05:12:00.000Z","4.4",[114,23,24],"https","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fforce-https-srcset","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fforce-https-srcset.zip",{"slug":118,"name":119,"version":120,"author":121,"author_profile":122,"description":123,"short_description":124,"active_installs":125,"downloaded":126,"rating":70,"num_ratings":127,"last_updated":128,"tested_up_to":129,"requires_at_least":130,"requires_php":18,"tags":131,"homepage":135,"download_link":136,"security_score":137,"vuln_count":14,"unpatched_count":28,"last_vuln_date":138,"fetched_at":30},"adaptive-images","Adaptive Images for WordPress","0.6.73","Takis Bouyouris","https:\u002F\u002Fprofiles.wordpress.org\u002Fnevma\u002F","\u003Ch4>Adaptive Images\u003C\u002Fh4>\n\u003Cp>Resizes and optimizes images delivered to mobile devices, in a transparent way, so that the total download time is dramatically reduced. It works as a filter between your WordPress website and the devices and seves smaller images to them.\u003C\u002Fp>\n\u003Cp>Note that this is not a CSS nor a responsive images solution. It does not affect your themes layout and style. It simply sends smaller images to the devices without them noticing it!\u003C\u002Fp>\n\u003Ch4>Fundamental goals\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Reduce the total download time of a web page in mobile devices dramatically.\u003C\u002Fli>\n\u003Cli>Work transparantly and unobtrusively by being independant of your theme layout and style.\u003C\u002Fli>\n\u003Cli>Be agnostic of the yet not-standardised \u003Ccode>picture\u003C\u002Fcode> element or HTML the img \u003Ccode>srcset\u003C\u002Fcode> attribute.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Side benefits\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Respects search engines and sends them the orginal version of each image.\u003C\u002Fli>\n\u003Cli>If it does not recognise a device size it falls back to the original image size.\u003C\u002Fli>\n\u003Cli>It is lightweight, because it does not need to load the whole WordPress environment every time it server an image request.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Supported formats\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>JPEG\u003C\u002Fli>\n\u003Cli>PNG\u003C\u002Fli>\n\u003Cli>GIF (not animated)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>NOT Supported formats\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>WEBP\u003C\u002Fli>\n\u003Cli>GIF (animated)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>CDN\u002FVarnish\u002FNginx\u002Fexternal caching services\u003C\u002Fh4>\n\u003Cp>Since version 0.6.0 CDN\u002FVarnish\u002Fexternal caching service support has been added as an option, in an \u003Cstrong>\u003Cem>experimental\u003C\u002Fem>\u003C\u002Fstrong> mode. This means: i) it is not thorougly tested yet ii) however, it works in almost all test cases so far iii) it bears no dangers to your installation iv) it adds a special url parameter to your image urls, so it is slightly obtrusive.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Tested with MaxCDN, Varnish and Nginx up to now. \u003C\u002Fli>\n\u003Cli>Cannot handle CSS background images in this mode (yet). \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Cannot work, not even in experimental mode, with CDNs which use a different subdomain for images, because these setups completely bypass WordPress when delivering images. Feel free to ask for details on this in the support forum.\u003C\u002Fp>\n\u003Ch4>Default breakpoints\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>1024px wide screens\u003C\u002Fli>\n\u003Cli>640px wide screens\u003C\u002Fli>\n\u003Cli>480px wide screens\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Since version 0.5.0 and upwards it is configurable whether the plugin should take into account the landscape or the portrait orientation of each device. HiDPI (high device pixel density or retina) screens are supported too.\u003C\u002Fp>\n\u003Ch4>How to test\u003C\u002Fh4>\n\u003Cp>The esiest way to test is with your browser's device emulation mode (Responsive Design Mode) in it' Developer Tools. You can check this out in this video https:\u002F\u002Fwww.youtube.com\u002Fwatch?v=hCAC1XUUOvw\u002F as an example.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Test with a tool like Webpagetest http:\u002F\u002Fwww.webpagetest.org\u002F. Make sure you set the “Emulate Mobile Browser” setting in the “Advanced Settings” > “Chrome” tab. \u003C\u002Fli>\n\u003Cli>Test with an actual mobile device, a smartphone or tablet. Watch your website load in a snap.\u003C\u002Fli>\n\u003Cli>Check the \u003Ccode>\u002Fwp-contents\u002Fcache\u003C\u002Fcode> directory to see the \u003Ccode>\u002Fadaptive-images\u003C\u002Fcode> directory and its contents. This is where the resized images are kept and cached by default.\u003C\u002Fli>\n\u003Cli>View an image straight from a browser and add a \"?debug=true\" at the end of the url like this \"http:\u002F\u002Fwww.website.com\u002Fwp-content\u002Fuploads\u002F2015\u002F01\u002Fimage.jpg?debug=true\". This verifies that the plugin is working and should print useful debug information. If you keep seeing your image, then the plugin is not working as expected and the cause is probably a failure to update the .htaccess file properly.\u003C\u002Fli>\n\u003Cli>Add a \"?debug=original\" at the end of the url of an image and you will see the orginal version of the image even when a smaller version of it should have been shown.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Incompatibilities and issues\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>The plugin supports Nginx, if it is used as the main server, not as a caching server, but the server’s configuration file must be manually configured like this:\u003C\u002Fp>\n\u003Cp>\u003Ccode>location \u002F {\u003Cbr \u002F>\nrewrite \\.(?:jpe?g|gif|png)$ \u002Fwp-content\u002Fplugins\u002Fadaptive-images\u002Fadaptive-images-script.php;\u003Cbr \u002F>\n}\u003C\u002Fcode>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Windows IIS is not supported, but could be manually configured. Any IIS experts are welcome to contribute.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>Cannot work, not even in experimental mode, with CDNs which use a different subdomain for images. \u003C\u002Fli>\n\u003Cli>When using HTTPS\u002FSSL make sure that you update all your website urls and also the urls in your WordPress General\u003Cbr \u002F>\nsettings page, otherwise the plugin will not be able to locate your images. \u003C\u002Fli>\n\u003Cli>WordPress Multisite (Mu) is not supported (some plans for future support are being discussed).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Stuff to keep in mind\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>The plugin needs to add a little bit of code to your \u003Ccode>.htaccess\u003C\u002Fcode> file in order to function properly. It removes this code once disabled. If you are not cool with that, then… tough luck! \u003C\u002Fli>\n\u003Cli>The plugin does not care whether the device is actually mobile or not. It checks the device screen resolution. If you have set your breakpoints big enough then it should work just as good for desktop devices as well. However, it targets mostly the mobile ones.\u003C\u002Fli>\n\u003Cli>The resized versions of the pictures are kept in a special directory in the \u003Ccode>\u002Fwp-content\u002Fcache\u003C\u002Fcode> directory. This causes some storage overhead. It is up to you to judge whether this overhead is a sustainable option in your hosting environment. Usually it is not even remotely compared to the size of your original images directories.\u003C\u002Fli>\n\u003Cli>The plugin does not help with (nor hinder) art direction. Simple as that. Art direction https:\u002F\u002Fusecases.responsiveimages.org\u002F#art-direction in responsive images is an entirely different, yet important, problem. This plugin does not tackle with it. But it works in a supplementary way without interfering with other solutions that do. This means that you can combine it with any art direction solution.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>The plugin was originally based on the WP-Resolutions plugin https:\u002F\u002Fgithub.com\u002FJorgenHookham\u002FWP-Resolutions\u002F, but since version 0.3.0 it is a complete rewrite!\u003C\u002Fli>\n\u003Cli>Both plugins, WP-Resolutions and this one, have borrowed ideas from the Adaptive Images http:\u002F\u002Fadaptive-images.com\u002F solution, specially adapted for WordPress.\u003C\u002Fli>\n\u003Cli>Many special thanks to my good friend and colleague Antonis Zachopoulos for the countless times that he provided feedback, ideas and debugging hints.\u003C\u002Fli>\n\u003Cli>Many thanks to @railgunner for the initial idea on the CDN\u002FVarnish\u002Fexternal caching service feature in the plugin support forum. It showed the way that it was indeed possible!\u003C\u002Fli>\n\u003Cli>Thank you AJ at WpFASTER.org for being keen to test the above feature in a real environment.\u003C\u002Fli>\n\u003Cli>Thank you to the guys over at the Pressidium team for helping with debugging the CDN\u002FVarnish\u002Fexternal caching service feature and providing test environments.\u003C\u002Fli>\n\u003Cli>Thank you Andy Gray for helping debugging the weird filesystem path issues in managed hosting environments.\u003C\u002Fli>\n\u003Cli>Thank you @milenoi2016 for helping sort out one of the many cases of WordPress directories setup.\u003C\u002Fli>\n\u003Cli>Thank you @minorgod for the Windows path fix.\u003C\u002Fli>\n\u003Cli>Thank you Mark Gruffer for the global request variable exposure hint. \u003C\u002Fli>\n\u003Cli>Thank you @timholz for the SameSite cookie hint.\u003C\u002Fli>\n\u003Cli>Thank you @blackcapdesign for spotting the regular expression issue in version 0.6.70 and helping debug it.\u003C\u002Fli>\n\u003Cli>Lastly, a million thanks to all of you who provided useful feedback in the early versions of the plugin, where the inevitable glitches, due to server environment variations, were more than a few.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Please, do let us know how the plugin works (or doesn’t work) for you. We love comments and creative feedback!\u003C\u002Fp>\n","Adaptive images plugin transparently resizes your images, per device screen size, in order to reduce download times in mobile environments.",4000,175890,56,"2024-10-15T20:03:00.000Z","6.6.5","5.0",[118,132,133,134,23],"mobile-images","optimize-images","resize-images","http:\u002F\u002Fwww.nevma.gr","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadaptive-images.0.6.73.zip",90,"2022-01-11 00:00:00",{"attackSurface":140,"codeSignals":156,"taintFlows":163,"riskAssessment":164,"analyzedAt":167},{"hooks":141,"ajaxHandlers":152,"restRoutes":153,"shortcodes":154,"cronEvents":155,"entryPointCount":28,"unprotectedCount":28},[142,148],{"type":143,"name":144,"callback":145,"priority":28,"file":146,"line":147},"action","post_thumbnail_html","createThumbnail","post-script-responsive.php",165,{"type":143,"name":149,"callback":150,"file":146,"line":151},"the_content","createContentImage",166,[],[],[],[],{"dangerousFunctions":157,"sqlUsage":158,"outputEscaping":160,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":162},[],{"prepared":28,"raw":28,"locations":159},[],{"escaped":28,"rawEcho":28,"locations":161},[],[],[],{"summary":165,"deductions":166},"Based on the provided static analysis and vulnerability history, the \"post-script-responsive-images\" v2.1.0 plugin appears to have a strong security posture. The analysis indicates a complete absence of common attack vectors such as AJAX handlers, REST API routes, shortcodes, or cron events that could be exploited. Furthermore, the code signals reveal no dangerous functions used, all SQL queries are properly prepared, and all output is correctly escaped, demonstrating good development practices.  The lack of any file operations or external HTTP requests also reduces the potential attack surface.  The vulnerability history is clean, with no recorded CVEs, which suggests a history of secure development and maintenance.  However, the absence of nonce and capability checks, while not explicitly flagged as an issue due to the lack of exposed entry points, could become a concern if the plugin's functionality were to expand and introduce such points without these vital security measures.  Overall, this plugin presents a very low risk at this version, with strengths in its minimal attack surface and secure coding practices outweighing any potential future concerns.",[],"2026-03-16T22:13:39.512Z",{"wat":169,"direct":178},{"assetPaths":170,"generatorPatterns":173,"scriptPaths":174,"versionParams":175},[171,172],"\u002Fwp-content\u002Fplugins\u002Fpost-script-responsive-images\u002Fstyle.css","\u002Fwp-content\u002Fplugins\u002Fpost-script-responsive-images\u002Fscript.js",[],[172],[176,177],"post-script-responsive-images\u002Fstyle.css?ver=","post-script-responsive-images\u002Fscript.js?ver=",{"cssClasses":179,"htmlComments":180,"htmlAttributes":181,"restEndpoints":182,"jsGlobals":183,"shortcodeOutput":184},[],[],[],[],[],[]]