Flask-Security
Quickly add security features to your Flask application.
Notes on this repo
As of 7/30/2024, the independent fork Flask-Security-Too replaced the archived Flask-Security repo (now called Flask-Security-3.0). This repo is published at PyPI at both Flask-Security and Flask-Security-Too. Please consider changing your requirements file to point to flask-security.
Flask-Security-Too was a fork from the 3.0.0 version of the Original
Pallets Community Ecosystem
This project is part of the Pallets Community Ecosystem. Pallets is the open source organization that maintains Flask; Pallets-Eco enables community maintenance of related projects. If you are interested in helping maintain this project, please reach out on the Pallets Discord server <https://discord.gg/pallets>.
Goals
Use OWASP to guide best practice and default configurations.
Be more opinionated and ‘batteries’ included by reducing reliance on abandoned projects and bundling in support for common use cases.
Follow the Pallets lead on supported versions, documentation standards and any other guidelines for extensions that they come up with.
- Continue to add newer authentication/authorization standards:
‘Social Login (OAuth)’ integrated (using authlib) (5.1)
WebAuthn/Passkey support (5.0)
Two-Factor recovery codes (5.0)
First-class support for username as identity (4.1)
Support for freshness decorator to ensure sensitive operations have new authentication (4.0)
Support for email normalization and validation (4.0)
Unified signin (username, phone, passwordless) feature (3.4)
Two/Multi-Factor authentication supporting SMS, email, authenticator apps (4.0)
Contributing
Issues and pull requests are welcome. Other maintainers are also welcome. Please consult these contributing guidelines.
Installing
Install and update using pip:
pip install -U Flask-Security
Resources
1 maintainer
Metadata
1 maintainer
Release files for Flask-Security-Too 5.8.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| flask_security_too-5.8.3.tar.gz | 753.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flask_security_too-5.8.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / flask_security_too-5.8.3.tar.gz
| Download URL | flask_security_too-5.8.3.tar.gz |
|---|---|
| Size | 753.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ebcd3cbf0e128bd7d0c533efc58b4aabf1804c0e3c28a8c2793f0e01d4bc5877
|
|
BLAKE2b-256 checksum How to use checksums |
763b3d360a8f4f81accd556e80917333a5ff8cc4a2262a723c58d2b79786d78e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency logRelease files / flask_security_too-5.8.3-py3-none-any.whl
| Download URL | flask_security_too-5.8.3-py3-none-any.whl |
|---|---|
| Size | 493.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3e65ddc367f9a6acf8477362f0b08fd2c1ee1aa481bd8a1a18b965a19158c5ab
|
|
BLAKE2b-256 checksum How to use checksums |
a6553b0d42d25a57653d8bd61b64ac0f5d5063ccb246e191a0ba03299d8f0d78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 30, 2026.
Transparency log
