[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fcojd-tRC7UHsykJc6sx9jVp110_bzXpoUOWiY1sl31k":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":23,"download_link":24,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":35,"analysis":134,"fingerprints":179},"idna","IDNA","1.2.0","dwright","https:\u002F\u002Fprofiles.wordpress.org\u002Fdwright\u002F","\u003Cp>This plugin adds IDN support to WordPress, making it an IDNA application. An IDN is a domain name that contains non-ascii characters.\u003Cbr \u002F>\nThis plugin enables one to set the WordPress address (URL) to an IDN. (instead of the Punycode Representation)\u003C\u002Fp>\n\u003Cp>Examples of an IDN:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>bücher.ch\u003C\u002Fli>\n\u003Cli>domæne.dk\u003C\u002Fli>\n\u003Cli>nörgler.com\u003C\u002Fli>\n\u003Cli>uddannelsesstøtte.dk\u003C\u002Fli>\n\u003Cli>müller.de\u003C\u002Fli>\n\u003Cli>räksmörgås.nu\u003C\u002Fli>\n\u003Cli>画像.jp\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cblockquote>\n\u003Cp>“An IDNA-enabled application is able to convert between the internationalised\u003Cbr \u002F>\n  and ASCII representations of a domain name. It uses the ASCII form for DNS\u003Cbr \u002F>\n  lookups but can present the internationalised form to users who presumably\u003Cbr \u002F>\n  prefer to read and write domain names in non-ASCII scripts such as Arabic or\u003Cbr \u002F>\n  Hiragana. Applications that do not support IDNA will not be able to handle\u003Cbr \u002F>\n  domain names with non-ASCII characters, but will still be able to access such\u003Cbr \u002F>\n  domains if given the (usually rather cryptic) ASCII equivalent.” –\u003Cbr \u002F>\n  \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FInternationalized_domain_name\" rel=\"nofollow ugc\">IDN entry at Wikipedia\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>In simple terms, this plugin allows one to set their blog url to an IDN.\u003C\u002Fp>\n\u003Cp>If you are interested in seeing what the PUNYCODE version of your IDN is, here is an \u003Ca href=\"http:\u002F\u002Fmct.verisign-grs.com\u002Fconversiontool\u002F\" rel=\"nofollow ugc\">online conversion tool\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>As an example:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>Frau Müller has a blog and wants to use the IDN, http:\u002F\u002Fwww.müller.de\u003Cbr \u002F>\n  Currently, she would have to set the WP blog url, (General Settings menu) to\u003Cbr \u002F>\n  the Punycode version: \u003Cem>xn--mller-kva.de\u003C\u002Fem>, (which is the ascii representation\u003Cbr \u002F>\n  of müller.de) this would allow users using a IDN aware web browser to access\u003Cbr \u002F>\n  the site using the desired url: http:\u002F\u002Fwww.müller.de\u003Cbr \u002F>\n  (and also of course, xn--mller-kva.de).\u003C\u002Fp>\n\u003Cp>It is more convenient for Frau Müller to use the actual IDN\u003Cbr \u002F>\n  http:\u002F\u002Fwww.müller.de as the WP blog url setting (General Settings menu),\u003Cbr \u002F>\n  this plugin enables that functionality.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>There are a few caveats with using this plugin, depending on what Browser, Operating\u003Cbr \u002F>\nSystem and versions used, one can get unexpected results.\u003C\u002Fp>\n\u003Cp>Firefox >= 3.*\u003C\u002Fp>\n\u003Cp>Firefox supports IDN’s but maintains a ‘whitelist’ of ‘safe’ domains.\u003Cbr \u002F>\n.com, .net, .eu are not white listed for safety reasons, so IDN’s on these\u003Cbr \u002F>\ndomains will display as Punycode.  \u003Ca href=\"https:\u002F\u002Fsupport.mozilla.com\u002Fen-US\u002Fforum\u002F1\u002F545827\" rel=\"nofollow ugc\">see bug: \u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>There is an new (‘experimental’) Firefox add-on,\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Faddons.mozilla.org\u002Fen-US\u002Ffirefox\u002Faddon\u002F109224\" rel=\"nofollow ugc\">IDN Navbar\u003C\u002Fa>, which\u003Cbr \u002F>\nwill enable all (whitelisted – Punycode) domains to display as IDN’s.\u003Cbr \u002F>\nSo, if using Firefox and this plugin you (and your visitors) may want to install that addon.\u003C\u002Fp>\n\u003Cp>Internet Explorer >= 7.*\u003C\u002Fp>\n\u003Cp>Depending on your language set up, site’s that contain non ‘native language’\u003Cbr \u002F>\ncharacters will display as Punycode and not the IDN. More info\u003Cbr \u002F>\n\u003Ca href=\"http:\u002F\u002Fblogs.msdn.com\u002Fie\u002Farchive\u002F2006\u002F07\u002F31\u002F684337.aspx\" rel=\"nofollow ugc\">msdn blogs\u003C\u002Fa>\u003Cbr \u002F>\n\u003Ca href=\"http:\u002F\u002Fmsdn.microsoft.com\u002Fen-us\u002Flibrary\u002Fbb250505(VS.85).aspx\" rel=\"nofollow ugc\">msdn libs1\u003C\u002Fa>\u003Cbr \u002F>\n\u003Ca href=\"http:\u002F\u002Fmsdn.microsoft.com\u002Fen-us\u002Flibrary\u002Fdd565654(VS.85).aspx\" rel=\"nofollow ugc\">msdn libs2\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Safari\u002FOpera 10.* seem to display IDN’s for all domain’s fine. (untested)\u003C\u002Fp>\n\u003Ch3>Arbitrary section\u003C\u002Fh3>\n\u003Cp>WP plugins have a ‘stable tag’ requirement for distribution, however, at this\u003Cbr \u002F>\ntime, I consider this plugin to be \u003Cstrong>Beta\u003C\u002Fstrong> quality at best.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>It is possible to lock your self out of the administrative section of your blog\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE\u003C\u002Fstrong> make sure you are using an IDN capable web browser when enabling this plugin.\u003Cbr \u002F>\n\u003Ca href=\"http:\u002F\u002Fidn.icann.org\u002FIDN-aware_software#Browsers\" rel=\"nofollow ugc\">More\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE\u003C\u002Fstrong> Unfortunely, Current Firefox versions display the Punycode version and\u003Cbr \u002F>\nNOT the IDN. For more details, (and work around) see the ‘Other Notes’ Link\u003Cbr \u002F>\n(Arbitrary section – readme.txt)\u003C\u002Fp>\n\u003Cp>IE7\u002F8, Safari, Opera10 all display the actual IDN, Firefox (and Chrome)\u003Cbr \u002F>\nnavigation bar’s display the IDN as Punycode. (i.e. www.xn--)\u003C\u002Fp>\n\u003Cp>There are some security issues with multi-byte chars and phishing, so this is\u003Cbr \u002F>\nMozilla’s current approach, this may change in the future, as some folks are not\u003Cbr \u002F>\nhappy about it.\u003C\u002Fp>\n\u003Cp>https:\u002F\u002Fbugzilla.mozilla.org\u002Fshow_bug.cgi?id=542562\u003Cbr \u002F>\nanother related, one: https:\u002F\u002Fbugzilla.mozilla.org\u002Fshow_bug.cgi?id=354592\u003C\u002Fp>\n\u003Cp>Because this plugin effects how you access your site, installation is slightly more\u003Cbr \u002F>\ninvolved than most plugins.\u003C\u002Fp>\n\u003Cp>If you installing this plugin, I would recommend, if possible, that it is the\u003Cbr \u002F>\nfirst thing you do on your blog, before you add any content, just in case\u003Cbr \u002F>\nsomething goes wrong, this will minimize downtime.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE\u003C\u002Fstrong> If something goes wrong and you cant access the WP admin area after\u003Cbr \u002F>\nchanging your url, here are some instructions for\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FChanging_The_Site_URL\" rel=\"nofollow ugc\">resetting your url\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cem>Please report any bugs you find to the author of this plugin\u003C\u002Fem>\u003C\u002Fp>\n","This plugin adds IDN support to Wordpress. IDN (Internationalized domain name) is a domain name that contains non-ascii characters.",10,4440,100,2,"2010-05-10T08:18:00.000Z","3.0.5","2.7","",[20,21,22],"i18n","idn","punycode","http:\u002F\u002Fwww.dwright.us\u002Fmisc\u002Fidna\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fidna.1.2.0.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"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},1,30,84,"2026-04-04T05:51:33.012Z",[36,53,79,96,115],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":11,"downloaded":44,"rating":26,"num_ratings":26,"last_updated":45,"tested_up_to":46,"requires_at_least":47,"requires_php":18,"tags":48,"homepage":50,"download_link":51,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":52},"idn-ajax-workaround","IDN AJAX Workaround","0.1","Sergey Biryukov","https:\u002F\u002Fprofiles.wordpress.org\u002Fsergeybiryukov\u002F","\u003Cp>In jQuery 1.5+ (bundled with WordPress 3.2+), AJAX requests on sites with IDN domains don’t work in IE or Opera.\u003C\u002Fp>\n\u003Cp>On Edit Post screen, adding a new category results in JS error:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>Message: 'parsed.responses' - is null or not an object\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>On Categories screen, adding a new category silently fails.\u003C\u002Fp>\n\u003Cp>According to \u003Ca href=\"http:\u002F\u002Fbugs.jquery.com\u002Fticket\u002F8419#comment:3\" rel=\"nofollow ugc\">jaubourg’s comment\u003C\u002Fa> in jQuery bug tracker, the request is considered cross-domain and, since IE doesn’t support cross-domain requests, AJAX won’t find a suitable transport and bail out.\u003C\u002Fp>\n\u003Cp>This plugin implements a workaround suggested there by making AJAX requests relative.\u003C\u002Fp>\n\u003Cp>WordPress Trac ticket: \u003Ca href=\"https:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F18952\" rel=\"nofollow ugc\">#18952\u003C\u002Fa>\u003C\u002Fp>\n","Fixes AJAX requests on sites with IDN domains in IE and Opera.",3079,"2012-05-03T16:48:00.000Z","3.3.2","3.2",[49,20,21],"ajax","http:\u002F\u002Fcore.trac.wordpress.org\u002Fticket\u002F18952","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fidn-ajax-workaround.0.1.zip","2026-03-15T14:54:45.397Z",{"slug":54,"name":55,"version":56,"author":57,"author_profile":58,"description":59,"short_description":60,"active_installs":61,"downloaded":62,"rating":63,"num_ratings":64,"last_updated":65,"tested_up_to":66,"requires_at_least":67,"requires_php":68,"tags":69,"homepage":74,"download_link":75,"security_score":76,"vuln_count":77,"unpatched_count":26,"last_vuln_date":78,"fetched_at":28},"loco-translate","Loco Translate","2.8.3","Tim W","https:\u002F\u002Fprofiles.wordpress.org\u002Ftimwhitlock\u002F","\u003Cp>Loco Translate provides in-browser editing of WordPress translation files and integration with automatic translation services.\u003C\u002Fp>\n\u003Cp>It also provides Gettext\u002Flocalization tools for developers, such as extracting strings and generating templates.\u003C\u002Fp>\n\u003Cp>Features include:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Built-in translation editor within WordPress admin\u003C\u002Fli>\n\u003Cli>Integration with translation APIs including DeepL, Google, Lecto, Microsoft and OpenAI.\u003C\u002Fli>\n\u003Cli>Create and update language files directly in your theme or plugin\u003C\u002Fli>\n\u003Cli>Extraction of translatable strings from your source code\u003C\u002Fli>\n\u003Cli>Native MO file compilation without the need for Gettext on your system\u003C\u002Fli>\n\u003Cli>JSON (Jed) file compilation compatible with WordPress script localization\u003C\u002Fli>\n\u003Cli>Support for standard PO features including comments, references and plural forms\u003C\u002Fli>\n\u003Cli>PO source view with clickable source code references\u003C\u002Fli>\n\u003Cli>Protected language directory for saving custom translations\u003C\u002Fli>\n\u003Cli>Configurable PO file backups with diff and restore capability\u003C\u002Fli>\n\u003Cli>Built-in WordPress locale codes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Official \u003Ca href=\"https:\u002F\u002Flocalise.biz\u002F\" rel=\"nofollow ugc\">Loco\u003C\u002Fa> WordPress plugin by Tim Whitlock.\u003Cbr \u002F>\nFor more information please visit our \u003Ca href=\"https:\u002F\u002Flocalise.biz\u002Fwordpress\u002Fplugin\" rel=\"nofollow ugc\">plugin page\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Keyboard shortcuts\u003C\u002Fh3>\n\u003Cp>The PO file editor supports the following keyboard shortcuts for faster translating:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Done and Next: \u003Ccode>Ctrl ↵\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Next string: \u003Ccode>Ctrl \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">↓\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Previous string: \u003Ccode>Ctrl \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">↑\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Next untranslated: \u003Ccode>Shift Ctrl \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">↓\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Previous untranslated: \u003Ccode>Shift Ctrl \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">↑\u003C\u002Fspan>\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Copy from source text: \u003Ccode>Ctrl B\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Clear translation: \u003Ccode>Ctrl K\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Toggle Fuzzy: \u003Ccode>Ctrl U\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Save PO \u002F compile MO: \u003Ccode>Ctrl S\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Toggle invisibles: \u003Ccode>Shift Ctrl I\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Suggest translation: \u003Ccode>Ctrl J\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Mac users can use ⌘ Cmd instead of Ctrl.\u003C\u002Fp>\n","Translate WordPress plugins and themes directly in your browser. Versatile PO file editor with integrated AI translation providers.",1000000,34331592,96,447,"2026-03-14T11:53:00.000Z","6.9.4","6.6","7.4",[20,70,71,72,73],"l10n","language","multilingual","translation","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Floco-translate\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Floco-translate.2.8.3.zip",98,3,"2024-06-21 00:00:00",{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":61,"downloaded":87,"rating":13,"num_ratings":88,"last_updated":89,"tested_up_to":66,"requires_at_least":90,"requires_php":18,"tags":91,"homepage":94,"download_link":95,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"wp-multibyte-patch","WP Multibyte Patch","2.9.3","Seisuke Kuraishi","https:\u002F\u002Fprofiles.wordpress.org\u002Ftenpura\u002F","\u003Cp>Multibyte functionality enhancement for the WordPress Japanese package.\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Feastcoder.com\u002Fcode\u002Fwp-multibyte-patch\u002F\" title=\"Documentation in Japanese\" rel=\"nofollow ugc\">日本語の説明を読む\u003C\u002Fa>\u003C\u002Fp>\n","Multibyte functionality enhancement for the WordPress Japanese package.",7864798,24,"2025-12-01T21:45:00.000Z","5.2",[20,92,93,80],"japanese","multibyte","https:\u002F\u002Feastcoder.com\u002Fcode\u002Fwp-multibyte-patch\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-multibyte-patch.2.9.3.zip",{"slug":97,"name":98,"version":6,"author":99,"author_profile":100,"description":101,"short_description":102,"active_installs":103,"downloaded":104,"rating":76,"num_ratings":105,"last_updated":106,"tested_up_to":66,"requires_at_least":107,"requires_php":108,"tags":109,"homepage":113,"download_link":114,"security_score":13,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"performant-translations","Performant Translations","Pascal Birchler","https:\u002F\u002Fprofiles.wordpress.org\u002Fswissspidy\u002F","\u003Cp>Making internationalization\u002Flocalization in WordPress faster than ever before.\u003C\u002Fp>\n\u003Ch3>Disclaimer about WordPress 6.5\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Attention:\u003C\u002Fstrong> most functionality of this plugin has been merged into WordPress 6.5! You might not need it anymore.\u003C\u002Fp>\n\u003Cp>\u003Cem>However\u003C\u002Fem>, this plugin is still relevant for cases where language packs are not downloaded from WordPress.org but somewhere else, for example if you are developing your own plugins or using commercial plugins.\u003C\u002Fp>\n\u003Cp>The Performant Translations plugin converts the translation files of those plugins to the new file format introduced in WordPress 6.5, to really optimize them for speed.\u003C\u002Fp>\n\u003Ch3>What this plugin does\u003C\u002Fh3>\n\u003Cp>This project uses a new approach to handle translation files in WordPress, making localization blazing fast.\u003C\u002Fp>\n\u003Cp>An \u003Ca href=\"https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002F2023\u002F07\u002F24\u002Fi18n-performance-analysis\u002F\" rel=\"nofollow ugc\">in-depth i18n performance analysis\u003C\u002Fa> showed that localized WordPress sites load significantly slower than a site without translations.\u003C\u002Fp>\n\u003Cp>With this plugin’s new approach to localization, this overhead is massively reduced, making your site fast again. It does so by converting \u003Ccode>.mo\u003C\u002Fcode> translation files to \u003Ccode>.php\u003C\u002Fcode> files.\u003C\u002Fp>\n\u003Cp>If your site is using a language other than English (US), you should see immediate speed improvements simply by activating this plugin.\u003C\u002Fp>\n","Making internationalization\u002Flocalization in WordPress faster than ever before.",40000,192704,16,"2025-12-05T10:38:00.000Z","6.5","7.0",[20,110,111,112,73],"internationalization","localization","performance","https:\u002F\u002Fgithub.com\u002Fswissspidy\u002Fperformant-translations","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fperformant-translations.1.2.0.zip",{"slug":116,"name":117,"version":118,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":123,"downloaded":124,"rating":125,"num_ratings":126,"last_updated":127,"tested_up_to":128,"requires_at_least":129,"requires_php":18,"tags":130,"homepage":132,"download_link":133,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"js-composer-qtranslate-x","WPBakery Visual Composer & qTranslate-X","1.0","John Clause","https:\u002F\u002Fprofiles.wordpress.org\u002Fjohnclause\u002F","\u003Cp>Enables \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fqtranslate-x\u002F\" rel=\"ugc\">qTranslate-X\u003C\u002Fa> multilingual framework for plugin \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjs-composer-qtranslate-x\" rel=\"ugc\">WPBakery Visual Composer\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>At least version 3.3 of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fqtranslate-x\u002F\" rel=\"ugc\">qTranslate-X\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FqTranslate-Team\u002Fqtranslate-x\u002Farchive\u002F3.2.9.9.4.zip\" rel=\"nofollow ugc\">alpha pre-release\u003C\u002Fa> is required.\u003C\u002Fp>\n\u003Cp>This plugin is currently a work in progress, please review the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjs-composer-qtranslate-x\u002Fother_notes\u002F\" rel=\"ugc\">Known Issues\u003C\u002Fa> and report the features, which did not work for you.\u003C\u002Fp>\n\u003Ch3>Known Issues\u003C\u002Fh3>\n","Enables multilingual framework for plugin \"WPBakery Visual Composer\".",8000,149576,64,11,"2017-11-28T08:32:00.000Z","4.1.42","4.0",[131,20,70,71,72],"bilingual","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjs-composer-qtranslate-x","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjs-composer-qtranslate-x.1.0.zip",{"attackSurface":135,"codeSignals":167,"taintFlows":174,"riskAssessment":175,"analyzedAt":178},{"hooks":136,"ajaxHandlers":163,"restRoutes":164,"shortcodes":165,"cronEvents":166,"entryPointCount":26,"unprotectedCount":26},[137,143,147,150,153,156,160],{"type":138,"name":139,"callback":140,"priority":11,"file":141,"line":142},"filter","wp_redirect","login_idn_support","idna_wp.php",146,{"type":138,"name":144,"callback":145,"priority":11,"file":141,"line":146},"the_permalink_rss","idn_to_ascii",149,{"type":138,"name":148,"callback":145,"priority":11,"file":141,"line":149},"get_comment_link",150,{"type":138,"name":151,"callback":145,"priority":11,"file":141,"line":152},"bloginfo_rss",151,{"type":138,"name":154,"callback":145,"priority":11,"file":141,"line":155},"page_link",152,{"type":138,"name":157,"callback":158,"priority":11,"file":141,"line":159},"home_url","if_as_xml_feed__uri_to_ascii",154,{"type":138,"name":161,"callback":158,"priority":11,"file":141,"line":162},"post_link",156,[],[],[],[],{"dangerousFunctions":168,"sqlUsage":169,"outputEscaping":171,"fileOperations":26,"externalRequests":26,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":173},[],{"prepared":26,"raw":26,"locations":170},[],{"escaped":126,"rawEcho":26,"locations":172},[],[],[],{"summary":176,"deductions":177},"The \"idna\" plugin version 1.2.0 exhibits an exceptionally strong security posture based on the provided static analysis and vulnerability history. The static analysis reveals a complete absence of detectable attack surface points, meaning there are no exposed AJAX handlers, REST API routes, shortcodes, or cron events that could be targeted by attackers. Furthermore, the code itself shows excellent security practices, with no dangerous functions, all SQL queries utilizing prepared statements, and all output being properly escaped.  There are no file operations or external HTTP requests that could introduce vulnerabilities.\n\nThe lack of any recorded CVEs, past or present, further solidifies this plugin's security. This history indicates a mature and well-maintained codebase, or a plugin that has not historically attracted malicious attention, which is a positive sign. The absence of taint analysis findings also suggests that data is handled safely within the plugin, with no unsanitized paths or critical\u002Fhigh severity flows identified.\n\nIn conclusion, the \"idna\" plugin v1.2.0 appears to be very secure. Its strengths lie in its minimal attack surface, robust coding practices demonstrated in the static analysis, and a clean vulnerability history. There are no identified weaknesses in the provided data that would warrant deductions from a security standpoint.",[],"2026-03-17T00:42:49.994Z",{"wat":180,"direct":185},{"assetPaths":181,"generatorPatterns":182,"scriptPaths":183,"versionParams":184},[],[],[],[],{"cssClasses":186,"htmlComments":187,"htmlAttributes":188,"restEndpoints":189,"jsGlobals":190,"shortcodeOutput":191},[],[],[],[],[],[]]