[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fJk_5shWYw61mTlZTYB6PeHMzU2oA0_Pfc1-tLnFS9oU":3,"$fm2Q10B5drZs0tOs8AMdCB3ImlW42Y_wQzFLO_LhGuAc":200,"$fCBAY0Uo-HfM8VwccDwjCve9b7cXEUPuZgeM2QpXmHvI":205},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":22,"download_link":23,"security_score":24,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":26,"discovery_status":27,"vulnerabilities":28,"developer":29,"crawl_stats":25,"alternatives":37,"analysis":136,"fingerprints":176},"fernet-encryption","Fernet Encryption","1.1.0","Hubbard Labs","https:\u002F\u002Fprofiles.wordpress.org\u002Fhubbardlabs\u002F","\u003Cp>Fernet Encryption is a plugin that can be used to encrypt and decrypt data in WordPress using fernet.\u003C\u002Fp>\n\u003Cp>Development was originally sponsered by Access Networks.\u003C\u002Fp>\n\u003Ch3>Setup your Key\u003C\u002Fh3>\n\u003Cp>To setup your key, you need to add the following line to your wp-config file.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>`\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>define( ‘FERNET_KEY’, ‘YOUR_FERNET_KEY’ );\u003Cbr \u002F>\n    `\u003C\u002Fp>\n\u003Cp>If you choose not to setup your key, you will need to save a copy of the one provided upon activation of the plugin.\u003C\u002Fp>\n\u003Cp>\u003Cem>IMPORTANT: Changing your WordPress salts will invalidate the default Fernet key provided.\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch3>How to Use\u003C\u002Fh3>\n\u003Cp>To encrypt data simply use \u003Ccode>$token = fernet_encrypt( 'YOUR MESSAGE' )\u003C\u002Fcode> in your code.\u003C\u002Fp>\n\u003Cp>To decrypt the data simply use \u003Ccode>fernet_decrypt( $token )\u003C\u002Fcode> in your code.\u003C\u002Fp>\n\u003Cp>You can use the following shortcode to encrypt:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[fernet-encrypt]YOUR MESSAGE[\u002Ffernet-encrypt]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can use the following shortcode to decrypt:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[fernet-decrypt]YOUR-FERNET-TOKEN[\u002Ffernet-decrypt]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>We have also added useful helper functions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>fernet_get_post_meta\u003C\u002Fli>\n\u003Cli>fernet_add_post_meta\u003C\u002Fli>\n\u003Cli>fernet_update_post_meta\u003C\u002Fli>\n\u003Cli>fernet_get_user_meta\u003C\u002Fli>\n\u003Cli>fernet_add_user_meta\u003C\u002Fli>\n\u003Cli>fernet_update_user_meta\u003C\u002Fli>\n\u003Cli>fernet_add_option\u003C\u002Fli>\n\u003Cli>fernet_get_option\u003C\u002Fli>\n\u003Cli>fernet_update_option\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credit\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Illustrations provided by undraw.co\u003C\u002Fli>\n\u003Cli>Fernent PHP modified from Kelvin Mo – Fernet-PHP\u003C\u002Fli>\n\u003C\u002Ful>\n","Fernet Encryption is a plugin that can be used to encrypt and decrypt data in WordPress using fernet.",10,1733,0,"2025-01-05T02:14:00.000Z","6.7.5","6.4","8.0",[19,20,21],"encryption","fernet","security","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ffernet-encryption\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffernet-encryption.zip",92,null,"2026-04-16T10:56:18.058Z","no_bundle",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":32,"avg_security_score":33,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"hubbardlabs",4,20,89,30,86,"2026-05-19T22:53:20.663Z",[38,60,81,100,119],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":24,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":52,"tags":53,"homepage":57,"download_link":58,"security_score":59,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":26},"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,26121,16,"2021-05-25T19:04:00.000Z","5.7.15","4.4","",[54,19,55,56,21],"email","pgp","privacy","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":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":70,"num_ratings":71,"last_updated":72,"tested_up_to":73,"requires_at_least":74,"requires_php":52,"tags":75,"homepage":79,"download_link":80,"security_score":59,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":26},"semisecure-login-reimagined","Semisecure Login Reimagined","3.2.0","laceous","https:\u002F\u002Fprofiles.wordpress.org\u002Flaceous\u002F","\u003Cp>\u003Cstrong>Please note that I’ve moved away from WordPress for the time being. I have no plans to continue updating my plugins. If someone was thinking of forking this project, now would be the time.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Semisecure Login Reimagined increases the security of the login process by using a combination of public and secret-key encryption to encrypt the password on the client-side when a user logs in. JavaScript is required to enable encryption. It is most useful for situations where SSL is not available, but the administrator wishes to have some additional security measures in place without sacrificing convenience.\u003C\u002Fp>\n\u003Cp>This plugin is a “re-imagining” of the original \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fsemisecure-login\u002F\" title=\"Semisecure Login\" rel=\"ugc\">Semisecure Login\u003C\u002Fa> (which used one-way MD5 hashing). This version works with the new phpass hashed passwords that WordPress uses, as well as maintaining backwards compatibility with the older (pre WordPress 2.5) MD5 hashed passwords. Theoretically, it will also work with any other hashing algorithm (because this plugin simply adds an extra layer in the process rather than trying to authenticate anything itself).\u003C\u002Fp>\n\u003Cp>This plugin requires PHP to be compiled with openssl support, which is a pretty standard option for most hosts.\u003C\u002Fp>\n\u003Ch3>Additional Info\u003C\u002Fh3>\n\u003Cp>In general…\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Semisecure Login Reimagined 3.2.x is tested to work with:\n\u003Cul>\n\u003Cli>WP 3.1.x\u003C\u002Fli>\n\u003Cli>PHP 4.3.x – 5.3.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Semisecure Login Reimagined 3.1.x was tested to work with:\n\u003Cul>\n\u003Cli>WP 2.8.x – 3.0.x\u003C\u002Fli>\n\u003Cli>PHP 4.3.x – 5.3.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Semisecure Login Reimagined 3.0.x was tested to work with:\n\u003Cul>\n\u003Cli>WP 2.7.x – 2.9.x\u003C\u002Fli>\n\u003Cli>PHP 4.3.x – 5.3.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Semisecure Login Reimagined 2.x was tested to work with:\n\u003Cul>\n\u003Cli>WP 2.2.x – 2.8.x\u003C\u002Fli>\n\u003Cli>PHP 4.2.x – 5.2.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Semisecure Login Reimagined 1.x was tested to work with:\n\u003Cul>\n\u003Cli>WP 2.1.x – 2.7.x\u003C\u002Fli>\n\u003Cli>PHP 4.3.x – 5.2.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>** See the readme.txt file for each version for more specific information\u003C\u002Fp>\n","\"Re-imagined\" version of Semisecure Login that uses public and secret-key encryption to encrypt passwords when logging in.",80,51401,100,1,"2011-07-15T23:08:00.000Z","3.1.4","3.1",[76,19,77,78,21],"admin","login","rsa","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fsemisecure-login-reimagined\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsemisecure-login-reimagined.zip",{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":34,"downloaded":89,"rating":90,"num_ratings":91,"last_updated":92,"tested_up_to":93,"requires_at_least":94,"requires_php":52,"tags":95,"homepage":98,"download_link":99,"security_score":59,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":26},"wp-jcryption","WP jCryption Security","0.5.1","andreyk","https:\u002F\u002Fprofiles.wordpress.org\u002Fandreyk\u002F","\u003Cp>The plugin increases security of a site in case it has no SSL certificate,\u003Cbr \u002F>\nuseful for owners of small sites who want to secure their passwords and\u003Cbr \u002F>\nother posted data but don’t want to buy SSL certificate for each domain\u003Cbr \u002F>\nand subdomain: it protects from sniffering the most important data such as\u003Cbr \u002F>\npasswords when they are being sent from forms of your site to the server.\u003C\u002Fp>\n\u003Cp>When the form served by the plugin is submitted all input data are being\u003Cbr \u002F>\njoined into a string, then this string is being encrypted with AES algorythm\u003Cbr \u002F>\nby disposable key and only encrypred string will be sent.\u003C\u002Fp>\n\u003Cp>A browser encrypts the disposable key in javascript by the RSA public key\u003Cbr \u002F>\nand sends it to the server; then the server decrypts it with the RSA private\u003Cbr \u002F>\nkey and then use it to decrypt the posted data with AES.\u003C\u002Fp>\n\u003Cp>Translations included: Ukrainian, Russian, German and Brazilian Portuguese.\u003C\u002Fp>\n\u003Cp>I just adapted usage in WordPress the jCryption jQuery plugin, v. 3.1.0.\u003Cbr \u002F>\nPlease check www.jcryption.org to learn how jCryption works.\u003C\u002Fp>\n","Prevents forms data against sniffing network traffic through encryption provided by jCryption javascript library.",2835,94,3,"2015-05-16T10:34:00.000Z","4.8.28","3.8.1",[19,96,77,97,21],"forms","password","http:\u002F\u002Fandrey.eto-ya.com\u002Fwordpress\u002Fmy-plugins\u002Fwp-jcryption","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-jcryption.zip",{"slug":101,"name":102,"version":103,"author":104,"author_profile":105,"description":106,"short_description":107,"active_installs":32,"downloaded":108,"rating":70,"num_ratings":71,"last_updated":109,"tested_up_to":50,"requires_at_least":110,"requires_php":111,"tags":112,"homepage":116,"download_link":117,"security_score":59,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":118},"lockr","Lockr","3.0.4","Chris Teitzel","https:\u002F\u002Fprofiles.wordpress.org\u002Fcteitzel\u002F","\u003Ch4>API & ENCRYPTION KEY MANAGEMENT FOR WORDPRESS\u003C\u002Fh4>\n\u003Cp>Lockr is the first hosted secrets management solution for WordPress, providing an affordable solution for all sites to properly manage site secrets such as API and encryption keys used by their plugins. Lockr’s offsite key management solution protects against critical vulnerabilities, delivers best-practice security to help sites comply with many industry regulations, and provides a Defense in Depth approach to securing your data. Lockr also provides AES-256 encryption to your custom plugins in a seamless manner to protect data at rest in your site. And best of all, even though it delivers enterprise-grade key management, you can try it for 2 weeks free! Learn more at http:\u002F\u002Fwww.lockr.io.\u003C\u002Fp>\n\u003Ch4>Lockr Features:\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Easy to configure and setup in WordPress\u003C\u002Fli>\n\u003Cli>Simple UI to override any option stored by plugins\u003C\u002Fli>\n\u003Cli>Safe and Secure offsite key storage\u003C\u002Fli>\n\u003Cli>Works with any API and encryption key\u003C\u002Fli>\n\u003Cli>Built-in AES-256 Encryption functions to secure data in your site\u003C\u002Fli>\n\u003Cli>99.9% uptime guarantee (SLA Available for Enterprise Customers)\u003C\u002Fli>\n\u003Cli>Regular Backups\u003C\u002Fli>\n\u003Cli>Multiple Region Redundancy\u003C\u002Fli>\n\u003Cli>Backed by Townsend Security’s FIPS 140-2 compliant key manager, your keys are secured to industry standards.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Lockr is the first key management service for WordPress.\u003C\u002Fh4>\n\u003Cp>More and more plugins are leveraging 3rd party APIs. To securely access these APIs, a token, secret key, or password is necessary. Until now, these highly sensitive secrets were stored right in your database. We’ve seen a major need to secure sensitive data and communications by removing these API keys from your database, encrypting them, and storing safely in an offsite key vault. This limits the damage that could be done if your site is compromised or a developer has a local copy of your database. Lockr makes key management easy. Just install the plugin for WordPress, configure your account and begin securely storing your keys. Lockr provides patches for the major plugins used by hundreds of thousands of sites and with WP-CLI a single command will make sure your plugins use Lockr.\u003C\u002Fp>\n\u003Ch4>Who is Lockr for?\u003C\u002Fh4>\n\u003Cp>Lockr is available for WordPress sites of all sizes. Easy to use for the novice site owner and advanced enough for the expert developer, Lockr secures web transactions and data at rest by protecting API and encryption keys.\u003Cbr \u002F>\nFor Site Builders: fill out a single registration form and you’re set. To use with other plugins, look for those that have Lockr available or use our patch library to update your favorite plugin to use Lockr.\u003Cbr \u002F>\nFor Developers: Lockr provides an easy to use framework to “get and set” keys from your custom plugin. Additionally, Lockr provides a simple to use yet strong AES-256 encryption function, ensuring your data is encrypted according to industry best-practices and securely stored. Using Lockr helps keep the developer safe, by removing the sensitive passwords and key secrets from the code and database, following security best practices should a site be compromised.\u003C\u002Fp>\n\u003Ch4>Is Lockr Safe?\u003C\u002Fh4>\n\u003Cp>Lockr can secure any API key, secret key, and other types of credentials. Once enabled in WordPress, keys entered are encrypted, then sent over to the Lockr system and removed from the code repository and database. This encryption teamed with hosting provider based authentication prevents your key from being used outside your website. Lockr also manages keys on a “per environment” basis which helps eliminate the potential of keys being shared from production to development environments. No longer will you have to worry about sending a notification from development to your production users, or having production data decrypted in development environments.\u003C\u002Fp>\n\u003Cp>Leveraging proven enterprise-grade key management technology from Townsend Security, Lockr’s offsite key management delivers best-practice security to protect against critical vulnerabilities and help sites meet PCI DSS, HIPAA and other security requirements and regulations.\u003C\u002Fp>\n\u003Cp>This plugin is designed, written and maintained by experts in security, to the end user it is easy to use and understand. Let Lockr handle the difficult part of securing your site, so you can focus on delivering the best experience possible to your users.\u003C\u002Fp>\n","Lockr is the first API & Encryption key management service for WordPress, providing an affordable solution to secure secrets used by plugins.",3805,"2021-06-02T20:18:00.000Z","2.7","5.5",[113,19,114,115,21],"encrypt","secrets","secrets-management","https:\u002F\u002Flockr.io\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flockr.zip","2026-04-06T09:54:40.288Z",{"slug":120,"name":121,"version":122,"author":123,"author_profile":124,"description":125,"short_description":126,"active_installs":11,"downloaded":127,"rating":13,"num_ratings":13,"last_updated":128,"tested_up_to":129,"requires_at_least":130,"requires_php":52,"tags":131,"homepage":134,"download_link":135,"security_score":59,"vuln_count":13,"unpatched_count":13,"last_vuln_date":25,"fetched_at":26},"encryption-tools-generator","Encryption Tools Generator","0.1","Etienne Rached","https:\u002F\u002Fprofiles.wordpress.org\u002Fetiennerached\u002F","\u003Cp>This plugin Provides shortcodes to automatically generate a security and encryption tools on your wordpress website.\u003C\u002Fp>\n\u003Cp>The generated encryption currently supported are:\u003Cbr \u002F>\n1- htpasswd generator.\u003Cbr \u002F>\n2- MD5 generator.\u003Cbr \u002F>\n3- SHA1 generator.\u003C\u002Fp>\n\u003Cp>The shortcodes can be added on any page or post.\u003C\u002Fp>\n\u003Cp>The generated forms support bootstrap 3.\u003C\u002Fp>\n\u003Cp>More tools will be added every version.\u003C\u002Fp>\n","Convert your wordpress page or post to a security or encryption online tool generator.",2155,"2015-05-09T09:24:00.000Z","4.2.39","3.3.1",[19,132,21,133],"online-generator","tools","http:\u002F\u002Fwww.tech-and-dev.com\u002Fp\u002Fwordpress-encryption-tools-generator.html","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fencryption-tools-generator.0.1.zip",{"attackSurface":137,"codeSignals":164,"taintFlows":171,"riskAssessment":172,"analyzedAt":175},{"hooks":138,"ajaxHandlers":150,"restRoutes":151,"shortcodes":152,"cronEvents":162,"entryPointCount":163,"unprotectedCount":13},[139,145],{"type":140,"name":141,"callback":142,"file":143,"line":144},"action","admin_notices","fernet_admin_notice","fernet-encryption.php",148,{"type":140,"name":146,"callback":147,"file":148,"line":149},"rest_api_init","register_routes","includes\\class-fernet-rest-api.php",34,[],[],[153,158],{"tag":154,"callback":155,"file":156,"line":157},"fernet-encrypt","fernet_encrypt_shortcode","includes\\class-fernet-shortcodes.php",21,{"tag":159,"callback":160,"file":156,"line":161},"fernet-decrypt","fernet_decrypt_shortcode",22,[],2,{"dangerousFunctions":165,"sqlUsage":166,"outputEscaping":168,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":71,"bundledLibraries":170},[],{"prepared":13,"raw":13,"locations":167},[],{"escaped":163,"rawEcho":13,"locations":169},[],[],[],{"summary":173,"deductions":174},"The fernet-encryption plugin version 1.1.0 exhibits a strong security posture based on the static analysis. The absence of dangerous functions, file operations, and external HTTP requests is commendable. All SQL queries utilize prepared statements, and output escaping is correctly implemented, indicating good defensive coding practices against common web vulnerabilities. The plugin also demonstrates adherence to WordPress security best practices by including capability checks for its entry points.",[],"2026-03-17T01:39:47.625Z",{"wat":177,"direct":186},{"assetPaths":178,"generatorPatterns":181,"scriptPaths":182,"versionParams":183},[179,180],"\u002Fwp-content\u002Fplugins\u002Ffernet-encryption\u002Fassets\u002Fcss\u002Ffernet-encryption.css","\u002Fwp-content\u002Fplugins\u002Ffernet-encryption\u002Fassets\u002Fjs\u002Ffernet-encryption.js",[],[180],[184,185],"fernet-encryption\u002Fassets\u002Fcss\u002Ffernet-encryption.css?ver=","fernet-encryption\u002Fassets\u002Fjs\u002Ffernet-encryption.js?ver=",{"cssClasses":187,"htmlComments":189,"htmlAttributes":190,"restEndpoints":191,"jsGlobals":194,"shortcodeOutput":195},[188],"fernet-encryption-admin-notice",[],[],[192,193],"\u002Fwp-json\u002Ffernet\u002Fv1\u002Fencrypt","\u002Fwp-json\u002Ffernet\u002Fv1\u002Fdecrypt",[],[196,197,198,199],"[fernet-encrypt]","[\u002Ffernet-encrypt]","[fernet-decrypt]","[\u002Ffernet-decrypt]",{"error":201,"url":202,"statusCode":203,"statusMessage":204,"message":204},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Ffernet-encryption\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":163,"versions":206},[207,214],{"version":6,"download_url":208,"svn_tag_url":209,"released_at":25,"has_diff":210,"diff_files_changed":211,"diff_lines":25,"trac_diff_url":212,"vulnerabilities":213,"is_current":201},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffernet-encryption.1.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffernet-encryption\u002Ftags\u002F1.1.0\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Ffernet-encryption%2Ftags%2F1.0.7&new_path=%2Ffernet-encryption%2Ftags%2F1.1.0",[],{"version":215,"download_url":216,"svn_tag_url":217,"released_at":25,"has_diff":210,"diff_files_changed":218,"diff_lines":25,"trac_diff_url":25,"vulnerabilities":219,"is_current":210},"1.0.7","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffernet-encryption.1.0.7.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Ffernet-encryption\u002Ftags\u002F1.0.7\u002F",[],[]]