[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f6EBdMqfdoLIapBowF1rSSCedLzQGiikx2ZonsbHMI4c":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":14,"tags":17,"homepage":20,"download_link":21,"security_score":22,"vuln_count":13,"unpatched_count":13,"last_vuln_date":23,"fetched_at":24,"vulnerabilities":25,"developer":26,"crawl_stats":23,"alternatives":33,"analysis":139,"fingerprints":169},"remove-super-admin-from-user-list-table","Remove Super Admin from User List Table","3.0","Emerson Maningo","https:\u002F\u002Fprofiles.wordpress.org\u002Fcodex-m\u002F","\u003Cp>In a multisite, super admins are listed together with ordinary admins in the child site user list page. For example, say the main site is cooldomain.com and one of the child site is subdomain.cooldomain.com.\u003C\u002Fp>\n\u003Cp>Super admins appear in the user list page in subdomain.cooldomain.com , example here: subdomain.cooldomain.com\u002Fwp-admin\u002Fusers.php\u003C\u002Fp>\n\u003Cp>Some super admins may not want this for privacy and security. This plugin removes the super admin from the child site user list page.\u003C\u002Fp>\n","Remove Super Admin from User List Table simply removes super admin from all of the multisite child site user list page.",10,1700,0,"","6.9.4","3.7",[18,19],"multisite","super-admin","http:\u002F\u002Fwww.php-developer.org\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fremove-super-admin-from-user-list-table.3.0.zip",100,null,"2026-03-15T10:48:56.248Z",[],{"slug":27,"display_name":7,"profile_url":8,"plugin_count":28,"total_installs":29,"avg_security_score":22,"avg_patch_time_days":30,"trust_score":31,"computed_at":32},"codex-m",2,210,103,79,"2026-04-06T02:49:51.764Z",[34,55,72,97,117],{"slug":35,"name":36,"version":37,"author":38,"author_profile":39,"description":40,"short_description":41,"active_installs":11,"downloaded":42,"rating":22,"num_ratings":43,"last_updated":44,"tested_up_to":45,"requires_at_least":6,"requires_php":14,"tags":46,"homepage":51,"download_link":52,"security_score":53,"vuln_count":13,"unpatched_count":13,"last_vuln_date":23,"fetched_at":54},"extended-super-admins","Extended Super Admins","0.7b","Curtiss Grymala","https:\u002F\u002Fprofiles.wordpress.org\u002Fcgrymala\u002F","\u003Cp>The way that WordPress roles and capabilities are set up, there is only level of Super Admin available. Without this plugin, the only way to grant a user control over certain aspects of the network, you have to grant that user control over all aspects.\u003C\u002Fp>\n\u003Cp>This plugin allows you to revoke specific privileges from any Super Admin on the network. You can create new roles within the site, then assign any Super Admin to that role; effectively removing the appropriate privileges.\u003C\u002Fp>\n\u003Cp>This plugin does not grant any new privileges (with the possible exception of the ability to manage the settings for this plugin itself) to any users. It is only capable of removing privileges.\u003C\u002Fp>\n\u003Cp>This plugin is also built to be compatible with the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-multi-network\u002F\" rel=\"ugc\">WordPress Multi Network\u003C\u002Fa> plugin and the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fnetworks-for-wordpress\u002F\" rel=\"ugc\">Networks for WordPress\u003C\u002Fa> plugin. If either of those plugins is active, the options for this plugin will be saved and used for all of the networks within the installation.\u003C\u002Fp>\n\u003Cp>This plugin was developed by \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fprofile\u002Fcgrymala\" rel=\"ugc\">Curtiss Grymala\u003C\u002Fa> for the \u003Ca href=\"http:\u002F\u002Fumw.edu\u002F\" rel=\"nofollow ugc\">University of Mary Washington\u003C\u002Fa>. It is licensed under the GPL2, which basically means you can take it, break it and change it any way you want, as long as the original credit and license information remains somewhere in the package.\u003C\u002Fp>\n\u003Ch3>Important Notice\u003C\u002Fh3>\n\u003Cp>It is entirely possible that there could be serious bugs when used in different settings. At this time, I am seeking people to test the plugin, so please report any issues you encounter. Thank you.\u003C\u002Fp>\n\u003Cp>Also, if you are updating from the original public alpha of this plugin, you will need to delete the old version before installing this version. The folder name changed from extended_super_admins in the initial release to extended-super-admins in newer versions.\u003C\u002Fp>\n\u003Cp>If you downloaded and installed this plugin from the WordPress repository, you will not need to do so, as the folder name changed when adding this plugin to that repository.\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>This plugin requires WordPress. It might work with WordPressMU versions older than 3.0, but it has not been tested with those.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>This plugin requires WordPress to be setup in Multi Site mode. It will not do anything at all if the Multi Site functions are not enabled.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>This plugin also requires PHP5. Some attempt has been made to make it compatible with PHP4, but it has not been tested in that environment.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>To Do\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>Make the Codex retrieval more efficient (find a better way to cache the information and a better way to compare it to Codex revisions)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Continue to improve the UI for the plugin to make it as user-friendly as possible\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Known Issues\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>On occasion, the JavaScript in this plugin might cause CPU usage to spike and freeze the browser momentarily\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin allows you to create multiple levels of Super Admins in a multi-site configuration.",12752,1,"2013-09-03T17:54:00.000Z","3.6.1",[18,47,48,49,50],"role-manager","site-admin","super-admins","wpmu","http:\u002F\u002Fplugins.ten-321.com\u002Fextended-super-admins\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fextended-super-admins.0.7b.zip",85,"2026-03-15T15:16:48.613Z",{"slug":56,"name":57,"version":58,"author":59,"author_profile":60,"description":61,"short_description":62,"active_installs":11,"downloaded":63,"rating":22,"num_ratings":64,"last_updated":65,"tested_up_to":66,"requires_at_least":67,"requires_php":14,"tags":68,"homepage":70,"download_link":71,"security_score":53,"vuln_count":13,"unpatched_count":13,"last_vuln_date":23,"fetched_at":54},"wp-hide-super-admin-users","Hide Super Admin Users","1.0","Josh Eby","https:\u002F\u002Fprofiles.wordpress.org\u002Fjosheby\u002F","\u003Cp>Are you running a multisite installation and wish to hide the super admin users from the individual site administrators?\u003Cbr \u002F>\nThis plugin will hide super admin users from all users that are not a super admin themselves.\u003C\u002Fp>\n\u003Cp>Note: This plugin will have no effect on a non-multisite install.\u003C\u002Fp>\n","Hides super admin users from non-super admin users within the dashboard of a WordPress multisite install.",2722,3,"2022-01-28T03:06:00.000Z","5.9.13","4.0",[18,69,19],"network","https:\u002F\u002Fgithub.com\u002Fjosheby\u002Fwp-hide-super-admin-users","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-hide-super-admin-users.zip",{"slug":73,"name":74,"version":75,"author":76,"author_profile":77,"description":78,"short_description":79,"active_installs":80,"downloaded":81,"rating":82,"num_ratings":83,"last_updated":84,"tested_up_to":15,"requires_at_least":85,"requires_php":86,"tags":87,"homepage":92,"download_link":93,"security_score":94,"vuln_count":95,"unpatched_count":13,"last_vuln_date":96,"fetched_at":54},"code-snippets","Code Snippets","3.9.5","Code Snippets Pro","https:\u002F\u002Fprofiles.wordpress.org\u002Fcodesnippetspro\u002F","\u003Cp>\u003Cstrong>✂ Code Snippets\u003C\u002Fstrong> provides an effortless way to enhance your WordPress site.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>🚀 Upgrade to Code Snippets Pro\u003C\u002Fstrong> for complete CSS, JavaScript, Gutenberg, Elementor and cloud synchronisation integrations. \u003Cstrong>\u003Ca href=\"https:\u002F\u002Fcodesnippets.pro\u002Fpricing\" rel=\"nofollow ugc\">Elevate your snippets experience now!\u003C\u002Fa>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Say goodbye to the hassle of tweaking your theme’s \u003Ccode>functions.php\u003C\u002Fcode> file and downloading endless plugins – Code Snippets simplifies the process!\u003C\u002Fp>\n\u003Cp>A snippet is like a mini-plugin for your WordPress site, providing added functionality without the clutter.\u003C\u002Fp>\n\u003Cp>Unlike other solutions that involve dumping code into your \u003Ccode>functions.php\u003C\u002Fcode> file, Code Snippets offers an intuitive graphical interface for seamless integration and real-time execution. Managing snippets is as easy as activating and deactivating plugins, only without the bloat and overhead.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>🎥 Watch a quick overview by Imran Siddiq:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FuzND-wdSCMQ?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Cp>☁️ Each copy of Code Snippets includes full integration with the community-powered \u003Ca href=\"https:\u002F\u002Fcodesnippets.cloud\u002F\" rel=\"nofollow ugc\">Code Snippets Cloud\u003C\u002Fa> platform, providing easy access to hundreds of tweaks and enhancements ready to power-up any WordPress site.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>🌐 Connect with us:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fcode-snippets\" rel=\"ugc\">Support Forum\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ffacebook.com\u002Fgroups\u002Fcodesnippetsplugin\" rel=\"nofollow ugc\">Facebook Community\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fsnipco.de\u002Fdiscord\" rel=\"nofollow ugc\">Discord Community\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcodesnippetspro\u002Fcode-snippets\" rel=\"nofollow ugc\">GitHub Repository\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>🌟 Like our plugin? Find it useful? Please consider sharing your experience by \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fview\u002Fplugin-reviews\u002Fcode-snippets\" rel=\"ugc\">leaving a review on WordPress.org\u003C\u002Fa>. Your feedback is instrumental to shaping our future growth!\u003C\u002Fp>\n\u003Cp>🌍 We’d like to thank the wonderful people who have helped contribute translations to allow Code Snippets to be used in different languages. \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcodesnippetspro\u002Fcode-snippets\u002Fblob\u002Fcore\u002FCREDITS.md#translators\" rel=\"nofollow ugc\">You can find a full list here\u003C\u002Fa>.\u003C\u002Fp>\n","An easy, clean and simple way to enhance your site with code snippets.",1000000,19655832,94,494,"2026-02-05T11:03:00.000Z","5.0","7.4",[88,89,18,90,91],"code","css","php","snippets","https:\u002F\u002Fcodesnippets.pro","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcode-snippets.3.9.5.zip",89,7,"2026-02-05 19:33:02",{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":105,"downloaded":106,"rating":107,"num_ratings":108,"last_updated":109,"tested_up_to":15,"requires_at_least":110,"requires_php":86,"tags":111,"homepage":115,"download_link":116,"security_score":22,"vuln_count":13,"unpatched_count":13,"last_vuln_date":23,"fetched_at":54},"user-switching","User Switching","1.11.2","John Blackbourn","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnbillion\u002F","\u003Cp>This plugin allows you to quickly swap between user accounts in WordPress at the click of a button. You’ll be instantly logged out and logged in as your desired user. This is handy for helping customers on WooCommerce sites, membership sites, testing environments, or for any site where administrators need to switch between multiple accounts.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Switch user: Instantly switch to any user account from the \u003Cem>Users\u003C\u002Fem> screen.\u003C\u002Fli>\n\u003Cli>Switch back: Instantly switch back to your originating account.\u003C\u002Fli>\n\u003Cli>Switch off: Log out of your account but retain the ability to instantly switch back in again.\u003C\u002Fli>\n\u003Cli>Compatible with Multisite, WooCommerce, BuddyPress, and bbPress.\u003C\u002Fli>\n\u003Cli>Compatible with most membership and user management plugins.\u003C\u002Fli>\n\u003Cli>Compatible with most two-factor authentication solutions (see the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for more info).\u003C\u002Fli>\n\u003Cli>Approved for use on enterprise-grade WordPress platforms such as \u003Ca href=\"https:\u002F\u002Fwww.altis-dxp.com\u002F\" rel=\"nofollow ugc\">Altis\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwpvip.com\u002F\" rel=\"nofollow ugc\">WordPress VIP\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Note: User Switching supports versions of WordPress up to three years old, and PHP version 7.4 or higher.\u003C\u002Fp>\n\u003Ch3>Security\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Only users with the ability to edit other users can switch user accounts. By default this is only Administrators on single site installations, and Super Admins on Multisite installations.\u003C\u002Fli>\n\u003Cli>Passwords are not (and cannot be) revealed.\u003C\u002Fli>\n\u003Cli>Uses the cookie authentication system in WordPress when remembering the account(s) you’ve switched from and when switching back.\u003C\u002Fli>\n\u003Cli>Implements the nonce security system in WordPress, meaning only those who intend to switch users can switch.\u003C\u002Fli>\n\u003Cli>Full support for user session validation where appropriate.\u003C\u002Fli>\n\u003Cli>Full support for HTTPS.\u003C\u002Fli>\n\u003Cli>Backed by \u003Ca href=\"https:\u002F\u002Fpatchstack.com\u002Fdatabase\u002Fvdp\u002Fuser-switching\" rel=\"nofollow ugc\">the Patchstack Vulnerability Disclosure Program\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Visit the \u003Cem>Users\u003C\u002Fem> menu in WordPress and you’ll see a \u003Cem>Switch To\u003C\u002Fem> link in the list of action links for each user.\u003C\u002Fli>\n\u003Cli>Click this and you will immediately switch into that user account.\u003C\u002Fli>\n\u003Cli>You can switch back to your originating account via the \u003Cem>Switch back\u003C\u002Fem> link on each dashboard screen or in your profile menu in the WordPress toolbar.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>See the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for information about the \u003Cem>Switch Off\u003C\u002Fem> feature.\u003C\u002Fp>\n\u003Ch3>Other Plugins\u003C\u002Fh3>\n\u003Cp>I maintain several other plugins for developers. Check them out:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fquery-monitor\u002F\" rel=\"ugc\">Query Monitor\u003C\u002Fa> is the developer tools panel for WordPress\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-crontrol\u002F\" rel=\"ugc\">WP Crontrol\u003C\u002Fa> lets you view and control what’s happening in the WP-Cron system\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Statement\u003C\u002Fh3>\n\u003Cp>User Switching does not send data to any third party, nor does it include any third party resources, nor will it ever do so.\u003C\u002Fp>\n\u003Cp>User Switching makes use of browser cookies in order to allow users to switch to another account. Its cookies operate using the same mechanism as the authentication cookies in WordPress core, which means their values contain the user’s \u003Ccode>user_login\u003C\u002Fcode> field in plain text which should be treated as potentially personally identifiable information (PII) for privacy and regulatory reasons (GDPR, CCPA, etc). The names of the cookies are:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wordpress_user_sw_{COOKIEHASH}\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wordpress_user_sw_secure_{COOKIEHASH}\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wordpress_user_sw_olduser_{COOKIEHASH}\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See also the FAQ for some questions relating to privacy and safety when switching between users.\u003C\u002Fp>\n\u003Ch3>Accessibility Statement\u003C\u002Fh3>\n\u003Cp>User Switching aims to be fully accessible to all of its users. It implements best practices for web accessibility, outputs semantic and structured markup, adheres to the default styles and accessibility guidelines of WordPress, uses the accessibility APIs provided by WordPress and web browsers where appropriate, and is fully accessible via keyboard.\u003C\u002Fp>\n\u003Cp>User Switching should adhere to Web Content Accessibility Guidelines (WCAG) 2.0 at level AA when used with a recent version of WordPress where its admin area itself adheres to these guidelines. If you’ve experienced or identified an accessibility issue in User Switching, please open a thread in \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fuser-switching\u002F\" rel=\"ugc\">the User Switching plugin support forum\u003C\u002Fa> and I’ll address it swiftly.\u003C\u002Fp>\n","Instant switching between user accounts in WordPress and WooCommerce.",200000,5499975,98,239,"2026-02-27T00:17:00.000Z","6.1",[112,18,98,113,114],"fast-user-switching","users","woocommerce","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fuser-switching\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fuser-switching.1.11.2.zip",{"slug":118,"name":119,"version":120,"author":121,"author_profile":122,"description":123,"short_description":124,"active_installs":125,"downloaded":126,"rating":82,"num_ratings":127,"last_updated":128,"tested_up_to":15,"requires_at_least":129,"requires_php":86,"tags":130,"homepage":136,"download_link":137,"security_score":22,"vuln_count":43,"unpatched_count":13,"last_vuln_date":138,"fetched_at":54},"safe-redirect-manager","Safe Redirect Manager","2.2.2","10up","https:\u002F\u002Fprofiles.wordpress.org\u002F10up\u002F","\u003Cp>Safely manage your site’s redirects the WordPress way. There are many redirect plugins available. Most of them store redirects in the options table or in custom tables. Most of them provide tons of unnecessary options. Some of them have serious performance implications (404 error logging). Safe Redirect Manager stores redirects as Custom Post Types. This makes your data portable and your website scalable. Safe Redirect Manager is built to handle enterprise level traffic and is used on major publishing websites. The plugin comes with only what you need following the WordPress mantra, decisions not options. Actions and filters make the plugin very extensible.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002F10up\u002Fsafe-redirect-manager\" rel=\"nofollow ugc\">Fork the plugin on GitHub.\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Configuration\u003C\u002Fh3>\n\u003Cp>There are no overarching settings for this plugin. To manage redirects, navigate to the administration panel (“Tools” > “Safe Redirect Manager”).\u003C\u002Fp>\n\u003Cp>Each redirect contains a few fields that you can utilize:\u003C\u002Fp>\n\u003Ch3>“Redirect From”\u003C\u002Fh3>\n\u003Cp>This should be a path relative to the root of your WordPress installation. When someone visits your site with a path that matches this one, a redirect will occur. If your site is located at \u003Ccode>http:\u002F\u002Fexample.com\u002Fwp\u002F\u003C\u002Fcode> and you wanted to redirect \u003Ccode>http:\u002F\u002Fexample.com\u002Fwp\u002Fabout\u003C\u002Fcode> to \u003Ccode>http:\u002F\u002Fexample.com\u003C\u002Fcode>, your “Redirect From” would be \u003Ccode>\u002Fabout\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Clicking the “Enable Regex” checkbox allows you to use regular expressions in your path. There are many \u003Ca href=\"http:\u002F\u002Fwww.regular-expressions.info\" rel=\"nofollow ugc\">great tutorials\u003C\u002Fa> on regular expressions.\u003C\u002Fp>\n\u003Cp>You can also use wildcards in your “Redirect From” paths. By adding an \u003Ccode>*\u003C\u002Fcode> at the end of a URL, your redirect will match any request that starts with your “Redirect From”. Wildcards support replacements. This means if you have a wildcard in your from path that matches a string, you can have that string replace a wildcard character in your “Redirect To” path. For example, if your “Redirect From” is \u003Ccode>\u002Ftest\u002F*\u003C\u002Fcode>, your “Redirect To” is \u003Ccode>http:\u002F\u002Fgoogle.com\u002F*\u003C\u002Fcode>, and the requested path is \u003Ccode>\u002Ftest\u002Fstring\u003C\u002Fcode>, the user would be redirect to \u003Ccode>http:\u002F\u002Fgoogle.com\u002Fstring\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch3>“Redirect To”\u003C\u002Fh3>\n\u003Cp>This should be a path (i.e. \u003Ccode>\u002Ftest\u003C\u002Fcode>) or a URL (i.e. \u003Ccode>http:\u002F\u002Fexample.com\u002Fwp\u002Ftest\u003C\u002Fcode>). If a requested path matches “Redirect From”, they will be redirected here. “Redirect To” supports wildcard and regular expression replacements.\u003C\u002Fp>\n\u003Ch3>“HTTP Status Code”\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fwww.w3.org\u002FProtocols\u002Frfc2616\u002Frfc2616-sec10.html\" rel=\"nofollow ugc\">HTTP status codes\u003C\u002Fa> are numbers that contain information about a request (i.e. whether it was successful, unauthorized, not found, etc). You should almost always use either 302 (temporarily moved) or 301 (permanently moved).\u003C\u002Fp>\n\u003Cp>\u003Cem>Note:\u003C\u002Fem>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Redirects are cached using the Transients API. Cache busts occur when redirects are added, updated, and deleted so you shouldn’t be serving stale redirects.\u003C\u002Fli>\n\u003Cli>By default the plugin only allows at most 1000 redirects to prevent performance issues. There is a filter \u003Ccode>srm_max_redirects\u003C\u002Fcode> that you can utilize to up this number.\u003C\u002Fli>\n\u003Cli>“Redirect From” and requested paths are case insensitive by default.\u003C\u002Fli>\n\u003Cli>Developers can use \u003Ccode>srm_additional_status_codes\u003C\u002Fcode> filter to add status codes if needed.\u003C\u002Fli>\n\u003Cli>Rules set with 403 and 410 status codes are handled by applying the HTTP status code and render the default WordPress \u003Ccode>wp_die\u003C\u002Fcode> screen with an optional message.\u003C\u002Fli>\n\u003Cli>Rules set with a 404 status code will apply the status code and render the 404 template.\u003C\u002Fli>\n\u003Cli>Browsers heavily cache 301 (permanently moved) redirects. It’s recommended to test your permanent redirects using the 302 (temporarily moved) status code before changing them to 301 permanently moved.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Developer Documentation\u003C\u002Fh3>\n\u003Cp>Safe Redirect Manager includes a number of actions and filters developers can make use of. These are documented on the \u003Ca href=\"http:\u002F\u002F10up.github.io\u002Fsafe-redirect-manager\u002F\" rel=\"nofollow ugc\">Safe Redirect Manager developer documentation\u003C\u002Fa> micro-site.\u003C\u002Fp>\n","Safely manage your website's HTTP redirects.",40000,1922446,78,"2026-01-04T21:19:00.000Z","6.5",[131,132,133,134,135],"http-redirects","multisite-redirects","redirect-manager","safe-http-redirection","url-redirection","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsafe-redirect-manager","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsafe-redirect-manager.2.2.2.zip","2022-06-19 00:00:00",{"attackSurface":140,"codeSignals":152,"taintFlows":159,"riskAssessment":160,"analyzedAt":168},{"hooks":141,"ajaxHandlers":148,"restRoutes":149,"shortcodes":150,"cronEvents":151,"entryPointCount":13,"unprotectedCount":13},[142],{"type":143,"name":144,"callback":145,"file":146,"line":147},"action","pre_get_users","remove_super_admin_users_test","remove_super_admin_from_usertable.php",11,[],[],[],[],{"dangerousFunctions":153,"sqlUsage":154,"outputEscaping":156,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":158},[],{"prepared":13,"raw":13,"locations":155},[],{"escaped":13,"rawEcho":13,"locations":157},[],[],[],{"summary":161,"deductions":162},"The \"remove-super-admin-from-user-list-table\" plugin v3.0 exhibits a very strong security posture based on the provided static analysis and vulnerability history.  The absence of any identified dangerous functions, the exclusive use of prepared statements for SQL queries, and the complete lack of unescaped output are all excellent security practices.  Furthermore, the plugin has no known vulnerabilities, past or present, which is a significant indicator of a well-maintained and secure codebase.  The attack surface is also minimal, with no entry points identified that are not protected by authentication checks.\n\nWhile the static analysis reports no specific code signals or taint flows that indicate immediate risk, the complete absence of nonce checks and capability checks in the code is a notable oversight. Although the plugin's stated purpose likely doesn't involve user-facing interactive elements that would typically require these, their absence could represent a potential weakness if the plugin's functionality were to expand or interact with other components in unexpected ways. However, given the plugin's specific, limited functionality as suggested by its name, this is a less concerning issue than it would be for a more complex plugin.\n\nIn conclusion, this plugin appears to be highly secure due to its adherence to best practices in data handling and its clean vulnerability history. The primary area for potential improvement, though minor given the context, would be the inclusion of nonce and capability checks for any potential future-proofing or expansion. Overall, the plugin demonstrates a commitment to security.",[163,166],{"reason":164,"points":165},"No nonce checks implemented",5,{"reason":167,"points":165},"No capability checks implemented","2026-03-16T23:32:17.932Z",{"wat":170,"direct":175},{"assetPaths":171,"generatorPatterns":172,"scriptPaths":173,"versionParams":174},[],[],[],[],{"cssClasses":176,"htmlComments":177,"htmlAttributes":178,"restEndpoints":179,"jsGlobals":180,"shortcodeOutput":181},[],[],[],[],[],[]]