alexlundin

This is the long description. No limit, and you can use Markdown (as well as in the following sections).
For backwards compatibility, if this section is missing, the full length of the short description will be used, and 
Markdown parsed.
A few notes about the sections above:
<ul>
<li>“Contributors” is a comma separated list of wp.org/wp-plugins.org usernames</li>
<li>“Tags” is a comma separated list of tags that apply to the plugin</li>
<li>“Requires at least” is the lowest version that the plugin will work on</li>
<li>“Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on 
higher versions… this is just the highest one you’ve verified.</li>
<li>
Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use <code>/trunk/</code> for 
stable.
Note that the <code>readme.txt</code> of the stable tag is the one that is considered the defining one for the plugin, so 
if the <code>/trunk/readme.txt</code> file says that the stable tag is <code>4.3</code>, then it is <code>/tags/4.3/readme.txt</code> that’ll be used 
for displaying information about the plugin. In this situation, the only thing considered from the trunk <code>readme.txt</code> 
is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk <code>readme.txt</code> to reflect changes in 
your in-development version, without having that information incorrectly disclosed about the current stable version 
that lacks those changes — as long as the trunk’s <code>readme.txt</code> points to the correct stable tag.
If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where 
you put the stable version, in order to eliminate any doubt.
</li>
</ul>
<h3>Arbitrary section</h3>
You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated 
plugins where more information needs to be conveyed that doesn’t fit into the categories of “description” or 
“installation.” Arbitrary sections will be shown below the built-in sections outlined above.
<h3>A brief Markdown Example</h3>
Ordered list:
<ol>
<li>Some feature</li>
<li>Another feature</li>
<li>Something else about the plugin</li>
</ol>
Unordered list:
<ul>
<li>something</li>
<li>something else</li>
<li>third thing</li>
</ul>
Here’s a link to <a href="https://wordpress.org/" title="Your favorite software" rel="ugc">WordPress</a> and one to <a href="http://daringfireball.net/projects/markdown/syntax" title="Markdown is what the parser uses to process much of the readme file" rel="nofollow ugc">Markdown’s Syntax Documentation</a>. 
Titles are optional, naturally.
Markdown uses email style notation for blockquotes and I’ve been told:
<blockquote>
Asterisks for emphasis. Double it up for strong.
</blockquote>
<pre><code><?php code(); // goes in backticks ?>
</code></pre>

WP Battle by Alex Lundin

Here is a short description of the plugin.  This should be no more than 150 characters.  No markup here.

webvitalii

kudlav

This is fork of successful Anti-spam plugin v5.5 written by webvitalii, for more info visit <a href="https://github.com/kudlav/anti-spam/" rel="nofollow ugc">GitHub Fork</a>. 
From version 5.6 maintained by kudlav.
<ul>
<li><a href="https://github.com/kudlav/anti-spam/" rel="nofollow ugc">GitHub</a></li>
</ul>
Anti-spam Reloaded plugin blocks 100% of automatic spam messages in comments section and also blocks all trackbacks.No captcha required.
Plugin is simple and easy to use: just install it and it just works.
Blocked comments can be stored in the Spam area and converted to regular comments if needed.
Anti-spam Reloaded plugin is GDPR compliant and does not store any other user data except of the behaviour mentioned above.
Plugin blocks spam only in comments section.. 
Plugin does not block manual spam (submitted by spammers manually via browser).
<h3>Compatibility</h3>
All modern browsers and IE11+ are supported. 
Anti-spam Reloaded plugin works with disabled JavaScript. Users with disabled JavaScript should manually fill current year before submitting the comment.
Server compatibility:
<ul>
<li>WordPress 3.3 – 6.5</li>
<li>PHP 5.6 – 8.2</li>
<li>Doesn’t use jQuery</li>
</ul>
Plugin is incompatible with:
<ul>
<li>Disqus</li>
<li>Jetpack Comments</li>
<li>AJAX Comment Form</li>
<li>bbPress</li>
</ul>
If site has caching plugin enabled and cache is not cleared or if theme does not use ‘comment_form’ action 
and there is no plugin inputs in comments form – plugin tries to add hidden fields automatically using JavaScript.
<h3>How does it work?</h3>
The blocking algorithm is based on 2 methods: ‘invisible js-captcha’ and ‘invisible input trap’ (aka honeypot technique).
<h4>‘invisible js-captcha’</h4>
The ‘invisible js-captcha’ method is based on fact that bots does not have JavaScript on their user-agents. 
Extra hidden field is added to comments form. 
It is the question about the current year. 
If the user visits site, than this field is answered automatically with JavaScript, is hidden by JavaScript and CSS and invisible for the user. 
If the spammer will fill year-field incorrectly – the comment will be blocked because it is spam.
<h4>‘invisible input trap’</h4>
The ‘invisible input trap’ method is based on fact that almost all the bots will fill inputs with name ’email’ or ‘url’. 
Extra hidden field is added to comments form. 
This field is hidden for the user and user will not fill it. 
But this field is visible for the spammer. 
If the spammer will fill this trap-field with anything – the comment will be blocked because it is spam.

WP Battle by Alex Lundin vs Anti-spam Reloaded