captcha

git.splent.io/splent-io/splent_feature_captcha

v0.3.0 service security

About

The captcha every form shares: the CaptchaService interface its providers implement, the forms it protects and their checks, wired once

Provides

Services
CaptchaService
Hooks filled
auth.login.form_fieldsreset.form_fieldssignup.form_fields

Configuration

Setting Default What it does
CAPTCHA_PROTECTED_FORMS signup The forms whose submissions are checked, by the name of their signal: signup, login, reset, contact, comment and careers. A form left out goes through without an answer, and its widget is not drawn, the comment thread's included. Blank means the sign-up alone. A product without a sign-up names its forms: on the first request the log says which forms named here the product does not have, and when that leaves none, says captcha protects nothing.

These are the defaults. A product changes them in its own pyproject.toml, under [tool.splent.config], or in .env.deploy in production.

Dependencies

In product lines

Extension points

Services
CaptchaService
Routes
A refinement can add routes to its blueprint

Other features fill its hook slots. A refinement can override its templates and services or extend its models without forking it.

Compatibility

Python
>=3.13
SPLENT framework
No range declared