The author of this package has not provided a project description
3 maintainers
Metadata
3 maintainers
Release files for jinja-to-js 3.2.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 | Provenance | |
|---|---|---|---|---|
| jinja-to-js-3.2.3.tar.gz | 15.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jinja_to_js-3.2.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 26.8 kB
Release files / jinja-to-js-3.2.3.tar.gz
| Download URL | jinja-to-js-3.2.3.tar.gz |
|---|---|
| Size | 15.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
22898ade32cd6bad79ac38c28cc5d2c48d25c5d18222d12df0f1ad3e7b8ff3d1
|
|
BLAKE2b-256 checksum How to use checksums |
efec45f75dc48c4e4e4988d813a77a8f402acef29499258c2bf3b5aad5b576fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / jinja_to_js-3.2.3-py2.py3-none-any.whl
| Download URL | jinja_to_js-3.2.3-py2.py3-none-any.whl |
|---|---|
| Size | 10.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4a8fb0a8a71766a33e47d45a3ea12a1303a98b9377e04be0a53806fff5c48b71
|
|
BLAKE2b-256 checksum How to use checksums |
ba16599cf20ef3246e50571a908c72615a1ce39cb213167ceb4e9ab626df3f2e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jinja-to-js 3.2.3
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.
