Django Signoffs
A mico-framework for collecting lightweight, non-crypto "signatures" for virtually anything.
Signoff- a permitted user agrees to something at a time.Approval- a set ofSignoffsthat trigger a state change when theSigningOrderis complete.Approval Process- a sequence ofApprovalsthat drive a Finite State Machine.
Quick Start
-
Install the
django-signoffspackage from PyPI$ pip install django-signoffs
-
Add
signoffstoINSTALLED_APPS:INSTALLED_APPS = [ ..., "signoffs", ..., ]
Features
django-signoffs has 3 tiers. Import and use only the features you need...
signoffs.signoffs
A Signoff records that a user agreed to some statement at a time.
signoffs.signoffs provides a framework for defining use-cases
that fall within this broad requirement.
Core features:
AbstractSignetandAbstractRevokedSignetModels (persistence layer)- Base
SignoffTypes, with injectable business and presentation logic...SignoffLogic(permissions and buisness logic)SignoffFormsManagerandSignoffRenderer(presentation layer)SignoffUrlsManager(custom end-points)
- Signoff "forward" relation:
SignoffOneToOneField - Signoff "reverse" relation Manager:
SignoffSet(many-to-one) - Declarative signing order automation:
SigningOrder - Template tag:
{% render_signoff my_signoff %}
signoffs.approvals
An Approval records whether some condition was met at some point in time.
Essentially, it is a 2-state machine, designed to change states
when one or more Signoffs are completed, in some defined SigningOrder.
Core features:
AbstractApprovalSignetandAbstractApprovalStampModels (persistence layer)- Base
ApprovalTypes, with injectable business and presentation logic...ApprovalLogic(business logic)ApprovalStatusandApprovalRenderer(presentation layer)ApprovalUrlsManager(custom end-points)
- Approval "forward" relation:
ApprovalOneToOneField - Approval "reverse" relation Manager:
ApprovalSet(experimental) - Template tag:
{% render_approval my_approval %}
signoffs.process
An ApprovalsProcess defines a sequence of Approvals and the state changes and/or
side effects triggered by approving or revoking each of them.
Core Features:
ApprovalsProcess(a basic linear sequence ofApprovals)FsmApprovalsProcess(state-changes and sequencing defined bydjango-fsm)
Opt-in
Contrib Models
signoffs.contrib.signets
Signoffs core defines only abstract models, no migrations.
signoffs.contrib.signets provide concrete models that cover the basic use-cases. To opt-in, you must:
INSTALLED_APPS = [
...,
"signoffs.contrib.signets",
...,
]
$ python manage.py migrate signoffs_signets
Core Features:
- Concrete Models:
Signet, andRevokedSignetprovide persistence layer for - Concrete Signoffs:
SimpleSignoff,RevokableSignoff, andIrrevokableSignoff
signoffs.contrib.approvals
Approvals core defines only abstract models, no migrations.
signoffs.contrib.approvals provide concrete models with basic relations. To opt-in you must:
INSTALLED_APPS = [
...,
"signoffs.contrib.approvals",
...,
]
$ python manage.py migrate signoffs_approvals
Core Features:
- Concrete Models:
ApprovalSignet, andRevokedApprovalSignetdefine a FK relation to... Stampwhich provides persistence layer for...SimpleApprovalandIrrevokableApproval, which play nicely with...ApprovalSignoff, which uses the Concrete Models for persistence.
FsmApprovalsProcess
Signoffs is integrated with django-fsm, allowing approval processes to drive a finite state machine. To opt-in:
$ pip install django-signoffs[fsm]
Get Me Some of That
Check Out the Demo App
pip install -e git+https://github.com/powderflask/django-signoffs.git#egg=django-signoffspython django-signoffs/manage.py install_demopython django-signoffs/manage.py runserver
Acknowledgments
Special thanks to BC Hydro, Chartwell, and all Contributors
Technology Colophon
Without django and the django dev team, the universe would have fewer rainbows and ponies.
Signoffs approval process can be integrated on the deceptively clever django_fsm Friendly Finite State Machine.
Signoffs uses a global registry as store for singleton code objects - thanks persisting_theory!
This package was originally created with cookiecutter and the cookiecutter-pypackage project template.
For Developers
Create a virtual-environment (.venv by default) for this project
$ pip install tox && tox -e dev
Tests
Run tests in parallel
$ pytest -n logical
Code Style / Linting
$ ruff check
$ ruff format
Versioning
- Semantic Versioning
$ bumpver show
Docs
Build / Deploy Automation
- invoke
$ invoke -l $ inv -l
- GitHub Actions (see .github/workflows)
- GitHub Webhooks (see settings/hooks)
Metadata
Release files for django-signoffs 0.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django_signoffs-0.4.1.tar.gz | 99.4 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_signoffs-0.4.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 211.4 kB
Release files / django_signoffs-0.4.1.tar.gz
| Download URL | django_signoffs-0.4.1.tar.gz |
|---|---|
| Size | 99.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
399903e70fce14e7cc8041e1262dd635cdc207017bd358a5907c9d5de24c8bbb
|
|
BLAKE2b-256 checksum How to use checksums |
2bc9d8eb8a58ab4f225d993fbef6e7944ec8709044a3a0d99dac0d0d75f5fc89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 26, 2026.
Transparency logRelease files / django_signoffs-0.4.1-py3-none-any.whl
| Download URL | django_signoffs-0.4.1-py3-none-any.whl |
|---|---|
| Size | 112.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cc214e0b1ff8ab924bd6e9a5ccd51234a5de1064c91bb330084fb472633f7b23
|
|
BLAKE2b-256 checksum How to use checksums |
bc1fb3dfd4802bec069d6e64bb42b35160817275cff14ba00af44c70fa2c1c60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.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 Jul 26, 2026.
Transparency logSecurity for django-signoffs 0.4.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for django_signoffs-0.4.1.tar.gz
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 Jul 26, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.