securify
Secure and robust input handling for Python applications.
securify is a lightweight library designed to make user interactions more secure.
Its primary goal is to provide reliable ways to capture sensitive information, like
passwords, while enforcing strict security constraints.
Key Features
- Security First: Enforces interactive terminal (TTY) usage to prevent insecure input processing.
- Bot Protection: Built-in time delay checks to prevent automated script attacks.
- Double-Entry Verification: Simple logic to ensure users enter identical passwords.
- Developer Friendly: Fully type-hinted, 100% test coverage, and clean exception hierarchies.
Installation
pip install .
Quick Start
The core of the library is the PasswordDoubleCheck class. It ensures that a
password is typed correctly twice and that the user is actually sitting at a
terminal.
from securify.input.password import PasswordDoubleCheck
from securify.input.exceptions import PasswordError
# Initialize with a 1.5-second minimum delay
checker = PasswordDoubleCheck(min_delay=1.5)
try:
password = checker()
print("Password successfully verified!")
except PasswordError as e:
# Handles Mismatch, Speed, or Terminal errors
print(f"Verification failed: {e}")
Technical Background: Why TTY?
By default, securify rejects input that does not come from a real terminal. This
ensures that the tool only processes input from a secure, interactive source.
If the input is provided through a pipe or another non-interactive process, the checker will reject the operation. This prevents the application from being used in insecure workflows where passwords might be handled through unsafe channels.
Development
securify is built with a focus on stability and cross-version compatibility. It
is tested against Python 3.11 up to 3.15-alpha.
Running Tests
We use tox to manage environments and pytest for testing:
tox
Building Documentation
The documentation is built with Sphinx:
cd doc
make html
License
LGPLv2 or above.
Metadata
Release files for ftw-securify 0.1.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 | |
|---|---|---|---|
| ftw_securify-0.1.3.tar.gz | 36.2 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ftw_securify-0.1.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.2 MB
Release files / ftw_securify-0.1.3.tar.gz
| Download URL | ftw_securify-0.1.3.tar.gz |
|---|---|
| Size | 36.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
87fc5ac10fbab6843497dca7bcc3b57ff615a5f2b2a570d8a46cee14dd058e2c
|
|
BLAKE2b-256 checksum How to use checksums |
3eed6c243ada71a42e6461b81e458b53926d4316954f73a15e187574659dda0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 18, 2026.
Transparency logRelease files / ftw_securify-0.1.3-py3-none-any.whl
| Download URL | ftw_securify-0.1.3-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
015716e3c45523a6b2b359298b2506481ccbc90a0bb57a11f5ab2bb5800f34d4
|
|
BLAKE2b-256 checksum How to use checksums |
cfa63fa3c280f045d519c9d294b16f1e3f948c1c96125a5e0b4a39a32c816b76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 18, 2026.
Transparency log