[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fpF_bR5LE0RNnEtPlgQlUJnfdReVLb9esc2SMF8UG9-Q":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":40,"analysis":134,"fingerprints":168},"abbreviation-button-for-the-block-editor","Abbreviation Button for the Block Editor","0.1","Jb Audras","https:\u002F\u002Fprofiles.wordpress.org\u002Faudrasjb\u002F","\u003Cp>The goal of this plugin is to provide expansions or definitions for abbreviations by using the \u003Ccode>abbr\u003C\u002Fcode> HTML element. It helps to make your website compliant to the \u003Ca href=\"https:\u002F\u002Fwww.w3.org\u002FWAI\u002FWCAG21\u002FUnderstanding\u002Fabbreviations.html\" rel=\"nofollow ugc\">success criterion 3.1.4 of Web Content Accessibility Guidelines (WCAG)\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>It is always appropriate to use the \u003Ccode>abbr\u003C\u002Fcode> element for any abbreviation, including acronyms and initialisms. This HTML element helps to make sure the abbreviation is understood by assistive technologies, by informing the user agent that the characters are an abbreviation, and by providing its meaning using the \u003Ccode>title\u003C\u002Fcode> attribute.\u003C\u002Fp>\n\u003Cp>This plugin adds a new \u003Ccode>abr\u003C\u002Fcode> format button in the formatting toolbar of the block editor.\u003C\u002Fp>\n","Add an abbreviation format button to the formatting toolbar in the block editor.",200,9784,94,3,"2025-11-27T08:46:00.000Z","6.9.4","5.9","7.0",[20,21,22,23,24],"abbreviation","accessibility","acronym","block-editor","lang","https:\u002F\u002Fwhodunit.fr\u002Fgestion-des-abreviations-pour-lediteur-de-blocs-gutenberg","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fabbreviation-button-for-the-block-editor.0.1.zip",100,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":36,"avg_patch_time_days":37,"trust_score":38,"computed_at":39},"audrasjb",24,63620,98,661,78,"2026-04-04T04:25:10.379Z",[41,53,70,95,115],{"slug":42,"name":43,"version":44,"author":7,"author_profile":8,"description":45,"short_description":46,"active_installs":27,"downloaded":47,"rating":13,"num_ratings":14,"last_updated":48,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":49,"homepage":51,"download_link":52,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"lang-attribute","Lang Attribute for the Block Editor","0.3","\u003Cp>\u003Cstrong>Disclaimer: This plugin was merged into WordPress Core. It is not relevant anymore to install it. I plan to ask for a removal from the repo by the end of the year.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The intent of this plugin is to provide a way to ensure any language change in the content of a page is indicated to assistive technologies. This feature is not available by default in the block editor so it is difficult to make a website fully compliant to WCAG guidelines using the block editor for now.\u003C\u002Fp>\n\u003Cp>We clearly hope this feature will be natively implemented in the block editor in middle term, because this very simple feature is really needed to help people to create accessible websites. But in short terms, we need a solution and this plugin is a solution you may want to use to make your website compliant to accessibility guidelines 🙂\u003C\u002Fp>\n\u003Cp>For more context: this plugin helps you to make your website compliant to the Web Content Accessibility Guidelines (WCAG) success criterion 3.1.2: “Language of Parts”. The purpose of this success Criterion is to ensure that user agents can correctly present content written in multiple languages.\u003C\u002Fp>\n\u003Cp>As per Web Content Accessibility Guidelines:\u003C\u002Fp>\n\u003Cp>This makes it possible for user agents and assistive technologies to present content according to the presentation and pronunciation rules for that language. This applies to graphical browsers as well as screen readers, braille displays, and other voice browsers.\u003C\u002Fp>\n\u003Cp>Both assistive technologies and conventional user agents can render text more accurately if the language of each passage of text is identified. Screen readers can use the pronunciation rules of the language of the text. Visual browsers can display characters and scripts in appropriate ways.\u003C\u002Fp>\n\u003Cp>This is especially important when switching between languages that read from left to right and languages that read from right to left, or when text is rendered in a language that uses a different alphabet. Users with disabilities who know all the languages used in the Web page will be better able to understand the content when each passage is rendered appropriately.\u003C\u002Fp>\n","Add lang attribute to the text formatting toolbar in the block editor.",9607,"2025-11-27T08:53:00.000Z",[21,23,24,50],"language","https:\u002F\u002Fwhodunit.fr\u002Fattribut-lang-pour-gutenberg-plugin","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flang-attribute.0.3.zip",{"slug":54,"name":55,"version":56,"author":57,"author_profile":58,"description":59,"short_description":60,"active_installs":28,"downloaded":61,"rating":27,"num_ratings":62,"last_updated":63,"tested_up_to":18,"requires_at_least":17,"requires_php":64,"tags":65,"homepage":63,"download_link":68,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":69},"lang-attribute-blocks","Language Attribute for Container Blocks and Pages\u002FPosts","3.0","Naked Cat Plugins","https:\u002F\u002Fprofiles.wordpress.org\u002Fnakedcatplugins\u002F","\u003Cp>This plugin aims to ensure that any language change in a page’s content is indicated to assistive technologies at the container block level, helping a website comply with WCAG guidelines.\u003C\u002Fp>\n\u003Cp>This feature is available on the core block editor only at a text formatting level after code from \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Flang-attribute\u002F\" rel=\"ugc\">Jb Audras plugin “Lang Attribute for the Block Editor”\u003C\u002Fa> was merged into core. The objective of this plugin is to provide the same functionality at a container block level (Group – including all its variants, Columns, Cover, and other specific block types) so that the language applies to all child elements, no matter the kind of content inside.\u003C\u002Fp>\n\u003Cp>The plugin also supports setting the language at the page or post level, both on the blocks and classic editor. When an entire page is written in a different language than the website’s default, you can override the HTML \u003Ccode>lang\u003C\u002Fcode> and \u003Ccode>dir\u003C\u002Fcode> attributes for that specific page directly from the Document Settings sidebar, without needing to wrap everything in a container block.\u003C\u002Fp>\n\u003Cp>This plugin is heavily inspired by the Jb Audras plugin (including this readme file). The development started at WordCamp Europe 2025 Contributor Day, by Marco Almeida from \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fnakedcatplugins\u002F\" rel=\"nofollow ugc\">Naked Cat Plugins\u003C\u002Fa> \u002F \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fwebdados\u002F\" rel=\"nofollow ugc\">Webdados\u003C\u002Fa>, and the help from \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Fwelcher\u002F\" rel=\"nofollow ugc\">Ryan Welcher\u003C\u002Fa> on the code side and \u003Ca href=\"https:\u002F\u002Fprofiles.wordpress.org\u002Falh0319\u002F\" rel=\"nofollow ugc\">Amber Hinds\u003C\u002Fa> on the accessibility compliance side.\u003C\u002Fp>\n\u003Cp>For more context: this plugin helps you to make your website compliant with the Web Content Accessibility Guidelines (WCAG) success criteria:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>3.1.1 – Language of Page\u003C\u002Fstrong>: The default human language of each web page can be programmatically determined. Use the page-level setting when an entire page or post is written in a language other than the website’s default.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>3.1.2 – Language of Parts\u003C\u002Fstrong>: The human language of each passage or phrase in the content can be programmatically determined. Use the block-level setting when only specific sections within a page are in a different language.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The purpose of these success criteria is to ensure that user agents can correctly present content written in multiple languages.\u003C\u002Fp>\n\u003Cp>Keep in mind that you should set the \u003Ccode>lang\u003C\u002Fcode> and \u003Ccode>dir\u003C\u002Fcode> attributes only on a container block or page if the content is written in a language different from the one set globally on your website.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>As per Web Content Accessibility Guidelines:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This enables user agents and assistive technologies to present content according to the presentation and pronunciation rules of that language. This applies to graphical browsers, screen readers, braille displays, and other voice browsers.\u003C\u002Fp>\n\u003Cp>Both assistive technologies and conventional user agents can render text more accurately if the language of each passage of text is identified. Screen readers can use the language’s pronunciation rules. Visual browsers can display characters and scripts appropriately.\u003C\u002Fp>\n\u003Cp>This is especially important when switching between languages that read from left to right and languages that read from right to left, or when text is rendered in a language that uses a different alphabet. Users with disabilities who know all the languages used in the Web page will be better able to understand the content when each passage is rendered appropriately.\u003C\u002Fp>\n\u003Cp>That’s not just good for accessibility. It’s also great for SEO. Search engines like Google can better understand your content when languages are clearly defined. That means improved indexing and potentially better rankings.\u003C\u002Fp>\n\u003Cp>Banner photo by \u003Ca href=\"https:\u002F\u002Funsplash.com\u002F@hannahwrightdesigner?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash\" rel=\"nofollow ugc\">Hannah Wright\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Supported block types\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Group\u003C\u002Fstrong> (\u003Ccode>core\u002Fgroup\u003C\u002Fcode>): Group contents together and set a language for them\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Columns\u003C\u002Fstrong> (\u003Ccode>core\u002Fcolumns\u003C\u002Fcode> and \u003Ccode>core\u002Fcolumn\u003C\u002Fcode>): Organize content into a set of columns and set a language for all the columns or a specific column\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cover\u003C\u002Fstrong> (\u003Ccode>core\u002Fcover\u003C\u002Fcode>): Set the language to all the contents inside a cover block\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Navigation\u003C\u002Fstrong> (\u003Ccode>core\u002Fnavigation\u003C\u002Fcode>): Create full navigation menus in different languages\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Submenu\u003C\u002Fstrong> (\u003Ccode>core\u002Fnavigation-submenu\u003C\u002Fcode>): Set a different language on a sub-section of your menu (for example, if you have the default language pages on the first level and a sub-menu with pages in another language)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Page List\u003C\u002Fstrong> (\u003Ccode>core\u002Fpage-list\u003C\u002Fcode>): List all the pages on your website that are written in a different language and created as a child of the main page of that language\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Content\u003C\u002Fstrong> (\u003Ccode>core\u002Fpost-content\u003C\u002Fcode>): Set the post content on a custom template to a different language\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Set the language and text direction for an entire page or post, both on the blocks and classic editor: a “Page Language” panel in the Document Settings sidebar overrides the HTML \u003Ccode>lang\u003C\u002Fcode> and \u003Ccode>dir\u003C\u002Fcode> attributes for that specific page\u003C\u002Fli>\n\u003Cli>Add \u003Ccode>lang\u003C\u002Fcode> and \u003Ccode>dir\u003C\u002Fcode> attributes to Group, Columns, Cover, and other specific WordPress Blocks, mentioned above\u003C\u002Fli>\n\u003Cli>Show visual outline around blocks that have a language attribute set – For easy identification of blocks you have already set to a different language during your editing process, only for Administrators and Editors, and if enabled in Settings – Writing\u003C\u002Fli>\n\u003C\u002Ful>\n","Add lang and dir attributes to Group, Columns, Cover, and other specific WordPress Blocks, or to the whole page\u002Fpost.",612,1,"","7.2",[21,23,66,67,50],"classic-editor","gutenberg","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flang-attribute-blocks.3.0.zip","2026-03-15T10:48:56.248Z",{"slug":71,"name":72,"version":73,"author":74,"author_profile":75,"description":76,"short_description":77,"active_installs":78,"downloaded":79,"rating":80,"num_ratings":81,"last_updated":82,"tested_up_to":83,"requires_at_least":84,"requires_php":63,"tags":85,"homepage":91,"download_link":92,"security_score":93,"vuln_count":62,"unpatched_count":28,"last_vuln_date":94,"fetched_at":30},"text-hover","Text Hover","4.2","Scott Reilly","https:\u002F\u002Fprofiles.wordpress.org\u002Fcoffee2code\u002F","\u003Cp>This plugin allows you to easily define help text that appears when a visitor hovers their mouse over a word or phrase in a post or page.\u003C\u002Fp>\n\u003Cp>Via the plugin’s settings, simply specify the words or phrases that you want to be associated with hover text, and of course, the desired hover texts themselves. The format is quite simple; an example of which is shown here:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>WP => WordPress\nMatt => Matt Mullenweg\nThe Scooby Shack => the bar where the gang hangs out\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Additional features of the plugin controlled both via settings and filters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Hover text can be enabled for comments (it isn’t by default)\u003C\u002Fli>\n\u003Cli>Hover text can be made case insensitive (it is case sensitive by default)\u003C\u002Fli>\n\u003Cli>Hover text can be limited to doing only one replacement per term, per post (by default, all occurrences of a term are given hovertext)\u003C\u002Fli>\n\u003Cli>Hover text can be rendered using the default browser tooltip (by default, the better-looking \u003Ca href=\"http:\u002F\u002Fqtip2.com\u002F\" rel=\"nofollow ugc\">qTip2\u003C\u002Fa> library is used)\u003C\u002Fli>\n\u003Cli>Hover text can be expanded to affect other filters\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> This is not the same as my \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftext-replace\" rel=\"ugc\">Text Replace\u003C\u002Fa> plugin, which defines terms or phrases that you want replaced by replacement text when displayed on your site. Text Hover instead adds the hover text as additional information for when visitors hover over the term, which is otherwise displayed in the post as you typed it.\u003C\u002Fp>\n\u003Cp>Links: \u003Ca href=\"https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Ftext-hover\u002F\" rel=\"nofollow ugc\">Plugin Homepage\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftext-hover\u002F\" rel=\"ugc\">Plugin Directory Page\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcoffee2code\u002Ftext-hover\u002F\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa> | \u003Ca href=\"https:\u002F\u002Fcoffee2code.com\" rel=\"nofollow ugc\">Author Homepage\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Developer Documentation\u003C\u002Fh3>\n\u003Cp>Developer documentation can be found in \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fcoffee2code\u002Ftext-hover\u002Fblob\u002Fmaster\u002FDEVELOPER-DOCS.md\" rel=\"nofollow ugc\">DEVELOPER-DOCS.md\u003C\u002Fa>. That documentation covers the numerous hooks provided by the plugin. Those hooks are listed below to provide an overview of what’s available.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>c2c_text_hover_filters\u003C\u002Fcode> : Customize what hooks get text hover applied to them.\u003C\u002Fli>\n\u003Cli>\u003Ccode>c2c_text_hover_third_party_filters\u003C\u002Fcode> : Customize what third-party hooks get text hover applied to them.\u003C\u002Fli>\n\u003Cli>\u003Ccode>c2c_text_hover_filter_priority\u003C\u002Fcode> : Override the default priority for the \u003Ccode>c2c_text_hover\u003C\u002Fcode> filter.\u003C\u002Fli>\n\u003Cli>\u003Ccode>c2c_text_hover\u003C\u002Fcode> Customize or override the setting defining all of the text hover terms and their hover texts.\u003C\u002Fli>\n\u003Cli>\u003Ccode>c2c_text_hover_comments\u003C\u002Fcode> : Customize or override the setting indicating if text hover should be enabled in comments.\u003C\u002Fli>\n\u003Cli>\u003Ccode>c2c_text_hover_case_sensitive\u003C\u002Fcode> : Customize or override the setting indicating if text hover should be case sensitive.\u003C\u002Fli>\n\u003Cli>\u003Ccode>c2c_text_hover_once\u003C\u002Fcode> : Customize or override the setting indicating if text hovering should be limited to once per term per piece of text being processed regardless of how many times the term appears.\u003C\u002Fli>\n\u003Cli>\u003Ccode>c2c_text_hover_use_pretty_tooltips\u003C\u002Fcode> : Customize or override the setting indicating if prettier tooltips should be used.\u003C\u002Fli>\n\u003C\u002Ful>\n","Add hover text (aka tooltips) to content in posts. Handy for providing explanations of names, terms, phrases, abbreviations, and acronyms.",2000,62418,90,17,"2022-03-23T06:10:00.000Z","5.9.13","4.9",[86,87,88,89,90],"abbreviations","acronyms","help","terms","tooltips","https:\u002F\u002Fcoffee2code.com\u002Fwp-plugins\u002Ftext-hover\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftext-hover.4.2.zip",85,"2022-04-09 00:00:00",{"slug":96,"name":97,"version":98,"author":99,"author_profile":100,"description":101,"short_description":102,"active_installs":11,"downloaded":103,"rating":27,"num_ratings":104,"last_updated":105,"tested_up_to":16,"requires_at_least":106,"requires_php":107,"tags":108,"homepage":111,"download_link":112,"security_score":13,"vuln_count":113,"unpatched_count":28,"last_vuln_date":114,"fetched_at":30},"form-block","Form Block","1.7.1","epiphyt","https:\u002F\u002Fprofiles.wordpress.org\u002Fepiphyt\u002F","\u003Cp>WordPress offers several (contact) form plugins, but most of them are not up-to-date anymore when it comes to creating forms. Form Block tackles this problem by utilizing the block editor’s power. It enables you to create a form effortlessly within the block editor itself, which makes the process of creating a form much more enjoyable and similar to creating other types of blocks. This innovative approach to form creation ensures that Form Block stands out from other WordPress form plugins.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note: This plugins requires the PHP extension \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fbook.dom.php\" rel=\"nofollow ugc\">“Document Object Model” (php-dom)\u003C\u002Fa>.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Fully support of the block editor\u003C\u002Fli>\n\u003Cli>Built with accessibility in mind\u003C\u002Fli>\n\u003Cli>Create forms with an unlimited number of fields\u003C\u002Fli>\n\u003Cli>Select from a wide variety of field types\u003C\u002Fli>\n\u003Cli>Use a predefined form or start from scratch\u003C\u002Fli>\n\u003Cli>Store form submissions in the WordPress backend\u003C\u002Fli>\n\u003Cli>Integrated honeypot for spam protection\u003C\u002Fli>\n\u003Cli>Integrated knowledge base for field types\u003C\u002Fli>\n\u003Cli>Client-side and server-side validation\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Getting started\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Add the “Form Block” block anywhere you want to enable a form in your block editor.\u003C\u002Fli>\n\u003Cli>Select a predefined form or start from scratch.\u003C\u002Fli>\n\u003Cli>Add\u002FEdit\u002FRemove fields to your form as you like. You can select from input, select and textarea fields.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>After submission, the form data will be sent to the email address you have set in the settings.\u003C\u002Fp>\n\u003Ch4>Coming soon\u003C\u002Fh4>\n\u003Cp>There is much more planned for Form Block. Here is a small selection of features that are coming soon:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Flood Control\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fantispam-bee\u002F\" rel=\"ugc\">Antispam Bee\u003C\u002Fa> integration\u003C\u002Fli>\n\u003Cli>Custom date picker\u003C\u002Fli>\n\u003Cli>More customization options\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Pro version\u003C\u002Fh4>\n\u003Cp>There is also a Pro version of Form Block available. It offers additional features, such as:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Extended server-side validation\u003C\u002Fli>\n\u003Cli>Custom recipient(s) for each form\u003C\u002Fli>\n\u003Cli>Custom form action\u003C\u002Fli>\n\u003Cli>Upload via drag and drop\u003C\u002Fli>\n\u003Cli>Storing files in WordPress instead of attaching them to an email\u003C\u002Fli>\n\u003Cli>Global defined consent checkbox\u003C\u002Fli>\n\u003Cli>Field dependencies\u003C\u002Fli>\n\u003Cli>Advanced functionality for accessibility\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>You can find more information at \u003Ca href=\"https:\u002F\u002Fformblock.pro\u002Fen\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fformblock.pro\u002Fen\u002F\u003C\u002Fa>.\u003C\u002Fp>\n","An extensive yet user-friendly form block.",8843,4,"2026-01-31T09:38:00.000Z","6.7","7.4",[21,23,109,110,67],"contact-form","form","https:\u002F\u002Fformblock.pro\u002Fen\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fform-block.1.7.1.zip",2,"2025-08-07 00:00:00",{"slug":116,"name":117,"version":118,"author":119,"author_profile":120,"description":121,"short_description":122,"active_installs":27,"downloaded":123,"rating":124,"num_ratings":125,"last_updated":126,"tested_up_to":127,"requires_at_least":128,"requires_php":63,"tags":129,"homepage":63,"download_link":133,"security_score":93,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"acronyms-2","Acronyms 2","2.0.10","Chris","https:\u002F\u002Fprofiles.wordpress.org\u002Frenaissancedesign\u002F","\u003Cp>This WordPress plugin will allow users to maintain a list of acronyms and abbreviations which can be managed in the WordPress Dashbard. These acronyms will be automatically wrapped in the appropriate HTML markup when found in posts, pages and comments.\u003C\u002Fp>\n\u003Cp>The plugin will auto-detect whether the currently active theme uses HTML5, and will output the appropriate HTML acronym or abbreviation element, e.g. \u003Ccode>\u003Cacronym title=\"Hypertext Markup Language\">HTML\u003C\u002Facronym>\u003C\u002Fcode> (or \u003Ccode>\u003Cabbr title=\"Hypertext Markup Language\">HTML\u003C\u002Fabbr>\u003C\u002Fcode> for HTML5).\u003C\u002Fp>\n\u003Cp>Based on Joel Pan’s excellent Acronyms, which is no longer being actively maintained. The onset of HTML5 and the deprecation of \u003Ccode>\u003Cacronym>\u003C\u002Fcode> in favour of \u003Ccode>\u003Cabbr>\u003C\u002Fcode> led me to fork Joel’s plugin and create Acronyms 2.\u003C\u002Fp>\n","A plugin to automatically mark up known acronyms and abbreviations in posts and comments. Allows users to manage lists of acronyms through the WordPre …",8271,96,8,"2024-03-11T18:52:00.000Z","6.4.8","2.7",[20,22,130,131,132],"formatting","html5","post","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Facronyms-2.zip",{"attackSurface":135,"codeSignals":151,"taintFlows":158,"riskAssessment":159,"analyzedAt":167},{"hooks":136,"ajaxHandlers":147,"restRoutes":148,"shortcodes":149,"cronEvents":150,"entryPointCount":28,"unprotectedCount":28},[137,143],{"type":138,"name":139,"callback":140,"file":141,"line":142},"action","enqueue_block_editor_assets","abbr_button_enqueue_block_editor_assets","abbreviation-button-for-the-block-editor.php",27,{"type":138,"name":144,"callback":145,"file":141,"line":146},"init","abbr_button_set_script_translations",32,[],[],[],[],{"dangerousFunctions":152,"sqlUsage":153,"outputEscaping":155,"fileOperations":28,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":157},[],{"prepared":28,"raw":28,"locations":154},[],{"escaped":28,"rawEcho":28,"locations":156},[],[],[],{"summary":160,"deductions":161},"The abbreviation-button-for-the-block-editor plugin version 0.1 exhibits a strong security posture based on the provided static analysis. The absence of any identified dangerous functions, SQL queries without prepared statements, or unescaped output is highly commendable. Furthermore, the plugin demonstrates no external HTTP requests or file operations, which significantly reduces potential attack vectors. The zero-count for known CVEs and lack of past vulnerabilities suggests a history of secure development or a very limited attack surface that has not been exploited.\n\nWhile the static analysis shows an exceptionally clean codebase, the analysis does reveal certain areas that warrant attention. The complete absence of nonce checks and capability checks, coupled with zero AJAX handlers and REST API routes, might indicate a plugin that relies entirely on WordPress's core security for any potential interactions. This could be a strength if the plugin's functionality is minimal and doesn't require any sensitive operations. However, if future versions introduce any user-facing features or data manipulation, the lack of these fundamental security checks will become a significant concern.\n\nIn conclusion, the current version of the abbreviation-button-for-the-block-editor plugin appears to be very secure due to its minimal functionality and clean coding practices. However, the complete lack of authentication and authorization checks, even with a zero attack surface currently, presents a latent risk. Developers should remain vigilant and ensure that any future additions incorporate robust security measures.",[162,165],{"reason":163,"points":164},"No nonce checks detected",10,{"reason":166,"points":164},"No capability checks detected","2026-03-16T20:09:56.234Z",{"wat":169,"direct":178},{"assetPaths":170,"generatorPatterns":173,"scriptPaths":174,"versionParams":175},[171,172],"\u002Fwp-content\u002Fplugins\u002Fabbreviation-button-for-the-block-editor\u002Fbuild\u002Findex.js","\u002Fwp-content\u002Fplugins\u002Fabbreviation-button-for-the-block-editor\u002Fbuild\u002Findex.css",[],[171],[176,177],"abbreviation-button-for-the-block-editor\u002Fbuild\u002Findex.js?ver=","abbreviation-button-for-the-block-editor\u002Fbuild\u002Findex.css?ver=",{"cssClasses":179,"htmlComments":180,"htmlAttributes":181,"restEndpoints":182,"jsGlobals":183,"shortcodeOutput":184},[],[],[],[],[],[]]