Metadata
Release files for jinja-to-resume 0.2.0
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_resume-0.2.0.tar.gz | 2.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jinja_to_resume-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 5.8 kB
Release files / jinja_to_resume-0.2.0.tar.gz
| Download URL | jinja_to_resume-0.2.0.tar.gz |
|---|---|
| Size | 2.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a83a504ab05d6de3f84ebf9422fa5d9e906db6d2c1de3def9a3454a71f26136
|
|
BLAKE2b-256 checksum How to use checksums |
06e95fe35a522cb6a247512099c7e414dd51de0a63163fb7e86ebea19e056b83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.3
|
Release files / jinja_to_resume-0.2.0-py3-none-any.whl
| Download URL | jinja_to_resume-0.2.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d291cc2d76749385021ffc7a103270cb65eaadc8efe0382dedc5dd84724e875
|
|
BLAKE2b-256 checksum How to use checksums |
c83f95e2cf04b38e12a41ecbff0b912f19bf86bb9025579e3a2a2bf22aae7036
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.3
|
Security for jinja-to-resume 0.2.0
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.