[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f8U2VC7pTbTzgZCBnkE8DXCeTBNiTsCRdoTnIYYnkhyA":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"arnaudpf","https:\u002F\u002Fprofiles.wordpress.org\u002Farnaudpf\u002F",1,0,85,30,84,"2026-07-15T11:07:57.826Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":7,"num_ratings":7,"last_updated":20,"tested_up_to":21,"requires_at_least":22,"requires_php":23,"tags":24,"homepage":30,"download_link":31,"security_score":8,"vuln_count":7,"unpatched_count":7,"last_vuln_date":32,"fetched_at":33},"delivery-area-free-for-woocommerce","Delivery Area","1.0.0","\u003Cp>This is the long description.  No limit, and you can use Markdown (as well as in the following sections).\u003C\u002Fp>\n\u003Cp>For backwards compatibility, if this section is missing, the full length of the short description will be used, and\u003Cbr \u002F>\nMarkdown parsed.\u003C\u002Fp>\n\u003Cp>A few notes about the sections above:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>“Contributors” is a comma separated list of wordpress.org usernames\u003C\u002Fli>\n\u003Cli>“Tags” is a comma separated list of tags that apply to the plugin\u003C\u002Fli>\n\u003Cli>“Requires at least” is the lowest version that the plugin will work on\u003C\u002Fli>\n\u003Cli>“Tested up to” is the highest version that you’ve \u003Cem>successfully used to test the plugin\u003C\u002Fem>. Note that it might work on\u003Cbr \u002F>\nhigher versions… this is just the highest one you’ve verified.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use \u003Ccode>\u002Ftrunk\u002F\u003C\u002Fcode> for\u003Cbr \u002F>\nstable.\u003C\u002Fp>\n\u003Cp>Note that the \u003Ccode>readme.txt\u003C\u002Fcode> of the stable tag is the one that is considered the defining one for the plugin, so\u003Cbr \u002F>\nif the \u003Ccode>\u002Ftrunk\u002Freadme.txt\u003C\u002Fcode> file says that the stable tag is \u003Ccode>4.3\u003C\u002Fcode>, then it is \u003Ccode>\u002Ftags\u002F4.3\u002Freadme.txt\u003C\u002Fcode> that’ll be used\u003Cbr \u002F>\nfor displaying information about the plugin.  In this situation, the only thing considered from the trunk \u003Ccode>readme.txt\u003C\u002Fcode>\u003Cbr \u002F>\nis the stable tag pointer.  Thus, if you develop in trunk, you can update the trunk \u003Ccode>readme.txt\u003C\u002Fcode> to reflect changes in\u003Cbr \u002F>\nyour in-development version, without having that information incorrectly disclosed about the current stable version\u003Cbr \u002F>\nthat lacks those changes — as long as the trunk’s \u003Ccode>readme.txt\u003C\u002Fcode> points to the correct stable tag.\u003C\u002Fp>\n\u003Cp>If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where\u003Cbr \u002F>\nyou put the stable version, in order to eliminate any doubt.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>A brief Markdown Example\u003C\u002Fh3>\n\u003Cp>Ordered list:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Some feature\u003C\u002Fli>\n\u003Cli>Another feature\u003C\u002Fli>\n\u003Cli>Something else about the plugin\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Unordered list:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>something\u003C\u002Fli>\n\u003Cli>something else\u003C\u002Fli>\n\u003Cli>third thing\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Here’s a link to \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002F\" title=\"Your favorite software\" rel=\"ugc\">WordPress\u003C\u002Fa> and one to \u003Ca href=\"https:\u002F\u002Fdaringfireball.net\u002Fprojects\u002Fmarkdown\u002Fsyntax\" title=\"Markdown is what the parser uses to process much of the readme file\" rel=\"nofollow ugc\">Markdown’s Syntax Documentation\u003C\u002Fa>.\u003Cbr \u002F>\nTitles are optional, naturally.\u003C\u002Fp>\n\u003Cp>Markdown uses email style notation for blockquotes and I’ve been told:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>Asterisks for \u003Cem>emphasis\u003C\u002Fem>. Double it up  for \u003Cstrong>strong\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cpre>\u003Ccode>\u003C?php code(); \u002F\u002F goes in backticks ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n","A WooCommerce extention that allows you to define one custom delivery area by drawing polygons on a Google Map !",1095,"2021-11-17T22:28:00.000Z","5.8.13","5.6","7.0",[25,26,27,28,29],"area","delivery","polygons","woocommerce","zone","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdelivery-area-free-for-woocommerce.1.0.0.zip",null,"2026-04-16T10:56:18.058Z"]