[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fdzl73ZkcLvAN1zPS5iKjNMhxTENXgFa-GNjajpI-vio":3,"$fi3L8tNn6Hl2gDhgrI0HSQBhsdRqQiFlnvmAHx46M8UU":398,"$fxyoNxEfB_pD2Vvyc5g9L9tWyetJADBpre0Nf8Mt0u9Y":403},{"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":7,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":37,"analysis":132,"fingerprints":380},"hikari-email-url-obfuscator","Hikari Email & URL Obfuscator","0.08.10","","https:\u002F\u002Fprofiles.wordpress.org\u002Fshidouhikari\u002F","\u003Cp>Spam is website publishers #1 concern, we wanna share our and our visitors’ emails to those who should have access to them, but don’t want spam harvesters stealing them and sending garbage to us. A lot of techniques had been developed to hide our emails from these delinquents, while having them shown to real people.\u003C\u002Fp>\n\u003Cp>And together with spam harvesting, on 15 June 2009, Matt Cutts, a well known software engineer of Google, announced that Google Bot will no longer ignore nofollowed links for PageRank, and now we lose PR\u002Flink juice for every link we add to our pages, even if we use rel=”nofollow” on them. So, now we must hide links from Search Engines too!\u003C\u002Fp>\n\u003Cp>I’ve been searching for an ultimate obfuscation solution for both emails and URLs, that would be user-friendly for me the content publisher, and for my visitors. I’ve seen a lot of solutions, some that inspired me, but none that would fit my needs. It was time to start coding 🙂\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002FHikari.ws\u002Femail-url-obfuscator\u002F\" rel=\"nofollow ugc\">Hikari Email & URL Obfuscator\u003C\u002Fa> plugin obfuscates emails and URL links, to hide them from spam harvesters and Search Endigne crawlers. It  uses ROT13 or cc8b to encode each link while PHP is building the page, then uses JavaScript to decode it and show it to the user. If JavaScript is not available, it uses CSS to hide them.\u003C\u002Fp>\n\u003Cp>It doesn’t use shortcodes, it works directly over HTML links, parsing and obfuscating them. By default it filters all texts in posts, comments, comments authors and text widgets, but you can manually use it anywhere you want.\u003C\u002Fp>\n\u003Cp>Basically, Hikari Email & URL Obfuscator plugin searches for links that contain URLs and emails on their \u003Ccode>href\u003C\u002Fcode> atrribute. For each found link, it is replaced by an obfuscated string, and a JavaScript function is called, having in its parameters the required data for JavaScript to decode and recreate the original link.\u003C\u002Fp>\n\u003Cp>The obfuscated string is then merged back by CSS to a readable URL\u002Femail text, so that human visitors can read it while spam harvesters and searchbots will not be able to detect it as a valid email\u002FURL.\u003C\u002Fp>\n\u003Cp>And, for JavaScript-enabled visitors, this string is replaced by a link with the exact same behavior and attributes of your original link, so that they can interact with it as if there was no obfuscation in place!\u003Cbr \u002F>\n(Really, there is no way to diferenciate an obfuscated link generated by JavaScript from the original link, unless the HTML document’ source is verified or a development tool as FireBug is used!)\u003C\u002Fp>\n\u003Cp>It uses 4 obfuscation techniques, 2 JavaScript solutions and 2 CSS alternatives for JavaScript-disabled browsers.\u003C\u002Fp>\n\u003Cp>For CSS, it may \u003Cem>revert\u003C\u002Fem> the link string while PHP is building the page and then CSS reverts it back. Or it may add garbage text between the link, and CSS prevents this extra text from being rendered, so any user-agent that doesn’t use CSS can’t find the link but browsers show it clearly.\u003C\u002Fp>\n\u003Cp>Now, when JavaScript is available, it is delivered with the original link, encoded using \u003Cstrong>ROT13\u003C\u002Fstrong> or \u003Cstrong>cc8b\u003C\u002Fstrong> by PHP. The link is then decoded back by JavaScript and added to the page, so that real users don’t even notice the original link was replaced.\u003C\u002Fp>\n\u003Cp>And, disregarding the used technique, we content publishers must do nothing different while building our content, just activate the plugin and it does everything else for us 🙂\u003C\u002Fp>\n\u003Cp>I dedicate Hikari Email & URL Obfuscator to \u003Cstrong>Ju\u003C\u002Fstrong>, my beloved frient ^-^\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cem>Works instantly, no need to edit your posts to have your links obfuscated\u003C\u002Fem>: Hikari Email & URL Obfuscator plugin automatically detects them and starts obfuscating as soon as it is activated.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Unobstructive JavaScript\u003C\u002Fstrong>: links are obfuscated and shown for visitors with and without JavaScript, forget those “you must enabled javascript to see this email” messages!\u003C\u002Fli>\n\u003Cli>\u003Cem>They are real links!\u003C\u002Fem>: any attribute you can use in an \u003Ccode>\u003Ca>\u003C\u002Fcode> tag you also can use in obfuscated links (JavaScript version only).\u003C\u002Fli>\n\u003Cli>\u003Cem>Customization\u003C\u002Fem>: CSS doesn’t let we have real links, but we can at least choose if our obfuscated text will have email only, text only, or both!\u003C\u002Fli>\n\u003Cli>\u003Cem>XHTML 1.1 valid\u003C\u002Fem>: obfuscated links and JavaScript code are valid even in XHTML 1.1 standard. It makes the plugin valid inclusive in HTML 4.0, XHTML 1.0 Strict, XHTML 1.0 Transitional and HTML5!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Advantages over other obfuscation solutions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Your visitors will see your emails and URLs \u003Cem>even if they keep JavaScript disabled\u003C\u002Fem>.\u003C\u002Fli>\n\u003Cli>\u003Cem>Automatic\u003C\u002Fem>: you don’t need to take special actions to start obfuscating, as using shortcodes in place of links or an external tool to get your obfuscation code. Just normally use your links in your posts and let the plugin do the rest!\u003C\u002Fli>\n\u003Cli>\u003Cem>Sitewide\u003C\u002Fem>: instantly works in your existing posts, pages, comments and text widgets, just after you activate it.\u003C\u002Fli>\n\u003Cli>\u003Cem>Diversity\u003C\u002Fem>: for each link, it randomly chooses between 2 CSS and 2 JavaScript obfuscation methods, making it harder for spammers to crack it.\u003C\u002Fli>\n\u003Cli>\u003Cem>Extensible\u003C\u002Fem>: you can call it manually, and add it to other plugins and themes filters.\u003C\u002Fli>\n\u003Cli>\u003Cem>Customizable\u003C\u002Fem>: use custom parameters to force or avoid specific links from being obfuscated, and to define how non-JavaScript obfuscation will behave.\u003C\u002Fli>\n\u003C\u002Ful>\n","Email and normal links are obfuscated, hiding them from spambots. It automatically encodes each link, then uses JavaScript to decode and show them.",50,18640,0,"2010-10-14T05:01:00.000Z","3.0.5","2.8.0",[18,19,20,21,22],"email","javascript","obfuscate","page-rank","spam","http:\u002F\u002FHikari.ws\u002Femail-url-obfuscator\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.zip",85,null,"2026-04-06T09:54:40.288Z","no_bundle",[],{"slug":31,"display_name":31,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":25,"avg_patch_time_days":34,"trust_score":35,"computed_at":36},"shidouhikari",9,430,30,84,"2026-05-19T23:30:31.237Z",[38,63,84,100,115],{"slug":39,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":48,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":53,"tags":54,"homepage":7,"download_link":58,"security_score":59,"vuln_count":60,"unpatched_count":13,"last_vuln_date":61,"fetched_at":62},"email-address-obfuscation","Email Address Obfuscation","1.2.0","Neotrendy","https:\u002F\u002Fprofiles.wordpress.org\u002Fneotrendy\u002F","\u003Cp>A lightweight plugin that protects email addresses from email-harvesting bots, by converting email addresses characters to HTML entities. Hide email from Spam Bots using a shortcode \u003Ccode>[obfuscate_email]\u003C\u002Fcode> and built-in WordPress function \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Ffunctions\u002Fantispambot\u002F\" title=\"antispambot\" rel=\"nofollow ugc\">antispambot()\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Obfuscate plain email address\u003C\u002Fli>\n\u003Cli>Obfuscate href mailto link in HTML anchor element\u003C\u002Fli>\n\u003Cli>Support for custom CSS class\u003C\u002Fli>\n\u003Cli>Support for email subject\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Obfuscate plain email address\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[obfuscate_email email=\"your@email.com\"]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Create clickable email address\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[obfuscate_email email=\"your@email.com\" link=true]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Add CSS class to the HTML anchor element\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[obfuscate_email email=\"your@email.com\" link=true class=\"my-class another-class\"]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Obfuscate email address with email subject\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[obfuscate_email email='your@email.com?subject=My custom email subject']\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Shortcode parameter\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ccode>email\u003C\u002Fcode> required – Email address.\u003C\u002Fli>\n\u003Cli>\u003Ccode>link\u003C\u002Fcode> optional – Set true if you want to create clickable email address.\u003C\u002Fli>\n\u003Cli>\u003Ccode>class\u003C\u002Fcode> optional – Add space separated list of classes.\u003C\u002Fli>\n\u003C\u002Ful>\n","Email Address Obfuscation prevents email harvesting by hiding email address appearing in your pages, while remaining visible to your site visitors.",2000,10983,100,4,"2025-11-28T10:30:00.000Z","6.9.4","2.5","5.6",[55,18,20,56,57],"anti-spam","obfuscation","protect","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Femail-address-obfuscation.1.2.0.zip",99,1,"2024-12-03 23:42:14","2026-04-16T10:56:18.058Z",{"slug":64,"name":65,"version":66,"author":67,"author_profile":68,"description":69,"short_description":70,"active_installs":71,"downloaded":72,"rating":73,"num_ratings":74,"last_updated":75,"tested_up_to":76,"requires_at_least":77,"requires_php":7,"tags":78,"homepage":81,"download_link":82,"security_score":59,"vuln_count":60,"unpatched_count":13,"last_vuln_date":83,"fetched_at":62},"pixelines-email-protector","Pixeline's Email Protector","1.4.0","pixeline","https:\u002F\u002Fprofiles.wordpress.org\u002Fpixeline\u002F","\u003Cp>This plugin provides an unobtrusive yet efficient protection against email harvesters \u002F spambots. Here is a \u003Ca href=\"https:\u002F\u002Fpixeline.be\u002Fblog\u002Femail-protector-demo-4258.html\" rel=\"nofollow ugc\">demo\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Post\u002Fpage authors may write email addresses in their article in the usual format (“john@doe.com”) without exposing them to spam email harvesters. The plugin takes care of the obfuscation, implementing a graceful degradation technique focusing on usability so as to protect your email addresses from harvesters while keeping them usable to your human visitors.\u003C\u002Fp>\n\u003Cp>The plugin replaces any email address found in posts, pages, comments and excerpts, and replace them by a bit of html markup that should deceive most email harvesters: \u003Ccode>\u003Cspan class=\"email\">john(replace the parenthesis by @)doe.com\u003C\u002Fspan>\u003C\u002Fcode>.\u003Cbr \u002F>\nIf javascript is available, it will display a clickable link and display the original email to the human user. Maximum usability, maximum protection.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Please \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fpixelines-email-protector\u002F\" rel=\"ugc\">rate the plugin\u003C\u002Fa> if you like it.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Write your email addresses inside your posts and pages as usual. When the plugin is activated, it will replace them by a human-readable html string that explains how to deduce the email address, and if javascript is available (99.9% of the time), the original email address will be displayed as a clickable mailto: link. For example:\u003Cbr \u002F>\n    Hello john@doe.com. How are you today?\u003Cbr \u002F>\nwill become\u003Cbr \u002F>\n    John( replace these parenthesis by @ )doe.com.\u003C\u002Fp>\n\u003Cp>Additionally, you can specify what the mailto: link should look like by sticking a parenthesis inside of which you put the visible link text, like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Hello john@doe.com(John Doe). How are you today?\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>will become\u003Cbr \u002F>\n    John( replace these parenthesis by @ )doe.com.\u003C\u002Fp>\n\u003Ch4>inside a theme\u003C\u002Fh4>\n\u003Cp>If you need to protect emails inside your Theme’s files (like the footer.php for example), you can use the function safe_email() like this:\u003C\u002Fp>\n\u003Cpre>\u003Ccode> echo safe_email('you@domain.com'); \u003Ch3>Contribute\u003C\u002Fh3>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Github repo: https:\u002F\u002Fgithub.com\u002Fpixeline\u002Fpixeline-email-protector\u003C\u002Fp>\n","Write email addresses without worrying about spambots and email harvesters.",900,21586,86,8,"2025-09-06T20:47:00.000Z","6.8.5","2.7",[79,18,80,20,22],"address","harvest","https:\u002F\u002Fpixeline.be","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpixelines-email-protector.1.4.0.zip","2025-09-09 00:00:00",{"slug":85,"name":86,"version":87,"author":88,"author_profile":89,"description":90,"short_description":91,"active_installs":34,"downloaded":92,"rating":13,"num_ratings":13,"last_updated":93,"tested_up_to":94,"requires_at_least":95,"requires_php":7,"tags":96,"homepage":98,"download_link":99,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":62},"email-me","Email Me","1.0","robertkay","https:\u002F\u002Fprofiles.wordpress.org\u002Frobertkay\u002F","\u003Cp>Creates an email link from the shortcode [emailme] that spam bots don’t find.\u003Cbr \u002F>\nBy default it uses your wp admin email but you can specify as parameters either:\u003Cbr \u002F>\n  – ‘name’ (for the first portion of the email before the @ symbo)\u003Cbr \u002F>\n  – ‘addr’ for the full email\u003Cbr \u002F>\n  – ‘display’ for what the link should actually display in between the \u003Ca> tags.\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>If your wp-admin panel email (check your General Setting panel)\u003Cbr \u002F>\nis: info@freedomonlineservices.net then\u003Cbr \u002F>\nExamples: [emailme] => info@freedomonlineservices.net\u003Cbr \u002F>\n          [emailme name=’dave’] => dave@freedomonlineservices.net\u003Cbr \u002F>\n          [emailme addr=’someoneelse@somewhereelse.fake’] => someoneelse@somewhereelse.fake\u003Cbr \u002F>\n          [emailme display=”info at freedomonlineservices dot net”] => info at freedomonlineservices dot net (but linked to the actual email!)\u003Cbr \u002F>\nNote you can also set the ‘display’ option to an image tag if you use single quotes.\u003C\u002Fp>\n\u003Cp>More docs at http:\u002F\u002Ffreedomonlineservices.net\u002Fresources\u002Fhomegrown\u002Femailme-wp-plugin\u002F\u003Cbr \u002F>\nLive examples at http:\u002F\u002Fwww.freedomonlineservices.net\u002Fpluginshowroom\u002Femailme-plugin\u002F\u003C\u002Fp>\n","Creates an email link from the shortcode [emailme] that spam bots don't find. Has clever parameters for convenience...",2933,"2013-01-07T06:50:00.000Z","3.5.2","3.0.1",[18,19,20,97],"shortlink","http:\u002F\u002Ffreedomonlineservices.net\u002Fresources\u002Fhomegrown\u002Femailme-wp-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Femail-me.zip",{"slug":101,"name":102,"version":87,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":107,"downloaded":108,"rating":13,"num_ratings":13,"last_updated":109,"tested_up_to":110,"requires_at_least":41,"requires_php":7,"tags":111,"homepage":113,"download_link":114,"security_score":25,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":62},"makesafe","Make Safe","mattdeclaire","https:\u002F\u002Fprofiles.wordpress.org\u002Fmattdeclaire\u002F","\u003Cp>This plugin finds email addresses in the page (anywhere in the resulting HTML, not just the post content), and munges it into a random combination of encoded characters, and outputs a snippet of JavaScript to write the munged string to the page.\u003C\u002Fp>\n","Obfuscates email addresses.",10,1814,"2012-01-31T17:08:00.000Z","3.3.2",[18,20,112],"spam-protection","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fmakesafe","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmakesafe.zip",{"slug":116,"name":117,"version":118,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":107,"downloaded":123,"rating":48,"num_ratings":60,"last_updated":124,"tested_up_to":51,"requires_at_least":125,"requires_php":126,"tags":127,"homepage":130,"download_link":131,"security_score":48,"vuln_count":13,"unpatched_count":13,"last_vuln_date":26,"fetched_at":27},"planleft-contact-camo","Contact Camo","1.0.22","Plan Left","https:\u002F\u002Fprofiles.wordpress.org\u002Fplanleft\u002F","\u003Cp>Contact Camo protects email addresses by obfuscating or completely hiding them in both the source code and the DOM.\u003C\u002Fp>\n\u003Ch3>What Is It?\u003C\u002Fh3>\n\u003Cp>Contact Camo is a plugin for WordPress developed by Plan Left that effectively hides or obfuscates email addresses from scammers, web scrapers and internet bots to help minimize spam and other nefarious, automated actors.\u003C\u002Fp>\n\u003Cp>In addition to protecting  email addresses, Contact Camo also provides some granular control over how those protected  email addresses can be displayed and interacted with by users that are very useful to site builders and also help make site maintenance easier.\u003C\u002Fp>\n\u003Ch3>Example Use Cases\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Educational Organization with large faculty directories\u003C\u002Fli>\n\u003Cli>Nonprofits who need to be accessible without displaying in-content email addresses\u003C\u002Fli>\n\u003Cli>Large Organizations who have departmental pages and points of contact but don’t want to maintain multiple contact forms\u003C\u002Fli>\n\u003Cli>Anyone who doesn’t want to expose email addresses to the scammers, scrapers and bots of the internet.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Why Did You Make This Plugin?\u003C\u002Fh3>\n\u003Cp>We work with many non-profits and educational organizations that need to list contact info in directories on their website. Due to the public visibility of these and their large user base, our clients web properties are under constant threat from spammers and bots. We wanted to ensure that their user directories were safe from these threats while still being functional to visitors. In other words, we needed to hide a bunch of email addresses from the outside world while still allowing the outside world to contact those users via their email address. When we got to developing this plugin, we knew we had to provide a solution that was as bulletproof as possible while allowing our clients and customers the most amount of control over things as practical.\u003C\u002Fp>\n\u003Ch4>Ultimately, we needed to create a plugin that would:\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Optionally hide or obfuscate email addresses from scrapers and bots securely and confidently. For our use case, email addresses needed to be obfuscated in the source code, the DOM, and in HTTP requests. We took the email address out of the client-side equation completely by just tucking it safely away in the database in a lookup table instead of providing a workaround that simply disguises the email address. We essentially took the email address to a safe house and sent out its representative to interact with the outside world on its behalf. Nobody gets the email, not no way, not no how, see?!?\u003C\u002Fli>\n\u003Cli>Provide users with lots of control over the UX of protected  email addresses, but without the need for cumbersome configuration. We decided a shortcode with some good options and sensible defaults would foot the bill for most users.\u003C\u002Fli>\n\u003Cli>Be performant in capabilities, lightweight in footprint, and opinionated in scope.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The client was very pleased with the end-result and so were we. So, we decided to offer it back to the community. Our development team reviewed and scrutinized the existing plugin, found areas for improvements and further customizations, and baked them right in for everyone to use.\u003C\u002Fp>\n\u003Ch3>Who Is It For?\u003C\u002Fh3>\n\u003Cp>Site administrators and content editors\u002Fmoderators. Anyone with a WordPress site that would like the peace of mind of knowing that their user’s email addresses are safely hidden from spam bots and other unintended consumers with ill intent. Content creators that don’t want to worry about the complications and time expenditure of dealing with and managing their user base getting spammed from their platform. And especially when any of the above mentioned require some level of control over what’s displayed to their users, who may very well be their customers or clients or patients, etc…It’s for site builders that want protection AND customization without being overwhelmed.\u003C\u002Fp>\n\u003Ch3>What Problems Does It Solve?\u003C\u002Fh3>\n\u003Cp>Contact Camo hides or obfuscates email addresses in the source code AND the DOM. Not only this, it ensures the unobfuscated email address is never used in any page or ajax request from its originating context; all handling\u002Fprocessing is done server-side. Once obfuscated, the client-side never sees the original email address again (where obfuscated). The obfuscation (key) is a hash that is stored in a lookup table with the original email address.\u003C\u002Fp>\n\u003Cp>A few of the limitations we found in some existing (but great) plugins:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>email address only obfuscated in DOM, but not in source code\u003C\u002Fli>\n\u003Cli>email address only obfuscated in source code, but not in the DOM\u003C\u002Fli>\n\u003Cli>integrating with a 3rd-party service that scrapes entire pages and performs a search-and-replace of email addresses with obfuscated versions in the source code\u003C\u002Fli>\n\u003Cli>email address obfuscation using only html entities replacement\u003C\u002Fli>\n\u003Cli>few options for control   ling output\u003C\u002Fli>\n\u003Cli>no contact form or fallback options\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>How Does It Work?\u003C\u002Fh3>\n\u003Cp>Contact Camo provides a simple shortcode that can be used to manually obfuscate or hide email addresses and control how those email address are presented back to the end-user.\u003C\u002Fp>\n\u003Cp>This shortcode’s eventual default output is a clickable link with the obfuscated email address’s generated hash stored in a data attribute. On click, this hash is used to lookup the email address (or generate and store a new hash in your database for that email if one doesn’t already exist) and then open the browser’s configured email client with the “To” field pre-populated with the corresponding email address.\u003C\u002Fp>\n\u003Cp>The shortcode accepts several parameters for overriding the default output. Output a button instead of a link, add CSS classes, change the text output, etc… The sky’s the limit for display.\u003C\u002Fp>\n\u003Cp>The shortcode also has parameters for displaying an embedded contact form or an optional modal popup contact form instead of a clickable link that opens the browser’s default email client.\u003C\u002Fp>\n\u003Ch3>What is Hide vs Obfuscate?\u003C\u002Fh3>\n\u003Cp>For our plugin, we wanted to give site administrators the option to either completely hide the email address and never let any end content consumer see any piece of the email, or to hide the email until requested and reveal it in context after a specific action is taken.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Hiding the email address:\u003C\u002Fstrong> The site visitor will never see the email address, and instead only be presented a popup contact form that submits and mails through ajax. This option totally hides the email, and it will never be revealed unless the emailed recipient emails the form submitter back.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Obfuscating the email address:\u003C\u002Fstrong> The site visitor will not see the email address until the contact button (or link) is clicked. On click, the email address will be revealed and the visitor can copy or mail to that address.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>What Can I Do With It?\u003C\u002Fh3>\n\u003Cp>We chose to err on the side of simplicity, balanced with enough options as to be useful. To this, we default to an anchor tag output, or – if overridden – a clickable button. We give the user control over which of these as well as css classes and an id. The text output is configurable. And with one option, you can have a modal contact form popup when users click on your link. All without showing the email address you want to use, but hide. Hide for real for real.  The plugin includes template files if you wish to really change the output, like maybe you want a different wrapper, or need to include some custom data attributes for javascript to use. We thought about adding all that level of configuration to our shortcode, but figured if you were at that point, you’d probably also know how to edit a template file 😉\u003C\u002Fp>\n\u003Ch4>Basic Usage:\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>[contactcamo email=\"contact@example.com\"]\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>output: a basic anchor tag with default text\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>[contactcamo email=\"contact@example.com\" label=\"Contact Us\" form=true button=true]\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>output: a clickable button with text that says “Contact Us”.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>[contactcamo email=\"contact@example.com\" label=\"Contact Us\" form=true button=true popup=true]\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>output: a clickable button with text that says “Contact Us” that, when click, pops up a modal contact form\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>[contactcamo email=\"contact@example.com\" subject=\"ContactCamo\" class=\"mail-icon-lg mail-link\"]\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>output: a link with default text typographically styled along with an inline mail icon\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>\u003Ccode>[contactcamo email=\"contact@example.com\" id=\"one-contactcamo-to-rule-them-all\" label=\"Fly, You Fools!\" button=true class=\"btn btn-lg btn-lt-blue mail-icon-sm\"]\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>output: a large, light blue clickable button with text that says “Fly, You Fools!” along with an inline mail icon\u003C\u002Fp>\n\u003Ch4>Shortcode Parameters\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>email\u003C\u002Fstrong> \u003Cem>required string\u003C\u002Fem>\u003Cbr \u002F>\nthe email address to be obfuscated\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>label\u003C\u002Fstrong> \u003Cem>optional string default=”Email”\u003C\u002Fem>\u003Cbr \u002F>\nthe text output\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>subject\u003C\u002Fstrong> \u003Cem>optional string\u003C\u002Fem>\u003Cbr \u002F>\nthe text to populate mail subject lines\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>class\u003C\u002Fstrong> \u003Cem>optional string\u003C\u002Fem>\u003Cbr \u002F>\nthe css class(es) to add to the anchor\u002Fbutton html output, space delimited\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>id\u003C\u002Fstrong> \u003Cem>optional string\u003C\u002Fem>\u003Cbr \u002F>\nthe css id to add to the anchor\u002Fbutton html output\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>form\u003C\u002Fstrong> \u003Cem>optional boolean default=false\u003C\u002Fem>\u003Cbr \u002F>\nif true, output contact form in place of link\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>popup\u003C\u002Fstrong> \u003Cem>optional boolean default=false\u003C\u002Fem>\u003Cbr \u002F>\nif true, output link that opens modal contact form on click\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>button\u003C\u002Fstrong> \u003Cem>optional boolean default=false\u003C\u002Fem>\u003Cbr \u002F>\nif true, output link as a clickable button instead of an anchor tag\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>There is also an admin page for Contact Camo. From this page, you can configure where the contact form redirects after form submission.\u003C\u002Fp>\n","Contact Camo protects email addresses by obfuscating or completely hiding them in both the source code and the DOM.",2914,"2026-03-06T16:51:00.000Z","5.0","8.0",[55,128,18,20,129],"antispam","security","https:\u002F\u002Fplanleft.com\u002Fcontactcamo","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplanleft-contact-camo.1.0.22.zip",{"attackSurface":133,"codeSignals":215,"taintFlows":330,"riskAssessment":364,"analyzedAt":379},{"hooks":134,"ajaxHandlers":211,"restRoutes":212,"shortcodes":213,"cronEvents":214,"entryPointCount":13,"unprotectedCount":13},[135,141,145,149,156,159,162,165,168,171,174,177,180,183,186,189,192,195,199,203,207],{"type":136,"name":137,"callback":138,"file":139,"line":140},"action","init","startup","hikari-tools.php",34,{"type":136,"name":142,"callback":143,"file":139,"line":144},"admin_init","options_init",449,{"type":136,"name":146,"callback":147,"file":139,"line":148},"admin_menu","menuPrepare",450,{"type":150,"name":151,"callback":152,"priority":153,"file":154,"line":155},"filter","the_content","the_content_filter",1002,"hikariobfuscator-core.php",106,{"type":150,"name":157,"callback":152,"priority":153,"file":154,"line":158},"the_excerpt",107,{"type":150,"name":160,"callback":150,"priority":153,"file":154,"line":161},"comment_text",110,{"type":150,"name":163,"callback":150,"priority":153,"file":154,"line":164},"comment_text_rss",111,{"type":150,"name":166,"callback":150,"priority":153,"file":154,"line":167},"comment_excerpt",112,{"type":150,"name":169,"callback":150,"priority":153,"file":154,"line":170},"comment_url",113,{"type":150,"name":172,"callback":150,"priority":153,"file":154,"line":173},"get_comment_author_url_link",116,{"type":150,"name":175,"callback":150,"priority":153,"file":154,"line":176},"get_comment_author_link",117,{"type":150,"name":178,"callback":150,"priority":153,"file":154,"line":179},"get_comment_author_url",118,{"type":150,"name":181,"callback":150,"priority":153,"file":154,"line":182},"widget_text",121,{"type":150,"name":184,"callback":150,"priority":153,"file":154,"line":185},"widget_execphp",125,{"type":150,"name":187,"callback":150,"priority":153,"file":154,"line":188},"navt_codeblock",126,{"type":150,"name":190,"callback":150,"priority":153,"file":154,"line":191},"hksmtc_twitter_link",127,{"type":150,"name":193,"callback":150,"priority":153,"file":154,"line":194},"HkTC_get_comment_title",128,{"type":136,"name":196,"callback":197,"file":154,"line":198},"wp_print_styles","stylesAction",132,{"type":136,"name":200,"callback":201,"priority":13,"file":154,"line":202},"wp_head","header",133,{"type":136,"name":200,"callback":204,"priority":205,"file":154,"line":206},"inline_js_preparation",5,136,{"type":136,"name":208,"callback":209,"priority":205,"file":154,"line":210},"wp_print_footer_scripts","footer_js_insersion",138,[],[],[],[],{"dangerousFunctions":216,"sqlUsage":227,"outputEscaping":229,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":329},[217,221,224],{"fn":218,"file":154,"line":219,"context":220},"str_rot13",352,"$js_url = str_rot13($original_URL);",{"fn":218,"file":154,"line":222,"context":223},353,"$js_attibutes = str_rot13($attibutes);",{"fn":218,"file":154,"line":225,"context":226},357,"$js_content=str_rot13($original_content);",{"prepared":13,"raw":13,"locations":228},[],{"escaped":13,"rawEcho":230,"locations":231},59,[232,234,236,238,240,242,244,246,248,249,250,251,252,254,256,258,259,260,261,262,264,266,268,270,271,273,275,277,278,279,281,282,284,286,288,289,290,292,293,295,296,298,300,302,304,306,308,309,311,313,315,316,318,319,321,323,324,325,327],{"file":139,"line":188,"context":233},"raw output",{"file":139,"line":235,"context":233},134,{"file":139,"line":237,"context":233},135,{"file":139,"line":239,"context":233},140,{"file":139,"line":241,"context":233},147,{"file":139,"line":243,"context":233},156,{"file":139,"line":245,"context":233},588,{"file":139,"line":247,"context":233},590,{"file":139,"line":247,"context":233},{"file":139,"line":247,"context":233},{"file":139,"line":247,"context":233},{"file":139,"line":247,"context":233},{"file":139,"line":253,"context":233},592,{"file":139,"line":255,"context":233},609,{"file":139,"line":257,"context":233},611,{"file":139,"line":257,"context":233},{"file":139,"line":257,"context":233},{"file":139,"line":257,"context":233},{"file":139,"line":257,"context":233},{"file":139,"line":263,"context":233},613,{"file":139,"line":265,"context":233},622,{"file":139,"line":267,"context":233},624,{"file":139,"line":269,"context":233},630,{"file":139,"line":269,"context":233},{"file":139,"line":272,"context":233},635,{"file":139,"line":274,"context":233},644,{"file":139,"line":276,"context":233},659,{"file":139,"line":276,"context":233},{"file":139,"line":276,"context":233},{"file":139,"line":280,"context":233},660,{"file":139,"line":280,"context":233},{"file":139,"line":283,"context":233},664,{"file":139,"line":285,"context":233},673,{"file":139,"line":287,"context":233},693,{"file":139,"line":287,"context":233},{"file":139,"line":287,"context":233},{"file":139,"line":291,"context":233},694,{"file":139,"line":291,"context":233},{"file":139,"line":294,"context":233},698,{"file":139,"line":294,"context":233},{"file":139,"line":297,"context":233},700,{"file":139,"line":299,"context":233},765,{"file":139,"line":301,"context":233},766,{"file":139,"line":303,"context":233},767,{"file":139,"line":305,"context":233},798,{"file":139,"line":307,"context":233},823,{"file":139,"line":307,"context":233},{"file":139,"line":310,"context":233},833,{"file":139,"line":312,"context":233},848,{"file":139,"line":314,"context":233},850,{"file":139,"line":71,"context":233},{"file":139,"line":317,"context":233},972,{"file":139,"line":317,"context":233},{"file":139,"line":320,"context":233},1012,{"file":139,"line":322,"context":233},1014,{"file":139,"line":322,"context":233},{"file":139,"line":322,"context":233},{"file":139,"line":326,"context":233},1066,{"file":154,"line":328,"context":233},194,[],[331,354],{"entryPoint":332,"graph":333,"unsanitizedCount":60,"severity":353},"debugRequestParameters (hikari-tools.php:928)",{"nodes":334,"edges":349},[335,340,344],{"id":336,"type":337,"label":338,"file":139,"line":339},"n0","source","$_REQUEST",932,{"id":341,"type":342,"label":343,"file":139,"line":339},"n1","transform","→ dump()",{"id":345,"type":346,"label":347,"file":139,"line":237,"wp_function":348},"n2","sink","echo() [XSS]","echo",[350,352],{"from":336,"to":341,"sanitized":351},false,{"from":341,"to":345,"sanitized":351},"medium",{"entryPoint":355,"graph":356,"unsanitizedCount":60,"severity":353},"\u003Chikari-tools> (hikari-tools.php:0)",{"nodes":357,"edges":361},[358,359,360],{"id":336,"type":337,"label":338,"file":139,"line":339},{"id":341,"type":342,"label":343,"file":139,"line":339},{"id":345,"type":346,"label":347,"file":139,"line":237,"wp_function":348},[362,363],{"from":336,"to":341,"sanitized":351},{"from":341,"to":345,"sanitized":351},{"summary":365,"deductions":366},"The hikari-email-url-obfuscator plugin exhibits a mixed security posture. On the positive side, it demonstrates good practices by having no recorded CVEs, no file operations, no external HTTP requests, and all SQL queries utilizing prepared statements. The attack surface is also zero, with no AJAX handlers, REST API routes, shortcodes, or cron events, which significantly limits potential entry points. However, several critical concerns are raised by the static analysis. The plugin uses the `str_rot13` function, which is often associated with obfuscation and can be a red flag for potential security issues if not handled carefully. More significantly, 100% of output is not properly escaped, indicating a high risk of Cross-Site Scripting (XSS) vulnerabilities. Furthermore, the taint analysis reveals two flows with unsanitized paths, suggesting potential for path traversal or other file system-related vulnerabilities, even though no direct file operations were detected. The absence of any nonce or capability checks on any entry points, while the attack surface is zero, could still be a concern if the plugin were to evolve and add entry points without implementing proper authorization checks. The lack of historical vulnerabilities is a positive indicator, but it does not negate the risks identified in the current code analysis. The plugin's strengths lie in its limited attack surface and secure database interactions, but its weaknesses in output escaping and potential unsanitized paths present significant risks that require immediate attention.",[367,369,372,375,377],{"reason":368,"points":74},"100% of output is not properly escaped",{"reason":370,"points":371},"2 flows with unsanitized paths",7,{"reason":373,"points":374},"Dangerous function str_rot13 used",3,{"reason":376,"points":205},"0 Nonce checks on entry points",{"reason":378,"points":205},"0 Capability checks on entry points","2026-04-16T11:08:48.184Z",{"wat":381,"direct":388},{"assetPaths":382,"generatorPatterns":385,"scriptPaths":386,"versionParams":387},[383,384],"\u002Fwp-content\u002Fplugins\u002Fhikari-email-url-obfuscator\u002FHkMuob.css","\u002Fwp-content\u002Fplugins\u002Fhikari-email-url-obfuscator\u002FHkMuob.js",[],[384],[],{"cssClasses":389,"htmlComments":390,"htmlAttributes":393,"restEndpoints":394,"jsGlobals":395,"shortcodeOutput":397},[],[391,392],"Emails and URLs obfuscated by \n Hikari Email & URL Obfuscator - http:\u002F\u002FHikari.ws\u002Femail-url-obfuscator\u002F","\u003C!-- HkMuob NO OBFUSCATE -->",[],[],[396],"HkMuob",[],{"error":399,"url":400,"statusCode":401,"statusMessage":402,"message":402},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fhikari-email-url-obfuscator\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":404,"versions":405},12,[406,413,420,427,434,441,448,454,460,467,474,481],{"version":407,"download_url":408,"svn_tag_url":409,"released_at":26,"has_diff":351,"diff_files_changed":410,"diff_lines":26,"trac_diff_url":411,"vulnerabilities":412,"is_current":351},"0.07.17","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.0.07.17.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002F0.07.17\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2F0.06.06&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2F0.07.17",[],{"version":414,"download_url":415,"svn_tag_url":416,"released_at":26,"has_diff":351,"diff_files_changed":417,"diff_lines":26,"trac_diff_url":418,"vulnerabilities":419,"is_current":351},"0.06.06","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.0.06.06.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002F0.06.06\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2F0.05.01&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2F0.06.06",[],{"version":421,"download_url":422,"svn_tag_url":423,"released_at":26,"has_diff":351,"diff_files_changed":424,"diff_lines":26,"trac_diff_url":425,"vulnerabilities":426,"is_current":351},"0.05.01","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.0.05.01.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002F0.05.01\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2F0.04.05&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2F0.05.01",[],{"version":428,"download_url":429,"svn_tag_url":430,"released_at":26,"has_diff":351,"diff_files_changed":431,"diff_lines":26,"trac_diff_url":432,"vulnerabilities":433,"is_current":351},"0.04.05","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.0.04.05.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002F0.04.05\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2FHkMuob.css&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2F0.04.05",[],{"version":435,"download_url":436,"svn_tag_url":437,"released_at":26,"has_diff":351,"diff_files_changed":438,"diff_lines":26,"trac_diff_url":439,"vulnerabilities":440,"is_current":351},"HkMuob.css","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.HkMuob.css.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002FHkMuob.css\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2FHkMuob.js&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2FHkMuob.css",[],{"version":442,"download_url":443,"svn_tag_url":444,"released_at":26,"has_diff":351,"diff_files_changed":445,"diff_lines":26,"trac_diff_url":446,"vulnerabilities":447,"is_current":351},"HkMuob.js","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.HkMuob.js.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002FHkMuob.js\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2Fhikari-tools.php&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2FHkMuob.js",[],{"version":139,"download_url":449,"svn_tag_url":450,"released_at":26,"has_diff":351,"diff_files_changed":451,"diff_lines":26,"trac_diff_url":452,"vulnerabilities":453,"is_current":351},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.hikari-tools.php.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002Fhikari-tools.php\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2Fhikariobfuscator-core.php&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2Fhikari-tools.php",[],{"version":154,"download_url":455,"svn_tag_url":456,"released_at":26,"has_diff":351,"diff_files_changed":457,"diff_lines":26,"trac_diff_url":458,"vulnerabilities":459,"is_current":351},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.hikariobfuscator-core.php.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002Fhikariobfuscator-core.php\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2Fhikariobfuscator-options.php&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2Fhikariobfuscator-core.php",[],{"version":461,"download_url":462,"svn_tag_url":463,"released_at":26,"has_diff":351,"diff_files_changed":464,"diff_lines":26,"trac_diff_url":465,"vulnerabilities":466,"is_current":351},"hikariobfuscator-options.php","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.hikariobfuscator-options.php.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002Fhikariobfuscator-options.php\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2Fhikariobfuscator.php&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2Fhikariobfuscator-options.php",[],{"version":468,"download_url":469,"svn_tag_url":470,"released_at":26,"has_diff":351,"diff_files_changed":471,"diff_lines":26,"trac_diff_url":472,"vulnerabilities":473,"is_current":351},"hikariobfuscator.php","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.hikariobfuscator.php.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002Fhikariobfuscator.php\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2Flicense.txt&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2Fhikariobfuscator.php",[],{"version":475,"download_url":476,"svn_tag_url":477,"released_at":26,"has_diff":351,"diff_files_changed":478,"diff_lines":26,"trac_diff_url":479,"vulnerabilities":480,"is_current":351},"license.txt","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.license.txt.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002Flicense.txt\u002F",[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fhikari-email-url-obfuscator%2Ftags%2Freadme.txt&new_path=%2Fhikari-email-url-obfuscator%2Ftags%2Flicense.txt",[],{"version":482,"download_url":483,"svn_tag_url":484,"released_at":26,"has_diff":351,"diff_files_changed":485,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":486,"is_current":351},"readme.txt","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhikari-email-url-obfuscator.readme.txt.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fhikari-email-url-obfuscator\u002Ftags\u002Freadme.txt\u002F",[],[]]