[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$friihwE_oIz2xBRFNUM99z7iN7z2rE1o13rdkKuRJjFw":3,"$fVLQ3swYBV31BQ8_oZc396W6ILW0iu2RJdW1goMVgcGw":156,"$fnIy2oQqgY63_zXzIZhOlUQngp5A8-yoFWkGcrEp19Pc":161},{"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":96,"fingerprints":132},"content-visibility-specific-users","Content Visibility Specific Users","0.1.1","Rich Tape","https:\u002F\u002Fprofiles.wordpress.org\u002Fiamfriendly\u002F","\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.",10,2842,0,"2022-12-13T19:40:00.000Z","6.1.10","5.0","7.0",[19,20,21,22,23],"block","content","contentvisibility","user","visibility","https:\u002F\u002Frichardtape.com\u002Fcontent-visibility\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-specific-users.0.1.1.zip",85,null,"2026-04-16T10:56:18.058Z","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-20T06:55:27.303Z",[39,52,63,75,86],{"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":28},"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",{"slug":53,"name":54,"version":55,"author":7,"author_profile":8,"description":56,"short_description":57,"active_installs":11,"downloaded":58,"rating":13,"num_ratings":13,"last_updated":59,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":60,"homepage":24,"download_link":62,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"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,61,23],"date","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-date-and-time.0.1.3.zip",{"slug":64,"name":65,"version":66,"author":7,"author_profile":8,"description":67,"short_description":68,"active_installs":11,"downloaded":69,"rating":13,"num_ratings":13,"last_updated":70,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":71,"homepage":24,"download_link":73,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":74},"content-visibility-geolocation","Content Visibility Geolocation","0.1.2","\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.",3550,"2022-12-13T19:34:00.000Z",[19,20,21,72,23],"geolocation","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-geolocation.0.1.2.zip","2026-04-06T09:54:40.288Z",{"slug":76,"name":77,"version":78,"author":7,"author_profile":8,"description":79,"short_description":80,"active_installs":11,"downloaded":81,"rating":13,"num_ratings":13,"last_updated":82,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":83,"homepage":24,"download_link":85,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"content-visibility-user-role","Content Visibility User Role","0.1.6","\u003Cp>Need to show a content block to only your site’s authors? Or maybe just to admins only? The User Roles 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\u003Cp>Every block on your site (including widgets) can be shown or hidden to users who have any role (or roles).\u003C\u002Fp>\n\u003Ch3>Custom Roles\u003C\u002Fh3>\n\u003Cp>This add-on supports any custom role that your theme or plugins have registered, as well as the native WordPress roles.\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>Development is mostly done on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Frichardtape\u002Fcontent-visibility-user-role\u002Fissues\u002Fnew\" rel=\"nofollow ugc\">github\u003C\u002Fa> and releases are made there and here to the WordPress plugins directory.\u003C\u002Fp>\n","A user roles add-on for Content Visibility.",3169,"2023-02-09T20:47:00.000Z",[19,20,22,84,23],"users","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-user-role.0.1.6.zip",{"slug":87,"name":88,"version":55,"author":7,"author_profile":8,"description":89,"short_description":90,"active_installs":13,"downloaded":91,"rating":13,"num_ratings":13,"last_updated":92,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":93,"homepage":24,"download_link":95,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"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,94,23],"rss","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-rss-feed.0.1.3.zip",{"attackSurface":97,"codeSignals":113,"taintFlows":120,"riskAssessment":121,"analyzedAt":131},{"hooks":98,"ajaxHandlers":109,"restRoutes":110,"shortcodes":111,"cronEvents":112,"entryPointCount":13,"unprotectedCount":13},[99,105],{"type":100,"name":101,"callback":102,"priority":35,"file":103,"line":104},"action","content_visibility_enqueue_editor_assets","anonymous","includes\\content-visibility-specific-users.php",17,{"type":106,"name":107,"callback":102,"file":103,"line":108},"filter","content_visibility_rule_types_and_callbacks",64,[],[],[],[],{"dangerousFunctions":114,"sqlUsage":115,"outputEscaping":117,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":119},[],{"prepared":13,"raw":13,"locations":116},[],{"escaped":13,"rawEcho":13,"locations":118},[],[],[],{"summary":122,"deductions":123},"The \"content-visibility-specific-users\" plugin, in version 0.1.1, exhibits a remarkably clean static analysis report, with no identified dangerous functions, SQL queries without prepared statements, or unescaped output.  The absence of file operations and external HTTP requests further contributes to a seemingly secure codebase in these areas.  Furthermore, the plugin has no recorded vulnerability history, including CVEs, suggesting a lack of past security incidents.\n\nHowever, the complete absence of entry points (AJAX handlers, REST API routes, shortcodes, cron events) and also the complete absence of any capability checks or nonce checks is a significant concern. While this means there are no *currently identifiable* attack vectors through these common plugin interaction points, it also means the plugin is not designed to be interacted with in a secure, controlled manner if any functionality were to be added later. The lack of these security mechanisms means that any future additions to the plugin's functionality that introduce entry points would be inherently vulnerable without them. This indicates a potential for future security weaknesses if the plugin evolves.",[124,127,129],{"reason":125,"points":126},"No capability checks implemented",15,{"reason":128,"points":126},"No nonce checks implemented",{"reason":130,"points":47},"No attack surface entry points","2026-03-16T23:26:24.338Z",{"wat":133,"direct":142},{"assetPaths":134,"generatorPatterns":137,"scriptPaths":138,"versionParams":139},[135,136],"\u002Fwp-content\u002Fplugins\u002Fcontent-visibility-specific-users\u002Fbuild\u002Findex.js","\u002Fwp-content\u002Fplugins\u002Fcontent-visibility-specific-users\u002Fbuild\u002Findex.css",[],[135],[140,141],"content-visibility-specific-users\u002Fbuild\u002Findex.js?ver=","content-visibility-specific-users-panel?ver=",{"cssClasses":143,"htmlComments":149,"htmlAttributes":150,"restEndpoints":152,"jsGlobals":153,"shortcodeOutput":155},[144,145,146,147,148],"block-editor-block-list__block__drag-handle","block-editor-block-list__block__handle","block-editor-block-list__block__icons","block-editor-block-list__block__resize-handle","block-editor-block-list__block__remove",[],[151],"data-block=\"content-visibility\u002Fspecificusers\"",[],[154],"BlockVisibilitySpecificUsers",[],{"error":157,"url":158,"statusCode":159,"statusMessage":160,"message":160},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fcontent-visibility-specific-users\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":162,"versions":163},2,[164,170],{"version":6,"download_url":25,"svn_tag_url":165,"released_at":27,"has_diff":166,"diff_files_changed":167,"diff_lines":27,"trac_diff_url":168,"vulnerabilities":169,"is_current":157},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcontent-visibility-specific-users\u002Ftags\u002F0.1.1\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fcontent-visibility-specific-users%2Ftags%2F0.1.0&new_path=%2Fcontent-visibility-specific-users%2Ftags%2F0.1.1",[],{"version":171,"download_url":172,"svn_tag_url":173,"released_at":27,"has_diff":166,"diff_files_changed":174,"diff_lines":27,"trac_diff_url":27,"vulnerabilities":175,"is_current":166},"0.1.0","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcontent-visibility-specific-users.0.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcontent-visibility-specific-users\u002Ftags\u002F0.1.0\u002F",[],[]]