Invisible Anti-Spam & CAPTCHA · Version history
Invisible Anti-Spam & CAPTCHA changelog and version history
- Latest version
- 6.3.1
- Nov 4, 2026 (6 days ago)
- Releases
- 97
- since 2022
- In the last year
- 18
- about one every 7 days
- Tested up to
- WordPress 7.1.4
- PHP 7.1 or later
Releases each year
- 20224 releases
- 202355 releases
- 202414 releases
- 20256 releases
- 202618 releases
202618 releases
Invisible Anti-Spam & CAPTCHA 6.3.1Latest
- Changed: The proof of work runs in short slices, so the page stays responsive and no longer counts as blocking time.
Invisible Anti-Spam & CAPTCHA 6.3.0
- Fixed: The flag prefix now also reaches the e-mail for fields sent as JSON (e.g. Ninja Forms, REST requests).
- Fixed: A “Fieldname:prefix” line whose prefix contains a colon is no longer ignored.
- Fixed: The “Fieldname:prefix to flag spam” prefix now shows up in the e-mail the form sends again (lost in 4.1).
- Fixed: SureForms and Crowdsignal Forms submissions sent as PUT or PATCH are now checked like POST.
- Changed: REST requests from logged-in users who can edit posts skip the spam check (valid REST nonce needed).
- Fixed: The body of a PUT or PATCH request is now read, so the blocklist sees it too.
- Fixed: Saving a form in the WS Form editor could be rejected as spam; only visitor submissions are checked now.
- Added: Out-of-the-box detection for Directorist contact/report forms; registration and listings are recorded.
- Added: Out-of-the-box detection for Brave Popup Builder, Jetpack CRM lead forms and WP Job Openings (HireZoot).
- Added: Out-of-the-box detection for the Back In Stock Notifier waitlist form.
- Added: Out-of-the-box detection for Gwolle Guestbook, WP Customer Reviews and wpForo (new topics and replies).
- Fixed: Deleting the plugin on a multisite network now removes its data from every site, not just the main one.
Invisible Anti-Spam & CAPTCHA 6.2.0
- Fixed: The repeat-sender lock no longer remembers numbers, so order, product, event or phone numbers lock out no one.
- Changed: The server now waits up to 5 seconds for a slow device to finish its check before rejecting a submission.
- Changed: The invisible check now starts once the page has loaded, so visitors who submit quickly are no longer rejected.
- Fixed: One rejected cart request could block other shoppers of the same product for 36 hours.
- Fixed: The Add to Cart button could be rejected as spam; WooCommerce cart requests are no longer checked.
- Fixed: Saving the settings broke rule lines with => or & (they were stored HTML-encoded); such lines are repaired on update.
- Fixed: Deleting the plugin failed with a fatal error and left its tables and settings behind.
- Fixed: Sites that already monitored a checkout or registration form keep blocking spam on it after this update.
- Added: Out-of-the-box detection for Royal Elementor Addons, Happy Addons, Chaty, Jeg Kit and Element Pack Lite.
- Added: Out-of-the-box detection for Depicter, Hello Plus, PopupKit and Strong Testimonials.
- Added: Out-of-the-box detection for Customer Reviews for WooCommerce, Site Reviews and WP Ultimate Review.
- Added: Registration forms of BuddyPress, WP-Members and ProfilePress are recognised.
- Added: Checkouts and bookings of EDD, ProfilePress, CartFlows, Amelia and Bookly are recognised.
- Security: Password fields of Easy Digital Downloads, GiveWP and ProfilePress are no longer stored.
- Added: Checkout and registration forms are recognised and recorded; blocking them is a separate switch, off by default.
- Added: The WooCommerce block checkout (Store API) is recognised and recorded.
- Security: Card numbers, CVCs and IBANs are no longer stored in the spam folder.
- Fixed: REST submissions are judged by the method WordPress runs them as, so a header can no longer disguise one.
- Fixed: A blocked submission now answers HTTP 422, not 200, so forms no longer show success for a refused entry.
- Security: Card numbers are no longer hashed into the repeat-sender store as if they were phone numbers.
- Changed: The “Works with” list in the readme is grouped by kind instead of one long line.
- Added: Out-of-the-box detection for Hostinger Reach, FormLayer, My Sticky Elements and Visual Form Builder.
- Added: Out-of-the-box detection for Cool FormKit, including Elementor’s newer atomic form action.
- Added: The deactivation box now offers five reasons to click, and points to the support forum.
- Added: The deactivation box can attach technical details (versions, plugins) if you tick the box.
- Added: Out-of-the-box detection for Hustle, Brevo, MailerLite, Mailchimp List Subscribe and Email Subscribers.
- Added: Out-of-the-box detection for Quiz and Survey Master, WP-Polls, Form Maker, Gutena Forms and Happyforms.
- Added: Out-of-the-box detection for Calculated Fields Form, Pirate Forms and Crowdsignal Forms (NPS and feedback).
- Changed: The deactivation box no longer explains the plugin name and version with a second plugin that no longer exists.
Invisible Anti-Spam & CAPTCHA 6.1.0
- Changed: The deactivation box and the readme now also name what travels with a message: the plugin name and version.
- Note: Tested up to WordPress 7.1.
- Added: The direct-analysis overlay can save an action narrowed to selected field values.
- Changed: One-click and agent scope writes now validate JSON rule lines; agents get plain action names only.
- Added: MailPoet signups sent with JavaScript are now detected too, not just the no-JavaScript path.
- Added: Newsletter (The Newsletter Plugin) subscription forms are now detected out of the box.
- Added: CoBlocks contact form submissions are now detected out of the box.
- Added: Popup Builder subscription forms are now detected out of the box.
- Added: Action-list lines can be JSON rules that pin field values, for AJAX actions shared with a plugin’s backend.
- Added: WooCommerce’s ajax add-to-cart button (wc-ajax=add_to_cart) is now checked out of the box.
- Fixed: A pattern that discards a form posted through admin-post.php now triggers the follow-up admin notice.
- Changed: Plain GET requests are no longer checked — a link click cannot carry a proof of work.
- Note: WooCommerce cart links (?add-to-cart=) no longer produce inbox entries, nor does any GET form.
- Added: MailPoet’s subscription form is recognized out of the box on the path automated submissions take.
- Changed: The “Works with” list now names exactly the builders recognized out of the box.
- Added: Kadence Blocks, Essential Blocks, Popup Maker, UserFeedback and MW WP Form are named there now.
- Note: Registration forms are no longer listed as pre-configured — only login and password reset are.
- Added: out-of-the-box detection for MW WP Form
- Added: out-of-the-box detection for wpDiscuz comment forms (regular and inline)
- Added: out-of-the-box detection for Kadence Blocks forms (Form block and Advanced Form)
- Added: out-of-the-box detection for Essential Blocks forms
- Added: out-of-the-box detection for Popup Maker subscription forms
- Added: out-of-the-box detection for MetForm form submissions
- Added: out-of-the-box detection for UserFeedback survey responses
- Added: out-of-the-box detection for bbPress forum topics and replies
- Added: out-of-the-box detection for Mailchimp for WordPress (MC4WP) sign-up forms
- Security: One-click “monitor this” buttons now refuse a pattern or action that would evaluate wp-admin itself.
- Changed: Scope additions made through the Abilities API are judged by the same catalog as the settings page.
- Fixed: The over-broad pattern warning now also covers the Screen Options box and the classic editors.
- Fixed: The feedback box shown when deactivating the plugin never reached its recipient; messages were lost.
Invisible Anti-Spam & CAPTCHA 6.0.0
- Added: A message’s REST route line now says whether that route is monitored
- Note: New FAQ entry explaining what to do if a real message is refused as gibberish
- Added: Pick fields to check for gibberish with one click from a stored message, or type them in Settings
- Added: Saving the gibberish list points out unreadable lines and forms no longer monitored
- Note: A one-time notice explains that gibberish detection is off and how to switch it on
- Changed: Gibberish detection is off by default and only checks fields you select
- Changed: A gibberish verdict now names the field that triggered it
- Removed: The gdpr_pow_gibberish_exempt_fields filter – only selected fields are checked now
- Fixed: Gibberish detection no longer applies to the WordPress login form
Invisible Anti-Spam & CAPTCHA 5.6.0
- Fixed: Ninja Forms submissions were always blocked as “Gibberish content”.
- Added: Builders posting their whole form as JSON in one field now expose their single fields to rules.
- Changed: A “Known spam value” block no longer extends the 36-hour lock, so a false alarm cannot renew itself.
- Fixed: Jetpack Forms are watched again; the shipped action name was one Jetpack never registered.
- Fixed: WP User Frontend forms are watched again; both the detection path and the signature were wrong.
- Added: Formidable Forms is detected again – its classic and its AJAX submit are both watched out of the box.
- Fixed: An over-broad field pattern no longer discards your own wp-admin saves.
- Changed: Admin screens skip the spam check when the logged-in user can edit posts.
- Added: a Diagnostics button now produces a copyable status report that is safe to post in a public support forum.
- Fixed: “Save WooCommerce shopping carts” now also covers cart requests carrying add-to-cart in the URL query.
- Fixed: The “Thrive Comments detected” notice now names the recognition pattern actually added.
- Changed: removed 21 shipped recognition patterns that named form fields no product ever sends; coverage is unchanged.
- Changed: Jotform, Typeform and Zoho Forms are no longer listed as detected; their forms submit to their own servers.
Invisible Anti-Spam & CAPTCHA 5.5.0
- Added: submissions blocked as “Known spam value” now link directly to the setting that releases them.
- Fixed: submissions were incorrectly flagged as spam on sites using Cloudflare Turnstile.
- Added: the WordPress comment form is now protected by default; comment spam previously passed unchecked.
- Added: blocked-value rules that can never match are now labelled on save instead of appearing active.
- Added: a “Blocked values” entry can now be a rule that binds a value to a single field or form.
- Added: blocked-value rules that would discard an entire form are held back until you confirm them.
- Fixed: the one-time migration of blocked values now also handles pattern lists with classic Mac line endings.
Invisible Anti-Spam & CAPTCHA 5.4.0
- Changed: The “Apply on pattern” help now notes that a numeric value still needs its quotation marks.
- Changed: The help for “Apply on pattern” and “Blocked values” now shows real examples of the lines you would enter.
- Changed: Blocked sender values moved to their own “Blocked values” setting. Existing entries move over automatically.
- Added: {“*”:”value”} in “Apply on pattern” now matches any field carrying that value — it monitors, it does not block.
- Fixed: The notice about a discarded admin save now names whether a pattern or a blocked value was responsible.
- Fixed: A blocked email address or domain no longer stops a registered user from logging in with it.
- Added: A whole sender domain can be blocked in “Blocked values” with one line (@disposable.tld), subdomains included.
- Added: “Block this sender’s domain” button in the message view; the settings help now explains blocking values.
- Fixed: An admin-side ajax reply could carry a PHP warning ahead of its JSON on servers that display errors.
- Fixed: A block on a wp-admin screen no longer writes a fail2ban line, so an over-broad pattern cannot ban the admin.
- Added: A field pattern that also matches your admin screens now warns before saving, and asks you to confirm it.
- Added: An admin notice now names the field pattern when one of your own admin page saves was discarded as spam.
- Added: Settings now suggests the detected reverse-proxy address, with one click to add it to trusted proxies.
- Fixed: A handshake failure caused by a cache, proxy or clock issue no longer adds the sender to the 36-hour spam list.
Invisible Anti-Spam & CAPTCHA 5.3.4
- Fixed: submissions are no longer all flagged as spam on servers whose database connections disagree about the time zone.
- Fixed: the spam and health figures in the status bar and dashboard widget now count the right day on servers whose database time zone differs from the site’s.
- Fixed: old messages are now deleted exactly on schedule on sites whose time zone is not UTC, instead of a few hours early or late.
- Security: a “/0” range in the trusted proxy list no longer makes every visitor a trusted proxy.
- Security: the site whitelist can no longer be claimed with a forged Host header.
- Security: a submission can no longer exempt its own fields from spam analysis by declaring them password fields.
- Added: a “/0” entry in the trusted proxy list is now refused when you save it, with an explanation, instead of being stored and quietly doing nothing.
- Added: AI agents can be allowed to read stored submissions, and separately to change protection settings and delete submissions. Two switches, both off by default.
- Added: an option to trust a proxy on a private network when no trusted proxy is configured, for sites whose host does not publish the proxy address.
- Added: the analysis mode now shows why a submission was judged the way it was, not just what it was.
- Added: the status bar shows which address the plugin sees for you, and where it took it from.
- Fixed: the “submissions without a stamp row” figure now also counts when storing spam is switched off, where it used to read zero and look healthy.
- Fixed: the IP whitelist now understands subnets and different spellings of the same address, instead of matching text exactly.
- Changed: only the current puzzle format is accepted now; the transitional formats carried since 5.3.2 are gone.
- Note: site whitelist entries must name your site’s real address; an entry naming an alias (www versus the bare domain) no longer matches.
Invisible Anti-Spam & CAPTCHA 5.3.3
- Added: once you have fixed a storage problem, a green self-test clears the warning instead of leaving it up for a day
- Changed: the self-test and the two diagnostic resets now live on their own Diagnostics tab
- Changed: a self-test result now leads with its verdict and shows the error code, instead of one long coloured sentence
- Added: a blocked message links straight to the self-test, one click from where the problem is visible
- Added: a self-test button that runs the whole invisible check against your own site and answers in one sentence
- Added: the self-test now says outright when a solved puzzle could not be stored, instead of blaming stale code
- Fixed: where the time-window setting had gone missing, solved puzzles were discarded while still counted as valid
- Added: a blocked submission records what the server actually found, so a support case can be settled in one round
- Fixed: a solved puzzle the server could not store was still reported as accepted, so every later submission was blocked
- Fixed: the browser no longer treats an unanswered or rejected puzzle as solved, and retries the handshake instead
- Added: the settings screen now names it outright when solved puzzles cannot be written to the database
- New: AI agents can now run a plain-language self-test of the spam protection and read its health figures.
- New: optional and off by default — an AI agent can extend which forms are monitored, guarded against lockouts
- New: the plugin now appears on the Connectors screen of WordPress 7.0, stating plainly that it uses no external service.
Invisible Anti-Spam & CAPTCHA 5.3.2
- Fixed: the block reason shown for follow-up tokens no longer refers to a waiting window that no longer exists
- Removed: the extra second puzzle some visitors were given is gone — one puzzle per visitor, always
- Fixed: submissions sent while that second puzzle was still running are no longer flagged as spam
- Fixed: captcha fields are no longer misread as gibberish, and single-field random-letter spam is now caught
- Added: fields can be excluded from spam analysis via the skip list or the new gdpr_pow_gibberish_exempt_fields filter
Invisible Anti-Spam & CAPTCHA 5.3.1
- Added: Spectra forms are now protected automatically, with no manual setup required.
- Fixed: form builders that submit via URLSearchParams no longer drop the proof-of-work token.
- Fixed: token injection now detects request bodies created inside iframes.
Invisible Anti-Spam & CAPTCHA 5.3.0
- New: SureForms and JetFormBuilder are now recognised out of the box.
- The analysis mode shows the REST route for entries captured with the live overlay too, not just for logged ones.
- The analysis mode now records and shows the REST route of a submission, with one click to start monitoring it.
- Fix: default detection for WS Form, Everest Forms, and Otter Blocks never matched — now corrected.
- New: REST routes are now a third way to scope the spam check, covering WS Form and Otter Blocks out of the box.
- Hardening: exemptions from the spam and login checks are now server-side only; the ‘Apply on REST-API’ option is gone.
- Note: an over-broad field pattern (like just “email”) can now match admin screens too; keep patterns form-specific.
- New: status bar and dashboard show how many solved puzzles came back from another address than they were issued to.
- Privacy: nothing derived from the visitor address is in the page source, and the challenge answer carries a fingerprint.
- Hardening: only X-Forwarded-For is still evaluated, and only behind a trusted proxy; four spoofable headers are ignored.
- Fix: a cache, proxy pool or IPv4/IPv6 dual stack no longer flags every submission as spam; puzzles are address-free.
- Blocked messages now name the actual cause, not just the kind of block.
- Fix: submissions are no longer rejected while the site is under attack and an older cached token is solved
- Fix: the token request is no longer served from a page or CDN cache, which could make every submission look like spam
- New: confirm a password field the plugin does not recognise, and its values are redacted, in old messages too.
- Security: password field values could be stored with a submission in some cases; they are now always redacted.
- Security: existing stored entries are cleaned up once after the update.
Invisible Anti-Spam & CAPTCHA 5.2.1
- Fix: a difficulty above 20 made every submission spam — the server issued challenges its own check rejected.
Invisible Anti-Spam & CAPTCHA 5.2.0
- Spam messages now show why they were blocked, plus a health counter for submissions without a proof-of-work stamp.
Invisible Anti-Spam & CAPTCHA 5.1.1
- Security release. Fixes the three reported vulnerabilities and, after a full internal review, several related hardenings across the message-management area. * Security (SQL injection): admin-defined spam-analysis patterns are now escaped before they are interpolated into the LIKE conditions of the…
Invisible Anti-Spam & CAPTCHA 5.1
- This release brings stronger anti-spam layers to every site, alongside important reliability fixes. * New: gibberish detection — obvious keyboard-mash and random-string submissions are recognised and filtered, language-neutrally, while legitimate codes (VAT ids, serials, order numbers, product name…
Invisible Anti-Spam & CAPTCHA 5.0
- Major anti-spam hardening against protocol-aware bots: every proof-of-work is now bound to a single-use, HMAC-signed token per submission (replay of one solved challenge no longer works), with a per-token and per-IP usage limit
- Forwarded-For/Client-IP headers are only trusted behind a configurable trusted-proxy list (new option) — closes IP-spoofing of the whitelist
- Adaptive difficulty with an automatic site-wide “under-attack mode” (new option): the puzzle gets harder for everyone while a spam wave is running; no per-visitor data involved
- Proof-of-work now uses the browser’s native crypto engine where available (about 10x faster), with a fallback for older browsers and http-only sites
- Faster spam-check path: worker no longer sleeps up to 5 seconds under a spam flood
- Redesigned settings page: status strip, topic tabs, short descriptions with progressive-disclosure help on every option
- Reworked direct analysis mode: persistent guide bar with live coverage instead of stacked popups, entries persist server-side
- Security: password fields are never stored in captured submissions — neither in the classic analysis inbox nor in direct-analysis entries
- Security: CSRF protection (nonce) added to the direct-analysis pattern-save endpoint
- Security: SQL statements consistently use prepared placeholders; full WordPress coding-standards pass across the whole codebase
- Recognition patterns can no longer accidentally match on the plugin’s own injected fields
- All option texts are now translatable via the WordPress.org community catalog (translate.wordpress.org)
- Requires PHP 7.1 or newer (was effectively required before, now declared honestly)
20256 releases
Invisible Anti-Spam & CAPTCHA 4.1.2
- CSRF vulnerability fixed
Invisible Anti-Spam & CAPTCHA 4.1.1
- Improved Pattern recognition
- Solved: Warning for usage of empty keys
Invisible Anti-Spam & CAPTCHA 4.1
- Fail2Ban-Support added
- Problems with Thrive Comments and json-based submissions fixed
Invisible Anti-Spam & CAPTCHA 4.0
- The automatic mode has been removed. From now on, all form types require manual configuration of associated patterns and actions to ensure the spam protection functions correctly.
- During plugin installation, the appropriate actions and patterns for major form builders will be automatically added to the scope—provided the respective form builder is installed.
- Adding new form types to the spam protection, which are not yet included by default, can still be done via the analysis mode or direct analysis mode.
- If important patterns or actions are missing, I appreciate any feedback and suggestions for improvements.
- This update ensures targeted spam protection configuration while still allowing automatic detection of widely used form builders.
Invisible Anti-Spam & CAPTCHA 3.8.1
- Fixed: Erroneous error handling for file-uploads (i.e. Fancy Product Designer)
Invisible Anti-Spam & CAPTCHA 3.8
- Fixed: Problems with IP-Forwarding and load-balancing led to always false-positives
202414 releases
Invisible Anti-Spam & CAPTCHA 3.7.3
- SQL-Bug during installation routine fixed
Invisible Anti-Spam & CAPTCHA 3.7.2
Invisible Anti-Spam & CAPTCHA 3.7.1
Invisible Anti-Spam & CAPTCHA 3.7
Invisible Anti-Spam & CAPTCHA 3.6.10
Invisible Anti-Spam & CAPTCHA 3.6.9
Invisible Anti-Spam & CAPTCHA 3.6.8
Invisible Anti-Spam & CAPTCHA 3.6.7
Invisible Anti-Spam & CAPTCHA 3.6.6
Invisible Anti-Spam & CAPTCHA 3.6.5
Invisible Anti-Spam & CAPTCHA 3.6.4
Invisible Anti-Spam & CAPTCHA 3.6.3
Invisible Anti-Spam & CAPTCHA 3.6.2
Invisible Anti-Spam & CAPTCHA 3.6.1
202355 releases
Invisible Anti-Spam & CAPTCHA 3.6
Invisible Anti-Spam & CAPTCHA 3.5.8
Invisible Anti-Spam & CAPTCHA 3.5.7
Invisible Anti-Spam & CAPTCHA 3.5.6
Invisible Anti-Spam & CAPTCHA 3.5.5
Invisible Anti-Spam & CAPTCHA 3.5.4
Invisible Anti-Spam & CAPTCHA 3.5.3
Invisible Anti-Spam & CAPTCHA 3.5.2
Invisible Anti-Spam & CAPTCHA 3.5.1
Invisible Anti-Spam & CAPTCHA 3.5
Invisible Anti-Spam & CAPTCHA 3.4
Invisible Anti-Spam & CAPTCHA 3.3
Invisible Anti-Spam & CAPTCHA 3.2
Invisible Anti-Spam & CAPTCHA 3.1
Invisible Anti-Spam & CAPTCHA 3.0.8
Invisible Anti-Spam & CAPTCHA 3.0.7
Invisible Anti-Spam & CAPTCHA 3.0.6
Invisible Anti-Spam & CAPTCHA 3.0.5
Invisible Anti-Spam & CAPTCHA 3.0.4
Invisible Anti-Spam & CAPTCHA 3.0.3
Invisible Anti-Spam & CAPTCHA 3.0.2
Invisible Anti-Spam & CAPTCHA 3.0.1
Invisible Anti-Spam & CAPTCHA 3.0
Invisible Anti-Spam & CAPTCHA 2.5.2
Invisible Anti-Spam & CAPTCHA 2.5.1
Invisible Anti-Spam & CAPTCHA 2.5
Invisible Anti-Spam & CAPTCHA 2.4.1
Invisible Anti-Spam & CAPTCHA 2.4
Invisible Anti-Spam & CAPTCHA 2.3.3
Invisible Anti-Spam & CAPTCHA 2.3.2
Invisible Anti-Spam & CAPTCHA 2.3.1
Invisible Anti-Spam & CAPTCHA 2.3
Invisible Anti-Spam & CAPTCHA 2.2.2
Invisible Anti-Spam & CAPTCHA 2.2.1
Invisible Anti-Spam & CAPTCHA 2.2.0
Invisible Anti-Spam & CAPTCHA 2.1.5
Invisible Anti-Spam & CAPTCHA 2.1.4
Invisible Anti-Spam & CAPTCHA 2.1.3
Invisible Anti-Spam & CAPTCHA 2.1.2
Invisible Anti-Spam & CAPTCHA 2.1.1
Invisible Anti-Spam & CAPTCHA 2.1.0
Invisible Anti-Spam & CAPTCHA 2.0.5
Invisible Anti-Spam & CAPTCHA 2.0.4
Invisible Anti-Spam & CAPTCHA 2.0.3
Invisible Anti-Spam & CAPTCHA 2.0.2
Invisible Anti-Spam & CAPTCHA 2.0.1
Invisible Anti-Spam & CAPTCHA 2.0
Invisible Anti-Spam & CAPTCHA 1.4.3
Invisible Anti-Spam & CAPTCHA 1.4.2
Invisible Anti-Spam & CAPTCHA 1.4.1
Invisible Anti-Spam & CAPTCHA 1.4
Invisible Anti-Spam & CAPTCHA 1.2.0
Invisible Anti-Spam & CAPTCHA 1.3
Invisible Anti-Spam & CAPTCHA 1.2.1
Invisible Anti-Spam & CAPTCHA 1.1.1
20224 releases
Invisible Anti-Spam & CAPTCHA 1.1.0
Invisible Anti-Spam & CAPTCHA 1.0.2
Invisible Anti-Spam & CAPTCHA 1.0.1
Invisible Anti-Spam & CAPTCHA 1.0.0
Questions about Invisible Anti-Spam & CAPTCHA’s releases
What is the latest version of Invisible Anti-Spam & CAPTCHA?
6.3.1, released on Nov 4, 2026 (6 days ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.1 or later.
How often is Invisible Anti-Spam & CAPTCHA updated?
18 releases in the last year, about one every 7 days. Its first release on WordPress.org dates from November 2022.
Know when your rivals ship
Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.
Start freeRelease dates come from the day each version’s folder was made in Invisible Anti-Spam & CAPTCHA’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.