[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fPmrXreIs9BplMcpcDbkgMKARgfJtEANmHLofyaR_Eew":3,"$fSoluk48Aw-53UEdU_I3lB2KxVaJLDPvqxqEuvnS7qFo":124,"$fjrmRTr7-cXXh7nzn9vD8ExC1Z6HXA7AXIg6NSyrotW0":129},{"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,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":35,"analysis":26,"fingerprints":26},"codevera-ai-access-control","Codevera AI Access Control","1.1.4","codevera","https:\u002F\u002Fprofiles.wordpress.org\u002Fcodevera\u002F","\u003Cp>WordPress 7.0 introduced the Abilities API. Any active plugin can register an ability and the WordPress AI feature can then invoke it, consuming whatever credits or tokens your AI provider charges per call. By default every registered ability is exposed, and there is no built-in way to see what is exposed or to limit it.\u003C\u002Fp>\n\u003Cp>Codevera AI Access Control adds a single settings screen that lists every plugin which has registered AI abilities, grouped by source plugin, and lets you allow or block each plugin as a whole or each individual ability.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>How it works:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Col>\n\u003Cli>The plugin watches every call to \u003Ccode>wp_register_ability()\u003C\u002Fcode> and records which plugin made the call.\u003C\u002Fli>\n\u003Cli>The Settings -> Codevera AI Access screen groups those abilities by source plugin so you can see at a glance what is exposed.\u003C\u002Fli>\n\u003Cli>Untick a plugin or a single ability and save. From the next request onwards, the AI feature can no longer see or invoke it.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>\u003Cstrong>Free:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Per-plugin and per-ability granular controls\u003C\u002Fli>\n\u003Cli>Automatic detection of newly installed plugins that register AI abilities, with an in-admin notification so you can review them\u003C\u002Fli>\n\u003Cli>Tamper-detect signature on the saved settings, with a fail-closed mode that blocks every non-core ability if the settings option is modified outside the plugin\u003C\u002Fli>\n\u003Cli>Filter-level enforcement that neutralises a blocked ability before WordPress constructs it, plus a registry sweep that removes blocked abilities from the listings\u003C\u002Fli>\n\u003Cli>Self-check that re-attaches the enforcement hooks on init, admin_init and rest_api_init if another plugin removes them\u003C\u002Fli>\n\u003Cli>Search and filter inside each plugin card so large registries stay readable\u003C\u002Fli>\n\u003Cli>No external requests, no telemetry, no licence checks\u003C\u002Fli>\n\u003Cli>Works on multisite (per-site settings)\u003C\u002Fli>\n\u003Cli>Translation ready\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Works well for:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Sites where editorial staff use the WordPress AI feature and you want strict control over what context the AI can pull in\u003C\u002Fli>\n\u003Cli>Agency sites where new plugins are installed regularly and you want to review their AI exposure before letting them in\u003C\u002Fli>\n\u003Cli>Privacy-sensitive sites that need an explicit allow list of which plugins may expose data to an AI provider\u003C\u002Fli>\n\u003Cli>Compliance-driven environments that need an auditable record of which plugins have been allowed to register AI abilities\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Under the hood:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Uses only the official Abilities API surface: \u003Ccode>wp_register_ability_args\u003C\u002Fcode>, \u003Ccode>wp_abilities_api_init\u003C\u002Fcode>, \u003Ccode>wp_unregister_ability\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Source attribution from \u003Ccode>debug_backtrace()\u003C\u002Fcode> of the file that called \u003Ccode>wp_register_ability\u003C\u002Fcode>, normalised to a plugin slug\u003C\u002Fli>\n\u003Cli>HMAC-SHA256 signature on the settings option, keyed to a \u003Ccode>CVAIAC_SECRET\u003C\u002Fcode> constant or \u003Ccode>AUTH_SALT\u003C\u002Fcode> fallback\u003C\u002Fli>\n\u003Cli>No frontend assets shipped, all code runs in admin and on the AI Abilities REST routes\u003C\u002Fli>\n\u003Cli>No database tables, just two options in \u003Ccode>wp_options\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>External Services & Privacy\u003C\u002Fh3>\n\u003Cp>This plugin does not contact any external service. It reads only local WordPress data. No telemetry, no analytics, no licence checks, no remote update checks beyond what WordPress core itself performs.\u003C\u002Fp>\n\u003Cp>The plugin stores two options in the \u003Ccode>wp_options\u003C\u002Fcode> table:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>cvaiac_settings\u003C\u002Fcode> – your allow and block selections, signed with an HMAC-SHA256 signature\u003C\u002Fli>\n\u003Cli>\u003Ccode>cvaiac_ability_sources\u003C\u002Fcode> – a map of ability name to source plugin slug, populated automatically as plugins register their abilities\u003C\u002Fli>\n\u003Cli>\u003Ccode>cvaiac_schema_version\u003C\u002Fcode> – an integer that records the storage format version, used for migration\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>No personal data, no visitor data, and no AJAX requests to remote services.\u003C\u002Fp>\n\u003Cp>When the plugin is uninstalled, all three options are removed.\u003C\u002Fp>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>Email info@codevera.ai for support, bug reports, or feature requests. Include your WordPress version, PHP version, a list of other plugins that register AI abilities, and a description of the issue with steps to reproduce.\u003C\u002Fp>\n\u003Ch3>Technical Requirements\u003C\u002Fh3>\n\u003Cp>Minimum:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress 7.0 (required for the Abilities API)\u003C\u002Fli>\n\u003Cli>PHP 7.4\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Recommended:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WordPress 7.0 or higher\u003C\u002Fli>\n\u003Cli>PHP 8.0 or higher\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy & Security\u003C\u002Fh3>\n\u003Cp>The plugin does not collect or transmit any personal data. The settings option is stored locally and signed with an HMAC keyed to a site-specific secret. The source-tracker option contains only plugin slugs and ability names that are already public to any code running on the site.\u003C\u002Fp>\n\u003Cp>Form submissions use a nonce and require the \u003Ccode>manage_options\u003C\u002Fcode> capability. The enforcement hooks run on every request that loads the Abilities API, so blocking takes effect from the next request after a setting is saved.\u003C\u002Fp>\n\u003Cp>This plugin defends against opportunistic interference such as another plugin writing directly to the settings option, removing the enforcement hooks, or re-registering an ability that has already been blocked. It does not claim to be a security boundary against a fully hostile plugin that has code execution in the same PHP process. The safest practice is still to only install plugins you trust.\u003C\u002Fp>\n\u003Ch3>Links\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Website: https:\u002F\u002Fcodevera.ai\u003C\u002Fli>\n\u003Cli>Support: info@codevera.ai\u003C\u002Fli>\n\u003C\u002Ful>\n","Decide which plugins are allowed to expose their abilities to the WordPress AI feature. Block any plugin, or any single ability, with one click.",0,133,"2026-05-13T13:11:00.000Z","7.0.2","7.0","7.4",[18,19,20,21,22],"abilities","admin","ai","privacy","security","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcodevera-ai-access-control.1.1.4.zip",100,null,"2026-07-22T17:31:50.256Z","no_bundle",[],{"slug":7,"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},2,30,94,"2026-08-28T22:14:27.207Z",[36,51,71,89,109],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":11,"downloaded":44,"rating":25,"num_ratings":45,"last_updated":46,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":47,"homepage":49,"download_link":50,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"grumpy-ai-gate","Grumpy AI Gate","1.0.2","Lars Koudal","https:\u002F\u002Fprofiles.wordpress.org\u002Flkoudal\u002F","\u003Cp>\u003Cstrong>Grumpy AI Gate\u003C\u002Fstrong> helps you stay in control as AI features spread across WordPress. It \u003Cstrong>observes and intercepts\u003C\u002Fstrong> outbound HTTP \u003Cstrong>that other code on your site already initiates\u003C\u002Fstrong> (plugins, themes, or core)—so you can see \u003Cstrong>which plugin\u003C\u002Fstrong> was involved, \u003Cstrong>how much\u003C\u002Fstrong> activity you are seeing (including helpful estimates), and \u003Cstrong>optionally stop\u003C\u002Fstrong> unwanted \u003Cstrong>WordPress AI Client\u003C\u002Fstrong> traffic for specific plugins. \u003Cstrong>This plugin does not\u003C\u002Fstrong> call external AI APIs for its own dashboard, analytics, or licensing. Nothing is sent to us or to a third-party analytics service.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why use it\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Visibility\u003C\u002Fstrong> — Dashboard summaries, a per-plugin usage table, and a request log so surprises become visible early.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Spend awareness\u003C\u002Fstrong> — When other software calls paid APIs, usage adds up. Logging helps you notice patterns before invoices or quotas become a problem.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Safer sharing\u003C\u002Fstrong> — Knowing what leaves your server makes it easier to decide what belongs in prompts and what does not.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Optional blocking\u003C\u002Fstrong> — For paths that use WordPress’s AI Client, you can block generations from selected plugins under \u003Cstrong>Grumpy AI Gate \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings\u003C\u002Fstrong> (save to apply).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>How it works\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When the \u003Cstrong>WordPress AI Client\u003C\u002Fstrong> is available, the plugin records those requests from core lifecycle hooks (other code still drives the actual generation).\u003C\u002Fli>\n\u003Cli>For \u003Cstrong>HTTP fallback\u003C\u002Fstrong>, Grumpy AI Gate \u003Cstrong>hooks WordPress’s HTTP API\u003C\u002Fstrong> (for example \u003Ccode>pre_http_request\u003C\u002Fcode>) to \u003Cstrong>inspect requests that are already in flight\u003C\u002Fstrong>. If a URL matches \u003Cstrong>built-in recognition rules\u003C\u002Fstrong> for major AI providers, a log row can be stored. \u003Cstrong>Grumpy AI Gate does not open those connections for its own purposes\u003C\u002Fstrong>—it only filters and classifies traffic \u003Cstrong>initiated elsewhere\u003C\u002Fstrong> on the site.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>HTTP fallback does not block\u003C\u002Fstrong> outbound API calls in the current release—it is there so you still get visibility when plugins talk to providers \u003Cstrong>directly over HTTP\u003C\u002Fstrong> instead of (or in addition to) AI Client flows.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Compatibility\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The plugin requires \u003Cstrong>WordPress 7.0+\u003C\u002Fstrong> (matches \u003Cstrong>Requires at least\u003C\u002Fstrong> in the plugin header). On WordPress \u003Cstrong>7.x\u003C\u002Fstrong>, it works with \u003Cstrong>core AI Client\u003C\u002Fstrong> functionality where available. Release testing included \u003Cstrong>WordPress 7.0 Beta 5\u003C\u002Fstrong>. \u003Cstrong>HTTP fallback\u003C\u002Fstrong> remains important on every supported version—it records calls to \u003Cstrong>recognized provider endpoints\u003C\u002Fstrong> that \u003Cstrong>other plugins\u003C\u002Fstrong> make \u003Cstrong>directly over HTTP\u003C\u002Fstrong>, which is still common alongside (or instead of) AI Client–based flows.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Privacy\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Everything is stored \u003Cstrong>locally in your WordPress database\u003C\u002Fstrong>. There is no cloud account, no telemetry, and no third-party analytics from this plugin.\u003C\u002Fp>\n\u003Cp>For technical details on logging, double-counting avoidance, and blocking limits, see the \u003Cstrong>FAQ\u003C\u002Fstrong> below.\u003C\u002Fp>\n\u003Ch3>External services\u003C\u002Fh3>\n\u003Cp>This plugin \u003Cstrong>does not\u003C\u002Fstrong> rely on third-party AI APIs, remote analytics, or any external service \u003Cstrong>for its own features\u003C\u002Fstrong>. All logging and settings stay on your site.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Provider names and URL patterns\u003C\u002Fstrong> included with the plugin are \u003Cstrong>local matching rules\u003C\u002Fstrong> only. They let Grumpy AI Gate \u003Cstrong>filter and classify\u003C\u002Fstrong> outbound HTTP requests that \u003Cstrong>plugins, themes, or WordPress core\u003C\u002Fstrong> may already be sending. They are \u003Cstrong>not\u003C\u002Fstrong> a list of servers this plugin calls to power the admin UI or to “phone home.”\u003C\u002Fp>\n\u003Cp>Your site may still contact third-party AI providers when \u003Cstrong>you or other software\u003C\u002Fstrong> use AI features—that traffic is separate from this plugin’s own network use (which does not include calling those providers for monitoring).\u003C\u002Fp>\n","Intercept and log AI-related HTTP from plugins\u002Fthemes; optional AI Client blocking. All data stays on your server.",333,1,"2026-04-29T15:11:00.000Z",[19,20,48,21,22],"monitoring","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fgrumpy-ai-gate\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgrumpy-ai-gate.1.0.2.zip",{"slug":52,"name":53,"version":54,"author":55,"author_profile":56,"description":57,"short_description":58,"active_installs":59,"downloaded":60,"rating":11,"num_ratings":11,"last_updated":61,"tested_up_to":62,"requires_at_least":63,"requires_php":23,"tags":64,"homepage":68,"download_link":69,"security_score":70,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"update-notifier","Update Notifier","1.4.1","Jon Cave","https:\u002F\u002Fprofiles.wordpress.org\u002Fduck_\u002F","\u003Cp>If you don’t check your admin panel on your WordPress install very often (maybe because you prefer to use remote publishing) or you want to make sure\u003Cbr \u002F>\nthat your clients’ WordPress installations are updated, then this is the plugin for you. You don’t have to login to your admin panel regularly,\u003Cbr \u002F>\nsuscribe to an RSS feed, or do anything apart from installing this plugin to be notified when an update to WordPress is released.\u003C\u002Fp>\n\u003Cp>All you have to do is install Update Notifier and forget it until you receive an email telling you to update.\u003C\u002Fp>\n\u003Cp>To change Update Notifier’s options, go to Update Notifier under the main Settings menu. From there you can add a secondary email address\u003Cbr \u002F>\nwhich will also receive update notifications and you can activate update notifications for themes and plugins.\u003C\u002Fp>\n","Sends email notifications if a new version of WordPress available. Notifications about updates for plugins and themes can also be sent.",700,18395,"2010-09-20T12:13:00.000Z","3.0.5","3.0",[19,65,66,22,67],"email","notification","upgrade","http:\u002F\u002Flionsgoroar.co.uk\u002Fwordpress\u002Fupdate-notifier\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fupdate-notifier.1.4.1.zip",85,{"slug":72,"name":73,"version":74,"author":75,"author_profile":76,"description":77,"short_description":78,"active_installs":79,"downloaded":80,"rating":25,"num_ratings":81,"last_updated":82,"tested_up_to":83,"requires_at_least":84,"requires_php":23,"tags":85,"homepage":87,"download_link":88,"security_score":70,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"logout-clear-cookies","Logout Clear Cookies","0.2","Joel","https:\u002F\u002Fprofiles.wordpress.org\u002Fjoelhardi\u002F","\u003Cp>This is an extremely simple plugin (one line of code!) that deletes all domain cookies whenever a user logs out of your WordPress site, and then redirects the user to the site homepage.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why?\u003C\u002Fstrong> Because by default, WordPress sets a number of cookies that it doesn’t remove on its own when you log out.\u003C\u002Fp>\n\u003Cp>There are security and privacy benefits, because if there are vulnerabilities in WordPress or in your browser, or if someone has access to your computer or device, they may be able to access these cookies. (That goes for you or for anyone who logs into your site to add a post or comment.)\u003C\u002Fp>\n\u003Cp>Likewise, when a user logs out of your site using a public or shared computer, there won’t be any domain cookies left behind.\u003C\u002Fp>\n\u003Cp>The plugin also gives you back the “regular user view” of your site, because after you log out you can browse your site as an anonymous user, without having to manually clear cookies in your browser. (There are many plugins that will display different content or show cached or uncached versions of pages if they see that WordPress cookies have been set.)\u003C\u002Fp>\n","Clears all domain cookies on logout. Because leaving a trail of cookies is bad.",500,9421,4,"2023-11-08T14:46:00.000Z","6.4.8","3.7",[19,86,21,22],"cookie","https:\u002F\u002Flyncd.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flogout-clear-cookies.zip",{"slug":90,"name":91,"version":92,"author":93,"author_profile":94,"description":95,"short_description":96,"active_installs":97,"downloaded":98,"rating":99,"num_ratings":100,"last_updated":101,"tested_up_to":102,"requires_at_least":103,"requires_php":23,"tags":104,"homepage":107,"download_link":108,"security_score":70,"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,26718,92,16,"2021-05-25T19:04:00.000Z","5.7.15","4.4",[65,105,106,21,22],"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",{"slug":110,"name":111,"version":112,"author":113,"author_profile":114,"description":115,"short_description":116,"active_installs":25,"downloaded":117,"rating":11,"num_ratings":11,"last_updated":118,"tested_up_to":14,"requires_at_least":15,"requires_php":119,"tags":120,"homepage":23,"download_link":123,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27},"disable-ai-for-security","Disable AI for Security","1.3.0","WPChef","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpchefgadget\u002F","\u003Cp>\u003Cstrong>Disable AI for Security\u003C\u002Fstrong> switches off the AI features introduced in WordPress 7.0 — quickly, cleanly, and without a single setting to configure.\u003C\u002Fp>\n\u003Cp>WordPress 7.0 introduces built-in AI connectors. They’re a great addition, but not every site needs them. If you prefer to keep your site lean and predictable, or your organization’s policy is to keep AI features off, this plugin gives you a simple one-click way to do exactly that.\u003C\u002Fp>\n\u003Cp>Just activate it. That’s it. There is no settings page, no configuration, and nothing to maintain — the plugin starts protecting your site the moment it’s enabled.\u003C\u002Fp>\n\u003Ch4>What it does\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Disables WordPress AI at the core level.\u003C\u002Fstrong> Core stops registering AI providers, rejects AI connectors, and won’t run AI prompts.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Works for every role.\u003C\u002Fstrong> AI is turned off site-wide — for administrators, editors, authors, and everyone else. No exceptions, no per-user toggles.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Hides the AI admin screens.\u003C\u002Fstrong> The Connectors and AI settings pages are removed from wp-admin, and direct links to them are blocked.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Shows a clear status badge.\u003C\u002Fstrong> A small green “AI Disabled” badge in the admin bar confirms protection is active.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Why you’ll like it\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Zero configuration.\u003C\u002Fstrong> No setup, no options, no learning curve.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Works out of the box.\u003C\u002Fstrong> Protection is on the instant you activate.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lightweight and focused.\u003C\u002Fstrong> It does one job and does it well.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Brought to you by the team behind \u003Cstrong>Limit Login Attempts Reloaded\u003C\u002Fstrong>.\u003C\u002Fp>\n","Turns off the WordPress AI connectors for security. Works instantly with no settings — AI is fully disabled for every user role.",287,"2026-06-17T07:48:00.000Z","7.2",[20,121,122,21,22],"connectors","disable-ai","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-ai-for-security.1.3.0.zip",{"error":125,"url":126,"statusCode":127,"statusMessage":128,"message":128},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fcodevera-ai-access-control\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":45,"versions":130},[131],{"version":6,"download_url":24,"svn_tag_url":132,"released_at":26,"has_diff":133,"diff_files_changed":134,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":135,"is_current":125},"https:\u002F\u002Fplugins.svn.wordpress.org\u002Fcodevera-ai-access-control\u002Ftags\u002F1.1.4\u002F",false,[],[]]