[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fhmdg81ZXtLVlfLLZRy7m2h3kcUl6d-w6rECBEzX2fsk":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":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":38,"analysis":127,"fingerprints":166},"events-made-easy-qtranslate-x","Events Made Easy & qTranslate-X","1.1","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\u002Fevents-made-easy\u002F\" rel=\"ugc\">Events Made Easy\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>At least version 3.2.2 of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fqtranslate-x\u002F\" rel=\"ugc\">qTranslate-X\u003C\u002Fa> is required.\u003C\u002Fp>\n","Enables multilingual framework for plugin \"Events Made Easy\".",30,3407,100,1,"2017-03-31T17:01:00.000Z","4.8.28","4.0","",[20,21,22,23,24],"bilingual","i18n","l10n","language","multilingual","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fevents-made-easy-qtranslate-x","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fevents-made-easy-qtranslate-x.1.1.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":27,"avg_patch_time_days":11,"trust_score":36,"computed_at":37},"johnclause",2,8030,84,"2026-04-04T14:05:47.847Z",[39,54,77,92,110],{"slug":40,"name":41,"version":42,"author":7,"author_profile":8,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":17,"requires_php":18,"tags":51,"homepage":52,"download_link":53,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"js-composer-qtranslate-x","WPBakery Visual Composer & qTranslate-X","1.0","\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",[20,21,22,23,24],"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjs-composer-qtranslate-x","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjs-composer-qtranslate-x.1.0.zip",{"slug":55,"name":56,"version":57,"author":58,"author_profile":59,"description":60,"short_description":61,"active_installs":62,"downloaded":63,"rating":64,"num_ratings":65,"last_updated":66,"tested_up_to":67,"requires_at_least":68,"requires_php":69,"tags":70,"homepage":72,"download_link":73,"security_score":74,"vuln_count":75,"unpatched_count":28,"last_vuln_date":76,"fetched_at":30},"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",[21,22,23,24,71],"translation","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Floco-translate\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Floco-translate.2.8.3.zip",95,4,"2026-03-30 15:35:09",{"slug":78,"name":79,"version":80,"author":81,"author_profile":82,"description":83,"short_description":84,"active_installs":28,"downloaded":85,"rating":28,"num_ratings":28,"last_updated":18,"tested_up_to":86,"requires_at_least":87,"requires_php":69,"tags":88,"homepage":89,"download_link":90,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":91},"frenglish-translations","Frenglish Translations","1.1.75","vivcheung","https:\u002F\u002Fprofiles.wordpress.org\u002Fvivcheung\u002F","\u003Cp>Frenglish provides a seamless way to translate your WordPress content into multiple languages. It integrates with your existing WordPress setup and provides an intuitive interface for managing translations.\u003C\u002Fp>\n\u003Cp>Key Features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Automatic language detection\u003C\u002Fli>\n\u003Cli>URL-based language switching\u003C\u002Fli>\n\u003Cli>Support for multiple languages\u003C\u002Fli>\n\u003Cli>Easy-to-use admin interface\u003C\u002Fli>\n\u003Cli>SEO-friendly URLs\u003C\u002Fli>\n\u003Cli>Compatible with most WordPress themes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Privacy Policy\u003C\u002Fh3>\n\u003Cp>Frenglish uses an external API service for translations. Visit frenglish.ai for additional information\u003C\u002Fp>\n","Frenglish is a translation plugin that enables multilingual content on your WordPress site with an easy-to-use interface.",1960,"6.8.5","5.0",[21,22,23,24,71],"https:\u002F\u002Fwww.frenglish.ai","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffrenglish-translations.1.1.75.zip","2026-03-15T14:44:11.924Z",{"slug":93,"name":94,"version":95,"author":96,"author_profile":97,"description":98,"short_description":99,"active_installs":100,"downloaded":101,"rating":13,"num_ratings":14,"last_updated":102,"tested_up_to":103,"requires_at_least":104,"requires_php":18,"tags":105,"homepage":108,"download_link":109,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"qtranslate-meta","qTranslate META","1.0.2","jstar198","https:\u002F\u002Fprofiles.wordpress.org\u002Fjstar198\u002F","\u003Cp>Adds an extra panel to the post\u002Fpage edit page which allows you to enter the META keywords & description for that page in each enabled language. Also adds an optional browser title override (does not affect post title).\u003C\u002Fp>\n\u003Cp>Note 1: This plugin requires that \u003Ca href=\"http:\u002F\u002Fwww.qianqin.de\u002Fqtranslate\u002F\" rel=\"nofollow ugc\">qTranslate\u003C\u002Fa> is installed and activated.\u003C\u002Fp>\n\u003Cp>Note 2: This plugin does not work well with \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fall-in-one-seo-pack\u002F\" rel=\"ugc\">All In One SEO\u003C\u002Fa> and potentially any other plugin or theme which tries to set your META tags.\u003C\u002Fp>\n\u003Ch4>Thanks\u003C\u002Fh4>\n\u003Cp>I’d like to thank the following people for their contributions (in chronological order):\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Victor Berchet — Help with initial localisation; French translation\u003C\u002Fli>\n\u003Cli>Benoit Gauthier — autosave bug fix\u003C\u002Fli>\n\u003Cli>Filippo Pisano — Italian translation\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fpc.de\u002F\" rel=\"nofollow ugc\">Marcis G.\u003C\u002Fa> — Belorussian translation\u003C\u002Fli>\n\u003Cli>Almaz — Russian translation\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fwww.heftrucknederland.nl\u002F\" rel=\"nofollow ugc\">Renate Kramer\u003C\u002Fa> — German translation\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fwpwebshop.com\u002Fblog\u002F\" rel=\"nofollow ugc\">Rene\u003C\u002Fa> — Dutch translation\u003C\u002Fli>\n\u003Cli>banane — Bugs with WordPress 3 compatability.\u003C\u002Fli>\n\u003Cli>Alexander of \u003Ca href=\"http:\u002F\u002Fwebhostinggeeks.com\u002F\" rel=\"nofollow ugc\">Web Hosting Geeks\u003C\u002Fa> — Romanian translation\u003C\u002Fli>\n\u003Cli>Branco Radenovich of \u003Ca href=\"http:\u002F\u002Fwebhostingw.com\u002F\" rel=\"nofollow ugc\">Web Hosting Watch\u003C\u002Fa> — Slovakian translation\u003C\u002Fli>\n\u003C\u002Ful>\n","For users of qTranslate, allows you to set multi-lingual META tags and a \u003Ctitle> override for your posts and pages.",400,32082,"2012-07-18T18:18:00.000Z","3.4.2","2.5",[21,22,106,24,107],"meta","qtranslate","http:\u002F\u002Fjohnjcamilleri.com\u002F2010\u002F01\u002Fqtranslate-and-multilingual-meta-tags\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fqtranslate-meta.zip",{"slug":111,"name":112,"version":113,"author":18,"author_profile":114,"description":115,"short_description":116,"active_installs":13,"downloaded":117,"rating":118,"num_ratings":34,"last_updated":119,"tested_up_to":120,"requires_at_least":121,"requires_php":18,"tags":122,"homepage":125,"download_link":126,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"xlanguage","xLanguage","2.0.4","https:\u002F\u002Fprofiles.wordpress.org\u002Fsam0737\u002F","\u003Cp>If your want to present your blog in different languages (totally with title, rss, categories working, not just the post) and allows visitors to pick the language they want, this plugin is for you.\u003C\u002Fp>\n\u003Cp>xLanguage is a full featured plugin allows you to blog in different language, and allows user to select which version to read.  It works for blog post, page, tags, categories.  The user language preferences will also select the right theme and plugins MO files.\u003C\u002Fp>\n\u003Cp>Customization is the No. 1 design goal, after all that’s probably the reason why you want to setup a multilingual blog.   The language configuration combination is highly customizable to facilitate multiple fallbacks.  Every UI is extracted out, which could be optionally overridden by theme design without touching the plugin file at all.\u003C\u002Fp>\n\u003Cp>The language preference is detected from browser’s preferences, as well as from Cookie if user visited before. Widget and template functions are also provided to allow user to switch the language easily. The presentation of the template functions can also be customized in your theme folder without touching the code in the plugins.\u003C\u002Fp>\n\u003Cp>See \u003Ccode>Other Notes\u003C\u002Fcode> for the comparisons against similar plugins.\u003C\u002Fp>\n\u003Ch4>Feature Highlights\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Does not touch the WordPress database schema at all. All language text are stored in the same post and hence more friendly to other plugins.\u003C\u002Fli>\n\u003Cli>For post that written in reader’s foreign language. You could hide them, or optionally show them with a notice prepended. Your choice!\u003C\u002Fli>\n\u003Cli>Optionally present a total independent view to the search engine crawlers. So that you can have all languages text being crawled under a single URL. Think of SEO!\u003C\u002Fli>\n\u003Cli>Each language can be presented in a different theme.\u003C\u002Fli>\n\u003Cli>Language composing are done in inline instead of separated side by side posting, see Screenshot 1. The former is like Simplified\u002FTraditional Chinese within Wikipedia-ZH, while latter is like Wikipedia-Zh and -EN version.\u003C\u002Fli>\n\u003Cli>Many-to-many mappings between viewable language and authoring language is possible. Hong Kong-based reader could read Cantonese and Chinese, but average Chinese reader could only read Chinese, xLanguage specifically enables this scenario!\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Usage Guide\u003C\u002Fh4>\n\u003Cp>To fully enjoy the power of customization, please refer to the usage guide hosted on my \u003Ca href=\"http:\u002F\u002Fhellosam.net\u002Fproject\u002Fxlanguage\" rel=\"nofollow ugc\">blog project page\u003C\u002Fa>.  Also see my blog for live demostration.\u003C\u002Fp>\n\u003Cp>There are some \u003Ca href=\"http:\u002F\u002Fhellosam.net\u002Fproject\u002Fxlanguage\" rel=\"nofollow ugc\">known problems and limitations\u003C\u002Fa>, please make sure you are aware of those.\u003C\u002Fp>\n\u003Ch4>Change Log\u003C\u002Fh4>\n\u003Cp>Please refer to my \u003Ca href=\"http:\u002F\u002Fhellosam.net\u002Fproject\u002Fxlanguage\" rel=\"nofollow ugc\">blog page\u003C\u002Fa> for recent changes.\u003C\u002Fp>\n\u003Ch4>Upgrade Notice\u003C\u002Fh4>\n\u003Cp>Permalinks \u003Ccode>Postfix\u003C\u002Fcode> appending position is known to be not working with WordPress 2.7 paged comments mode and potentially causing conflicts with many other plugins.  The mode will be changed to \u003Ccode>Prefix\u003C\u002Fcode> when you upgrade from v1.x. If you are using the \u003Ccode>Postfix\u003C\u002Fcode> mode and want to keep using it, please change the settings manually.\u003C\u002Fp>\n\u003Ch3>Comparisons\u003C\u002Fh3>\n\u003Ch4>Compare to qTranslate v2.0.2 (Jan 2009)\u003C\u002Fh4>\n\u003Cp>The logic behind qTranslate is similar to that of xLanguage – both using HTML tag to differentiate the contents of languages and requires no database modification. qTranslate uses HTML comment tag while xLanguage uses the lang=”..” attribute.\u003C\u002Fp>\n\u003Cp>The major differences lie within the admin interface, qTranslate provides strong Admin UI integration such that user enters the title, the category name and so on in independent textbox. The post is also to be post to an independent editor. While xLanguage, user enters the data in the same input box. For authoring in language that are very similar (like Cantonese and Written Chinese), and that cross-authoring is common, the method that xLanguage use will reduce much duplication work.\u003C\u002Fp>\n\u003Cp>Due to the above restriction, qTranslate supports only one-to-one mapping between authoring and viewable lanugage. while xLanguage does not have this restriction. And hence, xLanguage allows all texts to be presented under one single URL for search engine to crawl with. (Think of SEO)\u003C\u002Fp>\n\u003Cp>Feature-wise, xLanguage currently lacks of Pre-domain URL Permalinks mode, as well as automatic MO file download. (Note: MO does work in xLanguage but just have to be downloaded manually). Contribution would certainly help in accelerate these getting done :).\u003C\u002Fp>\n\u003Ch4>Compare to Gengo v2.5.3 (Jan 2009)\u003C\u002Fh4>\n\u003Cp>Gengo v2.5.3 is not tested with WordPress 2.7 according to the published plugin info.\u003C\u002Fp>\n\u003Cp>In Gengo, each translations is a standalone post, linked to the original post.  It enables you to create maps between different content.  Think of different language version of Wikipedia, basically Gengo is the same – and it helps you to maintain such link table.\u003C\u002Fp>\n\u003Cp>In xLanguage, everything is in the same post.  The xLanguage approaches make no structural changes to the WordPress itself, and hence should be easier maintain.  No extra magic in xLanguage is needed to keep the commenting, searching, popularity counter works.\u003C\u002Fp>\n\u003Ch4>Compare to Language Switcher v1.11 (Jan 2008)\u003C\u002Fh4>\n\u003Cp>This is actually the plugin that inspired me to build the xLanguage.  The Language Switcher and the xLanguage is working in a very similar way — Both enable multilingual post by tagging the it.  The Language Switcher uses square bracket instead of HTML tag, but have no assisting tools when composing the post.  The language code is limited to the length of 2, and offer no fallbacking and overlapping possibility.  The permalink url tag must be placed at the end.\u003C\u002Fp>\n\u003Cp>Same as xLanguage, it allows user to enable multilingual functionality on single line content like tag, title and such.\u003C\u002Fp>\n\u003Ch4>Compare to jLanguage v1.4 (Jan 2008)\u003C\u002Fh4>\n\u003Cp>Almost the same as Language Switcher, both functionality and working principle.  However, jLanguage v1.4 does not have widget for user to select their favorite language.  In addition, It currently offer almost no customization, plus it does not work for single line content.  The language selection could not affect the MO file selection.\u003C\u002Fp>\n\u003Cp>It enables the language tagging by using square brakets instead of standard tag, similar to that of Language Switcher.\u003C\u002Fp>\n\u003Ch4>Compare to Multilingual post v0.2 (Jan 2008)\u003C\u002Fh4>\n\u003Cp>Please be aware that Multilingual post v0.2 does not belong to this category at all.  It does not enable poster to publish mixed language in a post.  The user also cannot selectively view the post in a particular language.\u003C\u002Fp>\n\u003Cp>It only does insert the lang=”..” tag at the HEAD such that browser can render the page better.  xLanguage also does this.\u003C\u002Fp>\n\u003Ch4>Compare to Bunny’s Language Linker v0.2 (Jan 2008)\u003C\u002Fh4>\n\u003Cp>Bunny’s Language Linker’s way to enable multilanguage blog is minimal and simple, yet the integration is very loose.  It works like Gengo, the pros and cons compare to xLanguage is very similar.\u003C\u002Fp>\n\u003Ch4>Compare to Basic Bilingual v0.31 (Jan 2008)\u003C\u002Fh4>\n\u003Cp>Basic Bilingual v0.31 allows you to insert a summaries in a different language.  It is yet another very simple plugin.\u003C\u002Fp>\n","Allows you to blog in multi-language, and users to select which to read.  Works on every blog UI elements, not just the post.",79003,80,"2009-06-09T17:40:00.000Z","2.7.1","2.3.2",[123,22,23,124,24],"babel","multilanguage","http:\u002F\u002Fhellosam.net\u002Fproject\u002Fxlanguage","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fxlanguage.zip",{"attackSurface":128,"codeSignals":150,"taintFlows":157,"riskAssessment":158,"analyzedAt":165},{"hooks":129,"ajaxHandlers":146,"restRoutes":147,"shortcodes":148,"cronEvents":149,"entryPointCount":28,"unprotectedCount":28},[130,136,141],{"type":131,"name":132,"callback":133,"file":134,"line":135},"filter","qtranslate_compatibility","qeme_qtrans_compatibility","events-made-easy-qtranslate-x.php",17,{"type":137,"name":138,"callback":139,"file":134,"line":140},"action","qtranslate_init_language","qeme_init_language",28,{"type":131,"name":142,"callback":143,"file":144,"line":145},"qtranslate_load_admin_page_config","qeme_add_admin_page_config","qeme-admin.php",10,[],[],[],[],{"dangerousFunctions":151,"sqlUsage":152,"outputEscaping":154,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":156},[],{"prepared":28,"raw":28,"locations":153},[],{"escaped":28,"rawEcho":28,"locations":155},[],[],[],{"summary":159,"deductions":160},"The static analysis of the \"events-made-easy-qtranslate-x\" v1.1 plugin reveals an exceptionally clean codebase in terms of common vulnerability vectors. There are no identified AJAX handlers, REST API routes, shortcodes, cron events, dangerous functions, raw SQL queries, unescaped output, file operations, external HTTP requests, or missing nonce\u002Fcapability checks. The taint analysis also found no critical or high severity flows, indicating that user-supplied data is not being processed in a way that could lead to exploitation based on this analysis.\n\nThe plugin's vulnerability history is also clear, with no recorded CVEs. This suggests a strong track record of security or potentially limited scrutiny. However, the complete absence of certain security mechanisms like nonce checks, capability checks, and proper authorization on entry points, while yielding zero findings in the static analysis, is a significant concern. It implies that if any vulnerabilities were to arise, they could potentially be exploited without requiring authentication or user interaction that would typically be protected by these checks.\n\nIn conclusion, while the code is remarkably free of known vulnerabilities and follows good practices for SQL and output sanitization, the lack of foundational security checks on its attack surface (even if currently empty) represents a theoretical risk. A more comprehensive security posture would involve implementing these checks to prevent future issues, even if none are currently apparent.",[161,163],{"reason":162,"points":145},"No capability checks on entry points",{"reason":164,"points":145},"No nonce checks on entry points","2026-03-16T22:23:46.680Z",{"wat":167,"direct":174},{"assetPaths":168,"generatorPatterns":170,"scriptPaths":171,"versionParams":172},[169],"\u002Fwp-content\u002Fplugins\u002Fevents-made-easy-qtranslate-x\u002F",[],[],[173],"events-made-easy-qtranslate-x\u002Fevents-made-easy-qtranslate-x.php?ver=1.1",{"cssClasses":175,"htmlComments":176,"htmlAttributes":177,"restEndpoints":178,"jsGlobals":179,"shortcodeOutput":180},[],[],[],[],[],[]]