[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcWrIiocAePDzc-lD18BElE8y9ZPI592VlwzbiuRu2ns":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":35,"analysis":130,"fingerprints":301},"humangate","HumanGate","1.1.0","DarkAI","https:\u002F\u002Fprofiles.wordpress.org\u002Fa22mun\u002F","\u003Cp>HumanGate protects your WordPress site from AI training crawlers, search engine bots, and unauthorized scraping bots. Add global refusal signals (meta tags, HTTP headers, robots.txt), actively block bots (AI crawlers, scrapers, etc.), and deter large-scale bot extraction with lightweight JavaScript challenges—all without CAPTCHAs or heavy databases.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Perfect for:\u003C\u002Fstrong>\u003Cbr \u002F>\n* Journalists protecting sensitive content\u003Cbr \u002F>\n* Activists and independent creators\u003Cbr \u002F>\n* Nonprofits and whistleblower support projects\u003Cbr \u002F>\n* Anyone wanting to opt out of AI training data collection\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Core Features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Block Search Engines\u003C\u002Fstrong> – Clear, top-level setting to block all search engines (Google, Bing, etc.) via noindex\u002Fnofollow meta tags\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Global AI Refusal\u003C\u002Fstrong> – Adds AI-specific meta tags, HTTP headers (X-AI-Training), and robots.txt rules to refuse AI training crawlers\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Active Enforcement Modes\u003C\u002Fstrong> – Choose from Signals Only (default), Challenge Mode (JS verification), or Block Mode (403 Forbidden) for AI crawlers and other bots\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Bot Challenge System\u003C\u002Fstrong> – Automatically detects suspicious bot traffic patterns (burst traffic, sequential traversal, deep-link access) and serves lightweight JavaScript challenges to all bots—not just AI crawlers\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Emergency Lockdown\u003C\u002Fstrong> – One-click site lockdown with HTTP 451 responses and optional login-only access\u003C\u002Fli>\n\u003Cli>\u003Cstrong>SEO Plugin Compatible\u003C\u002Fstrong> – Works seamlessly with Yoast SEO, Rank Math, All in One SEO, and other SEO plugins\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Privacy-Focused Stats\u003C\u002Fstrong> – Lightweight telemetry using WordPress transients (no database bloat, no IP storage)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Performance Optimized\u003C\u002Fstrong> – DNS lookup caching and user agent pattern caching for faster response times\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Whitelist Support\u003C\u002Fstrong> – IP address and user agent whitelists to bypass blocking for trusted sources\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>How It Works:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cstrong>Block Search Engines\u003C\u002Fstrong> – Optional setting to block all search engines (Google, Bing, etc.) using noindex\u002Fnofollow meta tags. This is a separate, clear setting at the top of the plugin configuration.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>AI Refusal Signals\u003C\u002Fstrong> – Adds AI-specific meta tags, HTTP headers, and robots.txt rules that tell AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) not to train on your content. This works independently from search engine blocking.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Active Enforcement\u003C\u002Fstrong> – Optionally block or challenge bots at the HTTP level:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Signals Only\u003C\u002Fstrong> (default): Sends refusal signals only\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Challenge Mode\u003C\u002Fstrong>: Requires JavaScript execution verification for all bots\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Block Mode\u003C\u002Fstrong>: Returns 403 Forbidden to AI crawlers and other unauthorized bots\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Selective Friction\u003C\u002Fstrong> – Automatically detects bot scraping patterns and serves invisible JavaScript challenges to any suspicious traffic:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Burst traffic detection (12+ pages in 5 seconds) – catches all bots, not just AI crawlers\u003C\u002Fli>\n\u003Cli>Sequential traversal detection (machine-like pagination)\u003C\u002Fli>\n\u003Cli>Deep-link access detection (direct access to old content)\u003C\u002Fli>\n\u003Cli>Auto-completing challenges (no user interaction required)\u003C\u002Fli>\n\u003Cli>Works against all types of bots: AI training crawlers, scrapers, data harvesters, etc.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Emergency Lockdown\u003C\u002Fstrong> – Instantly lock down your site with one toggle, returning HTTP 451 responses with optional login-only access.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Design Philosophy:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>HumanGate doesn’t try to perfectly identify machines. Instead, it makes large-scale extraction economically inefficient while keeping the experience invisible to 99% of real human users. No CAPTCHAs, no heavy databases, just lightweight protection.\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cp>For development, bug reports, and contributions, please visit the plugin’s GitHub repository at https:\u002F\u002Fgithub.com\u002FNomadBuilder\u002FHumanGate\u003C\u002Fp>\n","Protect your content from AI training crawlers and scraping bots. Add refusal signals, enforce blocks, and deter large-scale extraction.",0,125,"2025-12-25T16:50:00.000Z","6.9.4","5.0","7.4",[18,19,20,21,22],"ai","anti-scraping","privacy","robots-txt","security","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fhumangate\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhumangate.1.1.0.zip",100,null,"2026-03-15T15:16:48.613Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":25,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},"a22mun",1,30,94,"2026-04-04T10:22:02.499Z",[36,59,76,94,112],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":56,"download_link":57,"security_score":58,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"wp-pgp-encrypted-emails","WP PGP Encrypted Emails","0.8.0","Meitar","https:\u002F\u002Fprofiles.wordpress.org\u002Fmeitar\u002F","\u003Cp>WP PGP Encrypted Emails can automatically sign and encrypt any email that WordPress sends to your site’s admin email address or your users’s email addresses. You give it a copy of the recipient’s OpenPGP public key and\u002For their S\u002FMIME certificate, and it does the rest. You can even automatically generate an OpenPGP signing keypair for your site to use.\u003C\u002Fp>\n\u003Cp>Encrypting outgoing emails protects your user’s privacy by ensuring that emails intended for them can be read only by them, and them alone. Moreover, signing those emails helps your users verify that email they receive purporting to be from your site was \u003Cem>actually\u003C\u002Fem> sent by your server, and not some imposter. If you’re a plugin or theme developer, you can encrypt and\u002For sign \u003Cem>arbitrary data\u003C\u002Fem> using this plugin’s OpenPGP and S\u002FMIME APIs, which are both built with familiar, standard WordPress filter hooks. This enables you to develop highly secure communication and publishing tools fully integrated with your WordPress install. See the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffabacab\u002Fwp-pgp-encrypted-emails\u002F#readme\" rel=\"nofollow ugc\">\u003Ccode>README.markdown\u003C\u002Fcode>\u003C\u002Fa> file for details on cryptographic implementation and API usage.\u003C\u002Fp>\n\u003Cp>\u003Cem>Donations for this and my other free software plugins make up a chunk of my income. If you continue to enjoy this plugin, please consider \u003Ca href=\"https:\u002F\u002Fwww.paypal.com\u002Fcgi-bin\u002Fwebscr?cmd=_donations&business=TJLPJYXHSRBEE&lc=US&item_name=WP%20PGP%20Encrypted%20Emails&item_number=wp-pgp-encrypted-emails&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted\" rel=\"nofollow ugc\">making a donation\u003C\u002Fa>. 🙂 Thank you for your support!\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Plugin features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Processes \u003Cem>all\u003C\u002Fem> email your site generates, automatically and transparently.\u003C\u002Fli>\n\u003Cli>Configure outbound signing: sign email sent to \u003Cem>all\u003C\u002Fem> recipients, or just savvy ones.\u003C\u002Fli>\n\u003Cli>Per-user encryption keys and certificates; user manages their own OpenPGP keys and S\u002FMIME certificates.\u003C\u002Fli>\n\u003Cli>Compatible with thousands (yes, thousands) of third-party contact form plugins.\u003C\u002Fli>\n\u003Cli>Full interoperability with all standards-compliant OpenPGP and S\u002FMIME implementations.\u003C\u002Fli>\n\u003Cli>Options to enforce further privacy best practices (e.g., removing \u003Ccode>Subject\u003C\u002Fcode> lines).\u003C\u002Fli>\n\u003Cli>Fully multisite compatible, out of the box. No additional configuration for large networks!\u003C\u002Fli>\n\u003Cli>No binaries to install or configure; everything you need is in the plugin itself.\u003C\u002Fli>\n\u003Cli>Bells and whistles included! For instance, visitors can encrypt comments on posts so only the author can read them.\u003C\u002Fli>\n\u003Cli>Built-in, customizable integration with popular third-party plugins, such as \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwoocommerce\u002F\" rel=\"ugc\">WooCommerce\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Always \u003Cstrong>FREE\u003C\u002Fstrong>. Replaces paid email encryption “upgrades,” and gets rid of yearly subscription fees. (\u003Ca href=\"https:\u002F\u002Fwww.paypal.com\u002Fcgi-bin\u002Fwebscr?cmd=_donations&business=TJLPJYXHSRBEE&lc=US&item_name=WP%20PGP%20Encrypted%20Emails&item_number=wp-pgp-encrypted-emails&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted\" rel=\"nofollow ugc\">Donations\u003C\u002Fa> appreciated!)\u003C\u002Fli>\n\u003Cli>And \u003Cem>more\u003C\u002Fem>, of course. 😉\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The plugin works transparently for \u003Cem>all email\u003C\u002Fem> your site generates, and will also sign and encrypt outgoing email generated by other plugins (such as contact form plugins) or the built-in WordPress notification emails. All you have to do is add one or more OpenPGP keys or an S\u002FMIME certificate to the Email Encryption screen (WordPress Admin Dashboard → Settings → Email Encryption). Each user can opt to also remove envelope information such as email subject lines, which encryption schemes cannot protect. With this plugin, there’s no longer any need to pay for the “pro” version of your favorite contact form plugin to get the benefit of email privacy.\u003C\u002Fp>\n\u003Cp>Each of your site’s users can supply their own, personal OpenPGP public key and\u002For X.509 S\u002FMIME certificate for their own email address to have WordPress automatically encrypt any email destined for them. (They merely need to update their user profile.) They can choose which encryption method to use. Once set up, all future emails WordPress sends to that user will be encrypted using the standards-based OpenPGP or S\u002FMIME technologies.\u003C\u002Fp>\n\u003Cp>The OpenPGP-encrypted emails can be decrypted by any OpenPGP-compatible mail client, such as \u003Ca href=\"https:\u002F\u002Fgpgtools.org\u002F\" rel=\"nofollow ugc\">MacGPG\u003C\u002Fa> (macOS), \u003Ca href=\"https:\u002F\u002Fwww.gpg4win.org\u002F\" rel=\"nofollow ugc\">GPG4Win\u003C\u002Fa> (Windows), \u003Ca href=\"https:\u002F\u002Fwww.enigmail.net\u002F\" rel=\"nofollow ugc\">Enigmail\u003C\u002Fa> (cross-platform), \u003Ca href=\"https:\u002F\u002Fopenkeychain.org\u002F\" rel=\"nofollow ugc\">OpenKeychain\u003C\u002Fa> (Android), or \u003Ca href=\"https:\u002F\u002Fipgmail.com\u002F\" rel=\"nofollow ugc\">iPGMail\u003C\u002Fa> (iPhone\u002FiOS). For more information on reading encrypted emails, generating keys, and other uses for OpenPGP-compatible encryption, consult any (or all!) of the following guides:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fssd.eff.org\u002Fen\u002Fmodule\u002Fintroduction-public-key-cryptography-and-pgp\" rel=\"nofollow ugc\">The Electronic Frontier Foundation’s Surveillance Self-Defense guide to PGP\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fhelp.riseup.net\u002Fen\u002Fgpg-best-practices\" rel=\"nofollow ugc\">RiseUp.net’s OpenPGP best practices guide\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.openpgp.org\u002F\" rel=\"nofollow ugc\">OpenPGP.org\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The S\u002FMIME-encrypted emails can be decrypted by any S\u002FMIME-compatible mail client. These include \u003Ca href=\"http:\u002F\u002Fsiber-sonic.com\u002Fmac\u002FMailSMIME\u002F\" rel=\"nofollow ugc\">Apple’s Mail on macOS\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fsupport.apple.com\u002Fen-au\u002FHT202345\" rel=\"nofollow ugc\">iOS for iPhone and iPad\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fsupport.office.com\u002Fen-us\u002Farticle\u002FEncrypt-messages-by-using-S-MIME-in-Outlook-Web-App-2E57E4BD-4CC2-4531-9A39-426E7C873E26\" rel=\"nofollow ugc\">Microsoft Outlook\u003C\u002Fa>, \u003Ca href=\"http:\u002F\u002Fwww.claws-mail.org\u002Ffaq\u002Findex.php\u002FS\u002FMIME_howto\" rel=\"nofollow ugc\">Claws Mail for GNU\u002FLinux\u003C\u002Fa>, and more.\u003C\u002Fp>\n\u003Cp>For developers, WP PGP Encrypted Emails provides \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffabacab\u002Fwp-pgp-encrypted-emails\u002Fblob\u002Fdevelop\u002FREADME.markdown#openpgp-api\" rel=\"nofollow ugc\">an easy to use API to both OpenPGP\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ffabacab\u002Fwp-pgp-encrypted-emails\u002Fblob\u002Fdevelop\u002FREADME.markdown#smime-api\" rel=\"nofollow ugc\">S\u002FMIME\u003C\u002Fa> encryption, decryption, and integrity validation operations through the familiar \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FPlugin_API\" rel=\"nofollow ugc\">WordPress plugin API\u003C\u002Fa> so you can use this plugin’s simple filter hooks to build custom OpenPGP- or S\u002FMIME-based encryption functionality into your own plugins and themes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Security Disclaimer\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Security is a process, not a product. Using WP PGP Encrypted Emails does not guarantee that your site’s outgoing messages are invulnerable to every attacker, in every possible scenario, at all times. No single security measure, in isolation, can do that.\u003C\u002Fp>\n\u003Cp>Do not rely solely on this plugin for the security or privacy of your webserver. See the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-pgp-encrypted-emails\u002Ffaq\u002F\" rel=\"ugc\">Frequently Asked Questions\u003C\u002Fa> for more security advice and for more information about the rationale for this plugin.\u003Cbr \u002F>\nIf you like this plugin, \u003Cstrong>please consider \u003Ca href=\"https:\u002F\u002Fwww.paypal.com\u002Fcgi-bin\u002Fwebscr?cmd=_donations&business=TJLPJYXHSRBEE&lc=US&item_name=WP%20PGP%20Encrypted%20Emails&item_number=wp-pgp-encrypted-emails&currency_code=USD&bn=PP%2dDonationsBF%3abtn_donate_SM%2egif%3aNonHosted\" rel=\"nofollow ugc\">making a donation\u003C\u002Fa> for your use of the plugin\u003C\u002Fstrong> or, better yet, contributing directly to \u003Ca href=\"http:\u002F\u002FCyberbusking.org\u002F\" rel=\"nofollow ugc\">my Cyberbusking fund\u003C\u002Fa>. Your support is appreciated!\u003C\u002Fp>\n\u003Ch4>Themeing\u003C\u002Fh4>\n\u003Cp>Theme authors can use the following code snippets to integrate a WordPress theme with this plugin.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>To link to a site’s OpenPGP signing public key: \u003Ccode>\u003C?php print admin_url( 'admin-ajax.php?action=download_pgp_signing_public_key' ); ?>\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Plugin hooks\u003C\u002Fh4>\n\u003Cp>This plugin offers additional functionality intended for other plugin developers or theme authors to make use of. This functionality is documented here.\u003C\u002Fp>\n\u003Ch3>Filters\u003C\u002Fh3>\n\u003Ch4>`wp_user_encryption_method`\u003C\u002Fh4>\n\u003Cp>Gets the user’s preferred encryption method (either \u003Ccode>pgp\u003C\u002Fcode> or \u003Ccode>smime\u003C\u002Fcode>), if they have provided both an OpenPGP public key and an S\u002FMIME certificate.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Optional arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>WP_User\u003C\u002Fcode> \u003Ccode>$user\u003C\u002Fcode> – The WordPress user object. Defaults to the current user.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>`wp_openpgp_user_key`\u003C\u002Fh4>\n\u003Cp>Gets the user’s saved OpenPGP public key from their WordPress profile data, immediately usable in other \u003Ccode>openpgp_*\u003C\u002Fcode> filters.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Optional arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>WP_User\u003C\u002Fcode> \u003Ccode>$user\u003C\u002Fcode> – The WordPress user object. Defaults to the current user.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>`openpgp_enarmor`\u003C\u002Fh4>\n\u003Cp>Gets an ASCII-armored representation of an OpenPGP data structure (like a key, or an encrypted message).\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required parameters:\n\u003Cul>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$data\u003C\u002Fcode> – The data to be armored.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Optional parameters:\n\u003Cul>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$marker\u003C\u002Fcode> – The marker of the block (the text that follows \u003Ccode>-----BEGIN\u003C\u002Fcode>). Defaults to \u003Ccode>MESSAGE\u003C\u002Fcode>, but you should set this to a more appropriate value. If you are armoring a PGP public key, for instance, set this to \u003Ccode>PGP PUBLIC KEY BLOCK\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>string[]\u003C\u002Fcode> \u003Ccode>$headers\u003C\u002Fcode> – An array of strings to apply as headers to the ASCII-armored block, usually used to insert comments or identify the OpenPGP client used. Defaults to \u003Ccode>array()\u003C\u002Fcode> (no headers).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example: ASCII-armor a binary public key.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$ascii_key = apply_filters('openpgp_enarmor', $public_key, 'PGP PUBLIC KEY BLOCK');\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>`openpgp_key`\u003C\u002Fh4>\n\u003Cp>Gets a binary OpenPGP public key for use in later PGP operations from an ASCII-armored representation of that key.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required parameters:\n\u003Cul>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$key\u003C\u002Fcode> – The ASCII-armored PGP public key block.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example: Get a key saved as an ASCII string in the WordPress database option \u003Ccode>my_plugin_pgp_public_key\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$key = apply_filters('openpgp_key', get_option('my_plugin_pgp_public_key'));\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>`openpgp_sign`\u003C\u002Fh4>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.gnupg.org\u002Fgph\u002Fen\u002Fmanual\u002Fx135.html#AEN152\" rel=\"nofollow ugc\">Clearsigns\u003C\u002Fa> a message using a given private key.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required parameters:\n\u003Cul>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$data\u003C\u002Fcode> – The message data to sign.\u003C\u002Fli>\n\u003Cli>\u003Ccode>OpenPGP_SecretKeyPacket\u003C\u002Fcode> \u003Ccode>$signing_key\u003C\u002Fcode> – The signing key to use, obtained by passing the ASCII-armored private key through the \u003Ccode>openpgp_key\u003C\u002Fcode> filter.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example: Sign a short string.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$message = 'This is a message to sign.';\n$signing_key = apply_filters('openpgp_key', $ascii_key);\n$signed_message = apply_filters('openpgp_sign', $message, $signing_key);\n\u002F\u002F $signed_message is now a clearsigned message\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>`openpgp_encrypt`\u003C\u002Fh4>\n\u003Cp>Encrypts data to one or more PGP public keys or passphrases.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$data\u003C\u002Fcode> – Data to encrypt.\u003C\u002Fli>\n\u003Cli>\u003Ccode>array|string\u003C\u002Fcode> \u003Ccode>$keys\u003C\u002Fcode> – Passphrases or keys to use to encrypt the data.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example: Encrypt the content of a blog post.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F First, get the PGP public key(s) of the recipient(s)\n$ascii_key = '-----BEGIN PGP PUBLIC KEY BLOCK-----\n[...snipped for length...]\n-----END PGP PUBLIC KEY BLOCK-----';\n$encryption_key = apply_filters('openpgp_key', $ascii_key);\n$encrypted_post = apply_filters('openpgp_encrypt', $post->post_content, $encryption_key);\n\u002F\u002F Now you can safely send or display $encrypted_post anywhere you like and only\n\u002F\u002F those who control the corresponding private key(s) can decrypt it.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>`openpgp_sign`\u003C\u002Fh4>\n\u003Cp>Signs a message (arbitrary data) with the given private key.\u003C\u002Fp>\n\u003Cp>Note that if your plugin uses the built-in WordPress core \u003Ccode>wp_mail()\u003C\u002Fcode> function and this plugin is active, your plugin’s outgoing emails are already automatically signed so you do not need to do anything. This filter is intended for use by plugin developers who want to create custom, trusted communiques between WordPress and some other system.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$data\u003C\u002Fcode> – The data to sign.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Optional arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>OpenPGP_SecretKeyPacket\u003C\u002Fcode> \u003Ccode>$privatekey\u003C\u002Fcode> – The private key used for signing the message. The default is to use the private key automatically generated during plugin activation. The automatically generated keypair is intended to be a low-trust, single-purpose keypair for your website itself, so you probably do not need or want to use this argument yourself.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Example: Send a signed, encrypted JSON payload to a remote, insecure server.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$comment_data = get_comment(2); \u002F\u002F get a WP_Comment object with comment ID 2\n\u002F\u002F Create JSON payload\n$json = array('success' => true, 'action' => 'new_comment', 'data' => $comment_data);\n$url = 'http:\u002F\u002Finsecure.example.com\u002F';\n$response = wp_safe_remote_post($url, array(\n));\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>`openpgp_sign_and_encrypt`\u003C\u002Fh4>\n\u003Cp>A convenience filter that applies \u003Ccode>openpgp_sign\u003C\u002Fcode> and then \u003Ccode>openpgp_encrypt\u003C\u002Fcode> to the result.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$data\u003C\u002Fcode> – The data to sign and encrypt.\u003C\u002Fli>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$signing_key\u003C\u002Fcode> – The signing key to use.\u003C\u002Fli>\n\u003Cli>\u003Ccode>array|string\u003C\u002Fcode> \u003Ccode>$recipient_keys_and_passphrases\u003C\u002Fcode> – Public key(s) of the recipient(s), or passphrases to encrypt to.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>`wp_openpgp_user_key`\u003C\u002Fh4>\n\u003Cp>Gets the user’s saved S\u002FMIME public certificate from their WordPress profile data, immediately usable in other \u003Ccode>smime_*\u003C\u002Fcode> filters.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Optional arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>WP_User\u003C\u002Fcode> \u003Ccode>$user\u003C\u002Fcode> – The WordPress user object. Defaults to the current user.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>`smime_certificate`\u003C\u002Fh4>\n\u003Cp>Gets a PHP resource handle to an X.509 Certificate.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>mixed\u003C\u002Fcode> \u003Ccode>$cert\u003C\u002Fcode> – The certificate, either as a string to a file, or raw PEM-encoded certificate data.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>`smime_certificate_pem_encode`\u003C\u002Fh4>\n\u003Cp>Encodes (“exports”) a given X.509 certificate as PEM format.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>resource\u003C\u002Fcode> \u003Ccode>$cert\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>`smime_encrypt`\u003C\u002Fh4>\n\u003Cp>Encrypts a message as an S\u002FMIME email given a public certificate.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Required arguments:\n\u003Cul>\n\u003Cli>\u003Ccode>string\u003C\u002Fcode> \u003Ccode>$message\u003C\u002Fcode> – The message contents to encrypt.\u003C\u002Fli>\n\u003Cli>\u003Ccode>string|string[]\u003C\u002Fcode> \u003Ccode>$headers\u003C\u002Fcode> – The message headers for the encrypted part.\u003C\u002Fli>\n\u003Cli>\u003Ccode>resource|array\u003C\u002Fcode> \u003Ccode>$certificates\u003C\u002Fcode> – The recipient’s certificate, or an array of recipient certificates.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This filter returns an array with two keys, \u003Ccode>headers\u003C\u002Fcode> and \u003Ccode>message\u003C\u002Fcode>, wherein the message is encrypted.\u003C\u002Fp>\n\u003Cp>Example: send an encrypted email via \u003Ccode>wp_mail()\u003C\u002Fcode>. (You do not need to do this if the recipient is registered as your site’s user, because this plugin does that automatically. Only do this if you need to send S\u002FMIME encrypted email to an address not stored in WordPress’s own database.)\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$cert = apply_filters( 'smime_certificate', get_option( 'my_plugin_smime_certificate' ) );\n$body = 'This is a test email message body.';\n$head = array(\n    'From' => get_option( 'admin_email' ),\n);\n$smime_data = apply_filters( 'smime_encrypt', $body, $head, $cert );\nif ( $smime_data ) {\n    wp_mail(\n        'recipient@example.com',\n        'Test message.',\n        $smime_data['message'], \u002F\u002F message is sent encrypted\n        $smime_data['headers']\n    );\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Signs and encrypts emails using PGP\u002FGPG keys or X.509 certificates. Provides OpenPGP and S\u002FMIME functions via WordPress plugin API.",400,25921,92,16,"2021-05-25T19:04:00.000Z","5.7.15","4.4","",[53,54,55,20,22],"email","encryption","pgp","https:\u002F\u002Fgithub.com\u002Ffabacab\u002Fwp-pgp-encrypted-emails","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-pgp-encrypted-emails.0.8.0.zip",85,{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":33,"num_ratings":69,"last_updated":70,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":71,"homepage":74,"download_link":75,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"ai-scrape-protect","AI Scrape Protect","4.6","Daan Verbaan","https:\u002F\u002Fprofiles.wordpress.org\u002Fdaanverbaan\u002F","\u003Cp>\u003Cstrong>AI Scrape Protect\u003C\u002Fstrong> is a WordPress plugin designed to protect your website from scraping for AI training purposes. It achieves this by adding opt-out instructions to the \u003Ccode>robots.txt\u003C\u002Fcode> file for the most common AI scraping bots and including meta tags to control how your content is used.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Simplicity first:\u003C\u002Fstrong> This plugin is built to be as simple and user-friendly as possible. There are no complicated settings or configuration screens—just activate the plugin and your site is protected. Perfect for anyone who wants quick, effective AI scraping protection without any technical hassle.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> These instructions are not always respected by all bots.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Adds specific \u003Ccode>User-agent\u003C\u002Fcode> and \u003Ccode>Disallow\u003C\u002Fcode> rules to your \u003Ccode>robots.txt\u003C\u002Fcode> file to block a comprehensive list of AI scraping bots.  \u003C\u002Fli>\n\u003Cli>Introduces meta tags in the HTML \u003Ccode>\u003Chead>\u003C\u002Fcode> to provide additional instructions to AI bots, including new tags for Bingbot and general AI compliance.  \u003C\u002Fli>\n\u003Cli>Prepares for future standards with support for \u003Ccode>DisallowAITraining\u003C\u002Fcode> and \u003Ccode>noimageai\u003C\u002Fcode> meta tags.  \u003C\u002Fli>\n\u003Cli>Dedicated handling of specific bots like CCBot and Bingbot for better protection and compatibility.  \u003C\u002Fli>\n\u003Cli>Admin bar icon to indicate plugin activity.\u003C\u002Fli>\n\u003C\u002Ful>\n","Protect your website from AI scraping by adding opt-out instructions to your robots.txt file and including meta tags in the HTML `` with this easy-to- …",200,2456,3,"2025-11-29T14:24:00.000Z",[18,72,21,73,22],"ai-scraping-protection","scraping","https:\u002F\u002Fcodesurf.eu\u002Fwordpress-ai-scrape-protect-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fai-scrape-protect.4.6.zip",{"slug":77,"name":78,"version":79,"author":80,"author_profile":81,"description":82,"short_description":83,"active_installs":84,"downloaded":85,"rating":11,"num_ratings":11,"last_updated":86,"tested_up_to":14,"requires_at_least":15,"requires_php":87,"tags":88,"homepage":92,"download_link":93,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"protect-my-infos","Protect My Infos","1.3.8","Yuga Web","https:\u002F\u002Fprofiles.wordpress.org\u002Fyugaweb\u002F","\u003Cp>\u003Cstrong>Protect My Infos\u003C\u002Fstrong> is a WordPress plugin designed to protect sensitive information, such as phone numbers and email addresses, by obfuscating or hiding them on the frontend of your site.\u003C\u002Fp>\n\u003Cp>Emails and phone numbers are encoded and hidden from bots, while visitors can interact with placeholders to reveal the information.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Obfuscate sensitive information with placeholders, blur effects, or base64 encoding.\u003C\u002Fli>\n\u003Cli>Use the \u003Ccode>[protect_my_infos]\u003C\u002Fcode> shortcode for integration in posts or pages.\u003C\u002Fli>\n\u003Cli>Fully customizable settings for icons, colors, and reveal texts.\u003C\u002Fli>\n\u003Cli>Easy-to-use admin interface.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>External Services\u003C\u002Fh3>\n\u003Cp>This plugin integrates with the PayPal Donate API to facilitate donations via PayPal’s secure platform.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Service Name\u003C\u002Fstrong>: PayPal Donate API\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Purpose\u003C\u002Fstrong>: To provide a “Donate” button for collecting user donations securely via PayPal.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Data Sent\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>Donation amount\u003C\u002Fli>\n\u003Cli>Currency\u003C\u002Fli>\n\u003Cli>PayPal Merchant ID\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\u003Cstrong>When\u003C\u002Fstrong>: Data is sent to PayPal only when a user interacts with the “Donate” button.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Service Links\u003C\u002Fstrong>:\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.paypal.com\u002Fus\u002Fwebapps\u002Fmpp\u002Fua\u002Flegalhub-full\" rel=\"nofollow ugc\">PayPal Terms of Service\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.paypal.com\u002Fus\u002Fwebapps\u002Fmpp\u002Fua\u002Fprivacy-full\" rel=\"nofollow ugc\">PayPal Privacy Policy\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Note: This plugin does not store or process sensitive personal information. All payment transactions are handled securely by PayPal’s platform.\u003C\u002Fp>\n","Protect sensitive information like emails and phone numbers from bots with advanced obfuscation techniques.",90,914,"2025-12-11T15:33:00.000Z","7.2",[89,90,91,20,22],"anti-spam","email-obfuscation","phone-number-protection","https:\u002F\u002Fwww.yugaweb.com\u002Fprotect-my-infos\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fprotect-my-infos.1.3.8.zip",{"slug":95,"name":96,"version":6,"author":97,"author_profile":98,"description":99,"short_description":100,"active_installs":101,"downloaded":102,"rating":25,"num_ratings":103,"last_updated":51,"tested_up_to":104,"requires_at_least":105,"requires_php":16,"tags":106,"homepage":51,"download_link":110,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":111},"ai-scraping-protector","AI Scraping Protector","Debashish Mondal","https:\u002F\u002Fprofiles.wordpress.org\u002Fdba6060\u002F","\u003Cp>AI Scraping Protector helps safeguard your WordPress site from automated AI content scraping tools like ChatGPT, Claude, and other aggressive crawlers.\u003C\u002Fp>\n\u003Cp>The plugin combines \u003Cstrong>bot detection, IP blocking, rate limiting, and content protection\u003C\u002Fstrong> to ensure your valuable content stays safe while keeping the site experience smooth for legitimate visitors.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Features:\u003C\u002Fstrong>\u003Cbr \u002F>\n* \u003Cstrong>Content Protection\u003C\u002Fstrong> – Prevents automated tools from copying your posts\u002Fpages.\u003Cbr \u002F>\n* \u003Cstrong>Advanced Bot Detection\u003C\u002Fstrong> – Identifies AI scrapers and malicious bots via user agent patterns and IP ranges.\u003Cbr \u002F>\n* \u003Cstrong>Rate Limiting\u003C\u002Fstrong> – Two-tier protection:\u003Cbr \u002F>\n  – Burst: 30 requests per minute\u003Cbr \u002F>\n  – Standard: 1000 requests per hour\u003Cbr \u002F>\n* \u003Cstrong>Security Headers\u003C\u002Fstrong> – Adds multiple HTTP headers (X-Frame-Options, X-Robots-Tag, etc.) for extra protection.\u003Cbr \u002F>\n* \u003Cstrong>Per-Post\u002FPage Control\u003C\u002Fstrong> – Enable or disable protection individually.\u003Cbr \u002F>\n* \u003Cstrong>Extensive Bot Network Blocking\u003C\u002Fstrong> – Includes Google, Microsoft, and other known scraper networks.\u003Cbr \u002F>\n* \u003Cstrong>Admin Tools\u003C\u002Fstrong> – Logging, status reporting, and reset options.\u003C\u002Fp>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>This plugin does not collect or process personal data of any kind.\u003C\u002Fp>\n","Protect your WordPress content from AI scraping bots with advanced detection, rate limiting, and security measures.",80,1129,2,"6.8.5","5.8",[107,19,108,109,22],"ai-protection","bot-blocker","content-protection","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fai-scraping-protector.1.1.0.zip","2026-03-15T10:48:56.248Z",{"slug":113,"name":114,"version":115,"author":116,"author_profile":117,"description":118,"short_description":119,"active_installs":120,"downloaded":121,"rating":11,"num_ratings":11,"last_updated":51,"tested_up_to":122,"requires_at_least":123,"requires_php":51,"tags":124,"homepage":128,"download_link":129,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":111},"behind-closed-doors","Behind Closed Doors","1.1","spencersokol","https:\u002F\u002Fprofiles.wordpress.org\u002Fspencersokol\u002F","\u003Cp>Keep your site behind closed doors with this plugin, by redirecting visitors to a single page, and optionally giving users a login form to view the remainder of your site.\u003C\u002Fp>\n\u003Cp>Basic uses:\u003Cbr \u002F>\n1. Keeping your site hidden while in initial development, while still allowing test users and clients to login\u003Cbr \u002F>\n2. Putting your site in a “maintenance mode” quickly\u003C\u002Fp>\n\u003Ch3>Upgrade Notices\u003C\u002Fh3>\n\u003Ch3>Future Releases\u003C\u002Fh3>\n","Keep your site behind closed doors, by redirecting visitors to a single page, optionally giving them a login form to view the remainder of your site.",10,1806,"5.0.25","3.5",[125,126,127,20,22],"login","maintenance","maintenance-mode","http:\u002F\u002Fspencersokol.com\u002Fprojects\u002Fbehind-closed-doors\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbehind-closed-doors.1.1.zip",{"attackSurface":131,"codeSignals":213,"taintFlows":233,"riskAssessment":295,"analyzedAt":300},{"hooks":132,"ajaxHandlers":200,"restRoutes":208,"shortcodes":209,"cronEvents":210,"entryPointCount":103,"unprotectedCount":11},[133,139,144,148,152,156,159,163,168,171,176,180,186,189,191,195],{"type":134,"name":135,"callback":136,"file":137,"line":138},"action","plugins_loaded","humang_plugin_init","block-ai-plugin.php",72,{"type":134,"name":140,"callback":141,"file":142,"line":143},"admin_menu","add_admin_menu","includes\\Admin.php",17,{"type":134,"name":145,"callback":146,"file":142,"line":147},"admin_init","register_settings",18,{"type":134,"name":149,"callback":150,"file":142,"line":151},"admin_enqueue_scripts","enqueue_admin_assets",19,{"type":134,"name":153,"callback":154,"file":142,"line":155},"admin_notices","display_compatibility_notices",20,{"type":134,"name":157,"callback":157,"file":158,"line":147},"add_meta_boxes","includes\\ContentControl.php",{"type":134,"name":160,"callback":161,"priority":120,"file":158,"line":162},"save_post","save_meta_box",21,{"type":134,"name":164,"callback":165,"priority":31,"file":166,"line":167},"template_redirect","enforce_lockdown","includes\\EmergencyLockdown.php",22,{"type":134,"name":169,"callback":165,"priority":31,"file":166,"line":170},"init",26,{"type":134,"name":172,"callback":173,"priority":31,"file":174,"line":175},"wp_head","add_refusal_meta_tags","includes\\RefusalLayer.php",50,{"type":134,"name":177,"callback":178,"priority":31,"file":174,"line":179},"send_headers","add_refusal_headers",53,{"type":181,"name":182,"callback":183,"priority":184,"file":174,"line":185},"filter","robots_txt","modify_robots_txt",99,57,{"type":134,"name":164,"callback":187,"priority":31,"file":174,"line":188},"enforce_ai_blocking",66,{"type":134,"name":169,"callback":187,"priority":31,"file":174,"line":190},68,{"type":134,"name":164,"callback":192,"priority":31,"file":193,"line":194},"check_friction_triggers","includes\\SelectiveFriction.php",29,{"type":134,"name":196,"callback":197,"file":198,"line":199},"humang_weekly_cleanup","cleanup_old_counters","includes\\Telemetry.php",43,[201,207],{"action":202,"nopriv":203,"callback":204,"hasNonce":205,"hasCapCheck":203,"file":193,"line":206},"humang_verify_challenge",false,"verify_challenge",true,25,{"action":202,"nopriv":205,"callback":204,"hasNonce":205,"hasCapCheck":203,"file":193,"line":170},[],[],[211],{"hook":196,"callback":196,"file":198,"line":212},41,{"dangerousFunctions":214,"sqlUsage":215,"outputEscaping":217,"fileOperations":11,"externalRequests":11,"nonceChecks":231,"capabilityChecks":69,"bundledLibraries":232},[],{"prepared":11,"raw":11,"locations":216},[],{"escaped":101,"rawEcho":218,"locations":219},5,[220,223,225,227,229],{"file":142,"line":221,"context":222},547,"raw output",{"file":142,"line":224,"context":222},1108,{"file":142,"line":226,"context":222},1166,{"file":174,"line":228,"context":222},586,{"file":193,"line":230,"context":222},253,4,[],[234,257,273,287],{"entryPoint":235,"graph":236,"unsanitizedCount":31,"severity":256},"enforce_ai_blocking (includes\\RefusalLayer.php:266)",{"nodes":237,"edges":253},[238,243,247],{"id":239,"type":240,"label":241,"file":174,"line":242},"n0","source","$_SERVER",347,{"id":244,"type":245,"label":246,"file":174,"line":242},"n1","transform","→ send_block_response()",{"id":248,"type":249,"label":250,"file":174,"line":251,"wp_function":252},"n2","sink","echo() [XSS]",476,"echo",[254,255],{"from":239,"to":244,"sanitized":203},{"from":244,"to":248,"sanitized":203},"medium",{"entryPoint":258,"graph":259,"unsanitizedCount":103,"severity":256},"\u003CRefusalLayer> (includes\\RefusalLayer.php:0)",{"nodes":260,"edges":269},[261,263,264,265,267],{"id":239,"type":240,"label":241,"file":174,"line":262},284,{"id":244,"type":249,"label":250,"file":174,"line":251,"wp_function":252},{"id":248,"type":240,"label":241,"file":174,"line":242},{"id":266,"type":245,"label":246,"file":174,"line":242},"n3",{"id":268,"type":249,"label":250,"file":174,"line":251,"wp_function":252},"n4",[270,271,272],{"from":239,"to":244,"sanitized":203},{"from":248,"to":266,"sanitized":203},{"from":266,"to":268,"sanitized":203},{"entryPoint":274,"graph":275,"unsanitizedCount":11,"severity":286},"render_settings_page (includes\\Admin.php:526)",{"nodes":276,"edges":284},[277,280],{"id":239,"type":240,"label":278,"file":142,"line":279},"$_POST",535,{"id":244,"type":249,"label":281,"file":142,"line":282,"wp_function":283},"update_option() [Settings Manipulation]",538,"update_option",[285],{"from":239,"to":244,"sanitized":205},"low",{"entryPoint":288,"graph":289,"unsanitizedCount":11,"severity":286},"\u003CAdmin> (includes\\Admin.php:0)",{"nodes":290,"edges":293},[291,292],{"id":239,"type":240,"label":278,"file":142,"line":279},{"id":244,"type":249,"label":281,"file":142,"line":282,"wp_function":283},[294],{"from":239,"to":244,"sanitized":205},{"summary":296,"deductions":297},"The humangate plugin v1.1.0 exhibits a generally good security posture based on static analysis.  It demonstrates strong adherence to secure coding practices, with no dangerous functions identified, all SQL queries utilizing prepared statements, and a high percentage of output being properly escaped. The presence of nonce and capability checks on entry points further strengthens its defense.  However, the taint analysis reveals a concern: two flows with unsanitized paths, though not classified as critical or high severity in this analysis, represent potential vectors for unexpected behavior or data manipulation if exploited in a specific context.  The plugin's vulnerability history is clean, with no recorded CVEs, which is a positive indicator of past security diligence. Despite the absence of critical vulnerabilities in the current analysis and history, the identified unsanitized paths warrant attention as they represent a potential weakness that could be exploited by an attacker, especially if combined with other factors or future code changes.",[298],{"reason":299,"points":120},"Flows with unsanitized paths detected","2026-03-17T06:34:18.711Z",{"wat":302,"direct":311},{"assetPaths":303,"generatorPatterns":306,"scriptPaths":307,"versionParams":308},[304,305],"\u002Fwp-content\u002Fplugins\u002Fhumangate\u002Fassets\u002Fcss\u002Fadmin-style.css","\u002Fwp-content\u002Fplugins\u002Fhumangate\u002Fassets\u002Fjs\u002Fadmin-script.js",[],[305],[309,310],"humangate\u002Fassets\u002Fcss\u002Fadmin-style.css?ver=","humangate\u002Fassets\u002Fjs\u002Fadmin-script.js?ver=",{"cssClasses":312,"htmlComments":315,"htmlAttributes":318,"restEndpoints":320,"jsGlobals":321,"shortcodeOutput":323},[313,314],"humangate-settings-wrap","humangate-admin-notice",[316,317],"\u003C!-- HumanGate Admin Settings -->","\u003C!-- HumanGate Compatibility Notice -->",[319],"data-humangate-id",[],[322],"humangate_admin_params",[]]