Metadata
1 maintainer
Release files for fdbuild-templates 0.0.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 | |
|---|---|---|---|---|
| fdbuild-templates-0.0.0.tar.gz | 1.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fdbuild_templates-0.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.9 kB
Release files / fdbuild-templates-0.0.0.tar.gz
| Download URL | fdbuild-templates-0.0.0.tar.gz |
|---|---|
| Size | 1.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4de43770e8eef7f268a87022fd31e2027af4baeee64eba4967c0298b842a51e8
|
|
BLAKE2b-256 checksum How to use checksums |
dc02b7084c717963a945b8ebfc23ef9ce8423cc604f2e7d57b7d135d7f44508a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Release files / fdbuild_templates-0.0.0-py3-none-any.whl
| Download URL | fdbuild_templates-0.0.0-py3-none-any.whl |
|---|---|
| Size | 1.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c55276cc164845082698807117861715d51cda0ab51ce0db95953e29aeaf7e0
|
|
BLAKE2b-256 checksum How to use checksums |
e74eee5a38b976ffc5a398a0dfd54ce5ea936cb16ff348d8f5e316bc078a7b83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.8
|
Security for fdbuild-templates 0.0.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.
