[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fWgLXC4RQJcWg_Y445B8sTfvT_2z6e99K5a-h58SlYzA":3,"$fZ3FrPk3XY52KZcQ4iIYwGj_9rmsgJkl3J6hPOgwMKGk":185,"$fT9j02qvUTLK5eq5esGd7XIqhYJzMxRHTvn1BWQgRRok":190},{"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,"discovery_status":29,"vulnerabilities":30,"developer":31,"crawl_stats":27,"alternatives":37,"analysis":132,"fingerprints":172},"lh-add-headers","LH Add Headers","1.04","shawfactor","https:\u002F\u002Fprofiles.wordpress.org\u002Fshawfactor\u002F","\u003Cp>A \u003Ccode>304 Not Modified HTTP Header\u003C\u002Fcode> tells your visitors that nothing has changed since their last visit. This is important as without this header visitors may be downloading your webpages from scratch each time, slowing down their experience and your site.\u003C\u002Fp>\n\u003Cp>Generally if you do not pass \u003Ccode>304 Not Modified HTTP Header\u003C\u002Fcode> through your HTTP header, crawlers will fetch your whole website and then compare the content of your site with the already indexed content to check whether anything new has been updated on your website or not. But this process consumes a lot of your server resource and bandwidth.\u003C\u002Fp>\n\u003Cp>You can know more about it \u003Ca href=\"http:\u002F\u002Fwww.feedthebot.com\u002Fifmodified.html\" rel=\"nofollow ugc\">here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Before reading any further\u003C\u002Fh4>\n\u003Cp>Before reading any further it is important to understand this plugin uses output buffering, in fact the Etag sent by this plugin is a hash of the sites buffered content. If your site uses server side caching this plugin may break the caching functionality. Therefore I suggest that you please \u003Cstrong>make sure\u003C\u002Fstrong> you have studied the FAQ, before installation and activation.\u003C\u002Fp>\n","Adds the ETag, Last-Modified, and if appropriate 304 headers to HTTP responses generated by WordPress for more efficient caching.",10,2393,0,"2017-05-02T02:44:00.000Z","4.8.28","3.1.0","",[19,20,21,22,23],"cache-control","caching","expires","headers","last-modified","https:\u002F\u002Flhero.org\u002Fportfolio\u002Flh-add-headers\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flh-add-headers.zip",85,null,"2026-04-06T09:54:40.288Z","no_bundle",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":26,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},89,14520,7,90,"2026-05-19T19:22:46.127Z",[38,56,75,96,111],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":13,"num_ratings":13,"last_updated":48,"tested_up_to":15,"requires_at_least":49,"requires_php":17,"tags":50,"homepage":53,"download_link":54,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":55},"smart-wp","Smart WordPress","1.0.2","ggriesser","https:\u002F\u002Fprofiles.wordpress.org\u002Fggriesser\u002F","\u003Cp>Optimize the caching behavior of your Website! Smart WordPress by \u003Ca href=\"https:\u002F\u002Fwww.velocious.io\u002F\" title=\"Smart WordPress FAQs\" rel=\"nofollow ugc\">Velocious.io\u003C\u002Fa> only reloads pages if something has been changed.\u003C\u002Fp>\n\u003Cp>A huge number of users abandon websites that are slow to load. That’s no surprise! No one likes to browse a slow site!\u003C\u002Fp>\n\u003Cp>With Smart WP you are able to make your WordPress page load in a better way: Your content gets stored in your visitors browsers and is only reloaded if something changed.\u003C\u002Fp>\n\u003Cp>This way you can reduce the performance of your and provide your users with an improved experience.\u003C\u002Fp>\n\u003Cp>Your users will love it!\u003C\u002Fp>\n\u003Cp>\u003Cstrong>By using Smart WordPress you are able to:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>change the configuration of your ETags\u003C\u002Fli>\n\u003Cli>modify the configuration of the Last-Modified Header\u003C\u002Fli>\n\u003Cli>alter the configuration of the Cache-Control Header\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Acknowledges:\u003C\u002Fstrong> This plugin is based on the excellent work by George Notaras. It is a fork of his deprecated Add Headers Plugin – a plugin I have used myself for a bunch of years.\u003C\u002Fp>\n","Optimize the caching behavior of your Website the easy way and reload pages only if something has been changed.",20,2375,"2017-08-04T12:38:00.000Z","4.5",[51,19,20,52,23],"cache","etag","https:\u002F\u002Fwww.velocious.io\u002Fplugins\u002Fsmart-wordpress\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsmart-wp.1.0.2.zip","2026-04-16T10:56:18.058Z",{"slug":19,"name":57,"version":58,"author":59,"author_profile":60,"description":61,"short_description":62,"active_installs":63,"downloaded":64,"rating":65,"num_ratings":66,"last_updated":67,"tested_up_to":68,"requires_at_least":69,"requires_php":17,"tags":70,"homepage":73,"download_link":74,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":55},"Cache-Control","2.2.5","Dan","https:\u002F\u002Fprofiles.wordpress.org\u002Fgeekysoft\u002F","\u003Cp>Good caching policies is one of performance’s best friends, and it can be your new best friend too. Get friendly with intermediary and browser caches by taking control over your WordPress powered website’s HTTP \u003Ccode>Cache-Control\u003C\u002Fcode> headers.\u003C\u002Fp>\n\u003Cp>This is not a caching plugin in itself, but will enable you to leverage existing standard compliant caching systems better. You can set different policies for different kinds of pages to suite your website’s needs. The Cache-Control for WordPress plugin allows you to set different policies for shared\u002Fintermediary and private caches. The plugin sets some sensible defaults for a medium traffic blog that publishes an update or two per week.\u003C\u002Fp>\n\u003Cp>You can safely set long \u003Ccode>Cache-Control\u003C\u002Fcode> times as the \u003Ccode>max-age\u003C\u002Fcode> values is lowered automatically before a scheduled post is about to be published.\u003C\u002Fp>\n\u003Cp>Private pages (logged in users, the admin interface, etc.) will not be cached.\u003C\u002Fp>\n\u003Cp>The plugin has \u003Ca href=\"https:\u002F\u002Fwww.ctrl.blog\u002Fentry\u002Fwp-cache-control-documentation.html\" rel=\"nofollow ugc\">extensive documentation\u003C\u002Fa>.\u003C\u002Fp>\n","Configurable HTTP Cache-Control response headers for webpages generated by WordPress.",1000,99562,100,6,"2019-08-30T11:50:00.000Z","5.2.24","4.4.1",[19,20,71,72],"http","performance","https:\u002F\u002Fwww.ctrl.blog\u002Fentry\u002Fwordpress-cache-control-plugin.html","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-control.2.2.5.zip",{"slug":76,"name":77,"version":78,"author":79,"author_profile":80,"description":81,"short_description":82,"active_installs":83,"downloaded":84,"rating":13,"num_ratings":13,"last_updated":85,"tested_up_to":86,"requires_at_least":87,"requires_php":88,"tags":89,"homepage":17,"download_link":92,"security_score":93,"vuln_count":94,"unpatched_count":94,"last_vuln_date":95,"fetched_at":55},"cache-control-by-cacholong","Cache control by Cacholong","5.4.1","Preliot","https:\u002F\u002Fprofiles.wordpress.org\u002Fpreliot\u002F","\u003Cp>“Cache control by Cacholong” plugin automates purging of Nginx Pagespeed cache and Nginx FastCGI cache on your Nginx server(s). It is a backend plugin that is able to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Purge Nginx Pagespeed cache and\u002For Nginx FastCGI cache.\u003C\u002Fli>\n\u003Cli>Purge cache automatically, manually, with WordPress cronjobs and WP-CLI.\u003C\u002Fli>\n\u003Cli>Purge caches on one or more servers (See hosts.json section for more details).\u003C\u002Fli>\n\u003Cli>Use commandline (WP-CLI) to purge caches or reset to factory settings.\u003C\u002Fli>\n\u003Cli>Remove id tag from stylesheet link tags, in order to allow Nginx Pagespeed to combine stylesheets.\u003C\u002Fli>\n\u003Cli>Allow purging of other cached items (see Settings > Cache control).\u003C\u002Fli>\n\u003Cli>Inform user of purge status.\u003C\u002Fli>\n\u003Cli>Support for single site and network sites\u003C\u002Fli>\n\u003Cli>Support for WP-CLI\u003C\u002Fli>\n\u003Cli>Support for WPML (including language negotiation type domain)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>When will it purge?\u003C\u002Fh4>\n\u003Cp>This plugin will work with default and custom post types. It will purge on a save, regular update, quick edit update, slug change, delete and undelete. The user is informed with one or more messages.\u003Cbr \u002F>\nThere are a few caveats:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When a user is using the Gutenberg editor, purge messages will not be displayed.\u003C\u002Fli>\n\u003Cli>When the user uses “Quick edit” and “Updates” the post, no messages will be displayed, because there’s no page refresh. Those messages will be shown on the next request. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It is possible to purge with WordPress cronjobs. Adjust the ‘Cronjob settings’ to perform a daily purge of caches.\u003C\u002Fp>\n\u003Cp>You can also purge items manually. Go to the WordPress dashboard and navigate to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Settings > Cache control > purge single item\u003C\u002Fli>\n\u003Cli>Settings > Cache control > purge all caches\u003C\u002Fli>\n\u003Cli>Admin Toolbar > purge all caches\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>File with hosts (JSON):                 File with information about one or more hosts for this WordPress installation. See hosts.json section for more details. \u003C\u002Fli>\n\u003Cli>Pagespeed optimized CSS:                Remove ID tag from all WordPress stylesheet link tags to improve Nginx Pagespeed caching. Will only work on frontend.\u003C\u002Fli>\n\u003Cli>Purge settings default post types:      Select one or more options when purging a default post type. Possible to purge post url (default), home page, all connected WordPress categories or all caches.\u003C\u002Fli>\n\u003Cli>Purge settings default custom type(s):  Select one or more options when purging a custom post type. Possible to purge post url (default), home page, all connected WordPress categories or all caches.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Cronjob Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Cronjob purging:                        Enable or disable cronjob purging. \u003C\u002Fli>\n\u003Cli>Cronjob time of each day:               Enter HH:MM in 24 hour notation for cronjob time of day. Will fallback to 00:00 when wrong format is given.\u003C\u002Fli>\n\u003Cli>Purge caches                            Select caches to purge on given cronjob time. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>hosts.json\u003C\u002Fh4>\n\u003Cp>Hosts.json is a JSON file with information about one or more servers for this WordPress installation. Remember that this file must contain information about all servers, including the\u003Cbr \u002F>\none with this plugin. Default path is: wp-content\u002Fuploads\u002Fcacholong-cache-control\u002Fhosts.json.\u003C\u002Fp>\n\u003Cp>Here is an example of a hosts.json file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\"servers\":\n    [\n        {\"name\": \"server1\", \"ip\": \"127.0.0.1\", \"pagespeed\": true, \"fastcgi\": false},\n        {\"name\": \"server2\", \"ip\": \"127.0.0.2\", \"pagespeed\": false, \"fastcgi\": true},\n    ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Each line contains information about one server. Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>name (string)\u003Cbr \u002F>\nName of host, something to identify this server.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>ip (string)\u003Cbr \u002F>\nIP address of server or full url. Format: scheme:\u002F\u002Fhost:port\u002Fpath\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>pagespeed (bool)\u003Cbr \u002F>\nServer uses Nginx Pagespeed (true) or not (false)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>fastcgi (bool)\u003Cbr \u002F>\nServer user Nginx FastCGI (true) or not (false)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When there is no hosts.json or the path is invalid, this plugin assumes the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\"servers\":\n    [\n        {\"name\": \"localhost\", \"ip\": \"127.0.0.1\", \"pagespeed\": true, \"fastcgi\": true}\n    ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>How does it work\u003C\u002Fh4>\n\u003Cp>“Cache control by Cacholong” empties partial or full cache for Nginx Pagespeed and FastCGI cache. WordPress HTTP API is used to make (post) request to\u003Cbr \u002F>\nspecific urls to trigger purges. Based on the http header responses this plugin determines if a purge is successful or not. The user is informed with messages, which are loaded after a purge and page refresh.\u003C\u002Fp>\n\u003Cp>There are several settings to tweak purging, see Settings > Cache control.\u003C\u002Fp>\n\u003Ch4>WP-CLI\u003C\u002Fh4>\n\u003Cp>There are several commands available for the commandline with wp-cli. Commands generate text output which can be suppressed with –quiet. When an error occurs, text will always be displayed.\u003C\u002Fp>\n\u003Ch4>WP-CLI exit codes\u003C\u002Fh4>\n\u003Cp>Exit codes are 0 (no errors) or 1 (generic error).\u003C\u002Fp>\n\u003Ch4>WP-CLI examples\u003C\u002Fh4>\n\u003Cp>Purge command with all arguments:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge [--cache=\u003Ccache>] [--ips=\u003Cips>]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx FastCGI:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=fastcgi\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx Pagespeed:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=pagespeed\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge all caches:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=all\nwp cacholong_cc purge\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx Pagespeed cache for ip address 127.0.0.1 and 127.0.0.2:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=pagespeed --ips=127.0.0.1,127.0.0.2\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge all caches for ip address 127.0.0.1 and 127.0.0.2:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --ips=127.0.0.1,127.0.0.2\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Factory reset options for given site_id or current blog if no site_id is given:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc factory_reset [--site_id=site_id]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Debug\u003C\u002Fh4>\n\u003Cp>Plugin will log basic purge information when WP_DEBUG is true (can be set in wp-config.php). Logs information in file wp-content\u002Fcacholong-cache-control.log.\u003Cbr \u002F>\nPlugin will log wp_remote_request details when CACHOLONG_CACHE_DEBUG_HTTP_API_REQUEST is true (can be set in wp-config.php). Logs information in file wp-content\u002Fcacholong-cache-control.log.\u003C\u002Fp>\n","“Cache control by Cacholong” is a cache control plugin for one or more Nginx servers.",500,6767,"2021-07-20T12:01:00.000Z","5.7.15","4.3.1","5.6",[51,19,20,90,91],"cacholong","pagespeed","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-control-by-cacholong.zip",43,2,"2025-04-01 00:00:00",{"slug":97,"name":98,"version":99,"author":100,"author_profile":101,"description":102,"short_description":103,"active_installs":104,"downloaded":105,"rating":65,"num_ratings":94,"last_updated":106,"tested_up_to":86,"requires_at_least":107,"requires_php":17,"tags":108,"homepage":17,"download_link":110,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":55},"last-modified-and-if-modified-since-headers","Last-Modified and If-Modified-Since Headers","1.0","zubovd","https:\u002F\u002Fprofiles.wordpress.org\u002Fzubovd\u002F","\u003Cp>This plugin adds the ‘Last-Modified’ header to each post and returns the ‘304 Not Modified’ header to the client without a body in the response if he sent the ‘If-Modified-Since’ header and the post has not changed since that date.\u003C\u002Fp>\n","Add Last-Modified anв support If-Modified-Since Headers",200,2524,"2021-07-20T14:31:00.000Z","5.2.4",[22,109,23],"if-modified-since","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flast-modified-and-if-modified-since-headers.zip",{"slug":112,"name":113,"version":114,"author":115,"author_profile":116,"description":117,"short_description":118,"active_installs":119,"downloaded":120,"rating":13,"num_ratings":13,"last_updated":121,"tested_up_to":122,"requires_at_least":123,"requires_php":17,"tags":124,"homepage":130,"download_link":131,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":55},"wp-super-secure-and-fast-htaccess","WP Super Secure and Fast htaccess","1.0.0","Andrea Pernici","https:\u002F\u002Fprofiles.wordpress.org\u002Fandreapernici\u002F","\u003Cp>This essential .htaccess rules plugin allow you to improve security and speed of your wordpress blog.\u003C\u002Fp>\n\u003Cp>More info:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>More info on \u003Ca href=\"http:\u002F\u002Fwww.andreapernici.com\u002Fwordpress\u002Fwp-super-secure-and-fast-htaccess\u002F\" rel=\"nofollow ugc\">WP Super Secure and Fast htaccess\u003C\u002Fa>, with info on how to configure it.\u003C\u002Fli>\n\u003Cli>Check out the other \u003Ca href=\"http:\u002F\u002Fwww.andreapernici.com\u002Fwordpress\u002F\" rel=\"nofollow ugc\">WordPress plugins\u003C\u002Fa> by the same author, and read his blog: \u003Ca href=\"http:\u002F\u002Fwww.andreapernici.com\" rel=\"nofollow ugc\">Andrea\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Special Thanks to \u003Ca href=\"http:\u002F\u002Fwww.salserocafe.com\u002F\" rel=\"nofollow ugc\">Salserocafe Article Marketing\u003C\u002Fa> for support.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Changelog\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>1.0.0\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>first release\u003C\u002Fli>\n\u003C\u002Ful>\n","This essential .htaccess rules plugin allow you to improve security and speed of your wordpress blog.",40,5833,"2010-02-11T09:09:00.000Z","2.9.2","2.6",[125,126,127,128,129],"htaccess","page-caching","page-expire-headers","web-performance-optimization","wordpress-security","http:\u002F\u002Fwww.andreapernici.com\u002Fwordpress\u002Fwp-super-secure-and-fast-htaccess\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-secure-and-fast-htaccess.1.0.0.zip",{"attackSurface":133,"codeSignals":149,"taintFlows":160,"riskAssessment":161,"analyzedAt":171},{"hooks":134,"ajaxHandlers":145,"restRoutes":146,"shortcodes":147,"cronEvents":148,"entryPointCount":13,"unprotectedCount":13},[135,141],{"type":136,"name":137,"callback":138,"priority":13,"file":139,"line":140},"action","shutdown","print_buffer","lh-add-headers.php",34,{"type":136,"name":142,"callback":143,"file":139,"line":144},"template_redirect","start_buffer",126,[],[],[],[],{"dangerousFunctions":150,"sqlUsage":151,"outputEscaping":154,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":159},[],{"prepared":152,"raw":13,"locations":153},1,[],{"escaped":13,"rawEcho":152,"locations":155},[156],{"file":139,"line":157,"context":158},111,"raw output",[],[],{"summary":162,"deductions":163},"The 'lh-add-headers' plugin version 1.04 exhibits a generally positive security posture based on the provided static analysis.  There are no identified dangerous functions, file operations, external HTTP requests, or SQL queries that do not utilize prepared statements. The absence of any known CVEs in its history is also a strong indicator of good security practices. However, a significant concern arises from the output escaping.  With 100% of outputs not being properly escaped, this presents a clear risk of Cross-Site Scripting (XSS) vulnerabilities if any dynamic data is reflected directly to the user.  Furthermore, the complete lack of nonce and capability checks, coupled with no identified attack surface, might suggest the plugin has limited functionality that doesn't require these checks. This could be a strength if the plugin is genuinely simple, or a weakness if its functionality is underestimated or could evolve to require such protections.",[164,166,169],{"reason":165,"points":66},"Output not properly escaped",{"reason":167,"points":168},"No nonce checks",4,{"reason":170,"points":168},"No capability checks","2026-04-16T11:33:31.992Z",{"wat":173,"direct":178},{"assetPaths":174,"generatorPatterns":175,"scriptPaths":176,"versionParams":177},[],[],[],[],{"cssClasses":179,"htmlComments":180,"htmlAttributes":181,"restEndpoints":182,"jsGlobals":183,"shortcodeOutput":184},[],[],[],[],[],[],{"error":186,"url":187,"statusCode":188,"statusMessage":189,"message":189},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Flh-add-headers\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":13,"versions":191},[]]