1 maintainer
Metadata
1 maintainer
Release files for silo-passport-api 0.0.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 | |
|---|---|---|---|---|
| silo_passport_api-0.0.1.tar.gz | 1.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| silo_passport_api-0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 kB
Release files / silo_passport_api-0.0.1.tar.gz
| Download URL | silo_passport_api-0.0.1.tar.gz |
|---|---|
| Size | 1.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f78aba8d0f161b6667614e2dbbca24b53b3dbbbd1a0365c8473fa6eaaac7d39
|
|
BLAKE2b-256 checksum How to use checksums |
2206b6441b76d55552f106a9fd47ea9a6571cda25f390ca287b758fdd6f2d043
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Release files / silo_passport_api-0.0.1-py3-none-any.whl
| Download URL | silo_passport_api-0.0.1-py3-none-any.whl |
|---|---|
| Size | 1.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e8fe11a056d571a37578895e52f84b92893654571eb8db5b5d754b56d54ea1ef
|
|
BLAKE2b-256 checksum How to use checksums |
f847cb33600e78b7afdb640e0f1af9922e039f8fce245645c470d192c02f07d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.13
|
Security for silo-passport-api 0.0.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.
