mosparo

Modern spam protection tool. It replaces other captcha methods with a simple and easy to use spam protection solution.

Steady · 64
64/100
Steady

Maintained, but at a slower pace than the leaders in its category.

Maintenance 21/40
Releases 25/25
Community 3/20
Momentum 15/15

Commit activity more than 53% of tracked projects; popularity more than 16%. How this is calculated.

Commits, last 11 months

2025-12: 11 commits 2026-01: 22 commits 2026-02: 18 commits 2026-03: 6 commits 2026-04: 53 commits 2026-05: 9 commits 2026-06: 58 commits 2026-07: 3 commits 2026-08: 4 commits 2026-09: 51 commits 2026-10: 123 commits
2025-12 358 total 2026-10
Stars317
Latest releasev1.5.15 · 16 Nov 2026
Repo updated19 Nov 2026
LicenceMIT
Built withPHP

Is mosparo actively maintained?

mosparo is under active development: 358 commits landed over the last 11 months, averaging roughly 59 commits a month in the most recent quarter.

Activity is accelerating: the last quarter carried 154% more commits than the one before it.

The most recent tagged release, v1.5.15, shipped within the last month — a current, installable version exists today.

mosparo ranks #26 of 77 in Miscellaneous, placing it mid-table for maintenance activity.

What mosparo actually does

Mosparo is a self-hosted spam protection tool designed to replace traditional CAPTCHA methods on web forms. It provides a straightforward backend service that validates form submissions to block automated bot traffic without relying on third-party services. The project is open-source under the MIT licence and built with PHP.

Best fit: This is a good fit if you want to eliminate third-party tracking from your form validation or prefer to host your own bot-mitigation infrastructure alongside your web applications.

Worth knowing: You will need to integrate this service into your existing web forms and manage its reliability yourself, meaning a server outage could disrupt your form submissions. It also represents a less widespread alternative to mainstream CAPTCHA providers, so integration guides for specific CMS platforms may be limited.

Deployment notes

As a PHP application, it typically requires a standard web server such as Nginx or Apache, along with a relational database like MySQL or PostgreSQL for data persistence. You will also need to handle TLS termination via a reverse proxy to secure API communication between your forms and the backend.


Alternatives to mosparo

Projects in the same categories, ordered by health score.