[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fM12BTuw1RYG-EZNz5A-8eLHUMnEq4rLhxFSem8NvMdQ":3,"$fDvzJN0dAr3UXn7NfLJUSUfjr94SRwRKHZ4jrwRtYqYI":157,"$f3onH9O1sUqzMWLgjmp3HLWAYEIiwWkDfXGRJSurX_E8":162},{"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":38,"analysis":105,"fingerprints":139},"content-visibility-geolocation","Content Visibility Geolocation","0.1.2","Rich Tape","https:\u002F\u002Fprofiles.wordpress.org\u002Fiamfriendly\u002F","\u003Cp>Content Visibility Geolocation is an add-on for \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcontent-visibility\u002F\" rel=\"ugc\">Content Visibility\u003C\u002Fa> – a plugin which allows you to decide when, where, and to whom each piece of your content is shown (or hidden!).\u003C\u002Fp>\n\u003Cp>The geolocation add-on allows you to show or hide any of your content blocks to users visiting your site from any country of your choosing.\u003C\u002Fp>\n\u003Cp>Need to only show a message to folks visiting from Canada 🇨🇦? No problems, eh.\u003C\u002Fp>\n\u003Cp>How about showing a banner to your British 🇬🇧 visitors? You got it, guvnor. (I’m a Brit living in Canada 😉 )\u003C\u002Fp>\n\u003Cp>Note: This uses cookies to help reduce API calls. If that is something you need to tell your users about, please make sure to do just that 🙂\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>Development is mostly done on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frichardtape\u002Fcontent-visibility-geolocation\u002Fissues\u002Fnew\" rel=\"nofollow ugc\">github\u003C\u002Fa> and releases are made there and here to the WordPress plugins directory.\u003C\u002Fp>\n","A geolocation add-on for Content Visibility.",10,3550,0,"2022-12-13T19:34:00.000Z","6.1.10","5.0","7.0",[19,20,21,22,23],"block","content","contentvisibility","geolocation","visibility","https:\u002F\u002Frichardtape.com\u002Fcontent-visibility\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-geolocation.0.1.2.zip",85,null,"2026-04-06T09:54:40.288Z","no_bundle",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":26,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"iamfriendly",6,140,30,84,"2026-05-20T08:03:45.538Z",[39,53,64,75,85],{"slug":40,"name":41,"version":42,"author":7,"author_profile":8,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":45,"num_ratings":47,"last_updated":48,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":49,"homepage":24,"download_link":51,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":52},"content-visibility","Content Visibility","0.2.9","\u003Cp>Your Content. Your Rules. Decide who sees what and when. No setup or complex settings. Write content, decide who should see it, and press publish.\u003C\u002Fp>\n\u003Cp>Content Visibility provides a set of controls to say whether each discrete piece of content (or ‘block’ in WordPress parlance) should be shown to users who are signed in to your site or not. Additional add-ons provide controls for \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frichardtape\u002Fcontent-visibility-user-role\" rel=\"nofollow ugc\">\u003Cstrong>role-based\u003C\u002Fstrong>\u003C\u002Fa> visibility, \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcontent-visibility-date-and-time\u002F\" rel=\"ugc\">\u003Cstrong>time-based\u003C\u002Fstrong>\u003C\u002Fa> visibility, and \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcontent-visibility-geolocation\u002F\" rel=\"ugc\">\u003Cstrong>location-based\u003C\u002Fstrong>\u003C\u002Fa> visibility. You can also show or hide blocks to folks using \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcontent-visibility-rss-feed\u002F\" rel=\"ugc\">RSS\u003C\u002Fa> Readers.\u003C\u002Fp>\n\u003Ch3>Individual Block Controls\u003C\u002Fh3>\n\u003Cp>Every individual block on all posts and pages (and custom post types) on your site can have their own controls. Mix and match the visibility of blocks on a single page. Need some blocks to show to everyone and a few to only be available to your site’s subscribers? No problem. Only want a message to appear on Christmas Day? You got it. Only want those who are signed in to your site to see certain pieces of content? Easy peasy.\u003C\u002Fp>\n\u003Ch3>At a glance\u003C\u002Fh3>\n\u003Cp>An icon next to each block with active rules allows your content authors to see which blocks may or may not be shown to certain audiences at a glance.\u003C\u002Fp>\n\u003Ch3>Reusable blocks\u003C\u002Fh3>\n\u003Cp>Use Reusable Blocks? No problem, Content Visibility handles those too.\u003C\u002Fp>\n\u003Ch3>Columns and Nested Blocks\u003C\u002Fh3>\n\u003Cp>Do you use columns and put other blocks in them? Content Visibility allows you to control both the ‘nested’ blocks (such as a paragraph block in a column block) or the ‘parent’ block themselves (perhaps hide an entire column for users who aren’t signed in?). Other examples of nested blocks are the Group Block or if you use an accordion or tabs block; all work!\u003C\u002Fp>\n\u003Ch3>Widgets\u003C\u002Fh3>\n\u003Cp>Since version 0.1.7 you are now able to control the visibility of your widgets. As long as you have version 9.9 or above of the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fgutenberg\u002F\" rel=\"ugc\">Gutenberg plugin\u003C\u002Fa> you are able to use content visibility on all of your widgets, just like you can with all of your blocks in the content editor. Limit display of your widgets on specific URLs on your site. Want to show a specific text block to only people who are signed in and ONLY on search results? You got it.\u003C\u002Fp>\n\u003Cp>Version 0.2.5 adds the ability to show or hide your widgets on posts that are in specific category or tags.\u003C\u002Fp>\n\u003Ch3>Coming Soon\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>[ ] A way to set replacement content when a block is hidden\u003C\u002Fli>\n\u003Cli>[ ] REST API exploration. Should be fine for non-authenticated requests, but need to dive deeper for auth’d requests\u003C\u002Fli>\n\u003Cli>[ ] Non-trivial dates. Think things like “Every Wednesday between 3pm and 4pm” or “First two weeks in November”\u003C\u002Fli>\n\u003Cli>[x] \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcontent-visibility-geolocation\u002F\" rel=\"ugc\">Geolocation\u003C\u002Fa>: Show this block only to users whose connection is in France.\u003C\u002Fli>\n\u003Cli>[x] \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcontent-visibility-specific-users\u002F\" rel=\"ugc\">Specific Users\u003C\u002Fa>: Show or hide a block to one or more specific users.\u003C\u002Fli>\n\u003Cli>[ ] Specific 3rd-party plugin integrations. Show a block when someone has purchased something from your WooCommerce store. Or when someone has submitted a specific Gravity Form.\u003C\u002Fli>\n\u003Cli>[ ] Do you have any feature requests? \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frichardtape\u002Fcontent-visibility\u002Fissues\u002Fnew\" rel=\"nofollow ugc\">Let me know!\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>Development is mostly done on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frichardtape\u002Fcontent-visibility\" rel=\"nofollow ugc\">github\u003C\u002Fa> and releases are made there and here to the WordPress plugins directory.\u003C\u002Fp>\n","Decide when, where, and to whom your blocks are visible.",100,6016,5,"2022-12-13T18:23:00.000Z",[19,20,21,50,23],"show","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility.0.2.9.zip","2026-04-16T10:56:18.058Z",{"slug":54,"name":55,"version":56,"author":7,"author_profile":8,"description":57,"short_description":58,"active_installs":11,"downloaded":59,"rating":13,"num_ratings":13,"last_updated":60,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":61,"homepage":24,"download_link":63,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":52},"content-visibility-date-and-time","Content Visibility Date and Time","0.1.3","\u003Cp>Need to show a content block between two dates? Or after a certain date and time? Or \u003Cem>until\u003C\u002Fem> a particular date in the future? The Date and Time add-on for \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fcontent-visibility\u002F\" rel=\"ugc\">Content Visbility\u003C\u002Fa> allows you to do just that!\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>Development is mostly done on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frichardtape\u002Fcontent-visibility-date-and-time\u002Fissues\u002Fnew\" rel=\"nofollow ugc\">github\u003C\u002Fa> and releases are made there and here to the WordPress plugins directory.\u003C\u002Fp>\n","A date and time add-on for Content Visibility.",3730,"2022-12-13T18:27:00.000Z",[19,20,21,62,23],"date","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-date-and-time.0.1.3.zip",{"slug":65,"name":66,"version":67,"author":7,"author_profile":8,"description":68,"short_description":69,"active_installs":11,"downloaded":70,"rating":13,"num_ratings":13,"last_updated":71,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":72,"homepage":24,"download_link":74,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":52},"content-visibility-specific-users","Content Visibility Specific Users","0.1.1","\u003Cp>Do you need to show or hide some of your content blocks to one or more users? The specific users add-on for Content Visibility lets you do just that.\u003C\u002Fp>\n\u003Cp>Want to preview a change on an already-live page that only you can see? Make the new block only shown to you and the old block NOT shown to you.\u003Cbr \u002F>\nDoes your colleague need to see a change before it’s approved? Uh huh!\u003Cbr \u002F>\nWant to leave yourself a note that only you should see? You got it.\u003Cbr \u002F>\nWant to show a form for one specific person so only they can fill it in? Yup.\u003Cbr \u002F>\nHide or show any block for any specific user or users.\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>Development is mostly done on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frichardtape\u002Fcontent-visibility-specific-users\u002Fissues\u002Fnew\" rel=\"nofollow ugc\">github\u003C\u002Fa> and releases are made there and here to the WordPress plugins directory.\u003C\u002Fp>\n","A Specific Users add-on for Content Visibility.",2842,"2022-12-13T19:40:00.000Z",[19,20,21,73,23],"user","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-specific-users.0.1.1.zip",{"slug":76,"name":77,"version":56,"author":7,"author_profile":8,"description":78,"short_description":79,"active_installs":13,"downloaded":80,"rating":13,"num_ratings":13,"last_updated":81,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":82,"homepage":24,"download_link":84,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":52},"content-visibility-rss-feed","Content Visibility RSS Feed","\u003Cp>Show or Hide certain pieces of content on your RSS Feeds. WordPress by default has RSS Feeds for a whole bunch of your content; posts, categories, tags, date, authors, and more besides. Content Visibility RSS Feeds allows you to choose precisely what is shown (And not shown) to RSS Feed Readers.\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>Development is mostly done on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frichardtape\u002Fcontent-visibility-rss-feed\u002Fissues\u002Fnew\" rel=\"nofollow ugc\">github\u003C\u002Fa> and releases are made there and here to the WordPress plugins directory.\u003C\u002Fp>\n","As RSS Feed add-on for Content Visibility.",3182,"2022-12-14T22:32:00.000Z",[19,20,21,83,23],"rss","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-rss-feed.0.1.3.zip",{"slug":86,"name":87,"version":88,"author":89,"author_profile":90,"description":91,"short_description":92,"active_installs":13,"downloaded":93,"rating":13,"num_ratings":13,"last_updated":94,"tested_up_to":95,"requires_at_least":96,"requires_php":97,"tags":98,"homepage":102,"download_link":103,"security_score":104,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"intelli-builder","IntelliBuilder","1.0.0","Yaseen Taha","https:\u002F\u002Fprofiles.wordpress.org\u002Fshowyaseen\u002F","\u003Cp>\u003Cstrong>IntelliBuilder\u003C\u002Fstrong> empowers WordPress administrators to dynamically control the visibility of Gutenberg blocks by implementing a broad range of customizable conditions. By integrating seamlessly with the Gutenberg editor, IntelliBuilder adds a new dimension to content management, allowing for finely tuned, personalized content delivery.\u003C\u002Fp>\n\u003Ch3>Key Features:\u003C\u002Fh3>\n\u003Cp>– \u003Cstrong>User Roles:\u003C\u002Fstrong> Target content based on specific user roles (e.g., Administrator, Editor, Subscriber).\u003Cbr \u002F>\n– \u003Cstrong>Geolocation:\u003C\u002Fstrong> Display or hide content based on the user’s country and city, leveraging real-time IP-based location detection.\u003Cbr \u002F>\n– \u003Cstrong>Browser Detection:\u003C\u002Fstrong> Customize content visibility according to the user’s browser (e.g., Chrome, Firefox, Safari).\u003Cbr \u002F>\n– \u003Cstrong>Device Type:\u003C\u002Fstrong> Tailor content for different device types, including Desktop, Tablet, and Mobile.\u003Cbr \u002F>\n– \u003Cstrong>Operating System:\u003C\u002Fstrong> Control visibility based on the user’s operating system (e.g., Windows, macOS, Linux, iOS, Android).\u003Cbr \u002F>\n– \u003Cstrong>Referral Source:\u003C\u002Fstrong> Show or hide content based on the user’s referral source, ideal for targeted marketing campaigns.\u003Cbr \u002F>\n– \u003Cstrong>Recurring vs New Users:\u003C\u002Fstrong> Differentiate content between first-time visitors and returning users.\u003Cbr \u002F>\n– \u003Cstrong>User Status:\u003C\u002Fstrong> Display content conditionally for logged-in or logged-out users.\u003Cbr \u002F>\n– \u003Cstrong>User-Specific Rules:\u003C\u002Fstrong> Target individual users by their username for a personalized experience.\u003Cbr \u002F>\n– \u003Cstrong>Browser Language:\u003C\u002Fstrong> Adapt content based on the language settings of the user’s browser.\u003Cbr \u002F>\n– \u003Cstrong>Scheduled Content:\u003C\u002Fstrong> Schedule the visibility of Gutenberg blocks to appear or disappear at specific times and dates.\u003C\u002Fp>\n\u003Ch3>Example Use Cases:\u003C\u002Fh3>\n\u003Cp>– \u003Cstrong>Membership Sites:\u003C\u002Fstrong> Display exclusive content to logged-in members only, enhancing membership value.\u003Cbr \u002F>\n– \u003Cstrong>Marketing Campaigns:\u003C\u002Fstrong> Tailor promotional content based on referral sources to improve conversion rates.\u003Cbr \u002F>\n– \u003Cstrong>Localization:\u003C\u002Fstrong> Serve region-specific information by utilizing the user’s geolocation and browser language.\u003Cbr \u002F>\n– \u003Cstrong>Device-Specific Content:\u003C\u002Fstrong> Optimize content delivery for different devices and operating systems for a seamless user experience.\u003C\u002Fp>\n\u003Ch3>How It Works:\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\u003Cstrong>Initialization:\u003C\u002Fstrong> Hooks into WordPress actions and filters via the \u003Ccode>intelli-builder.php\u003C\u002Fcode> file to initialize the plugin.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gutenberg Integration:\u003C\u002Fstrong> React components within \u003Ccode>src\u002Fblocks\u002Fvisibility-settings\u002F\u003C\u002Fcode> render the visibility settings interface directly within the Gutenberg block editor.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Rule Configuration:\u003C\u002Fstrong> Administrators configure visibility rules in the Gutenberg block settings panel.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Conditional Rendering:\u003C\u002Fstrong> When rendering a post or page, IntelliBuilder evaluates the defined visibility rules to determine which blocks should be displayed.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Third-Party Dependencies\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>1. CountriesNow API\u003C\u002Fstrong>\u003Cbr \u002F>\n– \u003Cstrong>Purpose:\u003C\u002Fstrong> Provides a list of countries and their cities for precise geolocation-based visibility rules.\u003Cbr \u002F>\n– \u003Cstrong>Integration:\u003C\u002Fstrong> Used in the \u003Ccode>GeoLocation\u003C\u002Fcode> React component to enable country and city selection.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. IP-API\u003C\u002Fstrong>\u003Cbr \u002F>\n– \u003Cstrong>Purpose:\u003C\u002Fstrong> Detects the user’s geographical location based on their IP address.\u003Cbr \u002F>\n– \u003Cstrong>Integration:\u003C\u002Fstrong> Utilized in the \u003Ccode>GeoIP\u003C\u002Fcode> PHP class to automatically retrieve user location data for geolocation rules.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. hisorange\u002Fbrowser-detect\u003C\u002Fstrong>\u003Cbr \u002F>\n– \u003Cstrong>Purpose:\u003C\u002Fstrong> Detects the user’s browser, device type, operating system, and language.\u003Cbr \u002F>\n– \u003Cstrong>Integration:\u003C\u002Fstrong> Powers several visibility rules, including browser name, device type, operating system, and browser language detection.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This plugin is licensed under the GPLv2 or later. See the \u003Ca href=\"https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\" rel=\"nofollow ugc\">GNU General Public License\u003C\u002Fa> for more details.\u003C\u002Fp>\n","IntelliBuilder: Control Gutenberg block visibility with custom rules for user roles, devices, locations, and more.",1069,"2024-08-27T18:31:00.000Z","6.6.5","5.5","7.2",[99,100,40,22,101],"browser-detection","conditional-blocks","user-roles","https:\u002F\u002Fwordpress.com\u002Fplugins\u002Fintelli-builder","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fintelli-builder.1.0.0.zip",92,{"attackSurface":106,"codeSignals":125,"taintFlows":134,"riskAssessment":135,"analyzedAt":138},{"hooks":107,"ajaxHandlers":121,"restRoutes":122,"shortcodes":123,"cronEvents":124,"entryPointCount":13,"unprotectedCount":13},[108,114,118],{"type":109,"name":110,"callback":111,"priority":35,"file":112,"line":113},"action","content_visibility_enqueue_editor_assets","anonymous","includes\\content-visibility-geolocation.php",16,{"type":115,"name":116,"callback":111,"file":112,"line":117},"filter","content_visibility_rule_types_and_callbacks",72,{"type":109,"name":119,"callback":111,"file":112,"line":120},"init",146,[],[],[],[],{"dangerousFunctions":126,"sqlUsage":127,"outputEscaping":129,"fileOperations":13,"externalRequests":132,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":133},[],{"prepared":13,"raw":13,"locations":128},[],{"escaped":130,"rawEcho":13,"locations":131},9,[],1,[],[],{"summary":136,"deductions":137},"The \"content-visibility-geolocation\" plugin v0.1.2 demonstrates a strong security posture based on the provided static analysis. The absence of any AJAX handlers, REST API routes, shortcodes, or cron events with unprotected entry points is a significant positive. Furthermore, the code signals indicate good development practices with no dangerous functions, 100% of SQL queries using prepared statements, and all output being properly escaped. The lack of file operations and the single external HTTP request, while noted, do not inherently represent a security risk without further context on the request's target and content handling.\n\nThe plugin's vulnerability history is completely clean, with zero known CVEs across all severity levels and no previously recorded vulnerabilities. This suggests a history of responsible development and maintenance, or simply that the plugin has not been a target of significant security research. The taint analysis also shows no critical or high severity flows, reinforcing the initial positive assessment.\n\nWhile the plugin exhibits excellent security practices in its current state, the small attack surface (zero entry points) and the early version number (0.1.2) might indicate limited functionality. The absence of capability checks and nonce checks is not a direct concern given the lack of exposed entry points, but it's something to monitor if functionality is added in future versions. Overall, the plugin appears secure for its current scope, but ongoing vigilance is always recommended, especially as features are added.",[],"2026-03-16T23:11:08.824Z",{"wat":140,"direct":149},{"assetPaths":141,"generatorPatterns":144,"scriptPaths":145,"versionParams":146},[142,143],"\u002Fwp-content\u002Fplugins\u002Fcontent-visibility-geolocation\u002Fbuild\u002Findex.js","\u002Fwp-content\u002Fplugins\u002Fcontent-visibility-geolocation\u002Fbuild\u002Findex.css",[],[142],[147,148],"content-visibility-geolocation\u002Fbuild\u002Findex.js","content-visibility-geolocation\u002Fbuild\u002Findex.css",{"cssClasses":150,"htmlComments":151,"htmlAttributes":152,"restEndpoints":153,"jsGlobals":154,"shortcodeOutput":156},[],[],[],[],[155],"BlockVisibilityGeolocation",[],{"error":158,"url":159,"statusCode":160,"statusMessage":161,"message":161},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fcontent-visibility-geolocation\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":163,"versions":164},3,[165,171,177],{"version":6,"download_url":25,"svn_tag_url":166,"released_at":27,"has_diff":167,"diff_files_changed":168,"diff_lines":27,"trac_diff_url":169,"vulnerabilities":170,"is_current":158},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcontent-visibility-geolocation\u002Ftags\u002F0.1.2\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fcontent-visibility-geolocation%2Ftags%2F0.1.1&new_path=%2Fcontent-visibility-geolocation%2Ftags%2F0.1.2",[],{"version":67,"download_url":172,"svn_tag_url":173,"released_at":27,"has_diff":167,"diff_files_changed":174,"diff_lines":27,"trac_diff_url":175,"vulnerabilities":176,"is_current":167},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-geolocation.0.1.1.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcontent-visibility-geolocation\u002Ftags\u002F0.1.1\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fcontent-visibility-geolocation%2Ftags%2F0.1.0&new_path=%2Fcontent-visibility-geolocation%2Ftags%2F0.1.1",[],{"version":178,"download_url":179,"svn_tag_url":180,"released_at":27,"has_diff":167,"diff_files_changed":181,"diff_lines":27,"trac_diff_url":27,"vulnerabilities":182,"is_current":167},"0.1.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-geolocation.0.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcontent-visibility-geolocation\u002Ftags\u002F0.1.0\u002F",[],[]]