Django Safe Template Engine
Django template engine to render untrusted template code
Table of contents
Requirements
Django 3.0 to 6.0
Available tools
Template engine
from django.template import Template
from django_safe_template_engine.engine import SafeTemplateEngine
safe_engine = SafeTemplateEngine()
Template(source, engine=safe_engine)
Validator
from django_safe_template_engine.validators import validate_safe_engine_template_syntax
template_code = '{% include "hacked.html" %}'
validate_safe_engine_template_syntax(template_code)
Trusted built-ins
The following tags and filters are allowed by this template engine.
Trusted tags
autoescapecommentcyclefilterfirstofforfor … emptyififchangedloremnowpartialpartialdefquerystringregroupresetcyclespacelesstemplatetagurlverbatimwidthratiowith
Trusted filters
addaddslashescapfirstcentercutdatedefault_if_nonedefaultdictsortdictsortreverseddivisiblebyescapeescapejsfilesizeformatfirstfloatformatforce_escapeget_digitiriencodejoinjson_scriptlastlength_islengthlinebreakslinebreaksbrlinenumbersljustlowermake_listphone2numericpluralizerandomrjustsafesafeseqsliceslugifystringformatstriptagstimetimesincetimeuntiltitletruncatechars_htmltruncatecharstruncatewords_htmltruncatewordsunordered_listupperurlencodeurlizeurlizetruncwordcountwordwrapyesno
Contribute
How to contribute
You want to add awesome features to Django Safe Template Engine? Here's how!
- Fork this repository
- Commit and push to your forked repository
- Open a pull request to merge your work into this repository
Code formatting and tests
You can use tox to run the code formatting / type checking tools, and run the test suite:
tox run
Ignore code formatting revisions from git blame
For a more relevant git blame you can set up your git to use the file .git-blame-ignore-revs in blame.ignoreRevsFile:
git config blame.ignoreRevsFile .git-blame-ignore-revs
1 maintainer
Metadata
1 maintainer
Release files for django-safe-template-engine 1.5.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_safe_template_engine-1.5.1.tar.gz | 11.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_safe_template_engine-1.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 18.7 kB
Release files / django_safe_template_engine-1.5.1.tar.gz
| Download URL | django_safe_template_engine-1.5.1.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d056c44b5f39e532453b205a55fa63a7a32399058b44e7f0b9b7e5a2c40465f
|
|
BLAKE2b-256 checksum How to use checksums |
5a0b9754ffa4bd19adf9c79a41fbed3c8cb847d023c5056a01803326f4835912
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.6
|
Release files / django_safe_template_engine-1.5.1-py3-none-any.whl
| Download URL | django_safe_template_engine-1.5.1-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f7255fe8050ceb6f28782b8133c793dd7c25638a6780f11e80884261db9c0d46
|
|
BLAKE2b-256 checksum How to use checksums |
da5f4f810b5b5afe5910e48d5356851b083e173a1da72a4fcf4119ee19530a27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.9.6
|
Security for django-safe-template-engine 1.5.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
