[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$flvhfNM6gRZGmI8dWFgr8yQjS7rg_h7a1N_sCGA1qewQ":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":35,"analysis":126,"fingerprints":198},"language-code","Language Code Classification","0.1.3 Beta","sillinguist","https:\u002F\u002Fprofiles.wordpress.org\u002Fsillinguist\u002F","\u003Cp>This plugin is designed to allow a WordPress user to add an ISO 639-3 language code to in a custom field related to their post so that their posts can be organized by ISO 639-3 code. One advantage of this would be to list their WordPress install as a language resource with \u003Ca href=\"http:\u002F\u002Fwww.language-archives.org\u002F\" title=\"OLAC: Open Language Archives Community\" rel=\"nofollow ugc\">OLAC\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Known bugs and\u002For conflicts\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>version 0.1.3 \u003Cstrong>None\u003C\u002Fstrong>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>version 0.1.2-beta  plugin folder needs to be renamed to langauge_code this is corrected in version 0.1.3\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Development Plan\u003C\u002Fh3>\n\u003Cp>0.1.4: IN PROGRESS\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>It would be nice to add the functionality to the plugin to allow an author to replace or insert any text field with the one auto suggesting language codes, by calling a function. It should probably have syntax or form after the order of: place \u003Ccode>\u003C?php do_action('plugin_name_hook'); ?>\u003C\u002Fcode> in the templates\u002Fwidget\u002F. The end result for the user would be that they could create a meta-data input from more than just the admin area (i.e. a from in another plugin, like a form creator, or the front end of WP.)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Need to Validate input against table (instead of writing straight to the DB, write to cache, validate and then to DB) e.g. what if someone types in ‘zzz’ and ‘zzz’ is not a language code?\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Add multiple codes to a post dynamically e.g. (I have a data file with 2 languages connected to one post, but not every post.)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Translation file (A \u003Ccode>.po\u003C\u002Fcode> file This is a two fold issue Language names are different in different languages i.e. Deutsch, German, Allemand. This might be a table being developed by another part of the ISO 639 standard. Possibly, 639-6 See this wikipedia article \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FISO_639-6\" title=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FISO_639-6\" rel=\"nofollow ugc\">http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FISO_639-6\u003C\u002Fa>)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Add hook for disply in theme per key\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because each of the ISO 639-3 codes are stored in a custom field, and each custom field has two parts, a key and a value, It is necessary to be able to set the key as well as the value (and the default key). The Plug-in in its current state has only focused on adding the value part of the key-value pair. It is important for developers to know that a single post should be able to have more than one key with language codes in them. For example, if I have a post which is a linguistics exercise in phonology, then I might want to put the language of the instructions of the exercise in one key and the language code of the exercise data in another key.\u003C\u002Fp>\n\u003Cp>An entirely different scenario is one where a post has two languages under one key. This is currently unaccounted for with the current state of the plug-in. E.g. If in the body of a post an author were to use two languages equally then they might want to use the same key to represent both languages.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Promote at Weblog Tools Collection\u003C\u002Fli>\n\u003Cli>Promote Using Social Networking\u003C\u002Fli>\n\u003Cli>Promote On Your Own Blog\n\u003Cul>\n\u003Cli>The download location.\u003C\u002Fli>\n\u003Cli>A list of features.\u003C\u002Fli>\n\u003Cli>Contact or support information (or comments enabled)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>0.1.5:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Auto detect and import of SIL’s tab file when SIL updates their tab file at: \u003Ca href=\"http:\u002F\u002Fwww.sil.org\u002FISO639-3\u002Fiso-639-3_20090210.tab\" title=\"http:\u002F\u002Fwww.sil.org\u002FISO639-3\u002Fiso-639-3_20090210.tab\" rel=\"nofollow ugc\">http:\u002F\u002Fwww.sil.org\u002FISO639-3\u002Fiso-639-3_20090210.tab\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Update notice to the user so that they know to update their plug-in every year when SIL updates their ISO changes. Or decide to follow a regular release cycle (at least annually) and maintenance with this plugin.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>pursue use of ISO 639-3 in conjunction with the doublin core metadata standard\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Doublin Core metadata plugin\n\u003Cul>\n\u003Cli>http:\u002F\u002Fwww.brainonfire.net\u002Fblog\u002Fadd-dublin-core-metadata-to-wordpress\u002F\u003C\u002Fli>\n\u003Cli>http:\u002F\u002Fwww.brainonfire.net\u002Fresources\u002Ffiles\u002Fdublin-core-for-wordpress\u002F\u003C\u002Fli>\n\u003Cli>http:\u002F\u002Fdublincore.org\u002Fdocuments\u002Fdcmi-terms\u002F\u003C\u002Fli>\n\u003Cli>http:\u002F\u002Fdublincore.org\u002Fdocuments\u002Fdcmi-terms\u002F#ses-ISO639-3\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>2.0 :\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Consider development beyond ISO 639-3 to ISO 639.\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin adds the ability to add an ISO 639-3 language code to the custom field of a post.",10,2574,0,"2010-01-01T18:30:00.000Z","2.9.2","2.7","",[19,20,21,22,23],"custom-field","language","library","linguistics","metadata","http:\u002F\u002FURI_Of_Page_Describing_Plugin_and_Updates","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flanguage-code.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":32,"trust_score":33,"computed_at":34},1,30,84,"2026-04-04T13:04:39.923Z",[36,61,75,87,110],{"slug":37,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":57,"download_link":58,"security_score":59,"vuln_count":31,"unpatched_count":13,"last_vuln_date":60,"fetched_at":28},"jsm-show-post-meta","JSM Show Post Metadata","4.8.0","JS Morisset","https:\u002F\u002Fprofiles.wordpress.org\u002Fjsmoriss\u002F","\u003Cp>The JSM Show Post Metadata plugin displays post (ie. posts, pages, and custom post types) meta keys (aka custom field names) and unserialized values in a metabox at the bottom of the post editing page.\u003C\u002Fp>\n\u003Cp>Note that if you’re using WooCommerce HPOS (High-Performance Order Storage), available since WooCommerce v8.2, then your WooCommerce orders are NOT post objects and you should use the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-order-meta\u002F\" rel=\"ugc\">JSM Show Order Metadata\u003C\u002Fa> plugin instead.\u003C\u002Fp>\n\u003Cp>There are no plugin settings – simply install and activate the plugin.\u003C\u002Fp>\n\u003Ch4>Available Filters for Developers\u003C\u002Fh4>\n\u003Cp>Filter the post meta shown in the metabox:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmspm_metabox_table_metadata' ( array $metadata, $post_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Array of regular expressions to exclude meta keys:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmspm_metabox_table_exclude_keys' ( array $exclude_keys, $post_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Capability required to show post meta:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmspm_show_metabox_capability' ( 'manage_options', $post_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Show post meta for a post type (defaults to true):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmspm_show_metabox_post_type' ( true, $post_type )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Capability required to delete post meta:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmspm_delete_meta_capability' ( 'manage_options', $post_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Icon for the delete post meta button:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmspm_delete_meta_icon_class' ( 'dashicons dashicons-table-row-delete' )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Related Plugins\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-comment-meta\u002F\" rel=\"ugc\">JSM Show Comment Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-order-meta\u002F\" rel=\"ugc\">JSM Show Order Metadata for WooCommerce HPOS\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-post-meta\u002F\" rel=\"ugc\">JSM Show Post Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-term-meta\u002F\" rel=\"ugc\">JSM Show Term Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-user-meta\u002F\" rel=\"ugc\">JSM Show User Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-registered-shortcodes\u002F\" rel=\"ugc\">JSM Show Registered Shortcodes\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Show post metadata (aka custom fields) in a metabox when editing posts \u002F pages - a great tool for debugging issues with post metadata.",10000,250292,100,12,"2026-03-11T18:09:00.000Z","6.9.4","6.0","7.4.33",[53,54,23,55,56],"custom-fields","inspector","post-types","posts","https:\u002F\u002Fsurniaulula.com\u002Fextend\u002Fplugins\u002Fjsm-show-post-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjsm-show-post-meta.4.8.0.zip",99,"2025-01-24 00:00:00",{"slug":62,"name":63,"version":39,"author":40,"author_profile":41,"description":64,"short_description":65,"active_installs":66,"downloaded":67,"rating":46,"num_ratings":68,"last_updated":69,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":70,"homepage":73,"download_link":74,"security_score":46,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"jsm-show-user-meta","JSM Show User Metadata","\u003Cp>The JSM Show User Metadata plugin displays user profile meta keys and unserialized values in a metabox at the bottom of the user profile editing page.\u003C\u002Fp>\n\u003Cp>There are no plugin settings – simply install and activate the plugin.\u003C\u002Fp>\n\u003Ch4>Available Filters for Developers\u003C\u002Fh4>\n\u003Cp>Filter the user meta shown in the metabox:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsum_metabox_table_metadata' ( array $metadata, $user_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Array of regular expressions to exclude meta keys:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsum_metabox_table_exclude_keys' ( array $exclude_keys, $user_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Capability required to show user meta:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsum_show_metabox_capability' ( 'manage_options', $user_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Show user meta for a screen base (defaults to true):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsum_show_metabox_screen_base' ( true, $screen_base )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Capability required to delete user meta:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsum_delete_meta_capability' ( 'manage_options', $user_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Icon for the delete user meta button:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsum_delete_meta_icon_class' ( 'dashicons dashicons-table-row-delete' )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Related Plugins\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-comment-meta\u002F\" rel=\"ugc\">JSM Show Comment Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-order-meta\u002F\" rel=\"ugc\">JSM Show Order Metadata for WooCommerce HPOS\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-post-meta\u002F\" rel=\"ugc\">JSM Show Post Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-term-meta\u002F\" rel=\"ugc\">JSM Show Term Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-user-meta\u002F\" rel=\"ugc\">JSM Show User Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-registered-shortcodes\u002F\" rel=\"ugc\">JSM Show Registered Shortcodes\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Show user metadata in a metabox when editing users - a great tool for debugging issues with user metadata.",3000,95927,2,"2026-03-11T18:12:00.000Z",[53,54,23,71,72],"profile","users","https:\u002F\u002Fsurniaulula.com\u002Fextend\u002Fplugins\u002Fjsm-show-user-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjsm-show-user-meta.4.8.0.zip",{"slug":76,"name":77,"version":39,"author":40,"author_profile":41,"description":78,"short_description":79,"active_installs":80,"downloaded":81,"rating":46,"num_ratings":68,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":82,"homepage":85,"download_link":86,"security_score":46,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"jsm-show-order-meta","JSM Show Order Metadata for WooCommerce HPOS","\u003Cp>The JSM Show Order Metadata for WooCommerce HPOS plugin displays order meta keys and unserialized values in a metabox at the bottom of the WooCommerce HPOS order and WooCommerce Subscriptions editing pages.\u003C\u002Fp>\n\u003Cp>Note that if you’re NOT using WooCommerce HPOS (High-Performance Order Storage), available since WooCommerce v8.2, then your WooCommerce orders are post objects and you should use the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-post-meta\u002F\" rel=\"ugc\">JSM Show Post Metadata\u003C\u002Fa> plugin instead.\u003C\u002Fp>\n\u003Cp>There are no plugin settings – simply install and activate the plugin.\u003C\u002Fp>\n\u003Ch4>Available Filters for Developers\u003C\u002Fh4>\n\u003Cp>Filter the order meta shown in the metabox:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsom_metabox_post_types' ( array $post_types )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Array of supported HPOS post types (i.e. ‘woocommerce_page_wc-orders’ and ‘woocommerce_page_wc-orders–shop_subscription’).\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsom_metabox_table_metadata' ( array $metadata, $order_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Array of regular expressions to exclude meta keys:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsom_metabox_table_exclude_keys' ( array $exclude_keys, $order_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Capability required to show order meta:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsom_show_metabox_capability' ( 'manage_options', $order_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Capability required to delete order meta:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsom_delete_meta_capability' ( 'manage_options', $order_obj )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Icon for the delete order meta button:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>'jsmsom_delete_meta_icon_class' ( 'dashicons dashicons-table-row-delete' )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Related Plugins\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-comment-meta\u002F\" rel=\"ugc\">JSM Show Comment Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-order-meta\u002F\" rel=\"ugc\">JSM Show Order Metadata for WooCommerce HPOS\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-post-meta\u002F\" rel=\"ugc\">JSM Show Post Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-term-meta\u002F\" rel=\"ugc\">JSM Show Term Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-user-meta\u002F\" rel=\"ugc\">JSM Show User Metadata\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fjsm-show-registered-shortcodes\u002F\" rel=\"ugc\">JSM Show Registered Shortcodes\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Show WooCommerce order metadata in a metabox when editing HPOS orders - a great tool for debugging issues with HPOS order metadata.",700,6714,[53,54,23,83,84],"orders","woocommerce","https:\u002F\u002Fsurniaulula.com\u002Fextend\u002Fplugins\u002Fjsm-show-order-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjsm-show-order-meta.4.8.0.zip",{"slug":88,"name":89,"version":90,"author":91,"author_profile":92,"description":93,"short_description":94,"active_installs":95,"downloaded":96,"rating":97,"num_ratings":98,"last_updated":99,"tested_up_to":100,"requires_at_least":101,"requires_php":17,"tags":102,"homepage":108,"download_link":109,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"acf-real-media-library-field","Advanced Custom Fields: Real Media Library Folder Field","1.1.4","Matthias Günter","https:\u002F\u002Fprofiles.wordpress.org\u002Fmguenter\u002F","\u003Cp>The plugin adds a custom field to select a folder of the \u003Ca href=\"https:\u002F\u002Fdevowl.io\u002Fwordpress-real-media-library\u002F\" rel=\"nofollow ugc\">Real Media Library\u003C\u002Fa> in a field group of Advanced Custom Fields (ACF).\u003C\u002Fp>\n\u003Cp>You can configure this field type with the following parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Disable selection: Allows you to disable some folder types for selection (for example, no collections).\u003C\u002Fli>\n\u003Cli>Return format: Get Real Media Library folder object or folder ID.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cp>This plugin is an add-on that allows you to use the following plugins together, which must be installed:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadvanced-custom-fields\u002F\" rel=\"ugc\">Advanced Custom Fields (ACF)\u003C\u002Fa> (Free or PRO, version 4.x or 5.x)\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdevowl.io\u002Fgo\u002Fcodecanyon\u002Freal-media-library?source=acf-rml-folder-field-wordpress-org\" rel=\"nofollow ugc\">Real Media Library\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Thanks to \u003Ca href=\"http:\u002F\u002Fwww.theimageyard.co.uk\u002F\" rel=\"nofollow ugc\">Jon Dennis\u003C\u002Fa> who started the development of this add-on.\u003C\u002Fp>\n\u003Cp>\u003Cem>This plugin is a free micro add-on for Real Media Library with limited support.\u003C\u002Fem>\u003C\u002Fp>\n","Media library folder field for Advanced Custom Fields (ACF). Folder created by Real Media Library.",200,9789,74,3,"2020-04-03T17:37:00.000Z","5.4.19","4.0",[103,104,105,106,107],"acf","advanced-custom-fields","folder-field","media-library-folders","real-media-library","https:\u002F\u002Fdevowl.io\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facf-real-media-library-field.zip",{"slug":111,"name":112,"version":113,"author":114,"author_profile":115,"description":116,"short_description":117,"active_installs":46,"downloaded":118,"rating":13,"num_ratings":13,"last_updated":119,"tested_up_to":120,"requires_at_least":101,"requires_php":17,"tags":121,"homepage":124,"download_link":125,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"advanced-custom-fields-wpml-language-selector","Advanced Custom Fields: WPML Language Selector Field","1.2.1","Ivan Paulin","https:\u002F\u002Fprofiles.wordpress.org\u002Fivan_paulin\u002F","\u003Cp>Custom field addon for Advanced Custom Fields plugin which provides a list of used WPML languages on website.\u003Cbr \u002F>\nPossibility to have multiple choices, or just one.\u003C\u002Fp>\n\u003Cp>It will not work if WPML plugin is not activated.\u003C\u002Fp>\n\u003Cp>Return type is array which holds the language code(it, en, fr, de, etc..).\u003C\u002Fp>\n\u003Ch4>Compatibility\u003C\u002Fh4>\n\u003Cp>This ACF field type is compatible with:\u003Cbr \u002F>\n* ACF 4\u003Cbr \u002F>\n* ACF 5\u003C\u002Fp>\n","Custom field addon for Advanced Custom Fields plugin which provides a list of used WPML languages on website.",3085,"2016-01-25T22:14:00.000Z","4.4.34",[103,19,20,122,123],"language-select","wpml","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadvanced-custom-fields-wpml-language-selector\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadvanced-custom-fields-wpml-language-selector.zip",{"attackSurface":127,"codeSignals":160,"taintFlows":188,"riskAssessment":189,"analyzedAt":197},{"hooks":128,"ajaxHandlers":156,"restRoutes":157,"shortcodes":158,"cronEvents":159,"entryPointCount":13,"unprotectedCount":13},[129,135,140,143,147,151],{"type":130,"name":131,"callback":132,"file":133,"line":134},"filter","the_content","print_language_code","language-code.php",78,{"type":136,"name":137,"callback":138,"file":133,"line":139},"action","admin_menu","language_code_add_custom_box",81,{"type":136,"name":141,"callback":142,"file":133,"line":33},"save_post","language_code_save_postdata",{"type":136,"name":144,"callback":145,"file":133,"line":146},"init","language_code_lib_javascript_autocompleter",161,{"type":136,"name":148,"callback":149,"file":133,"line":150},"wp_head","language_code_css_autocompleter",170,{"type":136,"name":152,"callback":153,"priority":154,"file":133,"line":155},"admin_head","language_code_javascript_autocompleter",1000,196,[],[],[],[],{"dangerousFunctions":161,"sqlUsage":162,"outputEscaping":176,"fileOperations":31,"externalRequests":13,"nonceChecks":31,"capabilityChecks":68,"bundledLibraries":187},[],{"prepared":163,"raw":164,"locations":165},5,4,[166,169,171,173],{"file":133,"line":167,"context":168},17,"$wpdb->get_var() with variable interpolation",{"file":133,"line":170,"context":168},60,{"file":133,"line":172,"context":168},101,{"file":174,"line":175,"context":168},"values.php",22,{"escaped":13,"rawEcho":164,"locations":177},[178,181,183,185],{"file":133,"line":179,"context":180},105,"raw output",{"file":133,"line":182,"context":180},120,{"file":133,"line":184,"context":180},121,{"file":174,"line":186,"context":180},28,[],[],{"summary":190,"deductions":191},"The \"language-code\" plugin v0.1.3 Beta exhibits a generally good security posture based on the provided static analysis.  The plugin has no recorded vulnerabilities, which is a positive indicator.  Furthermore, the attack surface is reported as zero, meaning there are no obvious entry points like AJAX handlers, REST API routes, shortcodes, or cron events that could be directly exploited.  The presence of nonce and capability checks, along with a reasonable proportion of SQL queries using prepared statements, also suggests some level of security awareness in its development.\n\nHowever, there are significant concerns that temper this positive outlook.  A striking 100% of output escaping is missing. This is a critical flaw as it opens the door to Cross-Site Scripting (XSS) vulnerabilities, where user-supplied data could be injected into the webpage and executed by other users' browsers.  While taint analysis did not reveal any flows, the lack of output escaping means that any data that *does* flow into the output functions is potentially dangerous. The presence of file operations also warrants caution, especially without further context on their nature and any associated validation or sanitization.\n\nIn conclusion, while the plugin has a clean vulnerability history and a small attack surface, the complete lack of output escaping presents a high-risk scenario for XSS vulnerabilities. The file operation also needs further scrutiny.  Developers should prioritize addressing the output escaping issues to mitigate these significant risks.",[192,195],{"reason":193,"points":194},"100% of output escaping is missing",15,{"reason":196,"points":98},"File operations present","2026-03-17T00:40:49.875Z",{"wat":199,"direct":207},{"assetPaths":200,"generatorPatterns":203,"scriptPaths":204,"versionParams":205},[201,202],"\u002Fwp-content\u002Fplugins\u002Flanguage-code\u002Fautocompleter.css","\u002Fwp-content\u002Fplugins\u002Flanguage-code\u002Fjquery.autocomplete.js",[],[202],[206],"language-code\u002Fjquery.autocomplete.js?ver=1.0",{"cssClasses":208,"htmlComments":209,"htmlAttributes":210,"restEndpoints":211,"jsGlobals":212,"shortcodeOutput":213},[],[],[],[],[],[214],"\u003Cp id='lanuage_code'>\u003Cstrong>Language:\u003C\u002Fstrong>"]